Airplane is a platform for engineers to quickly build high-quality internal tools.
Tasks can represent long-running, multi-step operations using the workflow runtime, which enables you to write orchestration logic as code.
Tasks take in parameters, and produce outputs. While executing, tasks can prompt for additional inputs and display richly-formatted information. Tasks 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, Customer onboarding, Fraud alerting workflow, Deploy infrastructure.
Examples: Billing dashboard, Support inbox, Team inspector.
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. Certain common operations can be performed from tasks via Airplane's built-in 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 and views. 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.
The Studio is Airplane's development environment. It allows you to develop on the platform without having to deploy your code through a real-time preview of your tasks and views.
In this series of getting started guides, we'll walk through building with the major components of Airplane, including tasks and views.
First, let's build a relatively simple task using just SQL.