Cursor lets agents ship live apps. IT just became the bouncer

The dashboard takes an hour to build. It goes live three weeks later. Anyone on a marketing team knows that gap. The code was never the problem. Everything around it was.

What Cursor built

According to Cursor's changelog from November 5, its cloud agents can now build and publish complete web apps. You explicitly ask the agent for an app, it scaffolds it, sets up a Postgres database if needed and provisions hosting. Login runs through Cursor SSO. If the app needs access to another system, say a data warehouse, the agent asks for the credentials. At the end you pick a domain and get a live link. Cursor's own examples: dashboards, portals, microsites.

Before anything publishes, security checks run, for instance for credentials sitting in the code. Only what passes and what you explicitly publish goes live. Team admins see every app and secret, can add their own review rules, approve blocked publishes and take any app offline. Per the docs, public sharing is off by default for Teams and Enterprise. The feature is on all paid plans with cloud agents.

Shadow IT gets a control room

Here's what I find interesting: Cursor isn't selling faster coding here. It's selling the last mile. Hosting, database, login, secrets. Exactly where internal tools built by business teams usually die, or quietly end up on someone's personal account.

I build my own website, funnel and dashboard with Claude. From where I sit, the code is now the easy part. The hard part is where the thing runs, who maintains it and who gets to switch it off. Cursor answers the first two with its own platform and the third with an admin console.

The bottleneck moves to approval

Translation: marketing ops can build its own campaign dashboard, lead routing tool or event microsite. IT goes from builder to bouncer. It no longer decides what gets built, it decides what's allowed to go live. That's a different job, and many IT teams don't have rules for it yet.

The catch

The apps run on Cursor's infrastructure, which is a new dependency. The changelog doesn't give pricing, limits or hosting details. And whoever ships an app owns it: updates, bugs, the person people call. An agent builds fast, but it doesn't maintain anything on its own.

What I'd do now

• Write an approval rule with IT before the first team starts: what can go live internally, what needs review, what's off limits.
• Name an owner for every app. No app without a person accountable for it.
• Start small: one internal reporting dashboard, nothing that exposes customer data externally.

Bottom line: When anyone can build software, code stops being scarce. Accountability doesn't.