Cursor now ships your app: database, sign-in and hosting included
Read in : Français

Contents
- What did Cursor launch on November 5, 2026?
- What security checks run before an app goes live?
- How much does it cost and who can use it?
- Why does this matter if you vibe code?
- It's built for teams first
- You rely on hosting you don't control
- The Lovable and Replit comparison shifts
- What to do next
- Frequently asked questions
- Frequently asked questions
- Sources
Since November 5, 2026, Cursor doesn't just write the code: it puts it online. The new "Build live apps" feature has a cloud agent build the app, add a Postgres database, set up sign-in and host it at a URL you choose. It's a direct move into Lovable and Replit territory, with one big difference: the main target is internal team tools.
What did Cursor launch on November 5, 2026?
Cursor now lets you describe an app and get a shareable link, without setting up hosting, a database or authentication yourself. The changelog starts from a blunt observation: agents made code cheap to write, yet most tools people build "never leave localhost."
Here's how it works, according to the changelog and official docs:
- You start a cloud agent and explicitly ask it to build an app. The feature isn't available with local agents.
- The agent scaffolds the web app, adds a Postgres database if needed, puts private and team apps behind Cursor sign-in and provisions hosting.
- If the app needs an outside system (a data warehouse, say), Cursor asks you for the secrets. The agent never sees their values.
- A preview appears. Nothing goes live until you publish.
- At publish time, you choose a unique URL and get a live link.
The code can come from a new repo on Cursor Origin, Cursor's code hosting platform, or from an existing GitHub repo. GitLab is "coming soon." Each app runs in a dedicated, isolated hosting account, created per team or per individual plan.
What security checks run before an app goes live?
Cursor blocks publishing until automatic checks pass. Four checks always run, even with the AI review turned off:
- secrets (API keys, access tokens) written in app files are blocked;
- credential files (private keys, service-account keys) are blocked;
.envfiles are never published;- source maps are removed.
On top of that, an AI security review reads the app's files and can block serious issues. Team admins can add their own rules, but can't remove the built-in checks, and can approve a blocked publish, except for malicious code, hardcoded secrets or exposed credentials.
How much does it cost and who can use it?
The feature is included in paid plans that come with cloud agents. Cursor hasn't published separate pricing for hosting or databases, and neither the changelog nor the docs list quotas, resource limits or hosting regions.
| Cursor individual plan | Monthly price | Cloud agents |
|---|---|---|
| Free | $0 | no |
| Plus | $8 | no |
| Premium | $30 | yes |
| Super | $100 | yes |
| Ultra | $200 | yes |
Prices taken from Cursor's official pricing page in November 2026, excluding tax. Teams starts at $30 per user per month.
So for an individual, access starts on the Premium plan. For the full picture of what a live app costs, read what a vibe-coded app really costs.
Why does this matter if you vibe code?
Deployment was where many Cursor projects stalled. Cursor has been the tool for people who want real code (see our Cursor review), while Lovable and Replit kept the all-in-one edge with built-in databases and hosting. That gap is shrinking.
Three things to keep in mind before you switch:
It's built for teams first
The examples Cursor gives are internal tools: event registration, desk seating, onboarding portals, sales dashboards. Private and team apps require Cursor sign-in. Only individual plans can share publicly by default; on Teams and Enterprise, public sharing stays off until an admin enables it. For an internal tool that replaces a spreadsheet, that's a great fit. For a consumer SaaS with its own customer accounts, less so.
You rely on hosting you don't control
The docs say hosting is provided "as is" and that Cursor can remove an app for terms violations or for business, financial or legal reasons. On Enterprise, a retention period can be set: inactive apps get unpublished, and their secrets and databases can't be recovered after that. Keep your code in a repo you own and export your data.
The Lovable and Replit comparison shifts
If you were torn between an app builder and an editor, the question becomes "who needs to sign in to the app?" rather than "who can handle deployment?" Our Lovable vs Bolt vs Replit comparison and the vibe coding tools comparison will help you decide.
What to do next
If you have a Cursor plan with cloud agents, here's a low-risk first test:
- Pick a small internal tool with no sensitive personal data.
- Write a precise request for the cloud agent:
Build an internal web app for booking meeting rooms.
- Users: members of my Cursor team only
- Data: rooms (name, capacity), bookings (room, date, time slot, author)
- Rule: users can only edit or delete their own bookings
- No secrets in the code; if a key is needed, ask me for it
- Before suggesting a publish, list the tables you created and who can read or write each one
- Test the preview with two different accounts: check that one user can't edit another user's booking.
- Read the check report at publish time and fix what it flags instead of asking an admin to force it through.
- Keep visibility on "team" until you've verified access rules.
And if your project needs to live outside Cursor, the usual options still apply: see Vercel, Netlify or shared hosting.
Frequently asked questions
Frequently asked questions
Can Cursor host my application now?
Yes. Since November 5, 2026, Cursor can host apps built by its cloud agents, with a Postgres database and a URL chosen at publish time. The feature is limited to paid plans with cloud agents. Each app runs in an isolated hosting account. Cursor hasn't published separate pricing or resource limits for this hosting.
Do my app's users need a Cursor account?
For a private or team app, yes: access goes through Cursor sign-in. Individual plans can make an app public, so anyone with the link can open it. On Teams and Enterprise plans, public sharing is off by default and must be enabled by an admin. Cursor API keys also let scripts and bots call the app.
Does Cursor Apps replace Lovable or Replit?
Not for every project. Cursor Apps mainly targets internal team tools protected by Cursor sign-in. Lovable and Replit are still designed for public apps with their own users and documented hosting prices. If your app needs outside customers with their own accounts, compare both approaches before moving anything.
Are Cursor's security checks enough?
No. They block secrets written in code, credential files, .env files and source maps, and an AI review looks for serious issues. They don't guarantee that each user only sees their own data. Test access rules yourself with several accounts before you open the app to anyone.
Can I use this feature on the free plan?
No. The feature requires a paid plan with cloud agents. According to Cursor's pricing page in November 2026, cloud agents aren't included in the Free and Plus plans and start with Premium at $30 a month for an individual user, excluding tax.


