NocoDB: The Self-Hosted Database Workspace That Replaces Airtable

If your team uses Airtable for anything serious, you have probably hit one of three walls: the record limit, the pricing cliff, or the moment you realized you cannot export your data cleanly and go somewhere else. NocoDB was built specifically for that moment. It is a free, self-hosted tool that gives you the same spreadsheet-style views (grid, kanban, gallery, calendar, form) but your data lives in a real database that you own and control. No per-seat tax for features. No vendor holding your records hostage.

The project lives at github.com/nocodb/nocodb and has accumulated 64,000+ stars, which puts it in the tier of tools with genuine production deployments behind the popularity count.

What NocoDB actually is

NocoDB is a no-code database platform. "No-code" here means the people creating and managing tables, views, and forms do not need to know SQL (a language used to query databases) or any other programming language. "Database platform" means your actual data is stored in a proper relational database (MySQL, PostgreSQL, SQLite, SQL Server, or others) rather than a proprietary format.

The interface looks like a spreadsheet: rows and columns, filters, sorts, grouping by field. But unlike a spreadsheet, it handles relational data properly. You can link records across tables, roll up values from linked records, and build lookup fields that pull data from one table into a view of another. These are the things Airtable does well, which is why NocoDB targets the same market.

The key architectural difference from Airtable is ownership. When you install NocoDB, you point it at a database on a server you control. Your data never moves to NocoDB's infrastructure unless you choose their hosted cloud product. For teams handling anything sensitive (contracts, customer records, financial data), that distinction matters and has real compliance implications.

NocoDB also connects to databases that already exist. If your company has a PostgreSQL database that a developer set up two years ago, NocoDB can read and write to it through a spreadsheet-style interface without any migration. That is a meaningful capability gap versus Airtable, which has no path to an existing database.

What you get after installing it

The core of NocoDB is its view system. Every table can be presented as multiple views simultaneously, each with its own filters, sorts, and visible columns, without affecting the underlying data:

• Grid view: the default spreadsheet interface with infinite scrolling and multi-cell selection. Handles large tables without slowing down.
• Form view: a public-facing or internal form that writes directly into a table. Supports conditional field visibility, custom branding, and URL-based pre-filling. Useful for intake workflows, feedback collection, or replacing Google Forms.
• Kanban view: cards organized by a status field, draggable between columns. Standard project-tracking layout.
• Gallery view: card-based layout for image-heavy records. Good for product catalogs, asset libraries, or any table with attachment fields.
• Calendar view: maps records to a date/time field. Shows what is due when.

On top of views, NocoDB ships:

Automation workflows (called Workflows V3 internally) built on a node-based engine. You connect trigger nodes (a new record is created, a webhook arrives, a schedule fires) to action nodes (send a Slack message, call an external API, update another record). Configuration is visual; no code required for standard patterns.

Webhooks: send a notification to any external service when records change. Connect to Zapier, Make, or a custom endpoint.

Dashboards and widgets: bar charts, line charts, pie charts, metric cards, tables, and maps built from your table data. No separate business intelligence tool required for basic reporting.

App store integrations: Slack, Discord, Mattermost (chat), AWS SES, standard email servers, MailerSend (email), AWS S3, Google Cloud Storage, Minio (file storage).

REST API: every table is exposed as a REST endpoint (a web address you can call programmatically to read or write data) automatically. Swagger documentation (an interactive reference for the API) is included. You can also use the NocoDB JavaScript SDK (a library developers use to call the API from code) if your team has someone building on top of it.

Role-based access: five roles (Owner, Creator, Editor, Commenter, Viewer) at the workspace, base, and view level. You can share a specific view with an external user without giving them access to the full base.

Documents and Scripts: rich-text pages organized hierarchically inside a base, and a scripting environment for running custom code against your data with sandboxed execution.

The install experience

There are three paths. The first two are for self-hosting; the third is the cloud option.

Docker (recommended for most teams). One command:

docker run -d \
  --name noco \
  -v "$(pwd)"/nocodb:/usr/app/data/ \
  -p 8080:8080 \
  nocodb/nocodb:latest

Open http://localhost:8080 in a browser. The setup wizard runs on first access and walks you through creating the first admin account. For SQLite (a lightweight local database, fine for evaluation and small teams), no additional configuration is needed. For production with PostgreSQL, you add the NC_DB environment variable with your database connection string.

Auto-upstall is the faster path for teams that want a production-ready deployment on a server with a real domain and automatic HTTPS (the padlock in your browser, meaning the connection is encrypted). One line:

bash <(curl -sSL http://install.nocodb.com/noco.sh) <(mktemp)

The script prompts for your domain name, installs Docker if it is not already present, and sets up NocoDB alongside PostgreSQL (a full-featured open-source database), Redis (a caching layer that speeds up reads), MinIO (file storage), and Traefik (a reverse proxy, meaning a program that sits in front of NocoDB and handles HTTPS certificates and routing). It generates secure passwords automatically and writes its configuration to a local state file so future runs upgrade rather than reinstall. For a non-technical operator, this is the cleanest path if you have a Linux server and a domain.

Binaries: single executable files for macOS, Linux, and Windows. Download and run. Good for a local trial without Docker. Not suitable for a shared team deployment.

NocoDB Cloud exists for teams that do not want to run any infrastructure. It is a hosted version of the same software with a free tier, which is a reasonable option if the self-hosting part is the dealbreaker.

The overall install experience is better than most self-hosted tools because the auto-upstall script handles the parts that normally require a developer (encrypted connection setup, routing, database configuration). A technically literate non-developer can follow it on a DigitalOcean or Hetzner virtual server in under 20 minutes.

Where it fits and what to compare it to

NocoDB competes directly with Airtable and with several other open-source tools in the same space.

Airtable is the obvious comparison. Airtable has a better-polished UI, more native integrations, and a marketplace of pre-built templates. NocoDB's advantages are cost (free on your own server), data ownership, and the ability to connect to an existing database. If your team is on Airtable's free plan and data ownership is not a concern, staying there is a reasonable choice. If you are on a paid Airtable plan and paying per seat for features you rarely use, NocoDB is worth the migration effort.

Baserow is the closest open-source competitor: another self-hosted spreadsheet-database platform with a clean UI and a hosted cloud option. It uses the MIT license, which means you can redistribute and commercially deploy it without restriction. NocoDB's Sustainable Use License restricts commercial redistribution but is effectively equivalent for internal team use. Baserow's UI is arguably cleaner; NocoDB has more database backends and a longer history.

Grist is a spreadsheet-database hybrid with a Python scripting layer and stronger formula support. Better for analysts who want to run calculations inside their tables. Less focused on the Airtable-replacement use case; more focused on replacing Excel for structured data work.

AppSmith and Budibase are no-code app builders that can front-end any database. More flexible than NocoDB for building custom interfaces, but they require more setup per use case. NocoDB gives you useful views immediately; an app builder gives you blank canvas with more power.

The decision tree is straightforward: if you want Airtable's specific feature set on your own infrastructure, NocoDB is the right tool. If you want to build custom internal apps on top of a database, look at Budibase or AppSmith instead.

Verdict

Install it if your team is paying for Airtable or a similar tool and data ownership matters, or if you want to put a usable interface on a database that already exists. The combination of multiple view types, automation workflows, role-based access, a REST API, and a self-hosting path with no per-seat fees is genuinely competitive with the paid tier of hosted alternatives.

Hold off if you need a zero-setup, no-maintenance experience and data ownership is not a priority. NocoDB's strength is that it runs on your infrastructure. If managing a server is a dealbreaker for your team, the NocoDB Cloud hosted option exists but narrows the cost advantage over Airtable.

One real caveat: the license. NocoDB uses the Sustainable Use License rather than the more permissive open-source licenses you may have seen elsewhere. For internal business use, this does not restrict you. If you are a developer or consultancy considering packaging NocoDB inside a product you sell, read the license terms at nocodb.com before committing.

The 64,000+ stars and multi-year production history mean you are not betting on an experiment. The auto-install script and Docker path mean your AI agent can have it running before you finish reading this article.

For your agent to install this

You can skip this section. It is the install details your AI agent needs. If you are using Cowork, Claude Code, ChatGPT Work, Codex, or Hermes, say "install NocoDB for me" and it will read the tables below.

System requirements

Install commands

Docker (local evaluation or team server, SQLite):

docker run -d \
  --name noco \
  -v "$(pwd)"/nocodb:/usr/app/data/ \
  -p 8080:8080 \
  nocodb/nocodb:latest

Then open http://localhost:8080.

Docker with PostgreSQL (production):

docker run -d \
  --name noco \
  -v "$(pwd)"/nocodb:/usr/app/data/ \
  -p 8080:8080 \
  -e NC_DB="pg://your-db-host:5432?u=username&p=password&d=dbname" \
  -e NC_AUTH_JWT_SECRET="your-secret-key" \
  nocodb/nocodb:latest

Auto-upstall (production server with domain and HTTPS):

bash <(curl -sSL http://install.nocodb.com/noco.sh) <(mktemp)

Prompts for your domain. Installs Docker, PostgreSQL, Redis, MinIO, and Traefik automatically.

Binary (macOS Apple Silicon, local trial):

curl http://get.nocodb.com/macos-arm64 -o nocodb -L && chmod +x nocodb && ./nocodb

First-run checklist

1. Open the NocoDB URL in a browser (default: http://localhost:8080)
2. Create the first admin account in the setup wizard
3. Create a new Base (a workspace container for related tables)
4. Create tables or import from a CSV file
5. Add views: click the plus icon next to the default Grid view to add Form, Kanban, Gallery, or Calendar
6. Set up roles: Invite users via the Base settings and assign roles (Editor, Viewer, etc.)
7. Connect to an existing database: use Base Settings to add an external data source