Product
Everything a CMS did. None of what it cost.
Your client is used to a CMS. Here they skip it: they change the real site at theirsite.com/edit by talking to it, and smart permissions make sure nothing breaks. You keep the code, the repository and the host.
Where it starts
From the site you built to a client who edits it.
- 01
Build it in code with your favorite AI. Then connect the repository.
Claude Code, Cursor, Codex or Lovable: any Node or plain HTML site in a GitHub repository. Install the Siteshare GitHub App on it and add the site. That's your setup, once.
- 02
Invite your client to the editor.
They open their own site with /edit at the end of the address, sign in with a code, and see the real site with a chat next to it. You choose what each of them may change.
- 03
Your client edits. You keep building.
They change texts and photos and press Publish. You keep building in the same repository with your own AI, as before.
The editor
Say it, point at it, or type it.
Chat in any language, select or draw on the real site, or type straight into the page.
Publishing
Nothing goes live that doesn't build.
A draft first, a clean build at Publish, one commit on main, and every version back with Restore.
Access and approvals
You decide what each client may change.
Four levels per client, protected parts by default, and approvals for anything above.
The editor
The chat on the left. Their own site on the right.
Not a copy, not a form: the real site, running in a sandbox of its own, with every change visible right away.
- Chat: say what should change, in any language.
- Select: point at a text, a photo or a section; click again for the block around it.
- Draw: circle or strike through what's wrong.
- Browse: use the site as a visitor would, menus and carousels included.
- Double-click a text to edit it right on the page, without the assistant.
- Photos: drop one in the chat or replace a selected one; it's resized for the site and gets a description.
Publishing
A draft first. Live when they say so.
Your client · yoursite.com/edit
Every change goes into a draft. Nothing is live yet.
Siteshare
Publish builds exactly what goes live on a clean copy.
Yours, as before
One commit on main. Cloudflare, Netlify, Vercel or any other host deploys it.
What a client may change
You decide, per client.
Four levels: Text and images (the default), Blocks and pages, Design and Everything. A change above a client's level is not refused: it waits for the owner of the site, who approves it, finishes it, or says no.
Approval
Above their level, it waits for you.
You get a mail with the page before and after. Approve it, reject it with a note, or finish it yourself. Until then it stays in their draft. More about access and approvals
History
Nothing is ever lost.
History shows the last 10 versions with who changed what. Look at any of them in the editor, and Restore it as a new version. Your main branch is never rewritten. More about History and Restore
Four safeguards on every change
Whoever makes the change, the client or their assistant, it passes all four.
- DraftYour client works on a draft branch, never on main.
- Clean buildBuilt on a clean copy of what goes live. If it doesn't build, nothing changes.
- ApprovalChanges above a client's level wait for the owner of the site.
- HistoryRestore is a new commit. The history of main is never rewritten.
Under the hood
Your repository and your host stay in charge.
Your client works on a draft copy in a sandbox. What passes the checks lands as one commit on main, and your host deploys it as always. Siteshare never hosts your site, and its content lives only in your repository.
Security
Your code stays yours.
Your repository is the only place your site lives. Siteshare is one of the things around it, and you can take it away without your site noticing. How we keep it safe.
A sandbox per site
Each site runs alone. The assistant can read and change that site's files, nothing else, and never sees its secrets.
Checks that don't trust the assistant
What may change and whether it builds is checked by the platform at Publish, whatever the assistant says.
Through a GitHub App
Access only to the repositories you choose. One commit per publish; no force pushes.
We don't host
Your host keeps deploying your main branch. If Siteshare were gone tomorrow, your site would not notice.
Sign-in without passwords
A code by mail, Google, or GitHub for builders. Every sign-in and publish is in the site's log.
Your data, briefly
Content lives in your repository, not with us. We keep names, addresses and the log, and delete them when you ask.
Questions
Is Siteshare a host like Netlify or Vercel?
No. Siteshare hosts nothing. It lets your client change the site and publishes as one commit on main in your GitHub repository; your host, such as Netlify, Vercel or Cloudflare, builds and serves the site as it always does.
Which sites does it work with?
Sites in a GitHub repository that run on Node or are plain HTML: Next.js, Astro, React + Vite, Vue / Nuxt, SvelteKit, Remix, Eleventy, Hugo, Gatsby, Plain HTML, and most others through a general route. PHP, Ruby and Python sites are not supported yet.
Does it change my repository?
Only when someone publishes: one commit on main with exactly what was approved. While your client works, the draft lives on a branch of its own. When you add a site, we offer to add one small page at /edit that leads to the editor; you can say no.
Which AI does it use?
Claude, through our own account. Neither you nor your client needs a key of your own, and the assistant only ever sees the one site it works on.
Can my client break the site?
Not live: a change that doesn't build is never published, and code, forms and scripts are protected unless you open them up. Anything that did go live comes back with Restore.
Hand it over. Get your evenings back.
Free for one site, forever. No card needed.