Airtable acquisition by Bending Spoons: what changes in 2026

Airtable has indeed been acquired by Bending Spoons

Bending Spoons announced on August 4, 2026, a definitive agreement to acquire Airtable.

The transaction valued Airtable at $1.285 billion in enterprise value and remained subject to customary closing conditions at the time. It was officially finalized on September 4, 2026: Bending Spoons acquired all of Airtable's shares.

For users, however, the transaction amount is less interesting than the intentions of the new owner.

Bending Spoons has announced its intention to invest heavily in the Airtable product, customer support, and its go-to-market capabilities in order to drive further growth.

This is what is known today.

It does not yet allow us to determine precisely how the product, its pricing, or its strategy will evolve in the coming months.

What changes today for Airtable users?

In the short term, very little has been announced.

Airtable is changing ownership. This does not mean that existing bases, Interfaces, automations, or integrations need to be redesigned.

No new Airtable pricing has been announced with the acquisition

The finalization of the acquisition is not accompanied by any new pricing plans.

It would therefore be premature to present the acquisition as the announcement of an Airtable price hike.

For a company choosing its plan today, the criteria remain the same: billable users, permissions, usage limits, AI needs, external access, and operational constraints. Our guide on Airtable pricing and plans details these criteria and the actual cost to consider.

A future pricing evolution remains obviously possible, as with any SaaS. But an architectural decision must stem from a real change, not an hypothetical increase.

No major product changes have been announced

The same observation applies to Airtable itself.

Bending Spoons has not announced the removal of features, a change to the API, or a new direction specific enough to call an existing architecture into question.

The official statement points in the opposite direction for now: the group says it wants to continue investing in the product.

This intention will have to be judged based on the developments actually delivered in the coming months.

The significant change is the owner

Airtable is no longer an independent company.

For a team using a few simple bases, this change has few immediate consequences.

For an enterprise where Airtable runs critical clients, contracts, projects, budgets, or workflows, the subject deserves more attention.

Not because a problem appeared on September 4, but because the more central a tool is to operations, the more the decisions made by its publisher matter.

Why Bending Spoons' strategy is worth watching

Bending Spoons itself explains that it does not acquire products to resell them, but to operate them for the long term. The group also specifies that the transformations carried out after an acquisition are often deep.

This is useful information to understand the context.

It is not a prediction of what will happen to Airtable.

Observing the evolution of Evernote, Vimeo, or another portfolio company and then mechanically deducing Airtable's future would be too simplistic. Products, markets, and economic situations are not identical.

For an Airtable customer, three elements seem particularly useful to monitor:

• pricing: evolution of plans, billable users, credits, or included features;

• the product: development priorities, the role of AI, Interfaces, automations, and Enterprise capabilities;

• service: quality of support, enterprise assistance, and partner ecosystem.

As long as these elements do not change significantly, the acquisition remains more of a signal to monitor than a problem to solve.

Should you review your Airtable architecture after the acquisition?

Not solely because Bending Spoons has become the owner of Airtable.

The acquisition can, however, serve as a good reminder: when a SaaS becomes critical to operations, it is better to understand precisely what depends on it.

Start by measuring your actual dependency

An Airtable base used to manage an editorial calendar and a system linking:

clients → contracts → projects → deliverables → budgets → invoicing

do not have the same level of criticality.

In the second case, the important question is not simply:

"Are we using Airtable?"

but rather:

"What would stop working if we had to evolve or replace Airtable?"

The more the answer concerns critical business processes, the more the system deserves to be documented and mastered.

This does not mean you should avoid centralizing operations in Airtable. That is precisely what can create its value.

The risk appears mainly when no one really understands the architecture anymore.

Check that your data and workflows remain understandable

Preparing a second complete system "just in case" would generally be a poor use of time.

Instead, a company should be able to identify:

• truly critical data;

• main tables and relationships;

• important automations;

• external tools that depend on Airtable;

• business rules that are difficult to rebuild.

The number of tables or automations is not the best risk indicator.

A relatively large but structured base can be more maintainable than a small base filled with legacy scripts and workarounds that no one dares to modify.

Do not confuse acquisition risk with an existing Airtable limit

If your system already requires multiple technical layers solely to bypass a structural limit of Airtable, it is legitimate to reassess the architecture.

But the problem likely existed before the acquisition.

This is an important distinction.

A minor limit that can be managed easily does not necessarily justify changing tools.

Conversely, if the entire architecture starts to be built around the platform's limits rather than around the business process, Airtable may no longer be the right central block.

The criterion must remain the need, not the name of the owner.

In which cases should you actually consider leaving Airtable?

A change of shareholder is not enough.

Concrete developments would carry much more weight in a migration decision.

If one of these problems actually arises, our comparison of alternatives to Airtable helps to start back from the need to solve rather than choosing a replacement by reflex.

This comparison is essential.

Changing a central business tool is not just about getting a new subscription.

It generally requires rebuilding part of the data model, interfaces, automations, and integrations, migrating history, testing processes, and then supporting adoption.

Migrating today solely because Airtable's future might evolve would therefore mean creating a certain cost to avoid a still hypothetical risk.

Our recommendation: monitor Airtable, don't anticipate a problem that doesn't exist

At this stage, we see no factual reason to leave Airtable simply because Bending Spoons has become its owner.

On the other hand, the coming months will allow us to judge the new direction on concrete elements: pricing, product, support, and development strategy.

If these changes actually affect your processes, your costs, or your system's limits, it will then be relevant to reassess Airtable.

A healthy architecture does not require being independent of all the tools it uses.

It mostly requires knowing its dependencies, keeping the system maintainable, and being able to question a choice when facts change.

If your challenge is already to make an existing system more reliable or simple, our Airtable consulting focuses precisely on architecture, rebuilding existing bases, automations, and adoption — regardless of the acquisition.

Frequently asked questions about the Airtable acquisition