Overview
Airplane turned internal scripts into tools that colleagues could run through forms, permissions and approvals. Its team joined Airtable in early 2024, while customers were told the platform would stop on March 1. A useful product and a team acquisition produced different outcomes for the people using it.[1][5][6][7]
The case tests a specific dependency: keeping your scripts does not preserve the hosted system that schedules them, checks permissions and presents their interface. Airplane’s execution agent could run inside a customer’s network, but the complete product still depended on its cloud control plane.[1]
Founding Story
Ravi Parikh and Josh Ma founded Airplane in 2020. Parikh had co-founded Heap; Ma had been Benchling’s CTO. Parikh described Ma as a friend. Both had seen engineers interrupted by operational requests and tested the problem through conversations with other developers.[1][3]
In the 2022 PodRocket interview, Parikh described the architecture as “not a fully self hosted product, it's hybrid.” He also wanted pricing that would “allow small companies to use this tool forever.” These statements explain both the operating dependency and the intended customer relationship. The latter was an aspiration, rather than a continuity guarantee.[1]
Timeline
- 2020: The founders explored internal operations and formed Airplane.[1][3]
- 2022: Airplane added Views and announced a $32 million Series B led by Thrive Capital, with Benchmark participating. Reported total financing reached $40.5 million.[3][4]
- November 2022: A founder interview described task-first onboarding, targeted scheduling campaigns and approval flows.[2]
- 2023: Former engineer Benjamin Yolken later described slowing growth, leadership changes and subsequent enterprise wins.[5]
- January 2024: The acquisition and planned March 1 retirement became public.[5][6]
- June 2025: Airtable introduced Omni, its conversational app builder. This was a later Airtable product, without evidence that it preserved Airplane’s service.[8]
What They Built
An engineer supplied a script and its inputs. Airplane added a form, access rules, notifications and execution records. A support colleague could request a sensitive action, with another authorized person approving it. Local execution through an agent kept some processing inside the customer’s network; the hosted interface and coordination remained external dependencies.[1]
Task-first onboarding reduced the initial project. Engineers could start with one operation, then combine tasks into larger tools. Templates and approval invitations helped bring colleagues into the product. That sequence addressed two separate buying conditions: developer usefulness and organizational permission to access production systems.[2]
Views expanded beyond a single action into visual internal tools.[4] This increased what customers could build, while expanding the interface and workflow behavior they would need to replace if the service ended.
The contemporary discussion records customers’ concern about replacing operational workflows. These comments demonstrate migration friction for those speakers; they do not measure its incidence across all customers. The thread also contains conflicting financial speculation, which cannot substitute for company accounts.[6]
Market Position
Target Customers
Engineers built the tools; support and operations colleagues used them. Airplane marketed specific jobs, including scheduled scripts, before asking buyers to adopt an entire internal platform. The developer could demonstrate usefulness, but production access still required leadership and security approval.[2]
Market Size
The reachable opportunity depended on recurring operations, time saved and willingness to entrust a vendor with execution. No reliable company-wide retention series, final recurring revenue or serviceable-market calculation was established. Financing measured resources to build the company, rather than the amount customers would spend.
Competition
Parikh distinguished Airplane from interface builders and orchestration tools. That breadth created several comparison sets rather than one clear category.[1] Today, Windmill already offers scripts, workflows and approval controls with self-hosting. Its free and paid editions differ materially in identity and approval features.[9][10]
Airtable also continues selling app building and automation, including Omni. Its current plans include free access and a Team plan at $20 per editing user monthly with annual billing. These are alternatives to evaluate by workflow, rather than evidence of a direct Airplane replacement.[8][11]
Business Model
Airplane sold a hosted developer platform while encouraging individual engineers to start before a company-wide sale. A contemporary report described nearly 100 paying customers.[4] The founder interview described deliberate patience about early monetization to preserve access for small companies.[1] That strategy required adoption eventually to support a durable service; public evidence does not establish the complete economics.
Its reported financing provided room for product development. It does not establish the final cash balance, profitability or acquisition consideration. No exact investor-return calculation is justified.[3]
Outcome and evolution
Yolken’s firsthand account supplies a counterpoint to a simple cash-exhaustion story. He described slower growth, a founder departure, later enterprise wins and substantial remaining cash. He also reported being told leadership saw a difficult path to much higher revenue. These are an employee’s observations and recollections, without audited financial confirmation or a complete management response.[5]
His account supports an interpretation that leadership chose a team transaction over continuing the existing product. It does not establish the motives of every participant. A category-wide downturn or weak expansion economics could have contributed; neither is quantitatively isolated here.
Airtable’s surviving page identifies acquisition of the teams behind Airplane and Balsa. Customer-facing retirement followed on a different track. The exact legal transaction scope, purchase price, final dissolution and individual payouts remain unverified.[7][5]
As reviewed in October 2026, Airtable markets a continuing AI app platform. That shows the acquirer’s subsequent direction, without proving technical continuity from Airplane or restoring the discontinued service.[8]
Key Lessons
- An execution agent leaves a hosted dependency. Airplane’s hybrid design kept customer-side execution separate from the control plane needed to operate it.[1]
- Start adoption with a concrete job. Scheduling campaigns and a single task made the first use more specific than a general internal-platform pitch.[2]
- Separate cash evidence from speculation. The named employee’s remaining-cash account conflicts with an unverified exhaustion narrative; neither provides audited accounts.[5][6]
- A team sale can interrupt customer operations. The Airtable move ended the platform relationship, leaving existing workflows to migrate.[5][7]
Sources
- PodRocket / Ravi Parikh — Founder interview transcript
- Zachary DeWitt / Ravi Parikh — Developer adoption and security approval
- The SaaS CFO — Founder interview episode context
- TechCrunch — Airplane Series B and Views
- Benjamin Yolken — The end of Airplane.dev
- Hacker News — Airtable acquires Airplane
- Airtable — Teams behind Airplane and Balsa
- Airtable / Howie Liu — Omni launch
- Windmill — Current pricing and edition differences
- Windmill — Approval workflow documentation
- Airtable — Current pricing