<div id="readability-page-1" class="page"><div><p>Devin was the moment the industry realized agents could do real engineering work. As agents become part of everyday software development, they need the same infrastructure as the developers they work alongside: the same dependencies, tooling, and access to internal systems. For many organizations, that also means keeping execution inside their own cloud.</p>
<p>Devin Outposts lets you run Devin sessions inside infrastructure you control. By pairing Outposts with our Bring Your Own Cloud (BYOC) offering, each Devin session runs on an E2B microVM that you can configure with the CPU, RAM, and disk your workload needs. Devin can securely access private repositories, internal APIs, package registries, and other VPC-only services while execution remains entirely within your cloud boundary.</p>
<p>E2B also adds snapshot functionality to every Outposts session. If a Devin session needs to be paused, it can be resumed quickly without losing its filesystem, running processes, or other state. Because E2B's microVMs are built on Firecracker, snapshotting and restoring are built in, and Devin can pick up exactly where it left off almost instantly.</p>
<p><strong>Get started:</strong> <a href="https://docs.e2b.dev/agents/devin-outposts" target="_blank" rel="noopener noreferrer" data-external="true">E2B + Devin Guide</a></p>
<p>We're excited to see what developers build with Devin and E2B.</p></div></div>

E2B Blog & Customer Stories

Vaclav Mlejnsky

Devin Outposts lets you run Devin sessions inside infrastructure you control, with each session running on an E2B microVM that keeps execution entirely within your cloud boundary.

Use E2B as the Execution Layer For Devin Outposts

댓글