Do I need a card?
No. The trial is 5 agent-hours (300 minutes) of running time over
14 days, with up to 2 tasks at once, no limit per run and up to 10 new tasks an hour
(resuming a paused task doesn't count against that). Paused time is free. The control plane enforces those limits, and nothing charges you automatically.
Upgrading is your choice.
Do I need a model subscription?
You bring your own agent account. The Codex, Claude Code and Pi CLIs are preinstalled. Codex runs on the account you
connect once, with no further sign-in; Claude Code and Pi sign in once in each task and stay signed in
across pause and resume. Model usage is billed by your model provider, separately from MicroDev compute.
What survives a pause?
Your whole workspace, byte for byte: every branch, stash and commit, and staged, uncommitted, untracked
and ignored files. Codex, Claude Code and Pi sign-in, session history and settings, so a resumed agent
starts signed in and past onboarding. Installed packages, other home-directory files, shell history,
agent caches and logs, environment variables and running processes are not kept: resume boots a fresh
copy of the pinned system image and runs your dotfiles again.
See the exact contract.
On subscription plans the contract is backed by the pause guarantee: if a completed pause loses committed, uncommitted or untracked work in your workspace, that billing period’s subscription fee is credited against your next renewal (a month’s fee on monthly plans, the year’s on annual plans). How it works.
Will auto-stop kill my build?
No. A build or test run spends CPU, a download or streaming model call moves data, and typing in the terminal is activity; any of them keeps the task running.
Auto-stop needs 15 continuous minutes in which every minute stayed under
2% of one vCPU and moved 32 bytes a second of data or more for less than half of it (packet headers and
your SSH sessions excluded), with no typing and no transcript change. An attached terminal or Mac app nobody types into doesn't count. A tool that only sleeps or polls now and then, with no CPU, is paused like a
finished agent, with its workspace kept.
On the trial, tasks also pause when the trial’s running time is used up or its 14-day window ends.
How isolated is a task?
Each task runs in its own Firecracker microVM under the jailer: its own jail, cgroup, root and workspace
disks, PID and mount namespaces, and a host UID and network namespace that no other running task shares.
From inside the guest, even as root, other tasks’ VMs, the host’s own services, cloud instance metadata
and private network ranges are unreachable; only the Internet is. A task placed in a slot another task
left starts with none of its connections. Physical hosts are shared: there is no dedicated-host guarantee.
How is this different from Git worktrees?
A worktree is another checkout, but its processes, ports and installed dependencies still live on the
same machine. MicroDev gives each task a separate Linux microVM, its own workspace and its own compute
lifecycle. You can still use worktrees inside a task.
Can my team use it?
Yes. Create an organization, invite your team and buy seats. Seats pool across the organization:
each one adds tasks at once and included agent-hours. Plans are Pro $29, Team $59, Business $119 per seat per month;
Team adds usage by member and starts at 2 seats.
See plans and pricing.