01One remote, then business as usual
The whole setup fits in one sentence: add a remote to the repository your Cursor project already is. The pillar guide covers what the host does on its side; from the editor's side, nothing else changes. Cursor proposes changes, you accept, the files update. When the site should go out, someone pushes to the remote, and the deploy is already underway before you switch windows.
Anyone with repository access can be the pusher: you, a teammate, or Cursor itself when you ask it to commit and push. All the host sees is the branch that received the push; whoever typed the command stays invisible to it.
02Two ways to push, both valid
Straight to main
The fastest loop. Every push goes live once the build validates, and rollback covers mistakes. For a small site with one reviewer, that is usually coverage enough.
Branch, then merge
Cursor works on a feature branch, you read the diff in a pull request, and merging is what publishes. One review step slower, and nothing unreviewed reaches visitors. Deployments follow main only.
03What belongs in the push
Push the files visitors receive. For plain HTML that is the whole folder; for a framework project it is the built output, which Cursor can generate and commit for you before pushing. What never goes live: the dev server, node_modules, and anything the site expects to call at runtime on a server, because the serving side is static. If a feature works on localhost and breaks after deploy, the usual culprit is exactly that: your machine was playing the role of a backend.
The same source-versus-output decision appears in the Claude Code flow, and the answer is the same in both.
04The limit of the loop
Deploying from Cursor does not give the editor eyes on the result. It cannot browse the live site or read the deployment history, and rollback is a portal button rather than an editor command, so checking each release stays a human job. That is the trade in a setup where the editor stays ordinary and the host stays out of sight: the last mile is yours.
Some people want the agent to verify its own work in production before anyone looks. Honest answer: no host hands that over today, and we will not claim otherwise. For the longer view of this pairing, the Cursor hosting guide covers what the setup feels like months in.
05Deploying from Cursor
Do I need a Cursor extension?
There is nothing to install. Git is the integration, and Cursor already speaks it fluently.
My repo is already on GitHub. Half done?
Yes. Connect it at signup and the next push deploys. Nothing needs migrating.
Can I keep the site in a monorepo?
The host deploys the repository you connect, from the branch it follows. Keeping the deployable site in its own repository makes the question disappear.
What happens to my address if I leave?
The repository is yours, so another static host can serve the same files. The address belongs to the service, as with any host.
Price after the trial?
$39 a month after fourteen free days, cancelled in the portal whenever you like.
Build it with your AI. Host it here.
Deploys on every push, from Australia, with nothing to maintain.