fshy

Home

zrok

zrok.io · 2 records in Egress and tunnels, Storage · JSON

Records 2

zrok.io/pricing/storage/zrokJSONcomparereport an error

Free allowance
Free plan is bandwidth-metered at 5 GB/day over a rolling 24-hour window, with 50 share backends.
Verdict
fails: egressdata cannot be read back out at a usable rate or price
Cost
not stated
Identity
email?placeholder, not evidence; card unknown, phone unknown
Binding limit
noneno named constraint binds
Evidence
documented6 sources; a first-party page was read and the sentence quoted
Freshness
stale on 2026-12-04checked 2026-11-03 (live); stale on 2026-12-04
Free tierFree plan is bandwidth-metered at 5 GB/day over a rolling 24-hour window, with 50 share backends. It is a tunnelling service, so all traffic transits their edge.
unit none; metered on none
Pricenone stated
Identityemail (placeholder) not published
EgressFree plan: 5 GB per day over a rolling 24-hour window; past it running shares are disabled and new shares are refused until usage falls under the limit.
Interfaceunknown
Toolingnot recorded
Evidence notedocumented pages read on 2026-11-03: zrok.io/pricing/ (Free plan: 5 Daily GB, 50 Share Backends (Ephemeral or Reserved)) and netfoundry.io/docs/zrok/myzrok/service-limits (running shares are disabled and new shares are refused when the daily bandwidth is exceeded, until bandwidth falls below the 24-hour limit; Bandwidth limits are based on a rolling 24-hour window.). The identity cost was not read on a vendor page and stays as recorded.
Evidence 6
datesourcewhat it proved
2026-10-21zrok.io/pricing/the text of Free tier, above
2026-10-21www.globalnerdy.com/2026/09/22/can-you-use-zroks-free-hostedcited as the basis of the rejection: Free plan is bandwidth-metered at 5 GB/day over a rolling 24-hour window, with 50 share backends. It is a tunnelling service, so all traffic transits their edge.
2026-11-03zrok.io/pricing/Free plan bandwidth is 5 GB per day
2026-11-03netfoundry.io/docs/zrok/myzrok/service-limitsexceeding the daily bandwidth disables shares
2026-11-03netfoundry.io/docs/zrok/myzrok/service-limitsthe daily limit is measured over a rolling 24-hour window
2026-11-03zrok.io/pricing/the Free plan lists 50 Share Backends (Ephemeral or Reserved)
More fields 1
dead end{"failure_class": "egress","why": "Free plan is bandwidth-metered at 5 GB/day over a rolling 24-hour window, with 50 share backends. It is a tunnelling service, so all traffic transits their edge.","retry_when": null,"first_recorded": "2026-10-21"}
Unknown values 6
  • chaining: no value was recorded for this field
  • interface: the access interface was not established
  • per object cap notes: no value was recorded for this field
  • per object cap stated: no value was recorded for this field
  • retention stated: no value was recorded for this field
  • tooling: no value was recorded for this field

zrok (hosted)

Egress and tunnels

zrok.io/pricing/Tunnel (hosted, OpenZiti)egress/zrok-hostedJSONcomparereport an error

Free allowance
5 GB/day, 25 environments, 50 share backends, 50 private access frontends
Verdict
fails: quotathe free allowance is too small to matter
Cost
free tier
Identity
emailno card, no phone
Binding limit
volume-quota5 GB per rolling 24 hours; on crossing it the running shares are disabled and new shares refused until the window falls back below the limit
Evidence
documented4 sources; a first-party page was read and the sentence quoted
Freshness
stale on 2026-11-23checked 2026-10-23 (live); stale on 2026-11-23
Free tier5 GB/day, 25 environments, 50 share backends, 50 private access frontends
unit GB; metered on downloaded-bytes
Pricenone stated
Limits
  • volume-quota (binding) 5 GB per rolling 24 hours; on crossing it the running shares are disabled and new shares refused until the window falls back below the limit source
  • request-rate 2000 requests per 300 s per IP address source
  • request-rate 7500 requests per 300 s per share, from any number of addresses source
the allowance is a byte volume over a period, which none of the six kinds names; the number is in egress.free_allowance and binding names per-ip-shaping as the nearest kind
Bindingvolume-quota 5 GB per rolling 24 hours is 150 GB in 30 days, or 0.136 TiB, so the daily byte window bands the month at about 7.3 times below 1 TiB. Crossing it disables running shares and refuses new ones until the window falls back, which is a hard stop rather than a throttle. Two request-rate caps sit underneath and would bind first for a request-heavy workload.
Identityemail a zrok account; no card required
Egressmetered at 5 GB/day, which is 0.5% of one day's workload
free allowance: 5 GB per rolling 24 hours
Per-object capnot applicable: a rolling daily allowance rather than a per-object cap
Retention5 GB per rolling 24 hours; shares are restricted on exceed
Interfacecli zrok share public against the hosted controller
Toolingpart of the text of Interface, above
Composes withcomposes with an origin and no domain, and the daily allowance is what stops it. The self-hosted build is the same software without the controller's journal.
ReliabilityThe limits agent has twice failed to release a limit once usage fell: a 2024 discourse thread and a 2026 repository commit both describe an account staying limited until the journal entry was cleared by hand.
NotesIt is on the page in the raw HTML, so it is documented. A 2024 forum answer says 10 GB per 24 hours, which the pricing page contradicts; the page is the owner. The record listed no limits and its binding_note complained that the vocabulary had no kind for a byte volume over a period, which it now does. It also omitted the two request-rate caps and what actually happens on crossing the daily allowance. Replaces the note that said the vocabulary could not name this constraint, and states the monthly product of a daily allowance. A known failure mode of the limiter matters more than the warning page for a client running at the edge of the allowance.
Parsed numbers
  • has-free-tier 1
  • volume-quota 5 GB
  • request-rate 2000 requests
  • request-rate 7500 requests
Evidence 4
datesourcewhat it proved
2026-10-22zrok.io/pricing/'5 Daily GB' in the Free column of the rendered HTML; the Markdown extraction drops it
2026-10-23netfoundry.io/docs/zrok/concepts/private-shares/'udpTunnel: Forwards raw UDP traffic to a target server' and the private-share access rule
2026-10-23netfoundry.io/docs/zrok/concepts/backend-modes/'zrok supports HTTP-based backends and raw TCP/UDP backends'
2026-10-23zrok.io/pricing/the free tier is 25 environments and 50 share backends; the 5 GB/day figure is no longer on the pricing page
More fields 4
stale after days180
bytes transityes
transit notethe hosted controller relays the share's bytes, which is what the 5 GB daily counter counts
wg pathnone