Home / Storage
Convex
www.convex.devPaaSstorage/convexJSONcomparereport an errorprovider JSON
- Free allowance
- 1 GB file storage on Free; 1 GB/month file egress; 0.5 GB database; 40 deployments
- Verdict
- fails: quotathe free allowance is too small to matter
- Cost
- free tier
- Identity
- email?placeholder, not evidence; card unknown, phone unknown
- Binding limit
- noneno named constraint binds
- Evidence
- reported3 sources; a third party said so
- Freshness
- stale on 2026-11-05checked 2026-10-21 (inherited); stale on 2026-11-05
| Free tier | 1 GB file storage on Free; 1 GB/month file egress; 0.5 GB database; 40 deployments unit GB; metered on stored-bytes |
|---|
| Price | none stated |
|---|
| Identity | email (placeholder) not published |
|---|
| Egress | 1 GB/month data egress total on Free (serving user files, accessing files in functions, backups) — equal to the storage size, so a full store can be fetched exactly once per month. free allowance: 1 GB per month |
|---|
| Per-object cap | not stated |
|---|
| Retention | not stated |
|---|
| Interface | rest, cli rest |
|---|
| Tooling | Convex client SDKs (JS/Python/Rust), HTTP actions, npx convex CLI, storage.getUrl() bearer URLs — 'anyone with the URL can access the file' (public, no auth) |
|---|
| Composes with | Free/Starter is per TEAM; 40 deployments per team on Free. But file storage is 1 GB total per team, not per deployment — so deployments do not multiply storage. Multiple teams/accounts is the only axis. Upload URLs are one-time and short-lived, which makes external tools awkward. |
|---|
| Reliability | Free has hard resource caps (Starter can exceed with usage-based billing). Well-behaved, no data loss reported; 100 MiB response cap breaks large-file serving via custom routes. |
|---|
| Parsed numbers | |
|---|
Evidence 3
More fields 1
| dead end | {"failure_class": "egress","why": "1 GB file storage on Free; 1 GB/month file egress; 0.5 GB database; 40 deployments","retry_when": null,"first_recorded": "2026-10-21"} |
|---|
Unknown values 4
- 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