fshy

Home / Storage

Veilid

veilid.com/how-it-works/networking/P2P relay networkstorage/veilidJSONcomparereport an errorprovider JSON

Free allowance
No quota and no account — 'All Veilid applications running veilid-core are nodes, and they are all equal in the eyes of the network.
Verdict
self-hosted, last resortverdict fails-quota: the free allowance is too small to matter. Self-hosted options are listed last, because this site is for users who have no hardware.
Cost
free tier
Identity
anonymousno card, no phone
Binding limit
write-gatedapplications running veilid-core are nodes, and they are all equal in the eyes of the netwo
Evidence
reported4 sources; a third party said so
Freshness
stale on 2026-11-05checked 2026-10-21 (inherited); stale on 2026-11-05
Free tierno quota and no account — 'All Veilid applications running veilid-core are nodes, and they are all equal in the eyes of the network. No nodes are special. Nodes are only limited by the resources they bring.'
unit unlimited; metered on unstated
Pricenone stated
Limits
  • write-gated (binding) applications running veilid-core are nodes, and they are all equal in the eyes of the netwo source
no congestion control implemented — open issue #404 'congestion control could be implemented with NodeStatus'; relay throttling is a to-do, not a feature.
Identityanonymous anonymous
Egressfree — peer-to-peer, with inbound/outbound relays only for reachability.
Per-object capnot stated
Retentionnot stated
Interfaceunknown AppMessage / AppCall primitives over routes; the core never parses app bytes. DHT for storage of small records.
Toolingveilid-core in Rust with bindings; veilid-server binary.
Composes withnot a file transport. Designed mobile-first for 'intermittent network connections, volatile IP addresses, CGNAT, limited storage and bandwidth' — the opposite of a bulk path.
Reliabilitysending bulk data through Veilid is unsupported in practice: without flow control a large transfer either starves or gets dropped. Eliminated on reliability, not on quota.
Parsed numbers
  • has-free-tier 1
Evidence 4
datesourcewhat it proved
2026-10-21veilid.com/how-it-works/networking/'No nodes are special ... Nodes are only limited by the resources they bring and the configuration of the network they are on'
2026-10-21gitlab.com/veilid/veilid/-/issues/404'congestion control could be implemented with NodeStatus'; 'max bytes a flow can consume in X minutes' proposed as an unimplemented idea
2026-10-21gitlab.com/groups/veilid/-/work_items/3'Relay traffic could use bandwidth throttling or roundrobin assignments' listed as To do
2026-10-21veilid.gitlab.io/developer-book/why-veilid/'limited storage and bandwidth' as a design assumption (mobile-first)
More fields 1
dead end{"failure_class": "write-gated","why": "no quota and no account — 'All Veilid applications running veilid-core are nodes, and they are all equal in the eyes of the network. No nodes are special. Nodes are only limited by the resources they bring.'","retry_when": null,"first_recorded": "2026-10-21"}
Unknown values 5
  • interface: the access interface was not established
  • per object cap notes: the field may be stated in a source that was not read
  • per object cap stated: the field may be stated in a source that was not read
  • retention notes: the field may be stated in a source that was not read
  • retention stated: the field may be stated in a source that was not read