# use cases

More than just
AI agents.

Real Linux microVMs unlock workloads containers can't.

AI agents / computer-use farms

Run coding agents, browser agents, and tool-use loops at high fan-out. MicroVMs win because every agent gets a real kernel, stable files, and forkable state.

AI-native CI / previews

Create disposable PR environments with code, browser, and secrets scoped to one run. MicroVMs win because previews boot fast without sharing a container host trust boundary.

Online IDEs + playgrounds

Give users a full Linux workspace behind a browser editor. MicroVMs win because terminals, daemons, package managers, and volumes behave like a real dev box.

Browser automation at scale

Run Playwright, Chromium, screenshots, scraping, and account-safe flows. MicroVMs win because noisy browser processes cannot escape into neighbors.

Plugin / marketplace sandboxes

Execute third-party extensions, workflows, and user scripts. MicroVMs win because untrusted code gets a hard KVM boundary instead of best-effort namespace isolation.

Notebook-as-a-service

Serve Python and data notebooks with persistent datasets and resumable sessions. MicroVMs win because hibernation makes idle notebooks feel always-on without always billing compute.

Online judges + interviews

Compile and run submissions with strict timeouts and preview links for reviewers. MicroVMs win because each candidate gets a clean, repeatable machine.

Per-match game servers

Spin up short-lived authoritative servers for matches, sims, and tournaments. MicroVMs win because state is isolated, migratable, and cheap after hibernation.

Security / malware analysis

Detonate files, run scanners, and inspect suspicious scripts in disposable hosts. MicroVMs win because analysis happens behind hardware virtualization, not a shared container runtime.

Edge functions with state

Run stateful functions close to users with warm snapshots and durable volumes. MicroVMs win because functions can keep Linux state while still scaling down cleanly.