기본 콘텐츠로 건너뛰기

Devin Apps Tutorial: Build a Private Internal App by Prompt

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

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

Uploaded Image Uploaded Image Uploaded Image Uploaded Image

댓글

이 블로그의 인기 게시물

브루(Vrew) 요금제 정리: 무료 200크레딧으로 어디까지 쓸 수 있나

요약: 영상 자막 편집기 브루(Vrew)는 2026년 4월 22일부터 기능별 사용량 대신 '통합 크레딧' 하나로 요금을 매겨요. 무료 플랜은 매달 200크레딧이 들어오는데, 음성 분석(자동 자막)만 쓰면 최대 200분 분량이라 짧은 영상 몇 편은 충분하지만, 영상 초반의 Vrew 마크를 지우려면 유료 플랜이 필요해요. 이 글은 브루 공식 가격 페이지와 고객센터 공지를 2026년 10월 23일에 다시 확인해, 크레딧 계산법과 플랜 고르는 기준을 정리했어요. 목차 브루 요금 구조: 통합 크레딧이란 1크레딧으로 할 수 있는 일 무료 플랜으로 되는 것과 안 되는 것 유료 플랜 4종 비교표 월 구독·연 구독·기간 이용권, 무엇이 이득일까 상황별 추천: 학생·직장인·유튜버 크레딧이 모자랄 때: 사용 기록 지우개 업그레이드·환불 전에 알아둘 규칙 운영자 메모, 자주 묻는 질문 1. 브루 요금 구조: 통합 크레딧이란 예전 브루는 플랜마다 음성 분석 몇 분, AI 목소리 몇 자, 번역 몇 자처럼 기능별 한도를 따로 줬어요. 그런데 보이저엑스(브루 운영사)가 실제 이용 데이터를 보니 한두 가지 기능만 집중해서 쓰는 사람이 훨씬 많았다고 해요. 그래서 2026년 4월 22일 업데이트부터는 플랜마다 정해진 크레딧을 받고, 어떤 기능에 쓸지는 내가 정하는 방식으로 바뀌었어요. 플랜별 매달 지급량은 Free 200 · Light 2,000 · Standard 10,000 · Business 12,000크레딧 이에요. 공식 공지에 따르면 무료 사용자는 매달 1일에, 유료 사용자는 매월 결제일에 충전되고, 남은 크레딧은 다음 달로 넘어가지 않아요. 바뀐 뒤 무엇이 좋아졌나 공지에 나온 예시가 이해하기 쉬워요. Standard 플랜에서 AI 목소리만 쓰면 예전에는 최대 50만 자였지만, 지금은 1만 크레딧을 모두 AI 목소리에 몰아 쓸 수 있어 최대 100만 자가 돼요. 반대로 여러 기능을 골고루 쓰는 사람은 크레딧이 기능끼리 ...

에이닷 전화 vs 익시오: 통화 녹음·AI 요약, 내 통신사·폰에 맞는 앱 고르기

요약: 통화 녹음과 AI 요약을 쓰고 싶다면 먼저 내 통신사와 휴대폰 종류부터 확인해야 해요. LG유플러스 고객은 무료 앱 익시오, SKT 고객은 에이닷 전화가 가장 기능이 많고, 다른 통신사의 아이폰 사용자는 iOS에 들어 있는 기본 통화 녹음·전사 기능이 현실적인 선택이에요. 이 글은 2026-10-30에 SKT·LG유플러스·Apple 공식 페이지와 도움말을 직접 확인해 세 가지를 비교했어요. 왜 '앱 기능'보다 '내 조건'을 먼저 봐야 할까요 통화 요약 앱 비교 글을 보면 기능 목록부터 나열하는 경우가 많아요. 그런데 실제로 써 보려는 사람에게 가장 먼저 걸리는 건 기능이 아니라 이용 조건 이에요. 익시오는 LG유플러스 고객 전용이고, 에이닷 전화는 누구나 설치할 수 있지만 통역콜·baro 같은 기능은 SKT 고객에게만 열려 있어요. 아이폰은 운영체제 구조상 앱이 통화를 마음대로 녹음하기 어려워서, 통신사 앱이 안 되면 iOS 기본 기능에 기대야 해요. 그래서 이 글은 "어떤 앱이 제일 좋은가"보다 "내 통신사·내 폰에서 무엇을 쓸 수 있나" 순서로 정리했어요. 기능 차이는 그다음이에요. 한눈에 비교: 에이닷 전화 vs 익시오 vs 아이폰 기본 통화 녹음 구분 에이닷 전화 (SKT) 익시오 ixi-O (LG유플러스) 아이폰 기본 통화 녹음 (Apple) 누가 쓸 수 있나 통신사 구분 없이 앱 설치 가능. 단, 통역콜·baro·그룹통화 발신 등은 SKT 고객 전용 U+ 모바일 고객. 타 통신사, 만 14세 미만, 선불요금제 고객은 제한 (공식 사이트 FAQ상 알뜰폰 중 KB리브엠은 예외) 지원 국가·언어의 iPhone 사용자. 1명과 통화할 때만 녹음 가능 지원 OS·기기 Android 10 이상, iOS 16 이상 iOS 17 이상 iPhone 12 이상 / Android...

타입캐스트 vs 클로바더빙: 수익 나는 채널에 쓸 때 무료·유료 조건 비교

요약 타입캐스트와 클로바더빙은 둘 다 글만 입력하면 한국어 AI 목소리를 만들어 주는 서비스지만, 무료로 쓸 수 있는 범위가 꽤 다릅니다. 클로바더빙 무료는 매달 15,000자까지 쓸 수 있는 대신 수익이 생기는 채널에는 쓸 수 없고, 타입캐스트 무료는 처음에 주는 약 5분 분량의 다운로드로 끝나는 체험판에 가깝습니다. 광고 수익이 붙은 유튜브나 쇼핑몰 영상에 넣을 목소리라면 처음부터 유료 플랜 조건을 보고 고르는 편이 안전합니다. 왜 이 두 서비스를 같이 비교하나 쇼츠 내레이션, 수업 자료 더빙, 상품 소개 영상처럼 "내 목소리 대신 AI 목소리"가 필요할 때 한국 사용자들이 가장 많이 찾는 곳이 네오사피엔스의 타입캐스트 와 네이버의 클로바더빙 입니다. 기능 소개만 보면 비슷해 보이지만, 실제로 문제가 되는 건 음질보다 "이 목소리를 내 채널에 써도 되나" 입니다. 그래서 이 글은 기능 나열보다 무료 사용 범위, 출처 표기 의무, 유료 플랜 가격과 다운로드 한도를 중심으로 정리했습니다. 모든 수치는 2026년 10월 25일에 두 서비스의 공식 요금 페이지와 고객센터 도움말에서 직접 다시 확인한 내용입니다. 한눈에 보는 비교표 항목 타입캐스트 무료 타입캐스트 베이직 클로바더빙 Free 클로바더빙 Standard 월 요금 0원 9,900원 (연간 결제 시 10% 할인) 0원 19,900원 (네이버 클라우드 플랫폼에서 결제) 무료·포함 사용량 음성 생성·재생 무제한, 다운로드는 최초 3,000크레딧(약 5분) 1회 지급 월 30,000크레딧(약 60분) 월 15,000자, 다운로드 월 20회, 프로젝트 누적 5개 (매월 1일 갱신) 월 30,000자, 다운로드 월 40회, 프로젝트 누적 20개 쓸 수 있...