Running when you need it, asleep when you don’t.
Start and stop workspaces on a schedule, and let them sleep when nobody uses them. The disk stays; hours count only while they run.
Schedules and idle sleep
Start and stop workspaces on a schedule, and let them sleep when nobody uses them. The disk stays; hours count only while they run.
WorkspaceStateScheduleSleeps
acme-apiRunningalways onafter 30 min idle
data-jobsScheduledweekdays 08:00–20:00after 30 min idle
web-appAsleepnoneidle 2 h
- Disk
- Persistent; repo, caches and history stay
- Hours
- Count only while it runs
- Idle time
- You choose it, per workspace or by policy
- Audit
- Starts, stops and wakes recorded
How it works
What happens, in order.
01Schedule
Set when a workspace starts and stops, per workspace.
02Sleep
It sleeps after a set idle time, with its disk kept.
03Wake
It wakes exactly as you left it.
Which plans
Workspaces come with Pro and up.
See pricing →Give every agent
a box of its own
Start free with 100 vCPU-hours a month. Upgrade when your agents need more.
A Firecracker microVM for every runNo network by defaultPause and resume with state keptVault keeps secrets out of promptsSSO, roles and audit logBring your own cloudWorks over MCP and the CLI