we_are_coded.by CODE · The world, decoded
БГ

Cognition · Builders

Devin Apps: you describe the internal tool, Devin builds it and puts it on a private address, and the bill runs while the machine is awake

On 13 November Cognition launched Devin Apps: you describe the tool, Devin builds it and puts it at an address you reach only by signing in to Devin. Billing follows how long the machine is awake. The announcement gives no prices, and by Cognition's own words the apps are not for high-traffic services.

Source
Cognition
Published
The event
Checked on
Responsible editor
Cvetelin Ivanov
How we work
MethodCorrections

The shared spreadsheet. That is exactly what Cognition names as something Devin Apps can replace. You describe the tool your team needs, Devin builds it, and the team opens it from a link, while the App is a private web application that lives on Devin's own cloud machine.

Fact

The facts: on 13 November 2026 Cognition announced Devin Apps - live, private web applications hosted directly on Devin's cloud computer. You create one like this: open Apps, describe what the App should do (there are also templates, such as a metrics dashboard, a project status page or a review queue) and choose Build with Devin. The App appears on the Apps page right away with its URL and has the status Building until the first version is live. Because they run on Devin's machine, Apps have access to your existing MCP, integrations and codebase. Everyone who opens an App has to sign in to Devin, and Apps are never public. You share with chosen people, with your organization or with your whole enterprise. Every change is a new version at the same URL; if a new version fails to start, the previous one keeps serving. The machine goes to sleep when nobody is using the App, the first load after a sleep can take a few seconds, and billing is based on how long the machine is awake. The stack is anything that serves HTTP on a port, and the database can be SQLite or Postgres on the same machine.

The sleeping is the most interesting detail. The App does not keep the machine running around the clock: it wakes when someone opens the link. The bill follows the awake time. What that comes to in practice, the page does not say, and it gives no prices.

A private address, one machine and a bill by awake time.

Cognition states the limit plainly. An App runs on one machine. It is a good fit for internal tools and dashboards, not for high-traffic production services. It is good that it says so, because this is not the place for your public site.

What teams build, by Cognition's list: admin panels, request forms, approval queues and small tools that replace a shared spreadsheet. Dashboards where Devin pulls from your own data sources and refreshes them on a schedule. And beta or staging copies of the product, with frontend, backend, database and workers, that teammates open from a link. The examples are Cognition's.

A dashboard that lives in a spreadsheet today is the right first candidate. One week of awake time will tell you more than the announcement.

The visual is generated code-art, no third-party images.