Tunnels, traffic capture, and replay

Capture traffic.
Mock what comes next.

Give a local service a stable public URL, inspect incoming and dependency traffic, then turn real exchanges into reusable mocks and replays.

mockingo

Mockingo command example:

  1. mockingo login
  2. Opening your browser to sign in to Mockingo...
  3. ✓ Signed in to Mockingo
  4. mockingo run --name my-api --http 8080
  5. Waiting for 127.0.0.1:8080...
  6. Application is ready.
  7. Public endpoint:
  8. https://my-api.mockingo.click
  9. Dependency proxy: http://127.0.0.1:8899
  10. ✓ Traffic capture and replay are active
Beyond the tunnel

Make integration behavior repeatable

Observe real HTTP exchanges once, keep the useful ones, and recreate the state your application needs without waiting on every system around it.

Stable public endpoints

Keep a memorable mockingo.click hostname while forwarding unmatched requests to your local service.

Capture real traffic

Inspect completed incoming requests and outbound dependency calls from one live traffic view.

Turn traffic into mocks

Save a real request and response, then serve matching calls from Mockingo Cloud whenever you need them.

Replay dependencies locally

Capture HTTP and HTTPS dependencies through the local proxy and replay exact matches before an origin call.

Switch complete scenarios

Bundle endpoint mocks and dependency replays into reusable project states, then activate them together.

Organize work as a team

Group related endpoints into projects and manage shared integration behavior in a collaborative workspace.

How it works

From live traffic to a reusable scenario

One local Agent connects your service and captures the exchanges you choose to keep.

  1. Connect your local endpoint

    Sign in once, choose a stable endpoint name, and point the Agent at your local HTTP port.

    mockingo run --name my-api --http 8080
  2. Observe both sides of the call

    See incoming requests alongside outbound HTTP and HTTPS dependency traffic in the console.

    Console · Traffic · Incoming + Dependencies
  3. Save behavior worth repeating

    Turn an incoming exchange into a cloud mock or an outbound exchange into a local dependency replay.

    Console · Saved traffic · Create behavior
  4. Switch the whole environment

    Collect mocks and dependency replays in a Project Scenario and activate the complete state together.

    Console · Scenarios · Activate
One place to stay oriented

Your endpoints remain easy to find

Manage local and always-on virtual endpoints, their stable hostnames, and current connection state from the same console.

Mockingo Console

Endpoints

PlatformEndpoints

Endpoints

Manage the public hostnames that connect to your local services.

Create endpoint
Filter
Name Public URL Origin Connection Local target Created Actions
default-project-1 https://default-project-1.mockingo.click Copy URL Local Connected HTTP → localhost:9999 5 Sept 2026, 12:52 UTC •••
demo-app https://demo-app.mockingo.click Copy URL Local Offline 29 Aug 2026, 09:24 UTC •••
no-project https://no-project.mockingo.click Copy URL Virtual Always available 23 Aug 2026, 08:10 UTC •••
Ready for the next integration state

Capture it once. Reuse it whenever you need it.

Start with a stable endpoint, then build mocks, dependency replays, and complete scenarios from real traffic.