fshy / Egress and tunnels / Storage
zrok
zrok.io · Egress and tunnels, Storage · 2 records · JSON
- zrok (netfoundry public instance) Storagefails: egressemail?card?R
- zrok (hosted) Egress and tunnelsfails: quotaemailno cardDvolume-quota
zrok (netfoundry public instance) Storage
fails: egressemail?card?R
| Free tier | 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. unit none; metered on none |
|---|---|
| Price | none stated |
| Per-object cap | not recorded |
| Retention | not recorded |
| Egress | not recorded |
| Identity | email (placeholder) not published |
| Binding | none no constraint of a named kind was recorded; the verdict rests on the quota sentence rather than on a named limit |
| Interface | unknown |
| Tooling | not recorded |
| Composes with | not recorded |
| Reliability | 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. |
| Notes | 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. |
| Evidence rung | reported |
| Checked | 2026-10-21 (inherited); stale on 2026-11-04 |
Evidence (2)
| date | source | what it proved |
|---|---|---|
| 2026-10-21 | zrok.io/pricing/ | 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-10-21 | www.globalnerdy.com/2026/09/22/can-you-use-zroks-free-hosted | cited 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. |
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 or withheld values (15)
$.chainingnot-recorded$.confidence_notewithheld$.egress.termsnot-recorded$.extras.dead_end.retry_whenprocess$.free_tier.notesprocess$.identity_cost.detaildefaulted$.identity_cost.kindidentity-defaulted$.interfaceinterface-unknown$.interface_detailwithheld$.limits_noteprocess$.per_object_cap.notesnot-recorded$.per_object_cap.statednot-recorded$.retention.notesprocess$.retention.statednot-recorded$.toolingnot-recorded
zrok (hosted) Egress and tunnels
fails: quotaemailno cardDvolume-quota
| Free tier | 5 GB/day, 25 environments, 50 share backends, 50 private access frontends unit GB; metered on downloaded-bytes |
|---|---|
| Price | none stated |
| Per-object cap | not applicable: a rolling daily allowance rather than a per-object cap |
| Retention | 5 GB per rolling 24 hours; shares are restricted on exceed |
| Egress | metered at 5 GB/day, which is 0.5% of one day's workload free_allowance: 5 GB per rolling 24 hours |
| Identity | email a zrok account; no card required |
| Limits |
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 |
| Binding | volume-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. |
| Interface | cli zrok share public against the hosted controller |
| Tooling | zrok |
| Composes with | composes 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. |
| Reliability | The 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. |
| Notes | The census called this figure reported because the read broker's Markdown view drops it. It 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. |
| Evidence rung | documented |
| Checked | 2026-10-23 (live); stale on 2026-11-22 |
| Parsed numbers |
|
Evidence (4)
| date | source | what it proved |
|---|---|---|
| 2026-10-22 | zrok.io/pricing/ | '5 Daily GB' in the Free column of the rendered HTML; the Markdown extraction drops it |
| 2026-10-23 | netfoundry.io/docs/zrok/concepts/private-shares/ | 'udpTunnel: Forwards raw UDP traffic to a target server' and the private-share access rule |
| 2026-10-23 | netfoundry.io/docs/zrok/concepts/backend-modes/ | 'zrok supports HTTP-based backends and raw TCP/UDP backends' |
| 2026-10-23 | zrok.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_days": 180,
"bytes_transit": "yes",
"transit_note": "the hosted controller relays the share's bytes, which is what the 5 GB daily counter counts",
"wg_path": "none"
}