Atlas: Preview Environments

Atlas Preview Environments

The core use case for Atlas is ephemeral environments backed by provider sandboxes and, for Firecracker, microVMs.

Recommended Flow

  1. Create or reuse a runtime profile that encodes provider, offering, and bootstrap defaults.
  2. Create a sandbox through the public API.
  3. Poll sandbox state until it reaches ready.
  4. Start or stop the sandbox as needed.
  5. Delete the sandbox when the branch, PR, or review session is finished.

Relevant Endpoints

  • GET /v1/runtime-profiles
  • POST /v1/runtime-profiles/{runtimeProfileId}/sandboxes
  • POST /v1/sandboxes
  • GET /v1/sandboxes
  • GET /v1/sandboxes/{sandboxId}
  • POST /v1/sandboxes/{sandboxId}/start
  • POST /v1/sandboxes/{sandboxId}/stop
  • DELETE /v1/sandboxes/{sandboxId}

Operational Advice

  • make sandbox names deterministic from branch or PR identifiers
  • prefer runtime profiles over raw provider-specific payloads
  • use provider capacity endpoints before high-volume batch creates
  • treat the public API as the source of truth; do not orchestrate directly against internal Firecracker services