Skip to content
Docs

Devin

Devin Outposts lets Devin run sessions on your own infrastructure. With the Devin Outposts for Vercel integration, the control plane runs entirely on Vercel. No worker process needs to stay online, so you can start sessions from any device, including a phone.

You need a Devin account with Outposts enabled and administrator access, and a Vercel team on a Pro or Enterprise plan. The one-minute cron schedule and up-to-24-hour sandbox sessions are not available on Hobby.

A cron job invokes a function once per minute, which polls Devin's queue every three seconds for pending sessions. Each session maps to one sandbox:

  • One microVM per session: Each Devin session runs in its own named, persistent sandbox.
  • State restoration: A session resumes from the sandbox's newest snapshot; only the newest snapshot is kept after each stop.
  • Network restrictions: Devin allowlists become sandbox firewall rules.
  • Automatic extension: The integration extends the sandbox lifetime when less than 10 minutes remain.
  1. Click Deploy with Vercel and choose the destination Vercel team. The template comes from the devin-outpost-vercel repository.

  2. Add Devin Outposts for Vercel when the Deploy Button asks for the required integration.

  3. Sign in to Devin as an administrator, review the suggested outpost name, and click Connect. The browser never sees a Devin token or secret. The integration exchanges Devin's short-lived, single-use authorization code server-to-server and adds the encrypted runtime configuration to the new Vercel project.

  4. Let Vercel finish creating and deploying the project. Queue polling begins within one minute of the production deployment.

    Cron jobs run only on production deployments, so a preview deployment never polls the queue.

  5. In Devin, start a session and select the new Vercel outpost as its virtual environment.

Optional environment variables on the deployed project, with defaults:

VariableDefaultDescription
SANDBOX_RUNTIMEnode24Legacy Sandbox runtime
SANDBOX_VCPUS2vCPUs per sandbox
SANDBOX_TIMEOUT_MS1200000Initial session timeout (20 minutes), extended automatically
MAX_CONCURRENT5Maximum concurrent sessions
POLL_INTERVAL_MS3000Queue poll interval

SANDBOX_RUNTIME configures a legacy Sandbox runtime. New SDK v3 sandboxes default to the Ubuntu-based vercel/sandbox/universal:latest managed image.

For local development mode and the full variable reference, see the devin-outpost-vercel repository and the Devin Outposts on Vercel Sandbox guide.

Last updated August 19, 2026

Was this helpful?

supported.