Self-Hosted Airtable Alternatives: Baserow, NocoDB, and Grist on Your Server
By the SoftSea editorial team
Photo: panumas nikhomkhai / Pexels
The trade is duties for caps
Every hosted Airtable alternative sells relief from a cap or a seat bill. Self-hosting sells something else: the caps and the bill both disappear, and in their place you acquire a small, permanent set of duties. This guide compares Baserow, NocoDB, and Grist as things you operate, not things you subscribe to: what runs on the server, what a backup really consists of, how upgrades behave, and where each tool's data lives when something goes wrong. If your question is which of these is open source, the license-checked companion guide answers it, including the January 2026 change that moved NocoDB to a fair-code license. This article assumes the license question is settled and the server question is the live one.
The economics, briefly: all three self-host free of license fees with no record or seat caps (Baserow's core under MIT, Grist under Apache-2.0, NocoDB's Community edition free forever under its Sustainable Use License). A VPS that runs any of them comfortably costs less per month than one Airtable Team seat at $20 per user per month billed annually. The variable that decides whether this is a saving is your time, priced honestly below.
Tool
What you run
Where the data lives
Backup unit
Baserow
App containers plus PostgreSQL
Baserow's database
Database dump plus file storage
NocoDB
One service over your database
Your PostgreSQL, MySQL, MariaDB, or SQLite
The database itself, your existing routine
Grist
One container, documents as files
SQLite-backed documents
Document files plus application data
Baserow self-hosted: the familiar grid, your machine
Baserow's self-hosted core gives the closest Airtable experience in this guide: linked records, forms, views, and the application builder, with no row limit because there is no vendor metering your rows. Operationally it is a small stack rather than a single process: the application, a PostgreSQL database, and supporting services, typically run as containers. Backups are a database dump plus the uploaded-files storage, and the failure to include the second half is the classic Baserow restore surprise: records return, attachments do not. Upgrades are regular and documented; the project ships steadily, which rewards a monthly update habit and punishes annual neglect, because jumping many versions at once is where self-hosted migrations go to be re-planned.
Sizing is modest: a small team instance is comfortable on a 2 to 4 GB VPS. The premium features are licensed separately from the MIT core, so decide which side of that line your deployment needs before you build workflows on a feature your self-hosted edition does not include.
Interactive tool
Comparison Builder
Pick two or three products and see them side by side on the numbers that decide the purchase.
Measure
Baserow
NocoDB
Grist
Starting paid price
$10 per user/mo, billed annually
$12 per user/mo, billed annually
$8 per user/mo, billed annually
Free option
Free plan: cloud Free with 3,000 rows and 2 GB per workspace; self-hosting the open-source core is free with no row limit
Free plan: cloud Free for up to 3 users with 1,000 records; the self-hosted Community edition is free forever with unlimited records and seats
Free plan: hosted Free with up to 5,000 records per document; the open-source Community edition is free to self-host
Plans
Free (Cloud): free · Premium: $10/user/mo annual · Advanced: $18/user/mo annual · Self-Hosted Core: free · Enterprise: not published
Free (Cloud): free · Plus (Cloud): $12/user/mo annual · Business (Cloud): $24/user/mo annual · Scale (Cloud): $45/user/mo annual · Community (Self-Hosted): free
Free: free · Pro: $8/user/mo annual · Business: $24/user/mo annual · Community (Self-Hosted): free · Enterprise: not published
Platforms
Web, Linux
Web, Linux, Windows, macOS
Web, Linux
Best for
teams leaving Airtable for open source, EU data residency on your own server, non-technical teams that know the Airtable grid
teams whose data already lives in PostgreSQL or MySQL, developers who want an API on their tables, self-hosters who accept a fair-code license
formula-heavy bases, teams that need record and cell level permissions, open-source self-hosters who think in spreadsheets
Strengths
Closest open-source match to the Airtable grid, so retraining is minimal; Self-hosting removes row and seat economics entirely; Application builder turns a base into a portal without another tool
Your data stays in a standard SQL database you can query directly; Self-hosted edition has no record limit beyond your server; Automatic REST APIs for every base
Formulas are real Python, so calculations outgrow spreadsheet syntax; Access rules work down to the cell, which Airtable cannot match; Fully open source under Apache-2.0, including the self-hosted edition
Watch out for
Core is MIT but premium and enterprise features sit outside it; Formulas use Baserow syntax, so Airtable formulas are rewritten by hand; Automations and interfaces do not import from Airtable
No longer OSI open source: the January 2026 move to a Sustainable Use License makes it fair-code, not open source; External database connections need the cloud Business plan; You run the server, backups, and upgrades on the self-hosted route
The interface thinks like a spreadsheet, not an Airtable base, so views are rebuilt; Airtable formulas arrive as comments and are rewritten by hand; Smaller template and integration ecosystem than Airtable
Lowest entry price: Grist at $8 per user/mo billed annually. Real free plan: Baserow, NocoDB, Grist. Entry price is the floor, not the decision: check the plan line above for the tier that actually includes the feature you need.
All figures from vendor pricing pages, checked November 18, 2026. Some vendors price by contacts, tasks, or operations instead of seats; those notes are in the plan data and the linked pricing guides.
NocoDB self-hosted: the database was already yours
NocoDB inverts the operational model. It does not bring a database; it sits on yours. Point it at PostgreSQL or MySQL and the bases it shows you are tables in a database your existing backup routine already covers, readable by any SQL tool, with automatic REST APIs generated per base. This is the strongest data-ownership story in the category: if the interface vanished tomorrow, your data remains in the most portable form software has. The self-hosted Community edition is free forever with unlimited records and seats.
The duties concentrate differently: you own database administration (which you may already do), NocoDB's own metadata and user store need backing up alongside the data database, and upgrades of the interface layer are frequent and usually smooth. The license deserves one sentence here because it changed: since January 2026 NocoDB is fair-code under a Sustainable Use License, free for this use, restricted mainly against reselling it as a service. The open-source guide carries the full analysis.
Grist self-hosted: documents you can carry
Grist's Community edition is a single container whose data lives in documents: discrete, copyable files with relational tables, Python formulas, and cell-level access rules inside them. Operationally this is the lightest serious option here. Backup is close to copying a directory, moving an instance is close to moving files, and a document can be lifted out and opened elsewhere, which makes Grist unusually forgiving of infrastructure changes. Its hosted tiers (Pro $8 per user per month billed yearly) exist for teams who want the same model without the server.
The operational caveat is shape: Grist thinks in documents and spreadsheets, so a deployment serving many small bases becomes a document library to organize, and its access rules, while powerful, are per-document machinery to maintain. For a handful of substantial, formula-heavy bases, it is the easiest self-host in this guide to live with for years.
The duties, priced
Whichever tool you choose, four obligations arrive with it. Tested backups: a restore rehearsed once a quarter, because an untested backup is a hope. Updates on a cadence: monthly is a rhythm, annually is a risk. TLS and access hygiene: a database interface on the public internet deserves the same care as any admin panel, ideally behind your VPN or identity provider. And a named owner with a deputy. In hours, a healthy small deployment costs roughly an hour a month plus an upgrade afternoon per quarter. Against Airtable Team at $20 per seat, a ten-person team saves about $2,400 a year in licenses; whether that is profit depends entirely on what the owner's hours are worth, which the checklist below forces into the open before migration day.
Interactive tool
Self-Host a Database Checklist
Check off each step as you finish it. Your progress stays on this page.
0 of 7 complete
0% done
The verdict
Choose Baserow when the team wants Airtable's grid on your infrastructure with the fewest behavioral changes. Choose NocoDB when the data's home matters most and a real SQL database underneath is the point, accepting its fair-code license with eyes open. Choose Grist when your bases are few, substantial, and formula-driven, and you want the lightest operations profile in the category. Choose none of them if nobody wants the duties: the hosted tiers in the main Airtable alternatives guide exist precisely for teams whose scarcest resource is attention, and the Microsoft-tenant alternative covers the other way to pay $0 at the margin.
Related guides
This decision rarely stands alone. The guides below cover the closest questions on the chart, each with prices checked on the vendor pages.
What is the best self-hosted alternative to Airtable?
Baserow, for most teams: the closest match to Airtable's grid and linked records, free to self-host under an MIT core license with no row limit. NocoDB is better when you want the data in your own PostgreSQL or MySQL database with automatic APIs. Grist is better when formulas and permissions dominate and you want documents you can back up by copying files.
How much does self-hosting cost in practice?
License fees are $0 for all three tools' self-hosted editions. The real costs are a VPS (a small one runs less per month than a single Airtable Team seat at $20) and admin time: roughly an hour a month for updates and checks, plus a quarterly backup-restore test and upgrade session. For a ten-seat team the license saving against Airtable Team is about $2,400 per year, against which those hours should be honestly priced.
What do I need to back up?
More than the obvious half. Baserow needs its database and its uploaded-file storage; restoring only the database returns records without attachments. NocoDB needs the underlying database (often already in your routine) plus its own metadata and user data. Grist needs its document files and application data. In all cases the rule is the same: the backup is not done until a restore has been performed from it at least once.
Is NocoDB free to self-host even though it is not open source anymore?
Yes. The self-hosted Community edition is free forever with unlimited records and seats under its Sustainable Use License. The January 2026 license change restricts mainly the resale of NocoDB as a hosted service to others; running it for your own organization is the use the license is built around. Organizations with a formal open-source procurement requirement should note it no longer qualifies as OSI open source, as the license guide explains.
How hard are upgrades on self-hosted instances?
Routine, if they are frequent. All three projects release steadily, and one-version steps are documented and quick. The pain in self-hosting is almost always version lag: an instance left alone for eighteen months faces a staircase of migrations, changed requirements, and stale documentation. A monthly update habit keeps each step small, which is why this guide treats update cadence as a selection criterion rather than a footnote.
Can we start self-hosted and move to hosted later, or the reverse?
Both directions are possible in this category because the data models are exportable (CSV at minimum, and in NocoDB's case the database itself). The practical path is to pilot on the hosted free tier (Baserow free allows 3,000 rows per workspace; Grist free 5,000 records per document), prove the shape fits, and then decide where it lives permanently. Confirm the export path during the pilot, while it is still a curiosity rather than a crisis.
Photo credits: panumas nikhomkhai (Pexels). Photos are served from this site; follow the credit to the library page for the original.