Cursor Apps Will Build, Host and Publish It for You. Read the Data Section First.
TL;DR: Cursor apps now go from a sentence to a live link. Describe what you want, and a cloud agent scaffolds it, provisions a Postgres database, sets up sign-in and hosts the result on a domain you choose. Four security checks run before anything publishes and an admin cannot switch them off. The gap is on the other side: the documentation says nothing about where your database lives, whether it is backed up, or how to delete it.
What cursor apps actually do
Cursor announced this on 5 November: “Now, you can build live apps directly in Cursor and share them with a link.”
The cursor apps flow, from Cursor’s documentation:
- Be explicit. Start a cloud agent and say you want to build an app. Note that “this feature is not supported locally” — this only runs in Cursor’s cloud.
- The agent provisions the boring parts. “Cursor handles the hosting, database, auth, and secrets.” If the app needs storage, “Cursor provisions a Postgres database for it automatically.” Each app gets “a dedicated account it creates for your team, or for you on an individual plan.”
- Preview, then publish. “Nothing goes live before you choose to publish.” You pick the URL, “which you can change later”, and Cursor returns a live link.
You can also point it at code you already have — “Deploy this repo as an app” works on an existing GitHub repository. GitLab is listed as coming soon.
This is the same movement we saw when Replit let non-engineers open pull requests on a company codebase: the agent takes over the parts that used to require a developer. The difference is that cursor apps do the hosting too.
The four cursor apps checks you cannot turn off
This is the part of cursor apps worth praising, and it is unusual enough to say so plainly. Before a publish succeeds, four checks run — and the docs say they are “always on, even when the security review is off”:
- Block secrets written in app files. A publish stops if a file contains an API key or access token.
- Block credential files. Private keys, service-account keys, files with auth tokens.
- Never publish `.env` files.
- Never publish source maps.
On top of that, “an AI security review reads the app’s files and blocks serious issues before the app goes live.”
Team admins get some override power, but not unlimited: they can “approve publishes the review blocked, except for malicious code, hardcoded secrets, or exposed credentials.” And custom rules are additive only — “Custom instructions can add rules, but they can’t remove Cursor’s built-in checks.”
After a week in which the news was mostly about safeguards that quietly failed to cover people, a vendor shipping guardrails that an administrator cannot disable is a genuinely good sign.
One more detail worth knowing: when the app needs a secret, “Cursor prompts you for the secrets it needs”, and “the agent never sees the values.”
What the cursor apps documentation does not say
Now the other side of cursor apps, and this is why you should read before you build something real on it.
Where your database lives. Cursor provisions a Postgres database for you. The documentation does not say which provider or region hosts it. There is nothing on backups. Nothing on deletion — how to get your data out or make it go away. Nothing on data residency, which matters if you have UK or EU customers.
What “see every secret” means. Both the changelog and the docs say “team admins can see every app and secret on the team.” Neither says whether an admin can read a secret’s value or only see that one exists. Those are very different things if your admin is a colleague rather than you. We could not resolve it from Cursor’s published material.
The hosting terms are candid, and worth reading twice. Cursor’s availability section says hosting is provided “as is” and “as available”, and that a published app “may be revoked, terminated, removed, or suspended … for business, financial, or legal reasons.” That is normal language for a new product. It is also not what you want underneath a thing customers depend on.
If “Postgres”, “source maps” or “data residency” are unfamiliar, our vibe coding glossary covers them.
Who gets to see your app
Three cursor apps sharing levels, per the docs:
- People you invite — specific members and groups, signed in to Cursor.
- Your whole team — everyone on the Cursor team, signed in.
- Public — “anyone with the link”.
Two things follow. Private and team apps sit behind Cursor sign-in, so anyone you share with needs a Cursor account — fine for colleagues, awkward for clients. And public sharing is treated differently by plan: individual users can share publicly without Cursor auth, while for Teams and Enterprise “public sharing is disabled by default” until an admin enables it.
Should you build on cursor apps?
- Internal tool for your business: yes, this is the sweet spot. Colleagues already have accounts, the sign-in requirement is a feature rather than friction, and the publish checks cover the mistakes people actually make.
- A quick thing to show someone: yes. A live link in an afternoon is exactly what this is for.
- A revenue app with customer data: not yet. Not because of the security checks, which are good, but because of the silence on backups, deletion and residency — and because “as is, as available” is the wrong foundation for something people pay for.
- Client work: check the sign-in requirement first. If your client will not create a Cursor account, you need public sharing, and on a team plan that needs an admin.
- No idea yet: the 60-second Tool Finder quiz will tell you whether you want a builder that hosts for you or one that hands you the code.
Our take
The security engineering in cursor apps is better than the category norm, and we would rather see a vendor ship four non-negotiable checks than a configurable system nobody configures. Cursor has clearly watched what goes wrong when people publish quickly.
What is missing is the unglamorous half: the lifecycle. Every tool in this space is excellent at the first hour and vague about month eighteen, and the thing that bites people is not a leaked key on day one — it is the app still running two years later with data in it that nobody can account for. That is the failure we described in the app you built and forgot, and the documentation for cursor apps does not yet answer it. Build internal tools on this today. Wait for the data answers before you build a business on it.
Not sure whether you want a builder that hosts for you? Take the 60-second Tool Finder quiz →
Some links on this page are affiliate links. If you buy through them we may earn a commission at no extra cost to you.
FAQ
What do cursor apps cost?
Cursor says Apps is available on all paid plans with access to cloud agents. The documentation does not state usage limits, quotas, or whether a running app consumes metered usage, so budget on the assumption that cloud agent work is billed as usual.
Do people need a Cursor account to open my app?
For private and team apps, yes — they sit behind Cursor sign-in. Public sharing does not require Cursor auth, but it is available to individual plans by default and disabled by default on Teams and Enterprise until an admin turns it on.
Can I use cursor apps with my existing code?
Yes. Cursor can deploy from new or existing repositories across Cursor Origin and GitHub — the documentation’s example prompt is “Deploy this repo as an app.” Support for other providers such as GitLab is listed as coming soon.
