Borealis Docs

Usage, limits, and billing

Check both available credit and technical limits when planning sandbox capacity.

Allocation and activity differ

A running sandbox reserves CPU and memory according to its resource profile. Compute accounting follows allocated resources while the sandbox is running, rather than only the CPU cycles your process happens to consume.

Stopping a sandbox ends its running compute use; it does not necessarily remove stored artifacts or other billable resources. Review the current account terms and usage details for storage and other charges.

Use smaller profiles for lightweight work and stop environments you no longer need. Do not use an idle timeout as the only control for critical cost limits.

Check your account

Review the billing summary, usage, and available limits in the app. The CLI exposes read commands:

borealis billing summary --json
borealis billing usage summary --json

Access depends on billing-read permission. Account changes, checkout, and automatic top-up configuration require additional rights.

Understand admission limits

Credit and technical entitlements are separate checks. A funded account can still be limited by allowed resources, available host capacity, concurrency, or eligible pool types.

If creation is rejected, inspect the returned reason. Adding credit does not fix an incompatible image, an unhealthy host, or a missing permission.

Review before changing plans

Use the live billing interface for current prices, included resources, and available plans. This guide intentionally does not repeat prices that may change.

Confirm the account and organisation before changing a plan or enabling automatic charges. Preserve the billing event or request identifier if a transaction’s result is uncertain, and inspect its state before retrying.