- Free allowance
- 500,000 rows and 24 columns per table.
- Verdict
- fails: quotathe free allowance is too small to matter
- Cost
- free tier
- Identity
- emailno card, no phone
- Binding limit
- per-object-capeach table cell is limited to 1kb; 500000 rows and 24 columns per table
- Evidence
- documented10 sources; a first-party page was read and the sentence quoted
- Freshness
- stale on 2026-12-05checked 2026-11-04 (live); stale on 2026-12-05
| 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 |
|---|
| Limits | - per-object-cap (binding) each table cell is limited to 1kb; 500000 rows and 24 columns per table source
fails-quota categorically. Still described as open beta with 'temporary limits while the production mainnet is further researched', so even the row cap is provisional. |
|---|
| Binding | per-object-cap each cell holds at most 1kb and each table at most 500000 rows by 24 columns; the docs state it is not a file storage solution |
|---|
| Identity | email email |
|---|
| Egress | Reads go through the Tableland gateway and are free; there is no egress meter because the payloads are rows. |
|---|
| Per-object cap | each table cell is limited to 1kb |
|---|
| Retention | not stated |
|---|
| 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 | As read on 2026-11-03, tableland.xyz and docs.tableland.xyz answer HTTP 302 to textile.io and then HTTP 302 to the 2026-10-30 post announcing the wind-down of Recall Labs. Beta-network limits were explicitly flagged as temporary. Do not build a chunk index on a limit that a mainnet launch can change. |
|---|
| Evidence note | documented re-read on 2026-11-03: the vendor docs limits page https://raw.githubusercontent.com/tablelandnetwork/docs/main/docs/fundamentals/limits.md (row, column and cell limits, not a file storage solution) and the Recall Labs wind-down post on x.com (RecallLabs_) that tableland.xyz and docs.tableland.xyz redirect to; identity, tooling and retention were not read |
|---|
| Parsed numbers | - has-free-tier 1
- per-object-cap 1 kb
|
|---|