Airplane Overview

What is Airplane?

Airplane is a platform for engineers to quickly build internal tools that power recurring workflows within their organization.

The Airplane platform has 4 main components:

  1. Tasks: A task takes in inputs, executes logic, and displays outputs. A task represents a single business operation (e.g. "delete a user's account" or "restart a microservice").

  2. Triggers: Airplane tasks can be triggered manually through the Airplane UI, via a Slack command, on a regular cron-like schedule, and more.

  3. Orchestration: Airplane tasks are executed through a gateway that ensures safety, accessibility, and flexibility. Airplane provides authentication, role-based access controls, approval flows, audit logs, input validation, resource limits, and more.

  4. Sessions (in beta): Airplane provides an interactive console where users can run tasks, leave notes, and perform ad-hoc work. Users can share Sessions of work with their teammates and create templates out of complex multi-stage operational workflows (e.g. "customer onboarding workflow").

This model may be familiar to people who have used Zapier, IFTTT, or similar services. However, Airplane is a developer platform built to handle a business's most bespoke workflows rather than just third-party tools. As a result, Tasks in Airplane are created in code and live in your git repository.

We provide SDKs and developer tools to make the process of creating Airplane Tasks incredibly simple. To get started with Airplane and create your first task, check out the Quickstart.

Why we built Airplane

Every business has internal workflows that their support, operations, engineering, customer success, sales, and other teams need to do on a recurring basis. Off-the-shelf software can cover some of these, but there are always tons of bespoke tasks that require engineers to build internal tools.

Internal tools are hard to build–just as hard to build as any other type of software–and often the needs of the business far outpace the development of internal tools. As a result, support, ops, and other teams are reliant on asking engineers to intervene constantly on a one-off basis (e.g. "Can you run this script or SQL query for me?").

Airplane solves this dilemma by letting engineers rapidly build internal tools by writing simple scripts. Engineers using Airplane can focus on the back-end business logic, and Airplane takes care of all the boilerplate.

What can I do with Airplane?

Any business process can be modeled in Airplane. The types of operations where engineers would typically run scripts or SQL queries on behalf of others are prime candidates for Airplane. A few examples:

  • Approving new customers into an invite-only beta

  • GDPR and other data deletion requests

  • Multi-step customer onboarding flows that touch the prod DB, third-party tools, and require manual inputs from the customer onboarding specialist

  • User account deletion

  • User email address changes

  • Restarting a microservice

  • Import data from a customer's CRM and other systems

  • Issue a refund for a customer's most recent payment