Skip to main content
Most Devin work follows the normal software delivery path: Devin works in your repository, opens a pull request, and your team reviews, merges, and ships it through its existing pipeline. This page covers a narrower, optional path: asking Devin to build a small standalone app from scratch and host it for you, giving you a live URL for prototypes, demos, or throwaway internal tools.
If you’re using Devin on an existing codebase, deployment happens through your own CI/CD pipeline, not through the hosted deployments described here. See Existing applications.

​
What a deployment is

A deployment is Devin publishing an app it built to Cognition-hosted infrastructure, so the app stays reachable at a public URL after the session ends. Devin can deploy two things:
  • Static frontends, served from devinapps.com.
  • FastAPI backends, deployed to Fly.io.
Deploying is not how Devin ships code to your infrastructure. When Devin pushes to Vercel, AWS, Netlify, or your own CI/CD pipeline, it is running your tooling with credentials you provide — see Existing applications. Deployments are intended for small apps Devin creates from scratch, such as prototypes, demos, and internal tools.

​
Availability

Deployment is available to non-enterprise organizations with secure mode off:
  • Enterprise organizations: deployment is disabled for all sessions. Deploy to your own infrastructure instead.
  • Secure mode: when secure mode is enabled, Devin loses native internet deployment capabilities. The setting lives under Security settings on the Customization page.
Because a deployment makes content publicly reachable on the internet, every deploy requires your explicit approval. Devin shows an approve/deny prompt in the session, and the deploy runs only after you approve it.

​
Frontend deployment

Devin uploads the contents of a build directory and serves them as a static site at a unique https://<name>.devinapps.com subdomain. The only requirement is that the directory contains an index.html — so any framework that produces a static build works, including Vite, Next.js static exports, Astro, SvelteKit’s static adapter, and plain HTML, CSS, and JavaScript. When Devin creates a frontend from scratch and you haven’t specified a stack, it scaffolds a Vite + TypeScript + Tailwind CSS + shadcn/ui app. That’s a default for new projects, not a restriction on what can be deployed.

​
Backend deployment

Devin deploys Python backends to Fly.io, generating the Dockerfile and fly.toml for you. The project must:
  • have a pyproject.toml with a project name, and
  • expose a FastAPI app named app in app/main.py.
Devin’s FastAPI scaffold already satisfies both. For any other backend stack or language, choose your own deployment method and give Devin the credentials and instructions it needs via Secrets and Knowledge.

​
Existing applications

Devin is not equipped to deploy pre-existing applications to Cognition-hosted infrastructure. A static frontend may work if it builds to a directory with an index.html, but existing backends generally will not, because they rarely match the FastAPI layout the deployer expects. For pre-existing applications, treat deployment like any other task you’d hand a new engineer: tell Devin which platform to use and store the credentials and commands in Secrets and Knowledge.