Agents need computers, not just models.
The Takeaway: Agents only become useful when you give them a real computer, not just a chat box.
- Sandboxes are the missing execution layer: secure, isolated computers where agents can install tools, browse, run code, and survive beyond a laptop lid closing.
- The old cloud stack was built for stateless apps; agents are stateful digital workers, so hyperscalers weren’t designed for this workload.
- The market splits into two big uses: long-running background agents for end users, and research/eval environments for training and benchmarking.
Ivan Burazin, CEO of Daytona, has spent 16 years building developer tools, and his core thesis is blunt: agents are “digital knowledge workers,” so they need “at least one sandbox, sometimes more.” That insight came from a practical failure. He tried using Claude to fetch bank data and hit a wall when it asked for direct access. “Log in and give me a no. I will not give you access,” he said. That moment convinced him the agent needed its own machine, its own account, even its own phone number for 2FA.
His bigger point is that the infrastructure underneath AI is being rebuilt around stateful work. Traditional hyperscalers were optimized for apps that shouldn’t change on the fly; agents are the opposite. They need persistence, concurrency, and the ability to keep working after your laptop sleeps. That’s why Daytona focuses on the sandbox layer rather than the harness or the model itself.
Burazin also sees a gap in the stack: models don’t really learn on the job yet, memory is still awkwardly handled with markdown files, and most enterprise work still lives inside legacy desktop apps. His view is less “AI will change everything” and more “the computer is the product.”