A public HTTPS URL without router setup
The CLI connects outward from your machine, so your local server can receive internet traffic without port forwarding or a public IP.
Product
A localhost tunnel built for the development loop.
GoPort handles the public route while you keep coding, debugging, and testing on your own machine.
Request inspection beside your app
Review request and response headers, bodies, status codes, and latency in the local dashboard. Replay a captured request after each fix.
HTTP and WebSocket traffic
Use the same localhost tunnel for ordinary HTTP requests and connections that upgrade to WebSockets.
Open source and self-hostable
Inspect the MIT-licensed code, run GoPort on your own infrastructure, and manage the domain used for your tunnels.
Webhook testing
Debug production webhooks on localhost instantly.
Use a GoPort URL as the provider endpoint. Deliveries reach your local handler, and the built-in inspector records each request and response for replay.
Webhook delivery200 OK
ProviderStripecheckout.session.completedPOST
Public endpointGoPort tunnel
checkout.goport.uz/stripeforwards
Local handlerYour app
localhost:8080/stripePOST checkout.session.completed✓ delivered to localhost:8080/stripe48 ms
Stripe
GitHub
Shopify
Slack
Discord
GitLab
Telegram
Twilio
Click
payme
MultiCard
Higgsfield
Receive live webhook deliveries on localhost
Inspect headers, bodies, and responses
Replay a request after each code change
These services can send callbacks to standard public HTTPS endpoints. Their names are examples, not partnership claims.
How it works
Follow every hop from the public URL to localhost.
A request reaches GoPort, travels through the CLI's outbound tunnel, and arrives at the local port where your application is listening.
How a GoPort localhost tunnel routes traffic
HTTP request
from the internet
GoPort Cloud
secure tunnel
GoPort CLI agent
on your machine
localhost:8080
your app
requestresponse
The CLI opens the connection from your machine. No inbound router port is required.