Skip to main content

​
Plans

AI Table offers different row caps per plan to fit different scales. Every plan keeps hot-row queries snappy — heavy data won’t slow you down.
PlanDefault rows per tableExpansionUse case
Free20,000Not availableSmall-team collaboration, personal projects, basic data tracking
Business30,000Up to 10 millionDay-to-day mid-to-large businesses, multi-store rollups, mid-scale analytics
Enterprise50,000Up to 10 millionGroup-level management, high-frequency data updates, large-scale analytics (e-commerce big sales, omnichannel ops)
Note: row counts cover all valid data rows in a table; empty rows don’t count toward your quota. The 10-million-row cap is per table and requires a paid expansion.

​
Per-table row rules

​
What happens when you hit the cap

When a table hits its row cap, you can’t add more records. Upgrade or expand to up to 10 million rows.

​
Expansion details

  • Business and Enterprise users can apply to expand a table to 10 million hot rows based on business need — the first smart-table product to support 10 million hot rows.
  • Expanded tables still get sub-second query response and keep core features: cross-table links, AI-field analysis, real-time dashboard updates. No manual sharding required.
  • Expansion is a paid add-on. Reach out to a DingTalk sales advisor or apply via the website for a quote. Apply for expansion

​
Edge-case row limits

​
Sync and import limits

Copy-paste limitA single copy-paste — within AI Table or from external data — is capped at 20,000 rows.
Local file import (.xlsx / .csv)Single file ≤ 20 MB; no extra row limit on import (still must fit your plan’s per-table cap).
Data-connector sync limitTables synced via the Data Connector Center cap at 20,000 rows per sync; each sync overwrites the previous data.

​
What happens when you exceed the cap

  • Free-plan users must upgrade to Business / Enterprise, or clean up old data so the table is below 20,000 rows again, before adding more records.
  • When form submissions, automation runs, or API calls push the table past your plan’s cap, the system pauses inserts automatically and notifies the table Owner.
  • Once over the cap, you can upgrade or expand. Once that’s done, inserts resume. Existing data stays viewable / editable / exportable — unaffected.

​
FAQ

Q1: After hitting the cap, are existing computed values and views affected? A: No. Existing data still supports filter / sort / group / formula. Views and dashboard links keep working. Only new-record inserts are blocked. Q2: How does the row quota carry over between plans? A: After upgrading, the per-table row cap immediately rises to the new plan’s default. If the table was at the old plan’s cap, you can insert right up to the new cap — no manual adjustment.