Horizon gives your local server an HTTPS address anyone can open, and shows every request that reaches it. No deploys, no port forwarding.
npm install -g @hrzn/cliPOST/webhooks/stripe
{
"id": "evt_1QxY2Z",
"type": "invoice.paid",
"data": {
"object": {
"id": "in_1QxY2Z",
"amount_paid": 1000,
"currency": "eur"
}
}
}$ hrzn tunnel http://localhost:3000 -s my-app
HORIZON: Tunnel connected
URL https://my-app.hrzn.run (reserved)
Forwarding http://localhost:3000
Request log https://hrzn.run/dashboard/tunnels/my-app
POST 200 /webhooks/stripe
How it works
Horizon forwards each request from your public URL to the port on your machine, and sends the response back.
Each URL has a valid certificate, so webhooks and phones accept it.
Live connections reach your local server as they are.
hrzn tunnel http://localhost:3000
Request log
The dashboard keeps what your terminal prints, with headers, bodies and a Replay button.
Open a webhook to read its headers and body. Fix your handler, then send it again with Replay.
POST/webhooks/github
{
"ref": "refs/heads/main",
"repository": {
"full_name": "acme/my-app"
},
"pusher": {
"name": "octocat"
}
}Authorization, cookies and token headers are masked before they are stored.
| authorizationBearer sk_l…cdefmasked |
| x-api-keykey_…a91bmasked |
| cookiesess…7c1emasked |
| content-typeapplication/json |
| user-agentStripe/1.0 (+https://stripe.com/docs/webhooks) |
Reserve a subdomain, so webhook settings keep working after a restart.
Subdomains
3 of 4 slots used| Subdomain | Tunnel | Reserved | Actions |
|---|---|---|---|
my-app.hrzn.run | Live for 2h 14m | Sep 12, 2026 | |
stripe-hooks.hrzn.run | Last active Oct 3, 2026 | Sep 12, 2026 | |
demo.hrzn.run | Never used | Oct 9, 2026 |
The log keeps the last day of requests, also after your CLI stops.
Workflows
Three reasons developers open a tunnel.
POST/webhooks/stripe
{
"id": "evt_1QxY2Z",
"type": "invoice.paid",
"data": {
"object": {
"id": "in_1QxY2Z",
"amount_paid": 1000,
"currency": "eur"
}
}
}Webhooks
Point a webhook at your tunnel and debug it on your own machine. Choose a service to open its guide.
Horizon
Pricing
Pay only for the subdomain slots you buy.
For quick shares and one-off tests.
€0
per month.
No card needed.
For URLs that other services depend on.
€0.83
per slot per month, billed yearly · or €1 monthly
€10 per slot, paid once a year.
1 slot holds 1 reserved name. Buy slots ahead and fill them later.
Yes. Tunnels on a random subdomain are free, with HTTPS, WebSockets and the request log. No card is needed. You only pay for a reserved subdomain that stays the same.
A slot is a paid place for one reserved subdomain. You can buy more slots than names, so a slot can stay empty until you need it. Each slot is billed monthly or yearly.
The name is held for you for 7 days. After that, others can claim it. The slot stays yours, empty and ready for another subdomain.
Yes, in Settings in the dashboard. The switch applies at your next renewal, and nothing is charged today. Your slots carry over.
Each request through your tunnel for 24 hours, up to the last 500 per subdomain: method, path, status, headers and bodies. Secret headers, such as Authorization and cookies, are masked before they are stored. The log stays readable after your CLI stops.
Yes. WebSocket connections to your public URL pass through the tunnel to your local server.
Install the CLI, sign in and run one command.
npm install -g @hrzn/cli$ hrzn tunnel http://localhost:3000 -s my-app
HORIZON: Tunnel connected
URL https://my-app.hrzn.run (reserved)
Forwarding http://localhost:3000
Request log https://hrzn.run/dashboard/tunnels/my-app
POST 200 /webhooks/stripe
GET 200 /