Public Tunnel use case
Test webhooks from localhost without deploying first
Give a public callback URL to Stripe, GitHub, PayPal, or another provider while your app still runs on your own machine.
- Public URL for a local app. Let outside services reach your development server during testing.
- Faster iteration. Debug payloads locally instead of deploying every small change.
- Web-first fit. Webhook callbacks are exactly the kind of HTTPS workflow Public Tunnel is meant to start with.
Good examples
- Payment status callbacks
- Git push or deployment hooks
- CRM and form integrations
- Webhook signature verification tests
Need SSH, RDP, or VPN instead? Static-IP Relay →
Typical flow
1. Run locallyYour app listens on a local development port.
2. Create a tunnelDNSExit provides a public HTTPS endpoint for that app.
3. Receive callbacksThe provider sends real webhook events into localhost through the tunnel.
More Public Tunnel use cases
Home server without port forwarding
Reach a self-hosted dashboard or web app when the router cannot accept inbound traffic.
View use case →Share a local web app
Send a preview link before you deploy a demo, review build, or temporary site.
View use case →Public Tunnel overview
Publish local web apps through an outbound-only tunnel without opening router ports.
Explore Public Tunnels →
Signup is open
Want a cleaner webhook testing loop?
Get started and tell us which local development workflow you need to test first.