Skip the CMS
Your code is the content model.
Your client selects the heading on their own site and types. Siteshare changes the component where that text lives, so there is no schema to define and no second system to keep in sync.
Who needs a CMS anymore?
Texts, photos, sections, even new pages. You decide how far each client goes; the rest waits for your approval.
No credit card needed.Why Siteshare
You build sites in code now. You talk to Claude Code or Cursor until it's right, or write it yourself in VS Code. Then your client asks if they can change the opening hours themselves.

Your time back
The new opening hours, a team photo, a typo on the contact page. Your client changes it on their own site while you build the next one. You only hear about it when they go beyond what you allowed, and then approving takes one click.
How it works
Your part is done once: install the GitHub App on the repository, add the site, invite your client. Any Node or plain HTML site. Getting started
In your own words, in any language. Or point at it on the page.
The real site, with the change in it, before anyone else sees it.
One button. It's checked first, then it's live.
For your client
The assistant answers in the language your client writes in, and writes on the site in the language of the site.
"Add the new opening hours", "Put this photo with the second article". Said the way you'd say it to a person.
Point at a heading, a photo or a whole section. Click again for the block around it. Double-click a text to edit it right there, no AI needed.
Circle what's wrong, strike through words. The assistant knows which block and which words were meant.
Why it works
Skip the CMS
Your client selects the heading on their own site and types. Siteshare changes the component where that text lives, so there is no schema to define and no second system to keep in sync.
AI for your client too
The same kind of AI you build with, on their own site, in their own language. They see each step while it works.
Smart permissions
Text and images, blocks and pages, design, or everything: you choose per client. One click to approve the rest.
Checked first
Publish builds the site on a clean copy, then puts it on your main branch as one commit.
History
The last 10 versions, with who changed what. Restore one, and it comes back as a new version.
Works with
Built with
Built the site with an AI coding tool or an AI site builder? As long as the code is in a GitHub repository, Siteshare can work with it.
Runs
Siteshare runs your site the way you do, with your own packages. Any Node or plain HTML site.
Hosted on
Your host keeps publishing your main branch. Siteshare never hosts your site.
Or any host that deploys from GitHub.
Compared
Your client may ask for WordPress, or for what they use at work. This is how they differ.
| Question | Siteshare | WordPress | Contentful | Webflow | Framer |
|---|---|---|---|---|---|
| How your client edits | Chats, points at it or types on the page | Admin screens and the block editor | Forms in the Contentful web app | An editor on the page, for text and CMS items | Editing on the page and CMS forms |
| Set up before the client can start | Nothing: your code is the content model | A theme, post types and fields | Content types, wired into your code | CMS collections | CMS collections |
| A site you built with AI, in your own code | Yes: any Node or plain HTML site | No: a PHP theme | Yes, once you connect it | No: you build it in Webflow | No: you build it in Framer |
| Where the site lives | Your repository and your own host | A PHP host with a database | The content at Contentful, the site on your host | On Webflow | On Framer |
| What keeps the client from breaking it | Four levels per client, approval above that, and a clean build before anything goes live | Roles per user | Roles and field validations | Editors change content, not the design | Roles for collaborators |
As of October 2026, from each product's own site: WordPress, Contentful, Webflow, Framer. More in Compare.
A new way of working together
Your client changes the content when it suits them. You build what's new with your own AI. Both land on the same main branch, so there is no export, no sync and no handover, and each of you sees what the other did.
Monday, 14:10
Your client
Put our new opening hours on the contact page.
In the editor, by chatting
Published: one commit on main
Monday, 21:30
You
Build a booking form on the contact page.
In your own code, with Claude Code
Pushed to main, and into their draft
Tuesday, 09:05
Your client
The form is great. Add our phone number under it.
Your form is already in their editor
Published: one commit on main
Your client writes a sentence. You get a change in your code with that sentence as its message.
Pricing
Your first site is free. Unlimited clients and builders on every site, and the assistant with fair use. VAT is added where it applies.
$36/month
The first site free.
Running 25 sites or more? Talk to us about volume pricing, invoicing and your own brand.
Typing on the page is unlimited and doesn't count. When a site reaches its limit, only the assistant waits: typing and publishing go on, and your client never sees a payment screen.
Free for one site, forever. No card needed.