Airplane is a platform for engineers to quickly build high-quality internal tools.
Tasks take in parameters, produce outputs, and support granular permissions for who can execute, request, or even view. Tasks can run on Airplane-hosted infrastructure or self-hosted infrastructure.
Examples: Issue stripe refund, Provision new account, List teams over limits.
Examples: Billing dashboard, Support inbox, Team inspector.
Runbooks are long-running, potentially manual, multi-step workflows comprised of blocks. Runbook blocks can call existing tasks, make use of built-in integrations to run e.g. SQL queries directly, and prompt for user input (via form blocks).
Examples: GDPR deletion process, Fraud alerting workflow, Semi-manual customer onboarding
Resources are Airplane's main way of configuring integrations with existing systems like databases and APIs. Creating a resource configures how to e.g. connect to a database, and users can use resources by attaching them to tasks.
Airplane supports standard, best-practices around role-based access control. Users can belong to groups, and both users/groups can be assigned permissions to tasks, views, and runbooks. We recommend you grant permissions to groups rather than users, so that as new users join your team you simply have to add them to a group to grant permissions.
In this series of getting started guides, we'll walk through building with the major components of Airplane, including tasks and views.
An example Airplane view
First, let's build a relatively simple task using just SQL.