Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- Starting from scratch creates a Cursor Origin repository; existing GitHub repositories also work. GitLab support is still planned.
- Cursor provisions Postgres when an app needs a database. Private and team apps use Cursor sign-in.
- Individual plans can share apps publicly. Public sharing is off by default for Teams and Enterprise, with team admins controlling whether to enable it.
- Baseline checks run on every publish. An additional AI security review can block deployment, and admin overrides have explicit limits.
Who can use it? Check the plan and cloud agent access first
Cursor announced Build Live Apps in Cursor on November 5, 2026. Its Apps documentation says the feature is available on all paid plans with access to cloud agents. Team admins can also turn Apps off for their team, so a paid subscription does not establish that every workspace has it enabled.
A Cloud Agent runs the task in a remote environment. Apps is not supported by local agents. Being able to run an ordinary Agent on your computer does not establish that the same mode can publish an app. Check cloud agent and Apps availability in the workspace you intend to use.
The announcement and Apps documentation reviewed here do not list a universal additional hosting rate, database allowance, complete regional availability list or service level. Confirm the terms for your plan and billing before adopting it. Paid-plan availability does not establish free or unlimited hosting or access in every region, and a proxy cannot replace those requirements.
How does a request become a live website?
Explicitly tell a cloud agent to build an app and describe the task the page should support. For a hypothetical weekly dashboard restricted to your team, start with the fields to display and the intended audience. This example illustrates how to specify the request; no app was created or run for this article.
Starting from scratch creates a Cursor Origin repository. You can also ask the agent to deploy an existing GitHub repository as an app. The announcement labels GitLab support as coming soon. An editor integration with a repository provider does not establish that Apps already supports that provider.
When the app is ready, Cursor presents a preview and publishing tray. Review the content and data scope, then explicitly publish and choose the app URL, which can be changed later. Publishing starts the checks. Cursor returns a live link when they pass; otherwise, fix the reported issues and publish again. A preview does not automatically become a public website.
Who handles hosting, the database and secrets?
Cursor creates a dedicated hosting account for the team or individual plan, isolated from other teams' and users' hosting accounts. It automatically provisions Postgres, a PostgreSQL database, when the app needs one. Hosting account isolation does not establish that the app's own business permissions are correct. Check who can actually read and change each part of the app.
Connections to your own systems can use secrets configured during the build or in the Apps dashboard. The documentation says the agent never sees their values. A team admin usually creates team secrets; users with permission to create personal secrets can add their own. Keep secrets out of app files and shared URLs.
Platform-managed hosting and databases do not automatically establish connectivity to external services or replace their authorization, charges and data rules. Identify the connections the app needs before granting access. The reviewed documentation does not establish connectivity guarantees across all regions and networks.
Should colleagues sign in, or should anyone with the link get access?
A private app can be shared with specific team members and groups; team visibility extends access to the whole Cursor team. Visitors must sign in to Cursor. A link alone does not admit someone outside the allowed audience. Choose the intended scope, then verify access with an identity within that scope.
Public apps can be opened by anyone with the link without Cursor sign-in. Individual plans can share publicly. Teams and Enterprise disable public sharing by default, and a team admin can enable it in the Apps dashboard. If an admin disables public apps again, existing public apps move back to team visibility.
For a hypothetical dashboard containing internal data, keep access restricted to invited members or the team. Making the link public is not a fix for a sign-in problem. Publishing an app and making it public are separate decisions. Confirm the intended audience before changing visibility just because a preview worked.
What do publishing checks block, and what can an admin approve?
Four baseline protections run on every publish: blocking hardcoded keys or tokens in app files, blocking credential files, excluding .env files, and removing source maps. A source map connects compiled code to its original source. Removing it does not mean that all app logic becomes invisible to visitors.
An additional AI security review reads app files and can block serious issues. Team admins can add review instructions, but custom instructions cannot remove Cursor's built-in checks. The four baseline protections still run when the extra security review is off. Passing automated checks does not establish that an app is free of every risk.
Admins can see all app and secret entries on the team and unpublish any app. They can also control Apps availability, public sharing and API key access. The documentation allows admins to approve some publishes blocked by the review, but not malicious code, hardcoded secrets or exposed credentials. Changes to these settings are recorded in the team's audit log.
What should you check when a script cannot open a private app?
A script cannot simply complete the interactive Cursor sign-in protecting a private or team app. Cursor documents API key access for automated callers. Personal keys can open apps their owner can access; team keys can open only team apps explicitly shared with that key. A key does not automatically gain access to every app on the team.
An authorized caller must send the key in the x-cursor-app-token HTTP header on every request. The documentation does not support a query parameter or cookie as a substitute. A key without access gets the same sign-in redirect as an unauthorized user. Check whether the admin allows API key access, the key's scope and the request header before treating this as a network fault.
Requests made with a key are marked as automated and identify the key, rather than impersonating a person. No keys were created, real apps called or resources submitted for this article. Changing IP addresses does not remove app access controls. Continue with network troubleshooting only when there is evidence such as a DNS failure, TLS error or connection timeout.
Sources
Frequently Asked Questions
Does publishing an app guarantee long-term hosting or continuous availability?
No such guarantee follows from publication. The Apps documentation provides hosting as is and as available, and publication is not an endorsement by Cursor. Apps, subdomains or associated accounts may be revoked or suspended for applicable terms violations or business, financial or legal reasons. Check the applicable commitments and your own recovery arrangements if you need a long-term service.
Do I have to replace an existing data warehouse or other resource with Cursor's database?
The documentation allows you to bring your own resources and integrations, configuring their secrets during the build or in the Apps dashboard. Automatic Postgres provisioning is a platform capability for apps that need a database, rather than a requirement to migrate all existing data. Confirm compatibility and external-system permissions for each integration.