Machines
A Clundra machine is a real, isolated Linux environment with root access — not a constrained runtime. This page covers how to size, run, and tear down machines.
$CLUNDRA_API as a placeholder for your Clundra API host.Sizes and resources
You pick a tier when you create a machine — that fixes its vCPU, memory, and disk. Resources are predictable: a machine gets exactly the tier you chose, with no surprise throttling. The dashboard's Deploy machine screen shows the current tiers and their resources and price; select one and create.
Over the API, the tier is the tier field on create:
curl -X POST $CLUNDRA_API/machines \
-H "X-API-Key: gopt_live_..." \
-H "Content-Type: application/json" \
-d '{ "tier": "small" }'Lifecycle
Creation is synchronous. The create call doesn't hand you a “provisioning” placeholder to poll — it waits for the machine and returns it already running, with an IP attached. Machines are ready in seconds.
List your machines, or fetch one by id:
# List
curl $CLUNDRA_API/machines \
-H "X-API-Key: gopt_live_..."
# Get one
curl $CLUNDRA_API/machines/$ID \
-H "X-API-Key: gopt_live_..."Run commands inside a machine with the exec console in the dashboard, or POST /machines/:id/exec — see the Quickstart.
Persistence
A machine keeps its state — its filesystem and everything you installed or wrote — for as long as the machine exists. That state is also what checkpoints capture: a checkpoint is a restore point you can return to at any time, so “persistence” on Clundra means both the machine remembers and you can rewind it to an earlier state. See Checkpoints & Rewind.
Deletion
Delete a machine from the dashboard, or over the API. Deletion tears down the machine and its resources.
curl -X DELETE $CLUNDRA_API/machines/$ID \
-H "X-API-Key: gopt_live_..."Where machines run
Machines run on EU infrastructure — hosted in Falkenstein, Germany. Every machine is isolated in its own microVM with its own kernel, memory, and filesystem.
Need help? support@gopilot.dev