Cursor now builds and hosts live web apps with Postgres and sign-in

Cursor has added a feature that lets its cloud agents turn a plain-language request into a working web application, host it, and return a shareable link. The company announced the capability on November 5, 2026 in its changelog under the title "Build Live Apps in Cursor", and the accompanying documentation calls the feature Apps. A user describes the app to a cloud agent, and Cursor scaffolds the code, creates a Postgres database when the app needs one, puts authentication behind Cursor sign-in and provisions hosting. When the app is ready, the user picks a unique address, Cursor runs a set of security checks, and only after an explicit publish step does the app go live.

The feature is available on all paid plans that have cloud agents enabled. Under the current pricing that Cursor calls The X Subscription, cloud agents start with the Premium plan at $30 a month and are included in Super ($100), Ultra ($200), Teams and Enterprise, while Free and the $8 Plus plan do not include them. Users on the legacy Start, Pro, Pro+ and Ultra plans also keep cloud agent access, according to Cursor's help pages. Apps can be built from a new repository on Cursor Origin or from an existing GitHub repository; support for other providers such as GitLab is described as coming soon.

The documentation lists dashboards, portals and microsites as typical examples of what the agents can build, and the default sharing model keeps every app behind Cursor sign-in unless an individual user or a team admin chooses to make it public. Cursor has published no price for hosting or for the database, and no storage or traffic limits.

··········

⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣

HOW CURSOR APPS TURN A CLOUD AGENT PROMPT INTO A HOSTED APP.

The workflow starts in a cloud agent, and Cursor's documentation states that app creation is not supported in local agents. The user starts a cloud agent session and says explicitly that the goal is an app. From that point the agent writes the application code, decides whether it needs persistent storage and, if so, provisions a Postgres database. It also sets up authentication so that visitors have to sign in with a Cursor account before the app opens. If the app has to reach outside systems, such as a company data warehouse in Cursor's own example, the agent asks the user for the credentials it needs instead of guessing or hardcoding them.

While the agent works, Cursor shows a tray where the user can preview the app before anything is exposed. At publish time the user chooses the URL, which can be changed later. Cursor then runs its checks and either returns a live link or a list of problems for the agent to fix, after which the user asks the agent to correct them and publishes again. The changelog puts the rule plainly: "Nothing goes live until the checks pass and you explicitly publish the app."

Each app runs inside a dedicated hosting account that Cursor creates for the team, or for the individual on a personal plan. The documentation says that each hosting account is isolated from every other team's and user's account. Cursor has not named the cloud provider behind the hosting or the regions where apps and databases run, which leaves open questions for companies with data residency requirements.

Secrets are handled outside the code. Cursor prompts for the values an app needs, and the documentation states that the agent never sees them. In a team, admins usually create shared team secrets in the Apps dashboard, and users with the right permission can add personal secrets. Teams can also connect their own resources and integrations and configure the keys either during the build or later from the dashboard.

··········

CURSOR APPS AVAILABILITY BY PLAN AND PRICE.

Cursor ties Apps to cloud agent access rather than to a separate subscription. The table below combines the plan prices published on Cursor's pricing help page with the cloud agent eligibility stated in its cloud agent documentation, both checked on November 6, 2026.

........

Plan	Monthly price	Cloud agents	Cursor Apps
Free	$0	Not included	Not available
Plus	$8	Not included	Not available
Premium	$30	Included	Available
Super	$100	Included	Available
Ultra	$200	Included	Available
Teams	$30, $100 or $200 per seat	Included	Available, public sharing off by default
Enterprise	Contact sales	Included	Available, public sharing off by default
Legacy Start, Pro, Pro+, Ultra	Unchanged	Included	Available

........

Annual billing is listed at $300 a year for Premium, $1,000 for Super and $2,000 for Ultra, with Plus at $80, all excluding tax. Cloud agents draw on the same plan usage as Agent in the editor and the CLI, at the rate of the model selected, so the work an agent does while building an app counts against the subscription's included usage like any other agent task. On legacy request-based plans, cloud agents always run in Max Mode and are charged at API rates plus the Max Mode upcharge. Cursor has not said whether hosting, database storage or app traffic will be billed separately in the future, and the current documentation contains no figure for any of them.

For readers comparing Cursor's subscription with other coding agents, our guide to AI coding agent pricing across Cursor, Claude Code, Codex and GitHub Copilot sets out the plans side by side.

··········

SHARING, SIGN-IN AND API KEYS FOR CURSOR APPS.

Every app has one of three visibility settings, and only one of them lets visitors in without a Cursor account. The documentation describes them as follows.

........

Visibility	Who can open the app	Sign-in required
People you invite	You plus chosen team members or groups	Yes, Cursor account
Team	Everyone on your Cursor team	Yes, Cursor account
Public	Anyone with the link	No

........

On individual plans, users can share an app publicly without any Cursor authentication. On Teams and Enterprise, public sharing is disabled by default and only a team admin can enable it from the Apps dashboard. If an admin later disallows public apps, existing public apps move back to team visibility.

Apps can also be opened by software. A user can provision a Cursor API key so that a script, a CI job or Grok Bot can call the app. Personal keys open the apps their owner can open, team keys open only the team apps they have been granted, and public apps accept either kind of key as they would any visitor. The key must be sent in the x-cursor-app-token HTTP header; the documentation states that query parameters and cookies are not supported. Requests made with a key are marked as automated and are attributed to the key rather than to a person, and a key without access receives the same sign-in redirect as an unauthorized user. Team admins can turn key access off entirely.

··········

[[ADPLUS_300x250_1]]

CURSOR APPS SECURITY CHECKS AND ADMIN CONTROLS.

Four deterministic checks run before every publish and cannot be switched off, even when the AI review is disabled. Publishing is blocked if a file in the app contains an API key or access token, or if the app includes credential files such as private keys, service-account keys or files holding auth tokens. Environment files ending in .env are never published, and source maps are removed so that visitors cannot read the original source code.

On top of those checks, an AI security review reads the app's files and blocks what it judges to be serious issues. Team admins can add their own instructions to that review prompt. Cursor specifies that custom instructions can add rules but cannot remove its built-in checks. If the review blocks a publish, an admin can approve it anyway, except where the problem is malicious code, a hardcoded secret or an exposed credential.

The admin controls cover the full lifecycle of a team's apps. Admins can turn Apps on or off for the whole team, allow or forbid public apps, allow or forbid API keys, see every app and every secret on the team, and unpublish any app. Changes to these settings are written to the team audit log. Cursor's terms for the feature say hosting is provided "as is" and "as available", that publishing is not an endorsement, and that apps can be revoked or suspended for breaches of the terms or the Acceptable Use Policy, or for business, financial or legal reasons.

··········

HOW TO PUBLISH A FIRST APP WITH CURSOR CLOUD AGENTS.

A team that wants to try the feature needs a paid plan with cloud agents and, for organizations, an admin who has left Apps enabled. Cloud agents themselves require an environment created in the Cloud Agents dashboard, where the user connects a Git provider, selects repositories and adds any secrets or environment variables. Cursor's documented sequence for an app then runs in five steps.

1. Start a cloud agent from Cursor (by choosing Cloud in the agent input), from cursor.com/agents or from another supported entry point, and state that the task is to build an app.

2. Describe the app, its data sources and who should use it; the agent scaffolds the code, a Postgres database if needed and Cursor sign-in.

3. Supply any secrets the agent requests, or have a team admin create them as team secrets in the Apps dashboard.

4. Preview the app in the tray, choose its URL and publish; if the checks fail, ask the agent to apply the listed fixes and publish again.

5. Set visibility to invited people, team or public, and create an API key if a script or bot needs to reach the app.

Teams already running agent work in the cloud through other tools will recognize the pattern. GitHub took a similar route when it let Copilot run cloud tasks from JetBrains Air on the user's Copilot plan, with the difference that Cursor now also hosts the result and controls who can open it.

··········

⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁤

CURSOR LIVE APPS: CONFIRMED FACTS AND OPEN QUESTIONS.

The confirmed part of the launch is well documented. Cursor cloud agents can build an app from a prompt, provision Postgres and Cursor sign-in, take secrets without exposing their values to the agent, and publish to a chosen URL after four mandatory checks and an AI review. Apps are available on every paid plan with cloud agents, which today means Premium at $30 a month and above plus Teams, Enterprise and the legacy plans. Deployment works from Cursor Origin and GitHub repositories, and organizations keep public sharing off unless an admin enables it.

Several practical details remain undisclosed. Cursor has not published any price or quota for hosting, database storage or traffic, has not named the hosting provider or regions, and gives no size limit for the Postgres databases it creates. The supported frameworks and stacks are not listed in the documentation, and the GitLab support mentioned in the changelog has no date. For teams deciding whether to move internal dashboards onto Cursor-hosted apps, those missing figures, together with the terms that let Cursor suspend apps for business reasons, are the points to settle with Cursor before relying on the feature for anything business-critical.

··········

FOLLOW US FOR MORE.

·····

DATA STUDIOS

·····

datastudios.org