Skip to main content
In direct mode the LaunchKit cloud speaks the E2B API straight to your plane. There is nothing for you to run; setup is an exchange of connection details.

​
Prerequisites

  • An E2B-compatible control plane reachable from the LaunchKit cloud over HTTPS.
  • The plane’s API URL or domain, and its API key.
  • If the plane sits behind an IP allowlist, contact LaunchKit for the current egress origins to permit.

​
What you hand your LaunchKit contact

​
How your key is protected

The API key is stored as an AWS KMS envelope (encrypted data key plus ciphertext), cryptographically bound to your workspace and this specific runtime record. It is entered through the console UI only, is never exported, and rotation is a re-entry: hand over the new key, the operator replaces it, and the probe re-runs.

​
The conformance probe

After the key is entered, LaunchKit runs a live probe against your plane: create a sandbox, execute a command, pause, kill, and check whether the plane supports template builds. The runtime flips to connected only when the probe passes, and re-validation can be run at any time.
With key validation disabled (the CubeSandbox case), the probe verifies reachability and API conformance rather than key authenticity, and records that scope honestly on the runtime. A connected status then means “the plane responds correctly”, not “the key was independently validated”.

​
Failure behavior

If your plane becomes unreachable or the key is rotated away, the next probe or task attempt marks the runtime error with the failure message, and tasks on this runtime fail loudly rather than migrating anywhere else.