goreplay.org valid

GoReplay

Open-source HTTP capture and replay. Use production traffic for shadow testing, load testing, and debugging — without putting a proxy on the critical path.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T21:06:17.723Z. Cached copy · Source on goreplay.org

# GoReplay

> Open-source HTTP capture and replay. Use production traffic for shadow testing, load testing, and debugging — without putting a proxy on the critical path.

GoReplay (also called Gor) listens on a network interface or port, records live HTTP requests, and replays them against another environment. It is not AWS VPC traffic mirroring, not a packet-level NTA product (Wireshark / SolarWinds / NetFlow), and not a synthetic load generator like JMeter or k6.

- Site: https://goreplay.org/
- GitHub: https://github.com/buger/goreplay
- Docs: https://goreplay.org/docs/
- Installation: https://goreplay.org/docs/installation/
- PRO (S3, WebSockets, TCP sessions, commercial license, $3000/year): https://goreplay.org/pro/
- Author: Leonid Bugaev

## What it is for

- Shadow testing / traffic replay: copy production HTTP onto staging to validate deploys
- Load testing with real production traffic (speed up replay, e.g. 200%)
- Capturing HTTP into files, Elasticsearch, Kafka, or S3 without application code changes
- Middleware to filter, rewrite, or mask payloads before replay

## What it is not

- Not cloud packet mirroring (AWS VPC Traffic Mirroring, TAP/span ports)
- Not network traffic analysis / NTA (NetFlow, DPI dashboards)
- Not a JMeter/k6 replacement for writing synthetic VU scripts
- Not a UI session-replay product (FullStory / Glassbox)

## Product pages

- Shadow testing: https://goreplay.org/shadow-testing/
- Load testing with production traffic: https://goreplay.org/load-testing/
- Load testing checklist: https://goreplay.org/load-testing-checklist/
- Monitoring (HTTP to ES/Kafka/S3): https://goreplay.org/monitoring/
- HTTP sessions (PRO TCP keepalive): https://goreplay.org/http-sessions/
- Case studies: https://goreplay.org/case-studies/
- Blog: https://goreplay.org/blog/

## Key commands

```
# Capture HTTP on port 8080 and print requests
sudo gor --input-raw :8080 --output-stdout

# Shadow production HTTP onto staging
sudo gor --input-raw :8080 --output-http="http://staging.example.com"

# Record to a file
sudo gor --input-raw :8080 --output-file=requests.gor

# Replay recorded traffic at 2x speed
gor --input-file "requests.gor|200%" --output-http="http://staging.example.com"

# Index request/response stats into Elasticsearch (with HTTP replay)
sudo gor --input-raw :8080 --output-http="http://staging.example.com" --output-http-elasticsearch="http://elasticsearch:9200/gor"
```

## Docs map

Canonical docs: https://goreplay.org/docs/
…

Related sites

Find similar publishers by meaning →

Other listed sites in Developer tools. See the whole category →

Machine-readable: GET /v1/resolve?q=goreplay.org · GET /v1/domain/goreplay.org · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for goreplay.org:
1. POST https://agentwebmap.com/v1/sites/goreplay.org/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://goreplay.org/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/goreplay.org/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/goreplay.org).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.