Cursor now builds and hosts internal web apps from a prompt, with sign-in, a database and a security check before anything goes live
On 5th Nov'26 Cursor added Apps to its cloud agents on all paid plans. You describe a tool, such as a sign-ups dashboard or a bug tracker, and the agent builds it, sets up a Postgres database if it needs one, hosts it in an account Cursor creates for your team, and puts it behind Cursor sign-in. Before anything is published, fixed checks block secrets in the app's files, credential files, .env files and source maps, and an AI review reads the code and blocks serious issues; admins can add rules to that review but cannot remove the built-in checks. Public links are off by default on Teams and Enterprise plans. Cursor has not published pricing or limits for Apps, and its terms say hosting is provided as is.
What it actually means
The hard part of an internal tool built outside engineering was never the screens, but where it runs and who can open it. Cursor now handles both, and its publish check is the safeguard Apiiro found missing in Claude Code's settings files, because it stops a key written into the code before the app goes live rather than after a scan finds it.
If you run operations or marketing, pick one spreadsheet your team updates by hand and ask Cursor to turn it into a team-only app this week. Ask your admin first who can see what, since admins can view every app and secret on the team, and check where the data lives before you point it at customer records, because the documentation does not say how you move the database elsewhere if you leave.
An internal tool was always easy to draw; the hard part was where it runs and who can open it, and Cursor now handles both.
Source: Cursor · Sunday, 8 November 2026