zrok
github.com · Egress and tunnels · 1 record · JSON
zrok (self-hosted) Egress and tunnels
paidanonymousno cardDvolume-quota
| Free tier | Apache-2.0; no limit imposed by the software unit unlimited; metered on none |
|---|---|
| Price | none stated |
| Per-object cap | not applicable |
| Retention | not applicable |
| Egress | whatever the host's NIC and the hosting bill allow |
| Identity | anonymous the software needs no account |
| Binding | volume-quota the software imposes no byte meter; what runs out is the monthly egress allowance of the host it runs on, and that host is a separate provider |
| Interface | cli zrok share public against your own controller |
| Tooling | zrok |
| Composes with | the front half of the self-hosted tunnel chain: your controller, your frontend, and then a plain VPS bill. The relay software is free and the egress is not. |
| Notes | The hosted limits are NetFoundry's policy; a default self-hosted controller has no bandwidth journal configured. Re-graded 2026-10-23: the software is free and the path is not, because it needs a host. The finding is the host. |
| Evidence rung | documented no probe: a self-hosted zrok controller needs an enrolment token and was not stood up |
| Checked | 2026-10-23 (live); stale on 2026-11-22 |
Evidence (2)
| date | source | what it proved |
|---|---|---|
| 2026-10-22 | zrok.io/pricing/ | 'Run Zrok on your own infrastructure with no limits' |
| 2026-10-22 | github.com/openziti/zrok | Apache-2.0 repository; docs/current/ holds the bandwidth-limit journal and relax cycle, so the hosted limits are controller policy rather than protocol |
More fields (4)
{
"stale_after_days": 180,
"bytes_transit": "self-hosted",
"transit_note": "the software runs on the operator's host and the bytes transit that host's NIC",
"hosting_requirement": "a rented or free compute service"
}Unknown or withheld values (1)
$.reliability_notewithheld