Hybrid agent model for internal tools

Airplane is using hybrid deployment to remove the biggest blocker in internal tools, which is letting a third party sit in the middle of production systems with write access. In practice, the sensitive work runs inside the customer’s own cloud, so databases and private APIs do not need to be opened to the public internet, while Airplane still keeps the hosted control plane that ships product updates and avoids the upkeep of a fully self managed install.

• This matters because internal tools are usually not read only dashboards. Teams use them to refund orders, change account settings, run workflows, and trigger backend actions. That means the tool needs deep access to live systems, which makes security review and deployment model a buying decision, not a technical footnote.
  1 sacra 4 sacra 5 sacra
• The main alternative is full self hosting. Retool used on prem deployment as a key enterprise feature, especially for companies with medical or other sensitive data, while Appsmith pushed open source and self hosting as its core wedge. Airplane’s agent model sits between those two, keeping the risky data path local without making the customer run the whole product.
  1 sacra 2 sacra 3 sacra 4 sacra
• The broader pattern in this market is that the real competitor is often building the tool in React or scripts in house. Hybrid deployment helps Airplane win those teams by preserving the speed of SaaS for builders, while giving security teams a concrete answer for where code runs and where data is processed.
  1 sacra 2 sacra 4 sacra

Going forward, deployment architecture will keep separating winners in internal tools. The products that grow fastest will be the ones that let ops and engineering teams act on production data quickly, while giving security teams a simple boundary they can approve. Hybrid models are a strong path to that balance, especially in regulated and larger enterprises.