NocoDB Review: The Database Bill That Stops Growing

Airtable's Team plan is $20 per user per month and caps a base at 50,000 records.

Fifty thousand listings is not a large directory. A single city's restaurants, salons and trades will get you most of the way there, and a national directory blows past it in the first import.

NocoDB's self-hosted Community edition has no record limit, no storage limit and no seat limit. You pay for the server it runs on and nothing else.

That is the whole argument, and for a directory it is a strong one, because a directory is a row-count business.

What NocoDB actually is

It puts a spreadsheet interface on top of a real database.

You get grid, gallery, kanban, form, calendar and map views over the same data. You get relational links between tables, so a Listings table can point at Categories and Cities the way a directory needs rather than duplicating strings down a column. And you get an auto-generated REST API over every table, which is how your front end reads the data.

If you have used Airtable you already know how to use it. That is deliberate, and NocoDB does not pretend otherwise.

The difference is where it runs. Airtable runs on Airtable's servers under Airtable's pricing. NocoDB runs wherever you put it, including a $6 VPS.

Why the record limit is the deciding factor

Every no-code database prices along the two axes a directory grows fastest: records and seats.

Records grow because that is what a directory is. Seats grow the moment you bring in a virtual assistant to clean data, or a partner to handle outreach, or a contractor to write descriptions.

So the tool that charges per record and per seat is charging you precisely for succeeding. That is a bad shape for a business whose whole model is "get to 10,000 listings and rank for all of them."

Self-hosted NocoDB removes both meters. Import 200,000 rows if your niche has them. Add five people to the workspace. The bill does not move.

What the free self-hosted edition includes

This is the part worth being specific about, because "open source" often means a hollowed-out version.

The Community edition gives you unlimited records, unlimited storage, unlimited seats, five permission roles, six view types (grid, gallery, form, kanban, calendar, map), and two automation workflows per base.

For running a directory, that list is essentially complete. Six view types covers everything from a bulk-edit grid to a form for accepting listing submissions.

What the free edition does not include

Table and field level permissions. Row-level security. Audit logs. SSO. The AI features. Connections to external databases.

Read that list and notice what it is. Every item is a governance or enterprise-integration feature. None of them is a limit on your data.

That is the right place to draw the line, and it means a solo directory builder can run the free edition indefinitely without hitting a wall that exists to push them onto a paid plan.

The licence is AGPLv3 for the core, with a separate proprietary licence on the Enterprise pieces.

Pricing

The cloud plans are priced per user, which reintroduces the seat meter. If you are one person running a directory, the free self-hosted edition is not a downgrade from the cloud tier, it is a different trade: you handle the server, you keep the unlimited data.

Where it fits in a directory stack

As the source of truth. Scrape into NocoDB, clean in the grid view, and let your directory front end read the REST API. Your listings live in a database you control, not inside a WordPress install you cannot easily export.

As the submission handler. The form view gives you a public form that writes straight into a table. Set a Status field, filter a view to Pending, approve in one click.

As the bulk-edit surface. This is the underrated one. Fixing 400 badly formatted phone numbers is unpleasant in any CMS and trivial in a grid.

Where it does not fit

You have to run it. Docker, a VPS, backups, updates. It is not hard, but it is a thing you now own, and if the phrase "restore from backup" makes you uneasy, the cloud plan or Airtable is worth the money.

It is a database, not a website. NocoDB stores and organises your listings. Something else has to render them. Pair it with a front end rather than expecting it to be one.

And two workflows per base is genuinely tight if you plan complex automation. That is where you either upgrade or hand the automation off to n8n.

Common questions

Is the self-hosted version crippled compared to cloud?

No, and this is unusual. The limits are on governance features, not on data. Unlimited records on the free tier is the headline and it is real.

Can it replace Airtable entirely?

For a directory, close to it. Airtable has a deeper integration ecosystem and a more polished interface. NocoDB has your data on your server with no record ceiling.

How do I get data out?

REST API, or CSV export, or query the underlying database directly. NocoDB sits on top of Postgres or MySQL, so worst case your data is in a standard database you can read without NocoDB at all. That is a meaningful difference from a proprietary store.

Does it handle images?

Yes, attachment fields with unlimited storage on self-hosted. For a directory with a photo per listing, that limit mattering is exactly the scenario the free tier handles.

Verdict

NocoDB is the right backend when your directory's growth is the thing that would otherwise cost you money.

The reasoning is not that it is cheaper today. At 500 listings, Airtable's free tier is fine and easier. The reasoning is that the pricing curve is flat, so the version of your directory that works does not cost more to run than the version that does not.

Install it on a small VPS, import your first scrape, and see whether the grid view is where you want to do your data work. If it is, you have a backend that never charges you for growing.