Ask HN: The new wave of AI agent sandboxes?

10 points - last Thursday at 7:51 PM


In the last couple of months, several new solutions for sandboxing AI agents have launched (microVMs, WASM runtimes, browser isolation, hardened tool containers, etc.). Curious to hear from people using them in production. Are they working as advertised, or are there still major tradeoffs around security, cost, and performance?

Here's my list of sandboxing solutions launched in the last year alone: E2B, AIO Sandbox, Sandboxer, AgentSphere, Yolobox, Exe.dev, yolo-cage, SkillFS, ERA Jazzberry Computer, Vibekit, Daytona, Modal, Cognitora, YepCode, Run Compute, CLI Fence, Landrun, Sprites, pctx-sandbox, pctx Sandbox, Agent SDK, Lima-devbox, OpenServ, Browser Agent Playground, Flintlock Agent, Quickstart, Bouvet Sandbox, Arrakis, Cellmate (ceLLMate), AgentFence, Tasker, DenoSandbox, Capsule (WASM-based), Volant, Nono, NetFence

Comments

QubridAI yesterday at 9:36 AM
They work, but with tradeoffs. MicroVMs are secure but slower & costly. WASM is fast & cheap but limited. Ultimately, to date, there isn't a perfect solution. A majority of people employ a hybrid solution.
agcat last Thursday at 10:40 PM
I know there are too many of them, found this benchmarks that my partner did - https://github.com/nickaggarwal/sandbox-test/blob/main/FULL_.... He is planning to add a few more of them.
ex-aws-dude yesterday at 12:14 AM
A tool so good that it requires 37 different sandboxes
cochinescu yesterday at 10:30 PM
[dead]
aimarketintel yesterday at 11:16 PM
[dead]
olivercoleai yesterday at 2:03 PM
[dead]