Skip to main content
Sailbox.create() boots a fresh VM and lists it under an App. Apps group Sailboxes within your organization. The VM is ready to use as soon as it returns.
Save the Sailbox ID to connect again later. Disconnecting your client does not terminate the Sailbox.

Resource limits

You do not need to choose a size. By default, each Sailbox has:
64-vCPU Sailboxes are in public beta. If you are interested, reach out to us in the community Slack.
These are limits, not reserved resources. You pay for actual usage. Set resource limits on an image to reuse them across creates. To override those limits for one create, pass vcpu_count, memory_limit_gib, or disk_limit_gib in Python; vcpuCount, memoryLimitGib, or diskLimitGib in TypeScript; or --vcpus, --memory-limit-gib, or --disk-limit-gib in the CLI. See create options for supported ranges. Explicit limits round up to powers of two. CPU, memory, and disk limits are independent. You can also change limits later.

Common options

See create options for limits, defaults, and all supported arguments.

Use a custom image

The first create may wait for the image to build. Later creates reuse it. See Custom images for Dockerfiles and Compose projects.

Copy an existing Sailbox

Take a checkpoint and start a new Sailbox from it. The copy has its own disk and identity. See Snapshots and forks.

Clean up

Termination permanently deletes the Sailbox. Use sleep or pause when you want to keep it.