Devin sessions can now run on Daytona sandboxes. Each session gets its own Linux or Windows environment, created on demand from a snapshot you define, stopped while the session sleeps, and deleted when the session ends.
Devin normally does its work on machines Cognition hosts: tool calls such as web searches and code execution, for example. Outposts splits that arrangement; the agent loop still stays with Cognition, but the machine used to execute Devin's tool calls runs wherever you put it. That matters when code can't leave your boundary, or when a session needs to reach internal services that a hosted machine can't.
This integration puts those machines on Daytona. We built a reference implementation that handles the whole lifecycle, along with a guide that walks through it.
How it works
Start a Devin session and select one of your registered outposts (see the Devin Outposts docs for more details).
You run a small orchestrator, on a machine you control, that watches the queue for your outpost. When someone starts a Devin session there, from the Devin UI or Slack, the orchestrator claims it, creates a sandbox from your snapshot, and launches Devin's remote inside. From then on Devin works in the sandbox like it would on any other machine.
Sandbox lifecycle
Every session gets its own sandbox. When a session goes to sleep, the orchestrator stops the sandbox. The filesystem stays intact, and you stop paying for compute while Devin waits. When the session wakes, the same sandbox starts back up with everything where Devin left it. The orchestrator deletes a sandbox only when its session terminates.
Linux and Windows
Outposts are per-platform, and the integration covers both. Linux sandboxes boot from a snapshot built on Daytona's standard image. The Windows builder included in the reference implementation installs pinned versions of Git, Chrome, and the Devin CLI, then verifies each on a fresh sandbox before calling the snapshot ready. Any additional toolchains or dependencies can be baked into the snapshot if needed, or you can have the orchestrator clone repositories in before the remote starts.
One command to connect
Our integration includes a command that launches Devin's connection page, allowing you to set the required Devin credentials in your project's .env in one click. After that you build a snapshot, start the orchestrator, and create sessions on the pool.
Get started
Outposts requires Devin Enterprise. Read the Devin Outposts on Daytona guide for the full setup, and Cognition's Outposts documentation for the official feature documentation.
