Cursor Build Live Apps lets you describe a web app in plain language, then have a cloud agent build it, host it and hand you a shareable link. Cursor announced it on November 5, 2026. If you already pay for Cursor with cloud agents turned on, you can try it now.
Quick facts first, so you can decide whether to keep reading:
- Announced Nov 5, 2026 in Cursor’s changelog.
- Works on all paid plans that have cloud agents enabled.
- The agent can add a Postgres database and sign-in behind Cursor SSO.
- Public sharing is limited to individual plans.
- Cursor’s changelog page lists no hosting prices.
The short version: you stay in Cursor from first prompt to live link, and a security check stands in the way before anything goes public.
How Cursor Build Live Apps works, from prompt to link
You start a cloud agent and describe what you want. The agent scaffolds the app, adds a Postgres database if it needs one, and puts sign-in in front of it using Cursor SSO. It also sets up hosting.
If the app needs something outside Cursor, such as a data warehouse, the agent asks you for the required secrets. When you’re ready, you pick a unique domain and Cursor returns a live link.
You aren’t limited to brand-new projects. Per Cursor’s changelog, you can deploy from new or existing repos on Cursor Origin and GitHub.
What changes compared with deploying by hand
Most small internal tools die in the gap between “it works on my machine” and “my team can open it.” The table below shows which chores Cursor now takes over.
| Step | Before | With Build Live Apps |
|---|---|---|
| Scaffold the app | You set up the project yourself | The cloud agent builds it from your prompt |
| Database | Sign up for a separate service | Cursor provisions Postgres if the app needs one |
| Sign-in | Wire up your own auth | Access sits behind Cursor sign-in |
| Hosting | Pick a host and deploy | Cursor hosts it and gives you a link |
| Pre-launch review | Whatever you remember to check | Automatic security checks before publish |
This matters most for dashboards, trackers and quick team tools. Those are the apps people rarely bother to deploy properly.
The security checks before anything goes live
Cursor runs both deterministic and agentic checks before publishing. They look for problems like secrets left in app files and exposed credentials.
The rule is simple: nothing goes live until the checks pass and you explicitly publish. Team admins get extra control too:
- See every app and secret on the team.
- Add custom rules to the security review.
- Approve a publish the review blocked.
- Unpublish any app.
That last point is the one to watch. AI coding tools have already had security trouble, as we covered in our EMBRACE vulnerability breakdown, so a review gate is welcome. It doesn’t replace reading what the agent built.
Limits to check before you rely on Cursor Build Live Apps
This is a first release, and the changelog is short on detail. Here is what it does say, plus what it leaves out.
- Git support covers Cursor Origin and GitHub only. GitLab and others are “coming soon.”
- Public sharing works only on individual plans, so team plans share inside the team.
- Shared apps sit behind Cursor sign-in, so outside visitors need access.
- The page doesn’t describe hosting limits, resource quotas or database options beyond Postgres.
The missing price is the biggest gap. Check your plan’s usage page before moving anything important onto it. Cursor is also part of a busy field of agent tools, like the one in our Conductor shutdown guide, so keep your code in a repo you control.
Who gets the most out of it
The sign-in wall and team sharing point to one clear audience: small teams that need a private tool fast. Think a status board, an approvals form or a simple report viewer that pulls from a data warehouse.
Solo builders get something different. On an individual plan you can share publicly, so a side project or demo can go live without you renting a server. Just remember the database and hosting are Cursor’s, not yours.
It’s a poor fit if you need a custom host, strict data residency or a code host other than GitHub. Cursor’s page says nothing on those points yet, so ask before you commit.
A sensible first test is an app with no sensitive data. Let the agent build it, read the code, run the security review and see how the publish flow feels. Then decide if it deserves a real project.
Frequently Asked Questions
Is Cursor Build Live Apps free?
No. It’s available on paid plans that have cloud agents enabled. Cursor’s changelog doesn’t give hosting prices.
Can anyone open the app I publish?
Not by default. Apps sit behind Cursor sign-in and can be shared with specific people, groups or your whole team. Public sharing is for individual plans only.
Which code hosts does it support?
Cursor Origin and GitHub for now. GitLab and other providers are listed as coming soon.
Can the agent publish something without my approval?
No. Cursor says nothing goes live until the security checks pass and you explicitly publish the app.
Should you try it?
If you already use Cursor and want a quick internal tool, yes, try it on a low-stakes project this week. Skip it for anything customer-facing until Cursor publishes pricing and limits. Review the code the agent wrote, because a passed check isn’t a guarantee.
Leave a Reply