# I run every AI agent run in its own Firecracker microVM. Here's what I learned.

> Source: <https://dev.to/sandscale/i-run-every-ai-agent-run-in-its-own-firecracker-microvm-heres-what-i-learned-35ce>
> Published: 2026-11-22 07:40:22+00:00

**Recommendation:** Isolate agent-written code in per-run Firecracker microVMs with separate kernels, and add a dedicated egress-filtering layer since Firecracker does not restrict network access itself.
More in the playbook "Securing agents and AI tools": <https://wpnews.pro/playbooks/agent-security>

Coding agents kept running commands I hadn't read, on machines I cared about. So each run in Sandscale now gets its own Firecracker microVM with its own kernel, and nothing is shared with the run next to it.

If you're choosing between containers, gVisor and microVMs for code your agent wrote, I wrote up the tradeoffs here: [https://sandscale.dev/blog/isolating-ai-agent-code-containers-gvisor-firecracker](https://sandscale.dev/blog/isolating-ai-agent-code-containers-gvisor-firecracker). One thing worth knowing: Firecracker doesn't filter network egress by itself. Network policy is a separate layer.

Billing is per awake vCPU-hour. Paused time and idle time between tool calls don't count against it (storage above the allowance still bills). Free is $0, Pro is $25/month, Team is $48 per member per month.

It's early access. I'd like to hear where it breaks for you. Try it: [https://cloud.sandscale.dev/auth/signup](https://cloud.sandscale.dev/auth/signup)

I'm the founder of Sandscale, so take my bias into account.
