Key takeaways
- Airtable is a relational database with a spreadsheet-style interface, so records link to each other instead of sitting in isolated cells.
- The grid you see first is the back end. What most of a team should actually use is an Interface built on top of it.
- Airtable was acquired by Bending Spoons in August 2026, which matters if you are deciding what to build your operation on.
Most explanations of Airtable stop at “a spreadsheet and a database had a baby”, which is accurate and tells you nothing you can act on.
We build operations systems on Airtable for service businesses, so this is the version we give clients on a first call: what it actually is, what the grid is hiding, what it is genuinely good at, and the points where we tell people not to use it.
We do not resell Airtable and we do not sell an alternative to it.
What is Airtable?
Airtable is a cloud-based relational database that you work with through a spreadsheet-style grid. Records in one table can link to records in another, so a client links to their projects, which link to their invoices, without anyone copying a name between tabs.
That is the whole difference from a spreadsheet, and everything else follows from it.
In a spreadsheet a cell holds a value. If a client’s company name appears in four tabs, you have four copies, and one day three of them will be right. In Airtable there is one client record. Everything that needs the client points at it. Change it once and it changes everywhere, because there was only ever one.
Is Airtable basically Excel?
No. It looks like Excel on purpose, and that is where the confusion comes from.
The two are built for different jobs. A spreadsheet is built for calculation: formulas across ranges, financial models, scenarios. A database is built for structure: keeping many related things consistent, and letting other systems read them reliably.
Where each one wins:
| Spreadsheet | Airtable | |
|---|---|---|
| Calculation across large ranges | Strong | Weak |
| Linking related records | Manual and fragile | Built in |
| Field types | Formatting only | Real types, enforced on entry |
| Multiple people editing | Conflicts and overwrites | Row-level, with history |
| Being read by another system | Fragile | API, built for it |
| Cost | Usually free | Per editor, per month |
If your work is modelling numbers, stay in the spreadsheet. Airtable is not trying to win that and will lose it.
The grid is the back end, not the product
Open Airtable for the first time and you land in a grid. Rows, columns, tabs along the top. It looks like the product.
It is not. The grid is where the data lives and where whoever builds the system works. What the rest of a team should be using is an Interface, which is a screen you build on top of the same data: only the fields that person needs, laid out for the job they are doing, with the rest hidden.
We say the same sentence on almost every project. What you took a screenshot of looks like Excel, and that is the back end.
This matters more than it sounds. Most Airtable systems that get abandoned were abandoned because everyone in the company was asked to work in the raw grid, which is confusing, error-prone and nothing like the job they were hired to do.
What is Airtable mainly used for?
The honest answer is that it is a general-purpose database, so it gets used for almost anything. The uses that hold up over time share a shape: several kinds of thing that relate to each other, changing often, with more than one person involved.
In the systems we have built, that has meant client and project tracking where one client has many projects and many invoices, caregiver and staff records with credentials and expiry dates attached, intake pipelines that move a lead through named stages, inventory and orders that link to suppliers, and compliance tracking where each record needs a document and a date.
Where it gets used and later regretted: as a to-do list for one person, where a note app is simpler, and as a financial model, where a spreadsheet is better.
The building blocks
The whole vocabulary is short.
Base. One database. Usually one base per operation rather than one per project.
Table. One kind of thing inside a base: clients, projects, invoices.
Field. A column, but typed. Date, checkbox, attachment, single select, and the important one, link to another record, which is what makes it relational.
View. A saved way of looking at one table: grid, calendar, kanban, gallery, timeline. Same data, filtered and sorted differently, for different people. Views do not copy data.
Interface. The screen you build for the people who should not see the grid.
Automations sit alongside these: when a field changes, send this, create that, call another system.
Is Airtable difficult to learn?
Using it is easy. Designing it is not, and the two get confused.
Anyone who has used a spreadsheet can enter data in Airtable within an hour. What takes real knowledge is deciding what the tables should be, which things link to which, and where the automations belong. Get that wrong and you get a system that works for three months and then fights you.
The most common structural mistake we see is one table doing several jobs at once, usually because it started as a spreadsheet tab and got imported as-is. Splitting it later means rebuilding every view, automation and link that touched it.
What are the downsides of using Airtable?
The list we give clients before they commit.
Record caps are per base. 1,000 on Free, 50,000 on Team, 125,000 on Business. Splitting data across bases to stay under them works until the halves need to talk, and syncing between bases is itself a paid feature.
You cannot export the whole thing. Airtable does not offer a full database download. You can export CSVs table by table, which loses the links between them. For anything that matters, the real exit route is the API, and that is a build rather than a button.
No self-hosting. Airtable is closed and cloud-only. For organisations with data-residency requirements, that decides it before any other consideration.
The API is rate limited. Heavy integrations run into it, and teams usually discover the ceiling after they have built against the assumption that it is not there. Check the current limit against Airtable’s own API documentation before you design around it.
Cost is per editor. Viewers are free, which helps, but the bill tracks how many people need to change data. We wrote the full pricing breakdown separately.
Who owns Airtable now?
Airtable is operated by Formagrid, Inc., and in August 2026 Bending Spoons announced an acquisition of the company for $1.3 billion.
We are including that because clients ask us what happens to a platform they have built their operation on, and it is a fair question. An acquisition does not change what the product does today. It does mean the pricing and packaging you are agreeing to are set by a new owner, and anyone deciding this month should factor that in rather than discover it later.
Nothing in Airtable’s published plans has changed as a result at the time of writing.
Before you build
Not sure whether your operation belongs in Airtable at all?
Bring the process that is causing the most friction and a rough sense of how many records it involves. The first call is free, thirty minutes, and you will leave knowing whether this is the right tool for it even if we never work together.
Book the free first callWhen Airtable is the wrong answer
We say so on the first call in these situations.
Your work is calculation. Financial modelling, large formula ranges, scenario analysis. A spreadsheet is better and Airtable will frustrate you.
You have hard data-residency or self-hosting requirements. Airtable is cloud-only and closed. That is the end of the conversation rather than a workaround.
Your dataset is genuinely large. Hundreds of thousands of rows in a single table, or heavy queries across them, is past what a hosted no-code database is built for. At that point the per-seat cost and the ceiling both point the same way.
Everything else is a design question rather than a platform question. If you have already decided to look elsewhere, the Airtable alternatives are sorted by the reason people leave.
Frequently asked questions
Is Airtable a real database?
Yes. Airtable is a relational database: tables hold records, fields have enforced types, and records link across tables. What it hides is the query language, so you get relational structure without writing SQL.
Is Airtable free?
Airtable’s Free plan is free with no time limit, capped at 5 editors, 1,000 records per base, 1 GB of attachments per base and 100 automation runs a month. There is no free trial of the paid tiers.
Can Airtable replace my CRM?
Often, yes, for a small service business. Airtable can hold contacts, link them to deals and projects, and move records through stages. What it will not give you out of the box is the packaged reporting and email sequencing a dedicated CRM ships with. We worked through the whole trade in Airtable as a CRM.
Can I get my data out of Airtable?
Partly. You can export each table as a CSV, but there is no full database export, and CSVs lose the links between tables. Anything that needs a real migration path should use the API.
How is Airtable different from Notion?
Notion is a document tool with database features. Airtable is a database with document-like conveniences. If your work is mostly writing with some structure attached, Notion fits better. If your work is mostly structured records that other systems need to read, Airtable does.
The short version: Airtable is a relational database that anyone can use, and the grid you see first is the least important part of it. What decides whether it works for an operation is the structure underneath, and that is a design decision rather than a feature comparison.
If you want the cost side, we broke down what Airtable actually costs by team shape. For the comparison against a spreadsheet, Airtable versus Google Sheets covers when to move and what breaks. If you are deciding whether to build an operation on it at all, that question is where our Airtable consulting work usually starts.