Skip to main content
Learn bead machine concepts for Linux commands, files, and optional desktop access. The CLI, SDKs, MCP, and dashboard use the same account resources.

​
Lifecycle

Create a machine from a template, wait for readiness, and run work. The machine’s kind determines what happens when it is idle or its runtime ends. Persistent machines default to a 15-minute idle timeout. Paused machines incur retained storage charges. Read Machine lifetime for funding and expiry details.

​
Words

​
Choose a starting point

Use a temporary job for a bounded command, worktrees for local development, and fleets or swarms for parallel work. A memory snapshot or fork keeps the source CPU and memory bounds. To choose a different size, create a new machine from a disk template. See Machine sizes.

​
Pay for what you use

CPU uses measured busy time. Memory uses configured running memory. Storage uses unique retained bytes. Check workload estimates, balance, and effective limits before provisioning.