Skip to main content
Airship launches one E2B sandbox per job in your team, with a team API key. Airship deletes the sandbox when the job completes; its timeout is the backstop.

Connect

1

Create a team API key

In the E2B dashboard, create an API key (e2b_...).
2

Connect it

In Airship’s dashboard, Cloud → E2B: paste the key. A self-hosted E2B takes its domain as well.

Configure

airship.yaml

Plan limits

E2B caps a sandbox’s timeout by plan: one hour on Hobby, 24 hours on Pro. Airship asks for the runner’s lifetime plus 15 minutes, so a Hobby team refuses every launch with a permanent error naming the limit. Use Pro, or shorten your runner lifetime.

What Airship creates

A sandbox with metadata airship-installation, airship-runner-id and airship-repository. Creation carries the runner’s ID as its idempotency key, so a retried launch returns the same sandbox. Airship uploads the boot script through the sandbox’s daemon and starts it as a tagged process. Auto-pause is off, so a timed-out sandbox is gone rather than paused.
Early access: tested against a model of E2B’s API on every build, not yet run against the live service.