Skip to main content

Overview

Sandboxes are ephemeral compute environments with configurable lifetimes. This guide covers creating, listing, updating, and terminating sandboxes.

Default timeout

  • Sandboxes auto-stop after 10 minutes by default.
  • You can extend this when creating or via setTimeout().
  • See Pricing for plan limits and max lifetimes.

Creating sandboxes

Extending timeout

Update the timeout on an existing sandbox:
The response includes the updated stopAt timestamp:

Rehydrating by ID

Save the sandbox ID and recreate a handle later:

Listing sandboxes

Get all sandboxes in your organization:

Refreshing state

Fetch the latest sandbox data from the server:

Terminating sandboxes

Clean up when done:

Sandbox data

Each sandbox handle exposes:

Best practices

  • Save IDs: Persist sandbox IDs to kill them later without maintaining handles.
  • Extend timeouts proactively: Don’t wait until the last second; extend before critical work.
  • Clean up: Always kill sandboxes when done to avoid unnecessary charges.
  • Check stopAt: Monitor stopAt to know when auto-termination will occur.