Stable public hostnames
Keep a memorable mockingo.click address for your service, even between development sessions.
Local development, publicly accessible
Expose your local services.
Expose your local services.
Without deploying them.
Create secure public tunnels to applications running on your machine. Sign in, run one command, and receive a stable public hostname.
No deployment required. Your service stays local.
Mockingo command example:
- mockingo login
- Opening your browser to sign in to Mockingo...
- ✓ Signed in to Mockingo
- mockingo expose --name my-api --http 8080
- Waiting for 127.0.0.1:8080...
- Application is ready.
- Public endpoint:
- https://my-api.mockingo.click
Built for the local loop
A public endpoint in one command
Keep building with your existing tools while Mockingo handles the secure route from the internet to localhost.
Secure HTTP forwarding
Forward public HTTPS requests to the HTTP service listening on your local machine.
No deployment required
Share work in progress without building an image, provisioning a server, or publishing a release.
How it works
From localhost to a public URL
Three focused steps. No deployment pipeline in the middle.
-
Install the CLI
Add the small Mockingo command-line client to your development machine.
mockingo --help -
Sign in in your browser
Start the secure OAuth flow without copying credentials into your terminal.
mockingo login -
Expose your service
Choose a stable name and forward it to the local HTTP port you are using.
mockingo expose --name my-api --http 8080
One place to stay oriented
Your endpoints remain easy to find
See the stable hostname and current state of each local service in the Mockingo console.
Total endpoints3
Online now2
EndpointsStable public hostnames
my-api my-api.mockingo.click Online
checkout checkout.mockingo.click Offline
webhook-dev webhook-dev.mockingo.click Online
Ready when localhost is
Share your local service in minutes.
Keep the fast development loop. Add the public URL only when you need it.