↓Skip to main content
  1. Writings/

I turned my database into a spreadsheet with NocoDB and it's surprisingly good

·7 mins
cover image for the nocodb article

I was looking for a simple way to organize my projects and ideas and maybe automate them with AI. Well the last part came up fairly recently during my experimentation but I needed something for that.

I have used Airtable in the past and it was my go-to tool for collecting data and collaborating with others. However, I soon started to hit the limit of free tier and some important enough features that I needed were paywalled. That got annoying pretty quickly.

So I started searching for tools that were similar to Airtable but open-source, which I can easily self-host on my own hardware. And that’s how I stumbled upon NocoDB, and it turned out to be much more than I expected.

Before I dive too much into its features and capabilities, let me give you a brief overview of what it is.

What exactly is NocoDB? #

It’s an source-available, fair-code no-code platform that transforms your database into something that feels much like a familiar spreadsheet interface.

“nocodb website homepage”
Instead of having to write SQL queries or manually interact with the database, it gives a visual interface where you can create tables, add records, organize information and establish relationships between different datasets.

Under the hood, it connects directly to standard databases like SQLite, PostgreSQL, MySQL and SQL Server. If you already have an existing database running on your server, you can point NocoDB right at it.

“different database integrations for nocodb”

Is it really free? #

The Community edition is free forever when self-deployed, with unlimited records, unlimited storage and unlimited seats. All five roles (owner, creator, editor, commenter, viewer), six view types, record comments and conditional webhooks are in the free tier.

Paid plan exists for teams that need additional functionality like SSO, table and field-level permissions, audit logs and row-level security, which start at $24 per seat / month on a Business plan.

“nocodb pricing page”

For a homelab or a small business, I believe the community edition gives plenty of features to get you started.

Setup and installation with docker #

Note: This section assumes that you already have Docker installed on your system and have some prior knowledge of compose files and mounted volumes .

The fastest way to setup NocoDB is with SQLite database and a simple docker command:

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

That’s it! Docker will create a container named noco, mount the nocodb bind mount for persistent data storage and expose the application on port 8080.

“docker command for nocodb sqlite container”

This setup is perfectly fine for getting started or running a lightweight installation. However, if you intend to use NocoDB regularly, especially with multiple users and larger datasets, I’d recommend using PostgreSQL as the underlying database.

I prefer to write my own stack of services using docker compose files. Here’s a minimal two-container version with NocoDB and Postgres.

First, create a separate directory that will hold our container stack and the bind mounts:

“creating new directory for nocodb”

After that, create the compose.yaml file:

services:
  nocodb:
    image: nocodb/nocodb:latest
    container_name: nocodb
    restart: unless-stopped
    ports:
      - "8080:8080"
    environment:
      - NC_DB=pg://nocodb-db:5432?u=noco&p=change-me&d=noco
      - NC_AUTH_JWT_SECRET=change-me-too
    volumes:
      - ./nocodb-data:/usr/app/data
    depends_on:
      - nocodb-db

  nocodb-db:
    image: postgres:16-alpine
    restart: unless-stopped
    environment:
      - POSTGRES_USER=noco
      - POSTGRES_PASSWORD=change-me
      - POSTGRES_DB=noco
    volumes:
      - ./pgdata:/var/lib/postgresql/data

“editing nocodb docker compose stack”

Before starting the containers, replace the example passwords and JWT secret with your own random values. Make sure the PostgreSQL password in NC_DB matches POSTGRES_PASSWORD.

Now run:

docker compose up -d

Give it a moment to pull the images and initialise the services. You can check whether everything is running with docker compose ps.

“checking nocodb container stack”

Open http://localhost:8080 in your browser, sign up, and you’re good to go. The first account you create automatically becomes super-admin.

“nocodb initial account setup”

Some things you should know about:

  • If you skip the NC_DB variable, NocoDB quietly creates a SQLite database inside the volume instead, which is fine for starting-up.
  • Set NC_AUTH_JWT_SECRET to something random.
  • Put your service behind a reverse proxy with TLS before you open the port to the internet, because anyone who can read port 8080 gets a login page and can brute force themselves in.

Feature that made me stay #

Now that we’ve got NocoDB up and running, let’s talk about its features:

Spreadsheets for everything #

The first thing you will notice when opening NocoDB is its spreadsheet-like interface. You can create tables, add columns, enter records, rearrange fields, apply filters, sort information and group records according to different criteria.

“spreadsheet view of nocodb”

But where it surpasses the spreadsheet is the variety of field types it offers. Apart from the usual text and number fields, you can create:

  • Date and time fields
  • Single-select and multi-select fields
  • Checkboxes fields
  • Attachment fields
  • Formula fields (just like excel)
  • Link fields (this one’s for creating relationships between tables)
  • Lookup and rollup fields

Different views make organising information much easier #

“available views for nocodb”

Everyone has a preference when it comes to organizing data depending on the task. NocoDB tackle this issue by providing different Views for the same underlying table without duplicating data:

“nocodb grid view”
“nocodb kanban view”
“nocodb gallery view”
“nocodb calendar view”
  • Grid view: This is the traditional spreadsheet-style view. It’s particularly useful when you are working with large datasets, editing multiple records, or simply need a quick overview of everything in a table.
  • Kanban view: Kanban organizes records into cards grouped by a particular field. For example you can group tasks according to their status and move them between columns as their progress changes.
  • Gallery view: It displays records as cards, making it particularly useful when working with images, attachments, or visually oriented datasets.
  • Calendar view: This one displays the records according to their date fields. Very useful for viewing which tasks are approaching their deadlines.

Each view saves its own filters, sorts, grouping, and visible fields.

Native forms for quick data capture #

This one is particularly handy for collecting information, same as Google forms. NocoDB lets you generate standalone web forms directly from any table. You can pick which columns appear on the form, customize the labels, and share the link.

“nocodb form view”

Whenever someone submits the form, it drops straight into the database as a new row.

You can establish relationships between different tables #

The most frustrating part of spreadsheets is repeating the same information across multiple tabs. NocoDB handles relational data effortlessly. You can link a “Projects” table to a “Tasks” using a simple “Link to Another Record” field.

“nocodb link to another table option”

Granular permissions and collaboration #

Even if you start out using NocoDB solo, you can easily invite teammates, editors, or clients later. It supports role-based access control, allowing you to lock down entire bases or restrict specific users to view-only or comment-only access.

“collaboration permission and security settings for nocodb”

You can also create password-protected public share links for specific views without giving outsiders access to the rest of the workspace.

Built-in REST APIs and automation hooks #

Every table created in NocoDB automatically generates its own REST API endpoints, complete with Swagger documentation built right into the dashboard.

“nocodb restapi page”

Better yet, it plays nicely with automation tools like n8n, Activepieces, and Zapier. You can trigger webhooks whenever a row is created, updated, or deleted.

“nocodb webhooks”

An MCP server, because it’s 2026 #

NocoDB ships an MCP server; what this means is that you can connect compatible AI-clients interact with the data through natural-language instructions.

> NOTE: Community Edition provides MCP access for reading and modifying records, while broader capabilities such as managing tables, fields, and workflows requires a licensed deployment.

“mcp connectors for nocodb”

My thoughts #

Airtable still has the better interface. I’m not gonna pretend otherwise, and if you need a base for two people and a few hundred rows, the free tier is fine. Stay where you are.

For me, NocoDB is essentially just a fancy wrapper around my data. The reason I chose it, if this project were to disappear tomorrow, or if I decided to migrate to a completely different frontend three years from now, I would not be stuck exporting messy CSV files or annoying proprietary backups.

Would I recommend it? If you already run Docker for something else, yes, without much hesitation. If you have never touched a server before then No because you become the sysadmin yourself and that means you have to look after the updates, periodic backups, TLS certificates and the restore process.

If you have already subscribed to some other platform, do what I did. Spin it up on a spare evening, move one table over, and test it for a week before you cancel anything.