Cognition launched Devin Apps on 13 November 2026. You describe an internal tool, Devin builds it on its own cloud machine, and your team opens it from a stable private link.
That matters because the usual gap between “the agent wrote it” and “people can use it” disappears. There is no hosting account to set up, and nothing goes public.
This guide covers who can use it, your first app step by step, sharing, billing, limits and how it compares with Lovable, Replit, Claude Artifacts and Cursor Live Apps.
- What: private full-stack web apps that Devin builds and serves from its own cloud machine.
- URL: a stable link like
https://<name>--<id>.preview.devinapps.comthat survives updates and renames. - Access: every visitor must sign in to Devin. Scope it to named people, your organization or your whole enterprise. Apps are never public.
- Billing: charged for the time the machine is awake. It sleeps 5 minutes after the last request, and a sleeping app costs nothing.
- Rollout: gradual. If Apps is not in your sidebar, it is not on for your account yet.
- Best for: dashboards, admin panels, approval queues and staging copies. Not for high-traffic public sites.
What Are Devin Apps?
Cognition calls Devin Apps “live, private web applications hosted directly on Devin’s cloud computer.” The key word is hosted. Nothing is deployed to a third-party host such as Vercel or a cloud account you manage.
Because the app runs on the same machine Devin works on, it can reuse what Devin already has access to. That includes:
- Your codebases: the app can live in one of your repos, and Devin commits before each deploy.
- Your MCPs and integrations: the same connections Devin uses in normal sessions.
- Your stack: any framework that serves HTTP on a port, or a built-in template.
- A database: SQLite or Postgres running on the same machine.
- The Devin API: so you can build small tools on top of Devin itself.
The machine uses memory snapshots to hibernate. When nobody uses an app, it sleeps. When someone opens the link, it wakes up and carries on where it stopped.
Who Can Use Devin Apps?
The official docs say the feature is rolling out gradually. If you do not see Apps in the Devin sidebar, it has not been enabled for you yet. Cognition has not published a plan-by-plan list for Apps.
Apps run on Devin’s cloud machine, so you need a plan with cloud agents. Here is the current Devin lineup from the official pricing page and billing docs (November 2026):
| Plan | Price | Usage | Cloud agents (Devin Cloud) |
|---|---|---|---|
| Free | $0 | Light quota, limited models | Not listed |
| Pro | $20/month | Daily and weekly allowance, extra usage at API pricing | Yes |
| Max | $200/month | Larger weekly allowance, no daily cap | Yes (everything in Pro) |
| Teams | $80/month minimum, $40 per full seat | Per-seat allowance plus shared on-demand credits, up to 100 users | Yes |
| Enterprise | Custom | Contract billing | Yes, plus SCIM and RBAC |
Note: the “Organization” and “Enterprise” sharing scopes only make sense on team accounts. On a single-user Pro or Max plan you share by adding named people.
How to Build Your First Devin App
The flow is short. Devin asks its questions up front, then builds and deploys without you touching a server.
- Open Apps in the sidebar. Go to app.devin.ai and click Apps. No Apps item means the rollout has not reached you yet.
- Describe the app or pick a template. Templates include a metrics dashboard, a project status page and a review queue. Say what data it shows, who uses it and where the data comes from.
- Click “Build with Devin”. Devin opens a new session and asks clarifying questions in its first reply. Answer them in one go to save time.
- Add secrets if the app needs outside data. Store third-party API keys as secrets. They stay on the app’s server and never reach the browser.
- Watch the status. The app appears on the Apps page with the status Building until its first version is live.
- Open the URL. You get a stable link in the form
https://<name>--<id>.preview.devinapps.com. Click through and check it works. - Share it. Open the Share dialog, set General access and copy the link (see the next section).
- Pin it. Use “Pin for me” so it stays at the top of your Apps home. Org admins can “Pin for everyone”.
Here is a sample first prompt you can adapt:
Build an internal app called "Support Pulse".
Show open tickets by priority and age from our helpdesk API.
Store a daily snapshot in SQLite so we can see a 30-day trend.
Only my team will use it. Keep the look simple and use our design system.
Tip: you can also ask for an app from any existing session. If Devin already showed you a browser preview you like, just ask it to publish that preview as an App.
What Devin does behind the scenes
The docs list a few habits Devin follows on every build. They are worth knowing because they explain what you will see in the session:
- Production build: it serves a production build, not the dev server.
- Git first: it commits before each deploy, and pushes or opens a PR if the app lives in your repo.
- Safe data: database files and uploads sit outside the rebuilt folder, so updates and rollbacks do not wipe them.
- Design system: it looks for your company’s design system in your repos unless you name a look, and tells you where the branding came from.
- Self-repair: if a deploy fails, it reads the error and redeploys.
- Thumbnail: it takes a screenshot for the app card on the Apps page.
Sharing and Access Scopes
Every Devin App is private. Anyone who opens it must sign in to Devin, and there is no public option. Access is set in the Share dialog under General access.
| General access | Who can open it | Sign-in needed? |
|---|---|---|
| Only people with access | The creator, org admins and people you add | Yes, Devin |
| Organization | Everyone in your organization, plus anyone you add | Yes, Devin |
| Enterprise | Members of every organization in your enterprise | Yes, Devin |
On top of General access, you can add individual people, groups or whole organizations. Each one gets a permission level:
- Open: can use the app.
- Edit settings: can change the app’s settings.
- Share: can share it with others.
Org admins can set default sharing for new apps under Sharing defaults. Secrets are not part of sharing settings, so sharing an app never hands out your API keys.
Warning: if the app calls the Devin API with your personal access token, everyone who uses the app acts with your permissions. Use a service user key for shared tools.
Updates, Versions and Rollbacks
To change an app, click Edit in session and describe what you want. Devin builds and redeploys, and the URL stays the same.
- Versions: each update is a version, listed under Deployments with status, description and commit.
- Safe failures: if a new version fails to start, the previous version keeps serving.
- Rollback: ask the session to deploy an older version.
- Analytics: the app page shows page views for the last 24 hours, 7 days or 30 days.
- Templates: “Use as a starting point” creates a new app from an existing one.
Scheduled refreshes with Automations
Automations can update an app hourly, daily or weekly, or on every push to a branch you follow. That is how a dashboard stays fresh without anyone asking.
Each automation run is a billed session. The docs warn that frequent runs can cost more than the app itself. Their suggestions:
- Run less often: daily instead of hourly if the data allows it.
- Use a cheaper model for routine refreshes.
- Fetch only new data with a small script instead of rebuilding everything.
- Set a per-session spend limit under Settings, Usage & limits.
What Devin Apps Cost
Cognition does not publish a separate hourly price for Apps. The docs say billing is based on how long the machine is awake, and it comes out of the same usage as your other Devin work.
| Activity | Billed? | How |
|---|---|---|
| Building the first version | Yes | Normal session work |
| Edits and redeploys | Yes | Normal session work |
| App awake (someone using it) | Yes | Awake machine time |
| App asleep (no visitors) | No | Nothing used while asleep |
| Idle after last request | Up to 5 minutes | Machine sleeps 5 minutes after the last request |
| Automation runs | Yes | Each run is a billed session |
Your usage then follows your plan rules. Pro and Teams full seats get daily and weekly allowances, and Max gets a weekly allowance. When the allowance runs out, prepaid on-demand credits keep you going, and purchased credits never expire.
On Teams, Automations draw from the shared on-demand credit pool, not from seat quota. If those credits run out, Automations stop. Older Devin docs describe usage in ACUs (Agent Compute Units), and Enterprise contracts still bill Enterprise ACUs under their order form.
Tip: watch real spend under Settings, Usage & limits for the first week. A dashboard opened all day by many people stays awake far longer than one checked twice a day.
Best Use Cases
Cognition positions Apps for three kinds of work. All of them are internal and low to medium traffic.
- Internal tools: admin panels, request forms, approval queues and replacements for shared spreadsheets.
- Dashboards: metrics, support queues and sales numbers pulled from your own data and refreshed on a schedule.
- Beta and staging copies: a full copy of your product (frontend, backend, database and workers) that teammates open from a link.
A few practical ideas that fit this shape:
- PR review queue: lists open pull requests by age and owner across repos.
- On-call handover page: shows incidents from the last shift.
- Feature flag viewer: read-only view of flags per environment for support staff.
- Demo environment: a staging build sales can open without asking engineering.
If you already use other cloud agents, our Claude Code on the web guide and OpenAI Codex guide show how those tools handle cloud runs.
Limits and Security
Hard limits from the docs
- No public apps: an app cannot be made public. Outside users need a Devin sign-in and access.
- One machine: each app runs on a single machine. It suits internal tools, not high-traffic production services.
- No service workers: apps cannot register one, so PWA offline mode is not available.
- Cold starts: the first load after sleep can take a few seconds.
- No auto-restart: a crashed server is not restarted automatically. You ask Devin to deploy again.
- Tied to the session: archiving or ending the session takes the app offline.
The docs do not mention custom domains, storage quotas or database size limits. Treat those as unknowns until Cognition documents them.
Security points to check
- Sign-in gate: every visitor authenticates with Devin, which is the main protection.
- Secrets stay server-side: API keys live on the app’s server, not in the browser.
- Token scope: prefer a service user key over a personal token for any shared app.
- MCP access: an app on Devin’s machine can reach the same tools Devin can. Review which integrations are connected. Our MCP security best practices post covers this.
- Repo hygiene: Devin commits before deploys, so keep secrets out of the repo and in Devin’s secret store.
Devin Apps vs Lovable, Replit, Claude Artifacts and Cursor
Several tools now turn a prompt into a hosted app. The big difference is who can open the result and what runs behind it.
| Tool | Hosting | Private access options | Public option | Backend | Best for |
|---|---|---|---|---|---|
| Devin Apps | Devin cloud VM, sleeps when idle | Named people, organization, enterprise (Devin sign-in) | No | Any HTTP stack, SQLite or Postgres on the machine | Internal tools using your repos and MCPs |
| Cursor Live Apps | Isolated hosting per team | Invited people or team (Cursor SSO) | Yes (off by default on Teams) | Auto-provisioned Postgres | Teams already on Cursor |
| Lovable | lovable.app subdomain, custom domain on paid plans | Invite only (up to 10 on Free and Pro), Workspace or Custom on Business and Enterprise | Yes (default) | Lovable Cloud | Polished MVPs and customer-facing sites |
| Replit | Replit deployments | Workspace only or Invite only, plus password protection | Yes | Full server and database | Builders who want to edit code in an IDE |
| Claude Artifacts | Hosted on claude.ai | Private by default, share with organization (Team, Enterprise) or by email invite | Yes, link sharing (admin-controlled on Team and Enterprise) | Pages with optional shared storage, not a server you run | Quick tools, reports and dashboards from chat |
Entry prices for comparison: Devin Pro $20/month, Cursor Premium $30/month, Replit Core $20/month. Lovable lists plans in credits, and Claude Artifacts sharing comes with your Claude plan.
For a wider view of coding agents, see Cursor vs Windsurf vs Claude Code vs Cline.
My Take
Devin Apps is the most “locked-down by design” option in this group. There is no public toggle to misconfigure, and the stable URL plus versioned deploys make it feel like a real internal platform.
The sleep-after-5-minutes model is smart for internal tools that get a few visits a day. The weak spots are the single machine, no auto-restart after a crash, and no published price for awake time.
If your team already lives in Devin, it is an easy win for dashboards and queues. If you need customers to open the app, pick Lovable, Replit or Cursor instead.
Troubleshooting Devin Apps
| Problem | Likely cause | Fix |
|---|---|---|
| No Apps item in the sidebar | Gradual rollout | Wait for the rollout, or ask your Devin admin or Cognition contact |
| App shows an offline page | First deploy not finished, or someone took it offline | Check the status on the Apps page, then redeploy from the session |
| App went offline suddenly | The session was archived or ended | Unarchive or resume the session |
| App stopped responding | The server crashed (no auto-restart) | Open the session and ask Devin to deploy again |
| First load is slow | The machine was asleep | Normal. Wait a few seconds; later loads are fast |
| Teammate cannot open the link | Not signed in to Devin, or outside the access scope | Add them in the Share dialog or widen General access |
| New version broke the app | Bad deploy | Ask the session to deploy an older version from Deployments |
| Data vanished after an update | Data stored inside the build folder | Ask Devin to move database files and uploads outside the rebuilt folder |
| Costs higher than expected | Frequent Automations or an always-open tab | Run Automations less often and set a per-session spend limit |
Frequently Asked Questions
When did Cognition launch Devin Apps?
Cognition announced Devin Apps on its blog on 13 November 2026. The docs say the feature is rolling out gradually, so not every account sees it yet.
Can I make a Devin App public?
No. Every visitor must sign in to Devin, and the docs list “can’t be made public” as a hard limit. Use Lovable, Replit or Cursor Live Apps for public apps.
What is the Devin Apps URL format?
Apps live at https://<name>--<id>.preview.devinapps.com. The URL stays the same across updates, and renaming the app does not change it.
How much does a Devin App cost to run?
You pay for the time the machine is awake, plus normal session usage for building and editing. A sleeping app uses nothing, and Cognition has not published a separate hourly rate.
How long until an idle Devin App sleeps?
The machine sleeps 5 minutes after the last request. The next visit wakes it, and that first load can take a few seconds.
Can a Devin App use a database?
Yes. You can run SQLite or Postgres on the same machine. Devin keeps database files outside the rebuilt folder so updates and rollbacks do not wipe your data.
What happens if I archive the Devin session?
Archiving or ending the session takes the app offline. Unarchive or resume the session to bring it back.



