Devin Apps, announced by Cognition on November 13, 2026, let you describe a small web tool in plain English and have Devin build it and keep it running on its own cloud machine at a stable, private URL. It is aimed at internal dashboards, request forms, review queues and staging copies, not public websites. This tutorial walks through creating, sharing, updating and budgeting an App, and shows where it stops being the right tool.
What a Devin App actually is
Devin already had browser previews: while a session works, you can open the app it is building. A preview belongs to one session and is meant for checking work in progress. A Devin App takes the same idea and makes it last. Devin builds the tool in a session, serves the production build from that session's machine, and gives it a URL in the form https://<name>--<id>.preview.devinapps.com that stays the same across every update and even after you rename the App.
Four facts from the documentation shape everything else in this guide:
- It runs on Devin's machine. Nothing is pushed to a third-party host. Because the App lives where Devin works, it can use the MCP servers, integrations and repositories your Devin setup already has.
- Any stack that serves HTTP on a port works. A database such as SQLite or Postgres can run on the same machine, and uploaded files live there too.
- Apps are private. They can never be made public; access is limited to people in your Devin organization or enterprise that you choose.
- One session owns the App. The session that built it also ships later changes, and archiving that session takes the App offline.
Before you start: check that you have it
Cognition says Apps are rolling out gradually. If there is no Apps entry in your Devin sidebar, the feature has not been turned on for your organization yet and there is nothing to configure on your side. Apps run on Devin's cloud machine, and the public pricing page lists cloud agents (Devin Cloud) from the Pro plan upward; the Free plan does not include Devin Cloud features. The Apps documentation itself does not name specific plans, so treat plan eligibility as "needs Devin Cloud, and the rollout must have reached you."
Step by step: build your first App
1. Write a prompt that answers Devin's questions in advance
Open Apps in the sidebar and describe the tool, or pick one of the prompt templates (the launch post mentions a metrics dashboard, a project status page and a review queue). Devin is built to ask all of its questions in its first reply, because people often leave after sending a request. You save a round trip if your prompt already covers the basics:
- Who uses it and for what: "a review queue for the support team to approve refund requests."
- Where the data comes from: a repository, a database, an integration Devin already has, or a CSV you will upload.
- What the screens are: a list view with filters, a detail page, an approve/reject button.
- Stack and look, if you care: otherwise Devin searches your repositories for a design system and uses its colors, fonts and components, and falls back to a plain default style.
A workable example prompt: "Build a Devin App that shows open pull requests across our three frontend repos, grouped by reviewer, with age in days and a filter for PRs older than 3 days. Use SQLite for a daily snapshot so we can see a 30-day trend. Keep it simple: one page plus a detail drawer."
2. Send it and answer the first message
After you send the prompt you land in a normal Devin session. Answer its questions, then let it work. The App appears on the Apps page immediately with its URL and the status Building until the first version is live. Behind the scenes Devin develops against a dev server, checks the result in a browser preview, then builds and serves the production version. It commits to git before every deploy, so each version maps to a commit, and if the App lives in one of your repositories it pushes the commits or opens a pull request.
You can also start from an existing session: ask "build this as a Devin App", or, if Devin has already shown you a browser preview, ask it to publish that preview as an App.
3. Share it with the right audience
Click Share to copy the link or change general access. There are three levels: Only people with access (the creator, organization admins and anyone you add), Organization, and Enterprise (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 re-share it. Admins can set a default sharing level for all Apps and can pin an App to the top of everyone's Apps home.
4. Update it without breaking the link
Open the App, click Edit in session and tell Devin what to change. Every update becomes a new version listed under Deployments with its status, description and commit. If a new version fails to start, the previous one keeps serving; to roll back, ask the session to deploy an older version again. The App page also shows page views for the last 24 hours, 7 days or 30 days, which is handy for deciding whether a tool is still used.
5. Keep data fresh with an automation (carefully)
A Devin automation can wake the App's session on a schedule (hourly, daily, weekly) to pull new data, or redeploy whenever a tracked branch changes. Ask the App's session to set it up and approve it once. This is the most common way to turn a one-off dashboard into something people rely on, and also the most common way to overspend, which brings us to cost.
What it costs to run
There are two separate meters. Building and changing an App is ordinary session work, billed like any other Devin session. Serving the App is billed by how long the machine is awake. The machine sleeps when nobody is using it, wakes when someone opens the App (the first load after a sleep can take a few seconds) and goes back to sleep 5 minutes after the last request. An App nobody visits uses nothing while asleep.
The trap is automations: every automation run is a full Devin session. The docs warn that an App refreshing every few minutes can cost much more than the App itself. Run refreshes hourly or daily, pick a cheaper model for the automation's sessions, have Devin write a small fetch script that runs on each update instead of re-solving the problem every time, and set a Spend limit per session on the automation.
Devin plans compared (as listed on the official pricing page)
| Plan | Price | Members | Devin Cloud (DeepWiki, Devin API, Ask Devin) | Sharing and collaboration | Concurrent sessions |
|---|---|---|---|---|---|
| Free | $0 | 1 | Not included | Not included | Not included |
| Pro | $20/month | 1 | Included | Not included | Up to 10 |
| Max | $200/month | 1 | Included, significantly higher quotas | Not included | Up to 10 |
| Teams | $80/month + $40/month per full dev seat | Up to 100 | Included | Included | Unlimited |
Paid plans come with a usage allowance that refreshes daily and weekly; beyond it, extra usage is bought at API pricing. The pricing page does not list a separate price for Apps, so App hosting draws on that same usage. Because Apps are about sharing tools with colleagues, the Teams plan (or Enterprise) is the natural fit; a solo Pro user can build Apps once the rollout reaches them, but has no team to share them with.
When a Devin App is the wrong choice
- Public or customer-facing pages. Apps cannot be made public, full stop.
- High traffic. An App runs on one machine. For production services, the docs recommend deploying to your own infrastructure with your existing CI/CD and giving Devin access through secrets and skills.
- Offline-capable PWAs. Apps cannot register their own service worker, so offline mode is not available.
- Anything that must survive without its session. Nothing restarts a crashed server automatically; the URL shows an error page until Devin deploys again.
- A quick one-time look. If you only need to show a teammate work in progress, a regular browser preview is enough and avoids keeping a session alive.
Editor's note
Good fit: engineering, ops and support teams already paying for Devin who keep a "temporary" spreadsheet or a half-maintained admin script. A PR-age dashboard, an approval queue or a staging copy of your product are exactly the cases Cognition documents.
Not a fit: people looking for a free website builder, anyone who needs public pages, or teams without a Devin Cloud plan.
Gotchas we found in the docs:
- Archiving the session kills the App. Devin warns before you archive a session that serves an App. If an App goes offline, open its session from the Apps page and ask Devin to deploy; unarchive or resume the session if needed.
- "Offline page" right after creating: normal until the first deploy finishes, or if someone took the App offline in settings.
- Slow first load: the machine was asleep. Expected, and the reason idle Apps are cheap.
- Secrets belong on the server side. Anything the App sends to the browser is visible to everyone who can open it. If the App calls the Devin API with a personal access token, every viewer acts with that person's permissions, so share such Apps narrowly.
- Data survives updates because Devin stores database files and uploads outside the rebuilt folder, but deleting the App makes the URL stop working for good. Taking it offline keeps history.
FAQ
Can I make a Devin App public, for example for a client demo?
No. The documentation states that Apps cannot be made public. The widest sharing level is your whole enterprise. For a client-facing demo, deploy to your own hosting instead.
Does an App cost money when nobody uses it?
Serving is billed by how long the machine is awake, and it sleeps 5 minutes after the last request, so an idle App uses nothing while asleep. Scheduled automations that refresh it are billed as full sessions, and those are where costs add up.
I don't see Apps in my sidebar. What should I change?
Nothing on your side. Cognition is rolling the feature out gradually, and the sidebar entry appears once it is enabled for you. Also check that your plan includes Devin Cloud, which the pricing page lists from Pro upward.
Related reading on lightmind24
- Windsurf Is Now Devin Desktop: Fixes for Common Problems
- Val Town Is Shutting Down: Move Vals and Crons by Dec 10
- Reason Pricing: $50 Pro, BYO Keys vs Codex and Cursor
If your team already pays for Devin, start with one small dashboard on a daily refresh and a spend limit, and let the page-view counter tell you whether it earned a permanent place.
Screenshots of the Devin Apps documentation (creating, billing, sharing levels, limits) and the Devin plan comparison are included at the end of this post. Image credit: screenshots from docs.devin.ai and devin.ai/pricing.
lightmind24 is an independent review site, not affiliated with Cognition or Devin.
Last verified: 2026-11-16
Sources:
Introducing Devin Apps (Cognition blog, Nov 13, 2026)
Devin Apps documentation
Devin automations documentation (limits and safeguards)
Devin Apps product page
Devin plans and pricing
댓글
댓글 쓰기