Horizon Tunnel
hrzn.run · Egress and tunnels · 1 record · JSON
Horizon Tunnel Egress and tunnels
fails: egressemailno cardDper-ip-shaping
| Free tier | Tunnels on a random subdomain are free, with HTTPS, WebSockets and the request log. No card is needed. The Free plan has no time limit. unit unlimited; metered on none |
|---|---|
| Price | USD 0 (reserved names paid) |
| Per-object cap | not applicable |
| Retention | not applicable |
| Egress | Unlimited tunnels on a random subdomain; no byte allowance is published in either direction.; ingress: http-only free_allowance: none published |
| Identity | email 'No card is needed'; a login is required to start a tunnel. |
| Limits |
|
| Binding | per-ip-shaping No quota is published, so at 1 TiB/month the thing that fails is an unpublished per-caller tolerance. Protocol fails first in practice: HTTPS and WebSockets only, with no TCP or UDP port. |
| Interface | cli CLI plus request log in the dashboard. |
| Tooling | vendor CLI. |
| Composes with | Webhook and demo ingress only. |
| Reliability | Random subdomain on free; reserved names are the paid feature. |
| Notes | Free is genuinely unmetered in count and time, which is rare; the disqualifier is the protocol. |
| Evidence rung | documented A TCP or UDP tunnel type on any plan would change this; the pricing page lists only HTTP-shaped features. |
| Checked | 2026-10-23 (live); stale on 2026-11-22 |
| Parsed numbers |
|
Evidence (1)
| date | source | what it proved |
|---|---|---|
| 2026-10-23 | hrzn.run/pricing | 'Tunnels on a random subdomain are free, with HTTPS, WebSockets and the request log'; 'The Free plan has no time limit' |
More fields (7)
{
"wg_path": "none",
"wg_detail": "",
"ingress": "http-only",
"volume_tib_month": null,
"volume_stated": "Unlimited tunnels on a random subdomain; no byte allowance is published in either direction.",
"bytes_transit": "yes",
"transit_note": ""
}Unknown or withheld values (2)
$.per_object_cap.statednot-applicable$.retention.statednot-applicable