How to self-host NocoDB in 2026: Airtable alternative

What NocoDB is and why people self-host it

NocoDB is open-source no-code database software — the closest equivalent to Airtable, with the source code on GitHub. 50,000+ stars in 2026. It turns any MySQL, PostgreSQL, MariaDB, or SQL Server database into a spreadsheet interface with views, forms, kanban boards, calendars, and automatic REST + GraphQL APIs on every table.

Three reasons to self-host instead of using Airtable.

Airtable's per-seat math. Airtable Team is $24/seat/month; Business is $54/seat/month. A 10-person team is $240–$540/month. NocoDB self-hosted is free for unlimited users at the same flat server cost.

Bring your own database. NocoDB's killer feature: connect it to a database you already have. Existing PostgreSQL production database? Point NocoDB at it, give your ops team a spreadsheet view into data they can't easily query themselves. Airtable can't do that — your data has to live inside Airtable.

Unlimited records, unlimited storage. Airtable caps records per base (1,500 on free, 50,000 on Team, 500,000 on Business). NocoDB self-hosted is limited only by your database's capacity — PostgreSQL handles tens of millions of records without breaking a sweat.

Three ways to self-host NocoDB

Path A: Auto-Upstall on a VPS (single-command setup)

NocoDB ships an "Auto-Upstall" script — a single command that sets up NocoDB plus PostgreSQL plus Redis plus Traefik (for SSL) on a clean VPS in one go. Spin up a 2 GB RAM VPS ($10/month at DigitalOcean, Hetzner), SSH in, run the install command, point your domain.

Realistic time-to-first-deploy: 30–60 minutes. NocoDB's setup script is one of the cleanest in the self-host ecosystem.

Path B: Docker Compose with your existing database

If you want NocoDB to manage an existing PostgreSQL database, write a custom docker-compose.yml with just NocoDB (skip the bundled Postgres) and point the metadata variables at your existing instance. Most powerful path for teams who already have production data they want to expose as a spreadsheet.

Path C: livemy.app one-click deploy

Pick the NocoDB template, point your domain, ship. livemy.app provisions PostgreSQL for the metadata store, mounts persistent volume, applies daily backups.

The good. Three-minute deploy. $20/month flat. The optional $5/month backups add-on covers your NocoDB schema + records.

From zero to NocoDB on livemy.app (about 3 minutes)

Step 1: Sign up at livemy.app, pick Maker

Go to livemy.app, click Start free, pick Maker ($20/month). Always-on is required — the REST/GraphQL APIs that NocoDB exposes are no good if the server sleeps.

Step 2: Deploy from the NocoDB template

In the dashboard: New project → Template → NocoDB. livemy.app pulls the official image and provisions a PostgreSQL instance for the metadata store.

Step 3: Configure the essential environment variables

Under Project Settings → Environment Variables:

• NC_DB — the metadata database connection string (auto-populated by livemy.app's NocoDB template; format is pg://user:pass@host:5432/dbname)

• NC_AUTH_JWT_SECRET — a 32+ character random string for signing auth tokens

• NC_PUBLIC_URL — the full public URL with https://

Plus SMTP variables if you want NocoDB to send invitation emails (Mailgun, Postmark, Resend work).

Step 4: Deploy and complete the setup wizard

Typical deploy time: 2–3 minutes. When status is Live, visit the URL. The first visitor creates the super-admin account.

Step 5: Connect a data source

In NocoDB, click + New project. Two paths:

• Create a new database from scratch — NocoDB creates fresh tables, you build your spreadsheets from zero

• Connect to an existing database — paste the connection string for your existing PostgreSQL or MySQL instance. NocoDB introspects the schema and gives you a spreadsheet view of every table

Existing-DB connection is where NocoDB really shines. Your ops team can edit production data through a spreadsheet UI without ever writing SQL.

Step 6: Point your domain

Add custom domain, update DNS, wait for SSL. Update NC_PUBLIC_URL to the final domain and redeploy — NocoDB uses it for share links and form URLs.

Five things that quietly break self-hosted NocoDB

1. Metadata DB confused with data DB

NocoDB has two database concepts: the metadata DB stores NocoDB's own data (users, views, settings); the data DB stores the actual records you're managing. They can be the same database (default) or separate (recommended for production). Many self-hosters mix these up and end up with their data and NocoDB's metadata in the same tables.

Fix. For production, use NC_DB for metadata (a small dedicated Postgres). Connect data sources separately via the NocoDB UI for each project. livemy.app's template pre-configures this correctly.

2. NC_PUBLIC_URL mismatch breaks share links

NocoDB builds public form URLs, share links, and webhook URLs from NC_PUBLIC_URL. If it points at the temporary subdomain after you moved to a custom domain, every shared link breaks.

Fix. Update NC_PUBLIC_URL after every domain change. Redeploy.

3. Lose NC_AUTH_JWT_SECRET = every user logged out

JWT secret signs auth tokens. Change the secret and every active session becomes invalid — users get bounced to the login page.

Fix. Generate the secret once at first deploy, store it in a password manager, never change it.

4. Connection string permissions are wrong on the data DB

When connecting NocoDB to an existing production database, the database user in the connection string needs read/write permissions on the tables you want to edit. Read-only connection = NocoDB shows the data but every edit fails with a permission error.

Fix. Create a dedicated NocoDB user on the data DB with appropriate permissions. For read-only ops dashboards, that's fine; for editing, GRANT SELECT, INSERT, UPDATE, DELETE on the tables you want managed.

5. Forms and webhooks fire to the old URL after migration

NocoDB stores form URLs and webhook URLs in the metadata DB. If you migrate the instance to a new domain and just update NC_PUBLIC_URL, existing forms and webhooks still reference the old URL.

Fix. After any URL change, walk through Settings → Webhooks and Settings → Forms in NocoDB UI to refresh URLs. Or accept that forms shared via the old URL just stop working.

Cost: Airtable vs self-hosted NocoDB

Real numbers for a 10-person team managing project records.

Airtable Team: $24/seat × 10 = $240/month for 50,000 records per base.

Airtable Business: $54/seat × 10 = $540/month for 500,000 records per base.

Self-hosted on a $10 VPS: $10/month flat for unlimited users, unlimited records.

Self-hosted on livemy.app: $25/month flat ($20 Maker + $5 backups), unlimited users, unlimited records, managed Postgres.

For a 10-person team, livemy.app saves $215–$515/month. Annual: $2,500–$6,000. Self-hosting NocoDB pays for itself in week one.

FAQ

Is NocoDB really free?

The Community Edition is free under the AGPL license — unlimited users, unlimited records, unlimited storage (limited only by your DB). You pay only for the server. Realistic total: $10–25/month depending on host. There's also a paid Cloud version (NocoDB Cloud), but self-hosting is the open-source path.

Can NocoDB really replace Airtable for my team?

For most teams, yes. Grid view, kanban, gallery, form, calendar views — all there. Linked records, lookups, rollups, formulas — all there. Where Airtable still wins: pre-built marketplace apps (Salesforce sync, etc.) and the polish on edge cases. For a database-as-spreadsheet workflow with custom integrations via the REST/GraphQL APIs, NocoDB matches or beats Airtable.

Can I connect NocoDB to my existing production database?

Yes — this is its standout feature. Point NocoDB at any PostgreSQL, MySQL, MariaDB, or SQL Server instance. NocoDB introspects the schema and gives you a spreadsheet view immediately. Read-only for safety, or with edit permissions if you trust your team to edit production via the UI.

Can I migrate from Airtable to NocoDB?

Yes. NocoDB has a built-in Airtable importer (Add new project → Import from Airtable). It pulls bases, tables, views, and records via Airtable's API. Some advanced field types (formulas referencing external data, marketplace blocks) need manual recreation.

What's the cheapest way to host NocoDB?

A $5–10/month VPS with the official Auto-Upstall script. Realistic total: $5–20/month including SSL (free SSL certificate) and SMTP (Mailgun free tier). Unlimited users on the same flat cost.

Will it auto-update?

On livemy.app, opt-in auto-update or pin to a specific version. NocoDB ships frequent updates including major UI improvements through 2025–2026. For a self-hosted database UI, staying current is recommended.

Self-host NocoDB — unlimited users, bring your own database

If you're paying Airtable per seat or running into base-size limits, NocoDB flattens both. The cheapest path is a $10 VPS with NocoDB's one-command installer. The fastest path is livemy.app's NocoDB template.

→ Start free on livemy.app · NocoDB template with Postgres metadata store, custom domain, SSL, backups, all on Maker at $20/month flat.

Connecting NocoDB to an existing production database and want help with the schema? Email hello@livemy.app. Replies inside one business day.

Read next

• How to self-host n8n in 2026: the complete guide

• How to self-host Outline wiki in 2026: Notion alternative

• How to self-host Ghost in 2026: own your blog and newsletter

• How to self-host Plausible Analytics in 2026