Skip to main content
Sailboxes charge for actual usage, not reserved capacity. A Sailbox using 0.01 vCPU pays for 0.01 vCPU, even if it can use 8 vCPUs.

Rates

The $0.01 creation charge applies once per new Sailbox on the Free plan, regardless of vCPU count, including copies created from checkpoints. Pro and Enterprise waive this charge.

When charges apply

  • CPU, memory, and disk: billed while the Sailbox is running. Sleeping, paused, checkpointing, and cold-starting time is not billed.
  • Volume storage: billed for each hour the volume exists, including when attached Sailboxes are asleep, until the volume is deleted.
Running usage is sampled every second and reported in roughly one-minute batches. Usage is not rounded up to whole minutes. Each Sailbox created from a checkpoint is billed for its own usage.

How memory is measured

Billed memory includes application memory, guest kernel memory, and the Linux filesystem cache inside the Sailbox. It measures physical RAM held by the Sailbox, capped at its memory limit. Sail’s separate disk cache is excluded. Linux keeps file data in memory after reading or writing it, for as long as memory is free. Sail gradually releases the part of that cache a running Sailbox has stopped reading, so files read once do not stay billed. Released data is not lost. Reading it again reads it from disk.

Optional limits

  • CPU: 1–64 vCPUs per Sailbox.
  • Memory: 16–256 GiB per Sailbox. Requests above 256 GiB are rejected.
  • Disk: 8–1024 GiB per Sailbox.
  • Limits round up to the next power of two.
  • Existing Sailboxes and saved checkpoints keep their configured limits. Leaving memory out of set_limits preserves it, including an older limit above 256 GiB.
Limits cap what a workload can use. Configured CPUs count toward your organization’s reserved-vCPU allowance while the Sailbox is active. Raising a limit does not add a running charge, and lowering one only reduces costs if it reduces usage. A running Sailbox can still use memory and disk while its application is idle. Set CPU, memory, and disk limits on an image, override them when creating a Sailbox, or change them with set_limits. Changing limits does not repeat the creation charge.

Where to see usage

  • Dashboard: view spend by app and Sailbox at app.sailresearch.com. Spend appears within a few minutes. The Billing page shows your balance and invoices.
  • CLI: sail box list shows current CPU, memory, and disk usage. sail box top shows live utilization.

When credits run out

Sail pauses running and sleeping Sailboxes and blocks operations that would add spend, including creates, resumes, and commands. It does not terminate them. Add credits on the Billing page, then resume the Sailboxes you need.