Tableland

tableland.xyz · Storage · 1 record · JSON

Tableland Storage

fails: quotaemailno cardR

tableland.xyz · web3-database · storage/tableland · JSON · compare

Free tier	500,000 rows and 24 columns per table. That is the entire quota — it is a SQL-over-SQLite network, not an object store. Byte capacity is implied by row content and is not published as a number, but 500k rows × 24 columns cannot reach 500 GB under any encoding. unit GB; metered on stored-bytes
Price	none stated
Per-object cap	not stated
Retention	not stated
Egress	Reads go through the Tableland gateway and are free; there is no egress meter because the payloads are rows.
Identity	email email
Binding	none no constraint of a named kind was recorded; the verdict rests on the quota sentence rather than on a named limit
Interface	rest, cli rest
Tooling	Studio web app + Studio CLI + JS SDK, and a documented SQL API. Clean for structured data; irrelevant for blobs. Their own docs recommend pushing large media to IPFS and storing only the CID in a table — which is an admission that the network is a pointer store.
Composes with	Tables are creatable per project and per team, so the multiplier is tables × 500k rows. Even at 10,000 tables this is a metadata tier, not a byte tier.
Reliability	Beta-network limits explicitly flagged as temporary. Do not build a chunk index on a limit that a mainnet launch can change.
Notes	500,000 rows and 24 columns per table. That is the entire quota — it is a SQL-over-SQLite network, not an object store. Byte capacity is implied by row content and is not published as a number, but 500k rows × 24 columns cannot reach 500 GB under any encoding.
Evidence rung	reported One page read moves it to documented.
Checked	2026-10-21 (inherited); stale on 2026-11-04

Evidence (3)

date	source	what it proved
2026-10-21	raw.githubusercontent.com/tablelandnetwork/docs/main/docs/fu	fetched raw: 'Table limits … Rows 500000 … Columns 24'; 'Since Tableland is still in open beta, each table is limited to the following constraints … These are temporary limits'.
2026-10-21	tableland.xyz/	opened: 'The decentralized cloud database … built on SQLite. Read and write tamperproof data from apps, data pipelines' — a database positioning, no storage claim.
2026-10-21	docs.tableland.xyz/playbooks/integrations/ipfs	surfaced: 'Tableland naturally imposes limits on the size of data you can store in a table. If you need to store larger pieces media, you can use IPFS to store the data and then reference unique Content Identifiers in a table.' Their own recommended alternative route concedes the point.

More fields (1)

{
 "dead_end": {
  "failure_class": "quota",
  "why": "500,000 rows and 24 columns per table. That is the entire quota — it is a SQL-over-SQLite network, not an object store. Byte capacity is implied by row content and is not published as a number, but 500k rows × 24 columns cannot reach 500 GB under any encoding.",
  "retry_when": null,
  "first_recorded": "2026-10-21"
 }
}

Unknown or withheld values (6)

$.extras.dead_end.retry_when process
$.free_tier.notes process
$.per_object_cap.notes not-extracted
$.per_object_cap.stated not-extracted
$.retention.notes not-extracted
$.retention.stated not-extracted