Last updated: November 14, 2026
Devin Apps, launched by Cognition on November 13, 2026, let Devin build a private web app from a prompt and keep serving it from Devin’s own cloud machine. Each App gets a stable URL, requires Devin sign-in, sleeps when idle and is billed for the time the machine is awake.
This guide is based on Cognition’s Introducing Devin Apps announcement and the Devin Apps documentation. For other recent Devin changes, see our Devin Desktop 3.12 guide.
Contents
- Devin Apps at a glance
- How to create a Devin App
- Sharing and access levels
- Updates, versions and automations
- Billing and plans
- Devin Apps vs. browser previews
- Limits and things to watch
- Frequently asked questions
Devin Apps at a glance
A Devin App can be an internal tool, a dashboard, a form, a tracker or a demo. The documentation also lists beta and staging copies of your product and rollout trackers. An App can use a database such as SQLite or Postgres on the same machine.
| Item | What the official sources say |
|---|---|
| Announced | November 13, 2026, on the Devin blog |
| Availability | Rolling out gradually; look for Apps in the sidebar |
| Where it runs | On Devin’s machine; nothing is deployed to a third-party host |
| Stack | Any framework or language that serves HTTP on a port |
| URL format | https://<name>--<id>.preview.devinapps.com, unchanged across updates and renames |
| Access | Devin sign-in required; never public |
| Sleep | Machine sleeps 5 minutes after the last request and wakes on the next visit |
| Billing | Based on how long the machine is awake; building and edits billed as normal sessions |
Because the App runs on Devin’s machine, the announcement says it can use your existing MCP servers, integrations and codebase, and it can call the Devin API so you can build your own tools on top of Devin.
How to create a Devin App
The documented flow takes three steps, and Devin handles the build and deploy in a new session.
- Open Apps: click Apps in the Devin web app sidebar.
- Describe the App: write what it should do, or pick a prompt template such as a metrics dashboard, a project status page or a review queue.
- Send the prompt: click Build with Devin. A session starts, and Devin asks any questions it has in its first message.
- Answer once and wait: the App appears under Apps right away with its URL and a Building status until the first version is live.
- Override defaults if needed: name the stack, database or look in your prompt; otherwise Devin looks for your design system in your repositories.
You can also ask for an App inside any session, for example “build this as a Devin App.” If Devin has already shown you a browser preview, you can ask it to publish that preview as an App.
Sharing and access levels
Click Share on an App to copy the link or change who can open it. General access has three levels:
- Only people with access: the creator, organization admins and the people you add.
- Organization: everyone in your organization, plus anyone you add.
- Enterprise: members of every organization in your enterprise.
You can also add specific people, groups or organizations and decide whether each can open the App, edit its settings or share it. Organization admins can set a default sharing level under Sharing defaults, and can use Pin for everyone to put an App at the top of the organization’s Apps home.
One caution from the docs: a personal access token used by an App acts as you, so every viewer acts with your permissions. Keep API keys in Devin secrets on the server side.
Updates, versions and automations
To change an App, open it and click Edit in session, then tell Devin what to change. Devin builds a new version and the URL stays the same. Each version is listed under Deployments with its status, description and commit. If a new version fails to start, the previous one keeps serving, and you can roll back by asking the session to deploy an older version.
The App page also shows page views for the last 24 hours, 7 days or 30 days.
Automations can keep an App current without you asking. The documentation describes two common setups: a schedule (hourly, daily or weekly data refreshes) and a redeploy on every push to a branch. Ask the App’s session to set this up, then approve the automation once.
Billing and plans
Cognition separates two costs. Running an App is billed for how long Devin’s machine is awake, and an App nobody visits uses nothing while asleep. Building and changing the App is ordinary session work. The Usage page explains that self-serve plans draw on included quota first and then on prepaid on-demand credits, while Enterprise customers consume Agent Compute Units (ACUs).
Automations need the most attention. The docs warn that every automation run is a Devin session billed like one, so an App that updates every few minutes “can cost much more than the App itself.” Cognition suggests running automations less often, using a more cost-efficient model, having Devin script the data fetch, and setting an ACU limit.
Cognition has not published a separate per-hour rate for Apps or a list of which plans include them. For context, the self-serve plans page lists Free, Pro at $20 per month, Max at $200 per month and Teams with an $80 per month minimum. Our Windsurf cost answer covers Cognition’s editor pricing, and our Devin Review 2.0 guide covers review usage.
Devin Apps vs. browser previews
Apps are served the same way as browser previews. The difference is purpose and lifespan.
- Browser preview: tied to one session, follows that session’s access, and stops working when the session is archived or ends. Meant for reviewing work in progress.
- Devin App: a stable URL that survives updates and renames, its own sharing settings, a deployment history, page-view counts and pinning. Meant for tools your team keeps using.
If you compare hosted agent-built apps from other vendors, see our Cursor Live Apps guide.
Limits and things to watch
- No public access. Every visitor must sign in to Devin, so Apps cannot serve customers outside your Devin organization or enterprise.
- One machine. Apps are not designed for high-traffic production services.
- No service workers. Apps can’t register their own service worker, so offline mode for progressive web apps is not available.
- Tied to a session. Archiving or ending the App’s session takes the App offline, and nothing restarts a crashed server automatically. Open the session from the Apps page and ask Devin to deploy again.
If you want a cheaper model for automation sessions, our SWE-2 Flash guide covers Cognition’s fast coding model.
Frequently asked questions
What are Devin Apps?
Devin Apps are private web apps that Cognition’s Devin agent builds in a session and keeps serving from its own cloud machine. Each App has a stable URL, and anyone who opens it must sign in to Devin. Cognition announced the feature on November 13, 2026.
Can I make a Devin App public?
No. Cognition’s documentation says Apps can’t be made public and visitors always sign in to Devin. You can share an App with specific people, your whole organization or every organization in your enterprise.
How are Devin Apps billed?
Billing for a running App is based on how long Devin’s machine is awake. The machine sleeps 5 minutes after the last request, so an idle App uses nothing. Building, editing and automation runs are billed as normal sessions.
Why don’t I see Apps in my Devin sidebar?
Devin Apps are rolling out gradually. The documentation says that if Apps is missing from your sidebar, the feature has not been turned on for your account yet. Cognition has not published a plan-by-plan availability list.
Can a Devin App run a production website?
Cognition advises against it. Each App runs on one machine, so it suits internal tools and dashboards, not high-traffic production services. For those, the docs recommend deploying to your own infrastructure with your existing CI/CD.
Sources
- Introducing Devin Apps, Cognition (November 13, 2026)
- Devin Apps documentation, Devin Docs
- Devin browser previews, Devin Docs
- Usage, Devin Docs
- Self-serve plans, Devin Docs