Internal Tools Versus Customer Apps
Ravi Parikh, CEO of Airplane, on building an end-to-end internal tools platform
The key strategic point is that internal tools win by being opinionated about control, not by being infinitely flexible. Airplane is optimized for employees working against production systems with known roles, low visual requirements, and predictable traffic. That is a very different problem from serving customers on the public internet, where design, scale, onboarding, and reliability expectations are far less constrained.
-
Internal tools usually look like the same basic pattern, a table, a form, a button, and permissions on top of a production database or API. That sameness is what makes products like Airplane and Retool fast. Customer apps break that pattern because they need more custom UI, branding, and edge case handling.
-
Airplane leans even further into the internal use case than Retool. It starts from scripts, workflows, auditability, and code ownership, so an engineer can turn a Python or JavaScript task into something ops or support can safely run. That is closer to an internal runbook system with UI than to Vercel's public app deployment layer.
-
The competitive boundary is less Airplane versus Vercel, and more Airplane versus building the tool in React from scratch. Vercel and Netlify are built around push button deployment, CDN delivery, serverless compute, and front end developer experience for public web apps, while internal tool builders are built around auth, access control, self hosting, and safe writes to company data.
Going forward, the internal tools stack is likely to get deeper rather than broader. As AI makes code cheaper to produce, platforms like Airplane can absorb more bespoke internal workflows that would otherwise become small SaaS purchases, while public app platforms continue optimizing for customer experience, traffic spikes, and internet scale.