Home / Storage
veilid for bulk data
gitlab.com/veilid/veilid/-/issues/404storage/veilid-for-bulk-dataJSONcomparereport an errorprovider JSON
- Free allowance
- No congestion control and no relay throttling implemented; relay bandwidth management is an open to-do.
- Verdict
- self-hosted, last resortverdict fails-egress: data cannot be read back out at a usable rate or price. Self-hosted options are listed last, because this site is for users who have no hardware.
- Cost
- not stated
- Identity
- email?placeholder, not evidence; card unknown, phone unknown
- Binding limit
- noneno named constraint binds
- Evidence
- reported2 sources; a third party said so
- Freshness
- stale on 2026-11-05checked 2026-10-21 (inherited); stale on 2026-11-05
| Free tier | No congestion control and no relay throttling implemented; relay bandwidth management is an open to-do. Mobile-first design assumes 'limited storage and bandwidth' at every node. unit none; metered on none |
|---|
| Price | none stated |
|---|
| Identity | email (placeholder) not published |
|---|
| Egress | not recorded |
|---|
| Interface | unknown |
|---|
| Tooling | not recorded |
|---|
Evidence 2
More fields 1
| dead end | {"failure_class": "egress","why": "No congestion control and no relay throttling implemented; relay bandwidth management is an open to-do. Mobile-first design assumes 'limited storage and bandwidth' at every node.","retry_when": null,"first_recorded": "2026-10-21"} |
|---|
Unknown values 7
- chaining: no value was recorded for this field
- egress terms: 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