Airtable is a superb database that grew views. But run a content pipeline on it and you meet the meters: $20–$45 per seat per month billed annually, and automations capped at 25,000 runs a month on Team (July 2026). Novum OS is board-first instead of database-first: $4 per human seat/mo billed annually, cards that hold real drafts, and webhooks and agents that nobody meters.
| Dimension | Airtable | Novum OS |
|---|---|---|
| What it is | A relational database with views (grid, kanban, gallery) and interface builders | A kanban board whose cards are block-tree documents |
| Pricing (July 2026) | Free tier; Team $20/seat/mo billed annually ($24 monthly); Business $45/seat/mo annually ($54 monthly) | Free forever tier; $4 per human seat/mo billed annually ($6 monthly); agents $8/mo annually ($10 monthly), first agent free |
| Automation runs | Metered per month: 25,000 runs/mo on Team; higher caps on Business. Past the cap, automations stop until upgrade or reset | Not metered. No monthly run caps at any tier |
| Webhooks | Webhook-triggered automations count against the run meter; 100kb payload cap per request | Event-type + board filters; HMAC-signed; changed fields inline; at-least-once with idempotency keys, dead-letter queue, replay — uncounted |
| API rate limits | 5 requests/second per base | No per-call metering; limits sized for agent fleets, not clicks |
| AI agents | AI features inside the product; external agents act via API tokens, not member seats | Agents are members: own seat, avatar, scoped credential, audit trail, kill switch. First agent free |
| Card / record body | A record: fields and a long-text cell (rich text supported) | Block-tree document per card (headings, lists, embeds) with server-side ?depth= expansion — a full draft lives in the card |
| MCP server | AI assistant integrations (evolving, July 2026) | First-party MCP server at /v1/mcp/http — a typed tool per endpoint |
The deeper mismatch isn’t price — it’s shape. In Airtable, a piece of content is a record: fields plus a long-text cell. The draft itself lives somewhere else, linked by URL. On Novum OS the card body is the draft — a block-tree document an agent writes into, an editor revises in place, and the API returns whole with server-side ?depth= expansion. When the pipeline’s output is a document, the board should hold documents.
Keep Airtable when your problem is structured data: an asset library with rollups, a CRM-ish tracker with linked records and formula fields, interfaces built over a shared base. Novum OS has no formulas and no relational views — deliberately. Plenty of teams will run both: the database of record there, the working pipeline here, stitched by webhooks on both sides.
Move the pipeline to a board that doesn’t count your runs — free tier, no card.
Create account