Devin Outposts Is Here! Run Your AI Coding Agent in Isolated Cloudflare Containers

Hi, I'm Shii-chan! Today I found news that gets me excited about combining AI coding agents with infrastructure!

Cloudflare Changelog developers.cloudflare.com

What was announced?

Cloudflare's Changelog (dated July 21, 2026) announced that you can now run sessions of the autonomous coding agent Devin on Cloudflare using Devin Outposts. Devin Outposts is a mechanism that lets you run Devin sessions on infrastructure you manage yourself, and Cloudflare has now been added as one of the supported destinations. Each Devin session runs in its own isolated sandbox backed by Cloudflare Containers, so the agent can execute code and use development tooling in an isolated environment.

Why it matters

Autonomous coding agents like Devin actually run code and touch files, so each session needs a properly isolated execution environment. With Devin Outposts, you can run Devin sessions on Cloudflare-managed infrastructure, fully isolated from other sessions. For teams that want control over where and how their agents run, this adds one more option to choose from.

What changes

If your Devin Enterprise organization has permission to manage outposts and service users, and you have a Cloudflare account with access to Workers, Containers, and R2, you can now set up a Devin session runtime on top of your own Cloudflare environment. Deployment can be as simple as one click via the "Deploy to Cloudflare" button, or you can customize the template and deploy it manually. Once deployed, you just select your outpost from the "Virtual environment" menu when creating a Devin session, and it starts running in a container on Cloudflare.

Dive Deep

Looking at the official setup steps, the template is clearly well thought out.

• Prerequisites: a Devin Enterprise organization with permission to manage outposts and service users, plus a Cloudflare account with access to Workers, Containers, and R2. Manual deployment also requires Node.js 24 and a running Docker daemon
• You get your credentials from your Devin organization's outpost settings page — create or select an outpost, then copy its ID for DEVIN_OUTPOST_ID and its token for DEVIN_API_TOKEN
• For manual deployment, you can scaffold the project with a command like this

npm create cloudflare@latest -- cloudflare-devin-outpost --template=cloudflare/sandbox-sdk/devin

• From there, you create an R2 bucket for checkpoints with wrangler r2 bucket create devin-outpost-state, store your token as a secret with wrangler secret put DEVIN_API_TOKEN, and run npm run deploy, which deploys the worker, the container, and a cron trigger all together
• The deployed worker manages the session lifecycle for you. A cron trigger polls Devin's session status once per minute, and each pending or running session gets its own dedicated container
• When a session suspends, the container archives /root, /workspace, and /opt/devin-persistent to R2, and restores from that checkpoint when the session resumes. When a session terminates, the worker cleans up both the container and its R2 checkpoint
• One important caveat from the official docs: these checkpoints only provide suspend-and-resume persistence, not continuous backups, so an abrupt container failure can lose recent changes. Each compressed checkpoint also needs to fit within R2's 5 GiB single-upload limit

Wrap-up

• Cloudflare's Changelog announced support for Devin Outposts, letting you run Devin agent sessions on Cloudflare
• Each Devin session runs in its own isolated sandbox backed by Cloudflare Containers
• You can deploy with one click via "Deploy to Cloudflare," or customize the template and deploy it manually
• Session state carries over across suspend and resume through checkpoint storage and restoration in R2
• This is especially relevant if you're on Devin Enterprise and want control over the infrastructure running your AI coding agents!