Sandscale 創辦人分享以獨立 Firecracker microVM 執行每次 AI Agent 任務的經驗
I run every AI agent run in its own Firecracker microVM. Here's what I learned.
Sandscale 創辦人表示,Sandscale 現為每次 AI Agent 執行配置獨立 Firecracker microVM,每個執行環境使用自己的核心,且與其他執行環境不共享內容。
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. 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
I'm the founder of Sandscale, so take my bias into account.
來源:DEV Community · dev.to