On November 13, Cognition launched Devin Apps. You describe the tool you need, Devin builds it as a web app in a session and serves it from its own cloud machine, with nothing deployed to a third-party host. Each App has a stable URL (name--id.preview.devinapps.com); everyone who opens it must sign in to Devin, Apps are never public, and they can be shared with people, an organization or a whole enterprise. Apps can use any stack, reuse connected MCPs, integrations and code, and keep data such as SQLite or Postgres on the same machine. The machine sleeps 5 minutes after the last request and wakes when someone opens the App; billing is by awake time, while building and changes bill as normal session work. Every update is a new version tied to a commit, and if a new version fails to start the previous one keeps serving. Apps are rolling out gradually.
Key Takeaways
- ✓Hosting: Apps run on Devin's own cloud machine with nothing sent to a third-party host, and data and uploads stay on that machine
- ✓Stable URL: shaped like name--id.preview.devinapps.com and unchanged by renames or updates; viewers must sign in to Devin and Apps are never public
- ✓Billing: the machine sleeps 5 minutes after the last request and bills by awake time, the first load after sleep takes a few seconds, and building and edits bill as normal sessions
- ✓Versions: Devin commits before every deploy, the previous version keeps serving if a new one fails to start, and the session can redeploy any older version
- ✓Use cases: internal tools, dashboards, staging copies and demos; rollout is gradual and Cognition lists no unit price
Key Decision Metrics at a Glance
Turn your technical choice into a development budget
Compare 40 dev plans & simulate token costs vs $20/mo subscriptions
Project Links & Resources
Direct AccessIn-Depth Technical Analysis
Background and pain points
Getting a coding agent to write a small internal tool is no longer hard; the hard part is where to put it. You need a host, a domain, sign-in and a database, so many prototypes never leave the session. Devin Apps, launched by Cognition on November 13, makes Devin's own cloud machine the server, merging building a tool and shipping it into one step. For companies already using Devin as a team tool, small internal tools can now be handled end to end by Devin.
Architecture highlights
An App is built by a Devin session and served from that session's machine. Any stack that serves HTTP on a port works, and the database and uploads live on the same machine, kept outside the build folder so updates and rollbacks do not wipe data. Because it runs on Devin's machine, an App can use connected MCPs, integrations and code. Devin's built-in rules include serving a production build rather than a dev server, committing before every deploy, using the company design system when it finds one, and fixing and redeploying after a failed deploy.
Benchmarks and data
This is a product feature, not a model, and Cognition has published no performance data. Verifiable rules from the docs: the machine sleeps 5 minutes after the last request, the first load after sleep takes a few seconds, and page views are shown for the last 24 hours, 7 days or 30 days. Billing is by awake time, but no unit price is listed; see Devin's usage docs.
Getting started
Open Apps in the sidebar, describe what you need or pick a template (metrics dashboard, project status page, review queue) and click Build with Devin. You can also say "build this as a Devin App" in any session, or publish an existing browser preview as an App. To change it, click Edit in session and message the original session. Rollout is gradual, so if Apps is missing from your sidebar it is not on for you yet. Check sharing settings before putting sensitive data in an App.
Benchmark side-by-side against alternatives, or calculate monthly token cost vs subscription break-even.
Discussion & Comments
0Sign in to join the discussion
Connect with AI developers to exchange benchmark insights.