Borealis Docs

Host pools and your own capacity

A host pool groups eligible compute capacity. Your organisation, permissions, and plan determine which pools you can use.

Choose a capacity model

These are placement models, not interchangeable security guarantees. Verify the available options in your account before designing around a particular pool type.

Place a sandbox

Use Placement in the creation form to choose eligible capacity. API clients can supply a placement.hostPoolId when creating a sandbox.

borealis host-pool list --json
borealis host list --pool POOL_ID --json

A pool can exist without enough healthy capacity for a request. Check host availability, resource allocation, and account limits when placement is delayed or rejected.

Enrol your own host

Client-managed capacity requires the relevant organisation permissions and entitlements. Create an enrollment session through the app’s host management flow and run its generated instructions on a supported host.

Treat the enrollment code and host credentials as secrets. Do not paste them into support tickets or commit generated configuration. The host uses the supported control connection; do not replace the enrollment flow with an arbitrary callback URL.

Your organisation is responsible for the host operating system, patching, network access, and local infrastructure. Only enrol machines whose operators you trust with the workloads they will run.

Maintain capacity

Use host health and heartbeat freshness to distinguish healthy capacity from stale information. Drain a host before planned maintenance so new work is not placed there, and inspect existing workloads before disabling, retiring, or removing it.

Do not assume draining performs live migration. Preserve required environment state and workspace files before moving work to replacement capacity.