Publish a website built with Cursor: Git to Hostbrid Projects

Cursor can help you write and review a website, but a preview in the editor is not a public address. To publish the project, keep its code in a supported repository, check which services it needs, and configure a deployment with your hosting provider.

The local editor, a Cloud Agent and a public URL

When you use Cursor Desktop with a local folder, the project stays on your computer until you send it to a Git repository. Cursor’s documentation explains how to review changes, sync and push with Git.

Cursor Cloud Agents can work with connected GitHub, GitLab, Bitbucket and other source-control providers. They can also forward ports so you can preview an app while it runs in their environment. That preview is for development; it is not a production website.

Cursor Cloud Agents’ Publish button connects a Vercel project, deploys its default branch and returns a URL. It requires a Vercel account. To publish on Hostbrid, use the repository workflow in Projects; do not assume that Cursor’s button deploys here.

1. Review the project before you push it

In Cursor, check the branch and diff before committing. Identify the framework and the actual commands in package.json. If you downloaded a ZIP from another tool, extract it and create or connect a Git repository: Projects connects repositories and does not accept the ZIP directly.

Check .gitignore and keep .env and files containing keys out of the repository. A variable that reaches browser JavaScript is not a secret. If the application uses an API, authentication or a database, note which service provides it and how it will authorise the new domain.

2. Publish the repository through Projects

Make sure the project is in GitHub, GitLab or Bitbucket and that you can access the branch you intend to publish. In Hostbrid Projects, connect the repository, select the production branch and review its install, build and output settings. For a Vite project, for example, the generated folder is often dist, but the repository’s actual configuration takes precedence.

For a reproducible recipe with a real React and Vite example, see the Git deployment and browser-routing guide. If your application needs a Node process or containers, check the runtime and plan limits before deploying it.

3. Test the URL before pointing your domain

Open the temporary address from another device. Load an internal route directly, reload it, and test forms, login and API calls. Review the logs and confirm that no keys are exposed. A successful build does not prove that external services work.

Once the project responds correctly, configure the domain and check HTTPS and redirects. Review the current Projects plans to choose an option that fits its requirements.

Cursor writes and maintains code; Git carries the changes; Projects runs the deployment from the repository configuration. This guide covers that workflow, not a one-click Cursor-to-Hostbrid integration or a deployment tested on a customer account.