I have built on Airtable, Make and Noloco for years, and I have also moved a large operation off that stack onto Supabase, Vercel and Next.js. So I have been getting the same message from several directions this month: "Should we leave Airtable?" My honest answer is that it depends on your renewal, your limits and your spend, not on the headlines. Let me walk through it calmly.
What happened
Bending Spoons, the Italian company behind a portfolio of acquired consumer apps, agreed to buy Airtable. The deal was reported on 4 August 2026 at roughly $1.285 billion in enterprise value, according to Dealroom and TechCrunch coverage summarised by Baserow. One source puts the equity value nearer $2.25 billion. The acquisition is reported to have closed on 4 September 2026.
In mid October 2026, the San Francisco Chronicle reported that Bending Spoons laid off a large portion of Airtable's roughly 800 staff. Airtable's own statement, as quoted in that coverage, is that customers' plans, prices and service offerings will not change.
That is the full extent of the hard facts. No pricing change, packaging change or roadmap change has been announced. Everything beyond this paragraph is history, inference or opinion, and I will label it as such.
Why people are nervous
Three things are driving the anxiety, and only one of them is about Bending Spoons.
The acquirer's pattern
Bending Spoons has a track record of buying established products and changing how they are monetised. The example people bring up most is Meetup. Reddit reactions collected by Baserow include an organiser saying that after Bending Spoons acquired Meetup, subscription prices went up sharply while little useful was added, and Softr's write-up quotes organisers saying their costs more than doubled. Whether that pattern repeats at Airtable is unknown. Airtable is a very different business from a consumer events app, with enterprise contracts and a sales team, and the company has explicitly said plans and prices will not change. But the precedent is why the default assumption in the community is "paywalls and price rises", and it is a reasonable assumption to plan around without treating it as fact.
Airtable's own August 2023 repackaging
The deeper reason for the nervousness is that Airtable has already done this once, before any acquisition. In August 2023 it merged the Plus and Pro plans into a new Team plan, cut API calls from unlimited to 100,000 per workspace per month, halved automation runs from 50,000 to 25,000, and removed multi-source sync. Business became the only path for heavier users. Since then the list prices have climbed further: PricingSaaS and Noloco track Team going from $12 to $20 per user per month and Business from $24 to $45, on annual billing. From October 2025 Airtable also stopped prorating refunds when you remove seats mid cycle.
The community reaction at the time still reads as raw. One consultant on the Airtable forum wrote that having just sold clients on Pro, the jump "makes me look like a fool or a liar". Another observed that Airtable "can now retroactively change pricing of the tool that you use as the foundation" of a business. That memory, not the acquisition itself, is what makes people flinch.
Competitors are already selling the exit
Softr published a post within a day of the announcement that frames price increases as "being treated as a given" and says "people mid-project feel exposed", then offers a free migration consultation into Softr Databases. Baserow, Retable and others have similar pieces. Read these as what they are: marketing by companies that benefit from Airtable churn. They are still a useful signal. When every competitor assumes a price rise, the market has priced one in, and your negotiating position at renewal is stronger than it was in July.
What I would actually do before my next renewal
Panic migrations are a bad idea. I have seen teams start rebuilding a working system on the day of a headline and regret it six months later. The advice circulating from nocode.mba and XRAY is sensible: inventory, back up, and use your renewal date as leverage. Here is my version.
- Check your renewal date and term. If you are on annual billing, note when it ends and whether it auto renews. Monthly billing costs more per seat ($24 versus $20 on Team) but keeps your options open. Remember that mid cycle seat removals are no longer prorated, so adding seats "just for a month" is not as cheap as it used to be.
- Export a full backup now, and understand why CSV alone is not enough. A CSV export flattens everything to text, so field types, select options and linked record relationships are lost. Attachment URLs in Airtable expire, so files have to be downloaded separately. Record IDs change when you duplicate a base, which breaks any links you have sent to customers. Use the API or a sync tool to pull schema, records, linked record IDs and attachments together.
- Document your automations and Make scenarios. Airtable automations do not export. List every automation, its trigger, and what it writes. Do the same for every Make scenario that touches a base. This is the part that always takes longer than the data.
- Measure how close you are to the caps. On Team that is 50,000 records per base, 100,000 API calls per workspace per month and 25,000 automation runs per month. Automations pause when the cap is hit. If Make is polling your bases, check how many of those API calls it is consuming.
- Estimate your fully loaded monthly spend. Airtable seats, plus Make, plus any portal layer like Noloco or Softr, plus the hours someone spends working around limits. The seat count is the usual surprise: anyone who edits a record is a paid seat.
- Decide your trigger conditions in advance. Write down, before any announcement, what would make you move: a price rise above a certain percentage, loss of a feature you rely on such as the API tier or sync, or a support response time you cannot live with. Deciding this now means a future announcement gets a plan rather than a panic.
Stay, hedge or move
Stay
Staying is a valid option, and for most small teams it is the right one. Kreante's criteria for staying are fewer than 20,000 records with low growth, a main use of internal reporting or ops workflows, nobody on the team comfortable with SQL, and non technical staff who need to change fields without a developer. Noloco's rule is similar: fewer than two warning signs and internal use only means stay. If that is you, renew on the shortest term you can tolerate and keep the backup fresh.
Hedge
This is the option I think is underused. Move the data to Postgres on Supabase using a sync tool such as Whalesync, which handles linked records as foreign keys, and keep Airtable as the interface your team already knows. The Airtable community has recommended this "Postgres as source of truth, Airtable synced as a view" pattern for years as an interim step. The point is that if a future price rise or feature cut pushes you out, the move becomes a UI change rather than a data migration, which is the hard and risky part. It suits teams that are approaching the caps, have customer facing links or portals built on Airtable, or simply want leverage at the next negotiation.
Move
Moving makes sense when you are already over the limits, when you have compliance needs that Airtable gates behind Enterprise Scale, when performance is visibly degrading, or when the fully loaded spend is over roughly $1,000 per month and still growing. Agencies I respect use lower thresholds, around 400 to 500 euros a month on Airtable or bases over 50,000 rows. At that point a Supabase and Next.js stack is usually cheaper to run and faster, and the acquisition is just the nudge to do what the numbers already said.
My honest take
I do not think anyone should migrate because of this acquisition alone, and I say that as someone who sells migrations. Airtable is still a good product, the company has said prices will not change, and the people who bought it have every incentive to keep large customers happy. What I do think is that the 2023 repackaging already showed how quickly the economics of a base can shift, and the acquisition has removed the benefit of the doubt. Back up properly, know your numbers, write down your triggers, and let the renewal date, not the news cycle, decide your timing.