Self-hosted Airtable alternative: a no-code database you own with Baserow

Somewhere between a spreadsheet and a real application sits the thing most teams quietly run on: a shared database with a friendly face. Airtable made that idea popular, then turned it into a meter — priced per seat, capped by row count, and parked on someone else's servers where your operational data lives at their discretion. Baserow is the same idea without the meter: a no-code database you host yourself, with a real API, built-in forms, and a plugin system, and nobody counting your rows or your teammates. We host this for people who want the tool, not the toll.

What Baserow is

Baserow is an open-source, no-code database you host yourself — a fully working product, not a time-limited trial. You get tables that behave like spreadsheets but hold real typed fields, link to one another, and compute with formulas. On top of that sits everything a team actually needs: multiple ways to view the same data, forms that write straight into tables, an automatically generated REST API, webhooks, and live collaboration. On your own box the meter simply isn't there: no row caps, no per-seat pricing, no storage ceiling — the exact limits Airtable charges to lift. The core database, API, forms, and webhooks are MIT-licensed and free to run; Baserow keeps a few extras — some view types, granular roles, SSO — in its own paid tier, but none of the metering that makes Airtable pricier every time you add a record or a teammate. The contrast is the whole point: there, the base is free until it isn't, and every new collaborator is another line on the invoice. Here, the ceiling is your hardware, and your data lives where you put it.

The features that actually matter

• A spreadsheet-database grid — Open a table and it behaves like a spreadsheet, but every column is a real typed field. Sort, filter, group, and hide fields, then save those arrangements as reusable views for different jobs.
• Fields that model real relationships — Link one table to another, pull values across with lookups, roll up totals, and calculate with a full formula language. This is what turns rows into an actual data model instead of a flat sheet.
• Form views built in — Turn any table into a shareable form and collect submissions directly into your data — no separate form tool, no export-and-reimport. Airtable reserves the richer form options for its paid tiers.
• A REST API for every table, generated for you — The moment a table exists, you get a documented REST API for it, with interactive docs and token authentication. Airtable rate-limits the equivalent; here it is yours to call as hard as your server allows.
• Webhooks that fire on change — Trigger outside systems when a row is created, updated, or deleted, so Baserow becomes the source of truth that pokes everything downstream — Zapier, Make, n8n, or anything that takes an HTTP callback.
• Real-time collaboration — Several people edit the same base at once, with changes landing instantly for everyone in it. No refresh, no emailing a copy around, no overwriting each other's work.
• Import, export, and plugins — no lock-in — Pull data in from CSV, Excel, JSON, or XML, or migrate straight from an existing Airtable base, and export it back out whenever you want. Because it is open source, you can extend it with self-hostable plugins for custom fields, views, and applications.

Why self-host it instead of the hosted version

Your data stays yours. The tables you build in a tool like this are the business itself — customers, inventory, hiring pipelines, roadmaps, content calendars. Self-hosting keeps all of it on infrastructure you control, not in a vendor's cloud where retention, access, and analytics are their call to make.

The cost stops scaling per person. Airtable's price climbs with every seat and every row band you cross. A database you own has none of that math: invite the whole company, load in as many records as your disk holds, and the bill does not move because someone new joined or a table got popular.

You control the whole thing. Your own domain, your own backups, your own export on demand. No feature you built a workflow around gets deprecated on a quarterly roadmap you don't sit on, and no upgrade prompt stands between you and the data you entered.

Who it's for

Small teams running the business on a shared base — a lightweight CRM, an inventory list, a content calendar, an asset tracker — who don't want that operational core sitting behind a per-seat meter.

Agencies and consultants building client-facing internal tools, who would otherwise pay for a seat every time they onboard someone else's staff into a workspace.

Developers and technical founders who want a real database with an instant REST API and a clean admin UI to prototype against — the backend for an internal tool, without standing up a schema and CRUD layer by hand.

The honest setup notes

Baserow is more than a single binary, and rolling your own means owning the moving parts. It wants a PostgreSQL database and Redis alongside the app, plus background workers for things like exports and webhooks — the all-in-one image bundles them, but they are still processes you're now responsible for. Backups mean two things, not one: the Postgres database *and* the uploaded files, since attachments live outside the tables. You'll want SMTP wired up so invitations, password resets, and form notifications actually leave the building. Give it a couple of gigabytes of RAM so it doesn't thrash, and plan for updates — new image, run the migrations, hope nothing drifted. None of this is exotic, but it is a standing chore, and it's real work that has nothing to do with the tables you actually wanted to build.

Or let us run it. We handle the database, the workers, the backups, and the updates, and hand you the app.

Deploy it in one click

Rolling your own is a docker-compose file, a Postgres you now babysit, a Redis, a reverse proxy, TLS, an SMTP relay, and a backup routine you'll mean to test one day. It works — and then it's yours to keep working, forever. On Caliber Node it's one click: deploy Baserow in one click and it comes up on your domain with the database, cache, workers, and mail path already stitched together and running. We keep the plumbing patched and backed up; you get real logs, SFTP into the container, and your data exportable whenever you ask. The difference isn't whether Baserow is good — it's whether you spend your first afternoon building tables or building infrastructure.

First run

1. Open Baserow on your domain and create the first account — the first user is the admin.
2. Create a workspace, then add a new database and your first table inside it.
3. Add a few fields — a single-select for status, a link to another table, maybe a formula that does the arithmetic for you.
4. Add a Form view, share its link, and watch submissions land straight in the table as new rows.
5. Open the API docs from the table menu, generate a token, and call your brand-new endpoint — your database is now also a backend.

The bigger picture

The database behind your operation shouldn't be something you rent by the head. It's where the real state of the business lives, and that's exactly the kind of thing worth owning outright — not because self-hosting is a badge, but because a tool this central shouldn't have a meter running on it or a landlord who can change the locks. Baserow gives you a genuine database, and running it yourself means the rows, the relationships, and the API are all genuinely, permanently yours.

Deploy Baserow in a few minutes → https://calibernode.com/cloud-apps

Or browse the full app catalog.

One-click self-hosted apps, managed for you — real logs, SFTP, and your data always exportable. Never a black box.