Your host
Vercel + Siteshare
Vercel hosts the site and deploys main to production. Siteshare lets your client change it and publishes as one commit on main. Add one line to vercel.json so Vercel skips the drafts. We tested this on 28 October 2026: the published change and the restore were in production on Vercel within minutes. Since 1 November 2026 your client also sees Live as soon as Vercel reports the deployment.
- 01
Host the repository on Vercel
Import the GitHub repository in Vercel, with main as the production branch.
- 02
Turn off previews of the draft branch
Vercel builds every branch, also commits marked [skip ci]. Add { "git": { "deploymentEnabled": { "concept": false } } } to vercel.json, with the name of Siteshare's draft branch.
- 03
Add the site to Siteshare
Install the Siteshare GitHub App on the same repository and add the site, or run npx siteshare connect in its folder.
- 04
On a private repository in an organization, allow Siteshare's commits
On Pro, Vercel deploys a private repository's commits only when the author is on your Vercel team, and Hobby can't deploy private repositories in an organization. Siteshare commits as Siteshare, so check that its deploys go through.
- 05
Invite your client
They open the site with /edit at the end of the address and sign in with a code.
| Question | Vercel | Siteshare |
|---|---|---|
| What it does | Builds the site from GitHub and serves it | Lets your client change the code, in drafts, and publishes |
| Your client's drafts | A preview per commit, unless you turn it off for the draft branch | A live preview of the draft on the real site |
| Publish | Deploys main to production | Builds a clean copy first, then one commit on main |
| Live | Reports the deployment on the commit in GitHub | Reads that report and tells your client when the site is live |
| Editing for clients | Edit Mode on Pro, with a headless CMS that supports Content Link | An editor on the site itself, no CMS, no Vercel seat |
A site you built with v0 or Next.js
Most sites on Vercel are Next.js, often built with v0 or another AI tool. Their texts sit in components, not in a CMS. Siteshare lets your client change them there, in a draft on the real site, and publishes one commit on main after a build on a clean copy. Vercel takes it from there.
Questions
Does Siteshare deploy to Vercel?
No. It only commits to main in your repository. Vercel sees the commit and deploys as it always does; Siteshare has no Vercel keys.
Why not Vercel's Edit Mode?
Edit Mode opens fields of a headless CMS from the page, on Pro and Enterprise. Your content has to live in that CMS first. Siteshare edits the site as you built it.
Does my client see when the site is live?
Yes. Vercel reports its deployment on the commit in GitHub, and Siteshare reads that report: your client sees Live as soon as Vercel is done, usually within a minute of Publish.
Hand it over. Get your evenings back.
Free for one site, forever. No card needed.