Veilid
veilid.com · Storage · 1 record · JSON
Veilid Storage
fails: quotaanonymousno cardRwrite-gated
| Free tier | 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.' unit unlimited; metered on unstated |
|---|---|
| Price | none stated |
| Per-object cap | not stated |
| Retention | not stated |
| Egress | free — peer-to-peer, with inbound/outbound relays only for reachability. |
| Identity | anonymous anonymous |
| Limits |
no congestion control implemented — open issue #404 'congestion control could be implemented with NodeStatus'; relay throttling is a to-do, not a feature. |
| Binding | write-gated the write is a queue with a person or a rule in it, so the upload rate is set by somebody else |
| Interface | unknown AppMessage / AppCall primitives over routes; the core never parses app bytes. DHT for storage of small records. |
| Tooling | veilid-core in Rust with bindings; veilid-server binary. |
| Composes with | not a file transport. Designed mobile-first for 'intermittent network connections, volatile IP addresses, CGNAT, limited storage and bandwidth' — the opposite of a bulk path. |
| Reliability | sending 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. |
| Notes | 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.' |
| Evidence rung | reported One page read moves it to documented. |
| Checked | 2026-10-21 (inherited); stale on 2026-11-04 |
Evidence (4)
| date | source | what it proved |
|---|---|---|
| 2026-10-21 | veilid.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-21 | gitlab.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-21 | gitlab.com/groups/veilid/-/work_items/3 | 'Relay traffic could use bandwidth throttling or roundrobin assignments' listed as To do |
| 2026-10-21 | veilid.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 or withheld values (7)
$.extras.dead_end.retry_whenprocess$.free_tier.notesprocess$.interfaceinterface-unknown$.per_object_cap.notesnot-extracted$.per_object_cap.statednot-extracted$.retention.notesnot-extracted$.retention.statednot-extracted