Airplane: an acquisition stranded internal-tool workflows
Airplane joined Airtable and closed its platform. A former employee’s account and contemporary customer comments show why a good tool still needs an exit plan.
- Product
- Airplane
- Founder
- Airplane founding team
- Launched
- n/a
- Model
- Former hosted internal-tool platform
Published · 2 min read · 2 sources
- #shutdown
- #acquisition
- #internal-tools
- #vendor-risk
Key takeaways
- Airplane’s acquisition and platform sunset were announced in January 2024, with a March shutdown deadline.
- A former engineer described slowing growth, a leadership transition and a deal that did not preserve the product.
- The employee account is one perspective; we do not treat public speculation about burn or valuation as fact.
What it is
Airplane was a developer-oriented internal-tool platform for operational interfaces and automated workloads. Former engineer Benjamin Yolken described using it to build customer workflows before Airtable acquired the company and the product closed (Former employee’s account).
Timeline
- March 2022: Yolken joined Airplane, according to his retrospective (Employee account).
- Summer–fall 2023: he described slowing revenue growth, departures and a founder leadership change, followed by new hires and enterprise deals. These are his recollections, not audited company disclosures (Employee account).
- 3 January 2024: the acquisition and shutdown became public. Contemporary HN discussion reproduced a notice setting March 1 as the platform sunset (Contemporary discussion).
- 3 March 2024: Yolken published his account of the deal and the March 1 shutoff, emphasizing customers’ migration burden (Employee account).
Why it worked
Airplane won genuine workflow adoption, not just attention. In the contemporary discussion, users described customer-support use and plans for more critical internal systems. Those are individual user accounts, not evidence of market-wide adoption (HN discussion).
That product utility did not ensure continuity. Yolken characterized the deal as an acqui-hire and said it did not preserve the product. His interpretation should not be confused with a disclosed acquisition contract (Employee account).
What to learn
- Review exportability and replacement effort before moving a critical workflow to a young hosted platform.
- Separate a product’s usefulness from the company’s incentives to keep operating it.
- Treat an acquisition as a fresh vendor-risk review, not automatic reassurance. Compare Skiff and RethinkDB’s community transition.
Risks and what didn't work
- Customers had to replace workflows on a short timetable. Public discussion documents frustration, while Yolken describes the migration work as substantial (HN discussion, Employee account).
- We deliberately omit public guesses about headcount, ARR and cash burn: the discussion contains conflicting claims and corrections (HN discussion).
- Yolken says the company had cash and did not run out of money. That is an attributed employee account, not independently verified financial evidence or proof of the founders’ motives (Employee account).
FAQ
Short answers drawn from the sections above.
What is Airplane?
Airplane was a developer-oriented internal-tool platform for operational interfaces and automated workloads. Former engineer Benjamin Yolken described using it to build customer workflows before Airtable acquired the company and the product closed (Former employee’s account).
Why did Airplane work?
Airplane won genuine workflow adoption, not just attention. In the contemporary discussion, users described customer-support use and plans for more critical internal systems. Those are individual user accounts, not evidence of market-wide adoption (HN discussion).
That product utility did not ensure continuity. Yolken characterized the deal as an acqui-hire and said it did not preserve the product. His interpretation should not be confused with a disclosed acquisition contract (Employee account).
What can indie builders learn from Airplane?
- Review exportability and replacement effort before moving a critical workflow to a young hosted platform.
- Separate a product’s usefulness from the company’s incentives to keep operating it.
- Treat an acquisition as a fresh vendor-risk review, not automatic reassurance. Compare Skiff and RethinkDB’s community transition.
What didn't work for Airplane, and what are the risks?
- Customers had to replace workflows on a short timetable. Public discussion documents frustration, while Yolken describes the migration work as substantial (HN discussion, Employee account).
- We deliberately omit public guesses about headcount, ARR and cash burn: the discussion contains conflicting claims and corrections (HN discussion).
- Yolken says the company had cash and did not run out of money. That is an attributed employee account, not independently verified financial evidence or proof of the founders’ motives (Employee account).
Sources
Every link cited above, in order of first use.
- 1.Former employee’s account (yolken.net)
- 2.Contemporary discussion (news.ycombinator.com)
Related case studies
More in Developer tools →Glitch: 1.8 million developers, a Fastly acquisition, and the end of app hosting
Glitch made it easy to build and remix small web apps in the browser. It raised $30M, shrank, sold to Fastly in 2022, and shut down project hosting in July 2025 as newer platforms caught up.
Skiff: a Notion acquisition still meant a product shutdown
Skiff’s encrypted workspace joined Notion, but its mail and collaboration services closed. Acquisition and customer continuity are different outcomes.
RethinkDB: the company closed, the open-source project survived
RethinkDB shut its company after failing to build a sustainable business. A later rights transfer kept the database alive under community stewardship.