Stable public endpoints
Keep a memorable mockingo.click hostname while forwarding unmatched requests to your local service.
Give a local service a stable public URL, inspect incoming and dependency traffic, then turn real exchanges into reusable mocks and replays.
Mockingo command example:
Observe real HTTP exchanges once, keep the useful ones, and recreate the state your application needs without waiting on every system around it.
Keep a memorable mockingo.click hostname while forwarding unmatched requests to your local service.
Inspect completed incoming requests and outbound dependency calls from one live traffic view.
Save a real request and response, then serve matching calls from Mockingo Cloud whenever you need them.
Capture HTTP and HTTPS dependencies through the local proxy and replay exact matches before an origin call.
Bundle endpoint mocks and dependency replays into reusable project states, then activate them together.
Group related endpoints into projects and manage shared integration behavior in a collaborative workspace.
One local Agent connects your service and captures the exchanges you choose to keep.
Sign in once, choose a stable endpoint name, and point the Agent at your local HTTP port.
mockingo run --name my-api --http 8080 See incoming requests alongside outbound HTTP and HTTPS dependency traffic in the console.
Console · Traffic · Incoming + DependenciesTurn an incoming exchange into a cloud mock or an outbound exchange into a local dependency replay.
Console · Saved traffic · Create behaviorCollect mocks and dependency replays in a Project Scenario and activate the complete state together.
Console · Scenarios · ActivateManage local and always-on virtual endpoints, their stable hostnames, and current connection state from the same console.
Manage the public hostnames that connect to your local services.
Start with a stable endpoint, then build mocks, dependency replays, and complete scenarios from real traffic.