Documents and notes decision

Airtable

Do not rebuild — a single developer can recreate a small portion, but Airtable's enterprise-grade scale, security certifications, and ecosystem are durable advantages that make a full replacement impractical for most teams.

Visit website
You pay

$20/mo

$240/yr

Per seat. Read off the official pricing page.

You’d pay instead

$100one-off80 h to build

$150/mo40 h/mo upkeep

On cash alone, building overtakes the subscription at 8 seats.

The code exists. It is not what you are paying for.

These 2 projects are real, published, and do the core job — and this page still says keep paying. What the subscription buys is infrastructure at scale, infrastructure at scale and compliance and regulation, and none of that ships in a repository. Fork one anyway if you want to. Go in knowing what it does not carry. What stays hard ↓ · All Airtable alternatives, with the arithmetic →

What a replacement has to do

  • A minimal replacement stores structured records, presents editable grid and form views, wires simple automations, and exposes a REST API for integrations.

What it still won’t have

  • Enterprise-grade scale and multi-100M record infrastructure
  • Certified compliance posture (ISO 27001, HIPAA, SOC 2)
  • Large integrations and marketplace ecosystem
  • Polished UI, templates, and onboarding flows
  • Advanced data residency / EKM features and audit tooling

What remains hard

  • Infrastructure at scaleHyperDB with record limits in the hundreds of millions
  • Infrastructure at scaleScale Build apps on top of massive data sets with 100M records
  • Compliance and regulationISO 27001, HIPAA, SOC 2 Type II, and GDPR compliant
Read the build prompt

First-year cost

Keep paying

Paying is—cheaper in year one.

On cash alone, building overtakes the subscription at 8 seats.

Paid seatsseats

Money you would actually spend

Keep paying
—

Subscription price × seats × 12

Build it
—

AI build —APIs + hosting —

Time you would spend

—

—

What you would spend

What we assumed

The verdict above measures whether you could build it. This one is only about money.

Runnable build prompt

Not run yet
Build a minimal Airtable-like app using Postgres, Next.js (React), and Supabase for auth and hosting. In scope: a Postgres schema supporting multiple workspaces and relational tables, a REST+GraphQL API to CRUD records and attachments, a React grid view, record detail and form views, workspace/user/role permissions (owner/editor/viewer), a basic automations engine (watch DB events and run webhook/email actions), and connectors for one external integration (Slack or Gmail). Out of scope: multi-100M record scale optimizations, enterprise compliance certifications, marketplace, and mobile apps. Include input validation, authentication error handling, retry logic for webhooks, and unit/integration tests for API and automations.
How we checked5 sources · 2/3 runs agreed · evidence score 25

How the score was reached

  • Pay verdict base20
  • An open-source build was found+5
  • 5 cited sources+3
  • Price verified on pricing page+3
  • Hard moats found in the evidence-6
  • Evidence score25

The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.

How scoring works →

Cited sources · 5

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

✓ Price read off the page! 2 of 3 runs agreed; the verdict is the majority✓ Citations limited to fetched pages! 3 moats quoted from the page