Skip to main content
v2026.11,986 entries · CC-BY 4.0

Editorial · CASRAI · AI and ML research outputs

Cognition launches Devin Apps for private hosted internal tools

Cognition announced Devin Apps on November 13, adding private hosted tools with Devin sign-in, sharing controls and a gradual rollout.

Published 16 Nov 2026· 5 minute read

Ask CASRAI · free to try

Ask about this story

2 free questions a day, no account.

An AI assistant for research: funder rules, compliance, methods and publishing. It links the sources behind its answers and labels answers that come from a web search.

Answers draw on CASRAI's guides and dictionary plus the federal and funder documents we index: Federal Register, Grants.gov, Regulations.gov and UKRI.

Works on this site and inside Claude, Cursor and the AI tools you already use.

Everything CASRAI publishes — this page, the dictionary, the guides and the news — stays open to read, with no account and no card.

CASRAI is the reference for research administration — bookmark it for the next question.

Cognition announced Devin Apps on November 13, 2026, adding private web applications built and hosted on Devin’s cloud computer. Teams can describe an internal tool and share its link with permitted users. For university researchers and research offices, the development brings dashboards and administrative prototypes into the coding agent’s hosted environment.

Devin adds hosted applications to its coding sessions

In its launch announcement, Cognition describes a workflow in which Devin asks clarifying questions, builds an application and puts it online. Starting templates include metrics dashboards, project status pages and review queues. Apps can use the team’s existing codebase, integrations and Model Context Protocol connections, according to the company.

The change builds on Devin’s existing browser previews. The preview documentation describes private links to HTTP applications running inside a session, with access following the session’s permissions. Apps make that work discoverable through an Apps page, with their own sharing settings and deployment history. Cognition distinguishes a preview used to inspect work in progress from an App intended for continued team use.

Private access has defined sharing boundaries

Every visitor must sign in to Devin. The Apps product guide says applications cannot be made public. General access can cover specific permitted users, an organization or all organizations within an enterprise. The narrowest setting also includes the creator and organization administrators. Additional permissions determine who can open an App, change its settings or share it.

Sulat’s November 14 report highlights these authentication and sharing restrictions alongside the stable application link. This matters for university collaboration: a URL alone does not provide anonymous access. A public recruitment page or open research demonstration would therefore fall outside the documented access model. An internal team dashboard is closer to the uses Cognition describes.

Cognition says changes produce a new deployment without changing the App’s URL. If a new version fails to start, the previous version continues serving. The documentation also describes git commits for deployments and keeping database files and uploads outside the rebuilt application folder. Those mechanisms give teams a version history to examine alongside code review for research software.

The service remains tied to a Devin session. Archiving or ending that session takes the App offline, and a crashed server does not restart automatically, according to the product guide. These are distinct conditions from a failed update leaving an earlier version running. Each App runs on one machine; Cognition positions the feature for internal tools and dashboards and directs high-traffic production services toward the team’s own infrastructure.

Sulat also reports the sleep-and-wake behavior: the machine sleeps five minutes after its last request and wakes on a visit. The first load after sleeping can take a few seconds. Hosting usage follows the machine’s awake time, while building or changing the application is normal session work.

Early coverage focuses on integration and authority

In its November 13 analysis, explainx.ai’s Yash Thakker emphasizes the implications of attaching a web interface to a session that already has repositories, connectors and secrets. His analysis centers on reviewing those access boundaries before extending an App across an organization. That is an assessment of the architecture described by Cognition, rather than evidence of institutional deployment results.

The company’s API documentation supplies a specific distinction behind that concern. Its authentication guide says personal access tokens operate with their creator’s identity and permissions. Service user keys instead operate as separately assigned non-human identities. The Apps guide warns that when an App uses a personal token, its users act with that token owner’s permissions. Signing in to view an App and authorizing its downstream actions are consequently separate questions.

What the launch means for research offices

For researchers, the documented prototype and staging uses offer a way to show colleagues a working interface. For research administrators, forms, approval queues and status dashboards suggest possible small workflow applications. These are illustrative applications of the published feature set, not reports that universities have adopted Devin Apps or achieved measured productivity gains.

The operational implication is that research data governance extends beyond deciding who receives the link. An office considering a shared tool would also need to understand which connected services it can use, whose authority it exercises and who maintains its session. The stable address does not remove those dependencies. The distinction between a prototype and an ongoing service also connects to the responsibilities described in research software engineering.

Automated maintenance adds another dependency. Cognition’s Automations documentation describes scheduled and event-driven triggers that can start or message sessions. The launch materials apply that capability to refreshing data and redeploying Apps after branch changes. For a research-office dashboard, the relevant distinction is between keeping the interface available and running the work that refreshes its underlying information.

Availability remains a gradual rollout

The Apps guide says the feature is rolling out gradually: accounts without Apps in the sidebar have not yet been enabled. The announcement therefore establishes a released capability with limited rollout, rather than availability to every Devin account. For teams evaluating it now, account enablement and the documented hosting limits define the immediate scope of the launch.

Sources

Referenced across the research world

University of Cambridge logoColumbia University logoCrossref logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logoUniversity of Cambridge logoColumbia University logoCrossref logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logo
  • University of Cambridge logo
  • Columbia University logo
  • Crossref logo
  • University of Edinburgh logo
  • Harvard University logo
  • University of Oxford logo
  • Princeton University logo
  • Stanford School of Medicine logo
  • University College London logo
  • ORCID logo

View CASRAI adoption →