Day 2 of how we built DevBox, our internal coding agent. This one is about where the agent actually runs. 🧵 The agent runs arbitrary code as root, so we needed real isolation. We also needed Docker + Compose for integration tests, our own network policy, and to run on our own Kubernetes, near our data. We looked at hosted sandbox providers like E2B, Daytona and Modal. For some, Docker support was still experimental. We also wanted strict path-based control over network egress and flexible credential injection that supports rotation. E2B was the closest fit but did not meet that last requirement. So we picked OpenSandbox, self-hosted on our EKS cluster. Each sandbox is a pod running inside a Kata Containers microVM. That VM is the security boundary. Inside it, the agent gets full access: no approval prompts, no nested sandboxing. We trust the box.

Every web era brought a new kind of user. Desktop. Mobile. Now agents. The companies that won each shift didn't block the new user. They learned to serve it first. Half your traffic is agents now. Which half of them are customers? This RudderStack Transformation will be handy to answer rudderstack.com/agent-detect…