NocoDB is a free and self-hostable open-source Airtable alternative that turns an existing relational database into an intuitive spreadsheet interface, built for teams who want no-code data management without moving their data into a hosted SaaS product.

What it is

NocoDB is a TypeScript no-code database platform that sits on top of a database and presents the underlying tables as spreadsheets. It lives in the Infrastructure & Operations / Databases category of this registry and is described by its own GitHub listing as "A Free & Self-hostable Airtable Alternative". The project ships as a Docker image, as prebuilt binaries for macOS, Linux and Windows, and through an installer script, and its topics list covers no-code-database, no-code-platform, low-code, spreadsheet, and automatic-api.

The concrete problem it solves is the gap between a real database and the people who need to work in it. Instead of a database administrator writing ad-hoc queries and exporting CSV files, or a team paying for a hosted grid product, NocoDB provides the spreadsheet view directly over the data, plus an automatically generated REST API over the same tables. It replaces Airtable and Microsoft Excel in that role: the interface and the API come from the project, while the data continues to live in a database the operator controls.

Key capabilities

• Spreadsheet interface over database tables, exposed in the browser dashboard at http://localhost:8080/dashboard.
• Automatic REST API generated over existing tables, so no separate API layer has to be written.
• PostgreSQL support through the NC_DB environment variable, for example pg://host.docker.internal:5432?u=root&p=password&d=d1.
• SQLite as the default local storage, used by the plain docker run path with a volume mounted at /usr/app/data/.
• Self-hosting through the published image nocodb/nocodb:latest, run on port 8080.
• Authentication configuration through NC_AUTH_JWT_SECRET, passed as an environment variable alongside the database connection.
• Low-code and no-code build model, aimed at users who work with data rather than with SQL or schema migrations.

Who uses it and how

• Self-hosters who run the nocodb/nocodb:latest container themselves and keep the database alongside it, rather than renting a hosted grid per seat.
• Teams already running PostgreSQL that want a spreadsheet front end and a REST API over the same tables without duplicating the data.
• Operators deploying to a server for production use, using the auto-upstall path, which generates a docker-compose configuration automatically.
• Developers who want a quick local instance, using the per-platform binaries for macOS, Linux or Windows.
• Organisations replacing spreadsheet-driven workflows, where Airtable or Microsoft Excel previously held the working data.

Getting started

The documented Docker path is a single docker run command against nocodb/nocodb:latest, with a volume mounted at /usr/app/data/ and port 8080 published. For production, the README documents auto-upstall, run as bash install.nocodb.com/noco.sh, which sets up NocoDB on a server and generates the docker-compose file behind the scenes.

How it compares

The project positions itself as an open alternative to Airtable and Microsoft Excel, both of which are proprietary paid products, while NocoDB is free and can be self-hosted. That shifts the cost model away from per-seat subscription pricing and keeps data ownership with the operator, since the records stay in the operator's own PostgreSQL or SQLite database. The trade-off is that the hosting, upgrades and backups become the operator's responsibility rather than the vendor's.

When to use it — and when not to

A self-hoster must run and maintain the application container along with whichever database backs it, either SQLite or PostgreSQL, and must set a JWT secret through NC_AUTH_JWT_SECRET. The licence is recorded as NOASSERTION, so anyone needing a clearly declared licence should confirm the terms before adopting it. The README is sparse, covering installation rather than a full feature list, and the binaries are documented as being for quick local testing only, not production; with 710 open issues, teams expecting a fully managed product should look elsewhere.

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

docker run -d \
  --name noco \
  -v "$(pwd)"/nocodb:/usr/app/data/ \
  -p 8080:8080 \
  -e NC_DB="pg://host.docker.internal:5432?u=root&p=password&d=d1" \
  -e NC_AUTH_JWT_SECRET="569a1821-0a93-45e8-87ab-eb857f20a010" \
  nocodb/nocodb:latest

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