{"slug": "i-run-every-ai-agent-run-in-its-own-firecracker-microvm-here-s-what-i-learned", "title": "I run every AI agent run in its own Firecracker microVM. Here's what I learned.", "summary": "Sandscale, founded by a developer who found coding agents running unread commands on machines they cared about, now runs every AI agent execution in its own Firecracker microVM with a dedicated kernel and no shared state between runs. The founder notes that Firecracker does not filter network egress on its own, so network policy is handled as a separate layer, and billing is per awake vCPU-hour with paused and idle time between tool calls excluded. The service is in early access, priced at $0 for Free, $25/month for Pro and $48 per member per month for Team.", "body_md": "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.\n\nIf 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.\n\nBilling 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.\n\nIt'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)\n\nI'm the founder of Sandscale, so take my bias into account.", "url": "https://wpnews.pro/news/i-run-every-ai-agent-run-in-its-own-firecracker-microvm-here-s-what-i-learned", "canonical_source": "https://dev.to/sandscale/i-run-every-ai-agent-run-in-its-own-firecracker-microvm-heres-what-i-learned-35ce", "published_at": "2026-11-22 07:40:22+00:00", "updated_at": "2026-11-22 07:42:37.976530+00:00", "lang": "en", "topics": ["ai-agents", "ai-safety", "ai-infrastructure", "developer-tools"], "entities": ["Sandscale", "Firecracker", "gVisor"], "also_reported_by": [], "takeaway": "Running each AI agent execution in its own Firecracker microVM with a separate kernel isolates agent-written code, but egress filtering must be added as a distinct network policy layer since Firecracker does not provide it.", "recommendation": {"advice": "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.", "playbook": "agent-security", "playbook_url": "https://wpnews.pro/playbooks/agent-security"}, "alternates": {"html": "https://wpnews.pro/news/i-run-every-ai-agent-run-in-its-own-firecracker-microvm-here-s-what-i-learned", "markdown": "https://wpnews.pro/news/i-run-every-ai-agent-run-in-its-own-firecracker-microvm-here-s-what-i-learned.md", "text": "https://wpnews.pro/news/i-run-every-ai-agent-run-in-its-own-firecracker-microvm-here-s-what-i-learned.txt", "jsonld": "https://wpnews.pro/news/i-run-every-ai-agent-run-in-its-own-firecracker-microvm-here-s-what-i-learned.jsonld"}}