Cursor Apps: Cursor’s Cloud Agents Can Now Build, Host, and Deploy Web Applications
Since November 5, a Cursor cloud agent can generate a web application, set up a Postgres database and authentication for it, and then deploy it to a chosen URL after passing security checks. The feature is available on all paid plans with cloud agents.
Cursor launched a feature dubbed Apps in its documentation on November 5, 2026: a cloud agent can now turn a prompt into a hosted web application shareable via a link. “Most applications never leave localhost,” the developer summarized in its changelog.
From Prompt to Link
Users must run a cloud agent and explicitly request an application; the capability does not exist locally. The agent generates the code, spins up a Postgres database if the application requires one, gates access behind Cursor authentication, and prepares the hosting environment. If the app needs to connect to an internal system (such as a data warehouse, in Cursor’s example), the agent requests the required secrets; according to the documentation, it never sees their actual values.
A preview panel lets users test the application. When it is time to deploy, the user selects the URL, which can be modified later. Repositories can be brand new (hosted on Cursor Origin) or existing projects on GitHub; GitLab support has been announced for a later release.
A Deployment Gate
The most notable aspect is the pre-deployment safeguards. Four automated checks run on every publish attempt, even if the security review is disabled: blocking hardcoded keys or tokens in files, blocking credential files, and excluding .env files and source maps. On top of that, an AI security review inspects the code and flags critical vulnerabilities. Nothing goes live unless these checks pass and the user explicitly clicks deploy.
At the team level, administrators can view all apps and secrets, enforce their own rules, approve blocked deployments, or unpublish an app. Sharing can be limited to invited individuals, the entire team, or set to public; public access is disabled by default on Teams and Enterprise accounts. Each team or user is allocated an isolated hosting account. While Cursor does not name its hosting partner, The New Stack reported that Vercel confirmed the feature runs on its Vercel for Platforms infrastructure.
Our take
Cursor is stepping onto the turf of Lovable, Replit, or Bolt, but from the opposite angle: rather than targeting the general public first, it targets internal tooling built by employees for their teams, with Cursor login acting as the default gate. The deployment gate tackles a very real issue: AI-generated apps pushed to production with exposed credentials or wide-open databases. However, it does not replace a manual audit, as an AI review remains an automated scan. Two questions remain unanswered for engineering teams: the usage-based pricing for hosting and databases—which neither the changelog nor the documentation clarifies—and how easy it is to export an app out of Cursor to host it elsewhere.
Sources
- Cursor — changelog “Build Live Apps in Cursor” (November 5, 2026) Primary source
- Cursor — Apps documentation (cloud agents) Primary source
- Cursor on X — announcement (November 5, 2026) Primary source
- The New Stack — Cursor takes on Lovable and Replit with fully managed app deployment Secondary source
A primary source comes directly from the company, lab or organization concerned. A secondary source reports the information without being its author: we flag it as such. Spotted an error? See our corrections policy.
