Who needs a CMS anymore?

Build your site in code.
Connect your repo.
Let your clients edit.

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

Building in code got easy. Handing it over didn't.

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.

Until now

You keep doing it yourself

Every new photo and every typo becomes an email to you. Too small to bill, big enough to break up your afternoon.

Until now

You move it onto a CMS

WordPress from the start, or Decap or Sanity bolted on later. Before your client can change a word, you move every text out of your code and describe every field.

Now

Or you use Siteshare

Keep building in code as you do now. Your client opens their own site, changes the opening hours, swaps a photo or adds a section. Anything beyond what you allowed waits for you.

What
An editor with AI on your client's own site, at theirsite.com/edit.
For
Web builders and agencies who build sites with AI and hand them to clients.
Not
A host or a site builder. Your site stays in your GitHub repository and on your own host.
Price
Your first site free, forever. Then $9 a site a month, down to $4 as you grow.

Your time back

Stop babysitting your clients.

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.

  • Nothing goes live that doesn't build. Publish checks the site on a clean copy first.
  • Design and code are closed by default. A change above your client's level waits for you.
  • Any of the last 10 versions comes back with Restore.

How it works

Your client says it, sees it, and publishes it.

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

  1. 01

    Say what should change

    In your own words, in any language. Or point at it on the page.

  2. 02

    See it on your own site

    The real site, with the change in it, before anyone else sees it.

  3. 03

    Publish

    One button. It's checked first, then it's live.

For your client

Talk, select or draw. Whatever comes naturally.

The assistant answers in the language your client writes in, and writes on the site in the language of the site.

Chat

"Add the new opening hours", "Put this photo with the second article". Said the way you'd say it to a person.

Select

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.

Draw

Circle what's wrong, strike through words. The assistant knows which block and which words were meant.

Why it works

No CMS in between. Nothing to break.

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.

AI for your client too

They ask, it changes.

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

Above their level, it waits for you.

Text and images, blocks and pages, design, or everything: you choose per client. One click to approve the rest.

Checked first

Nothing goes live that doesn't build.

Publish builds the site on a clean copy, then puts it on your main branch as one commit.

History

Every version comes back.

The last 10 versions, with who changed what. Restore one, and it comes back as a new version.

Works with

The tools you already build with.

Built with

Made with your AI tool

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.

  • Claude Code
  • Cursor
  • Codex
  • Lovable
  • v0
  • Bolt

Runs

Your framework, as it is

Siteshare runs your site the way you do, with your own packages. Any Node or plain HTML site.

  • Next.js
  • Astro
  • React + Vite
  • Vue / Nuxt
  • SvelteKit
  • Remix
  • Eleventy
  • Hugo
  • Gatsby
  • Plain HTML

Hosted on

Wherever it lives now

Your host keeps publishing your main branch. Siteshare never hosts your site.

  • Cloudflare
  • Netlify
  • Vercel
  • GitHub Pages

Or any host that deploys from GitHub.

Compared

Next to the CMS your client knows.

Your client may ask for WordPress, or for what they use at work. This is how they differ.

Siteshare next to WordPress, Contentful, Webflow and Framer
QuestionSiteshareWordPressContentfulWebflowFramer
How your client editsChats, points at it or types on the pageAdmin screens and the block editorForms in the Contentful web appAn editor on the page, for text and CMS itemsEditing on the page and CMS forms
Set up before the client can startNothing: your code is the content modelA theme, post types and fieldsContent types, wired into your codeCMS collectionsCMS collections
A site you built with AI, in your own codeYes: any Node or plain HTML siteNo: a PHP themeYes, once you connect itNo: you build it in WebflowNo: you build it in Framer
Where the site livesYour repository and your own hostA PHP host with a databaseThe content at Contentful, the site on your hostOn WebflowOn Framer
What keeps the client from breaking itFour levels per client, approval above that, and a clean build before anything goes liveRoles per userRoles and field validationsEditors change content, not the designRoles 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

One site, two people, the same code.

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.

  1. Monday, 14:10

    Your client

    Put our new opening hours on the contact page.

    In the editor, by chatting

    Published: one commit on main

  2. 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

  3. 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

Every change, from both sides

Your client writes a sentence. You get a change in your code with that sentence as its message.

What your client sees
What you see

Pricing

Pay per site. Less per site as you grow.

Your first site is free. Unlimited clients and builders on every site, and the assistant with fair use. VAT is added where it applies.

Your first site

One site of your own, or your first client.
$0 forever
  • About 30 assistant changes a month
  • Unlimited clients and builders
  • No card needed
Start free

The 2nd to 5th site

Your next clients.
$9/montha site
  • The assistant is unlimited on paid sites, with fair use
  • Unlimited clients and builders
Get started

The 6th to 20th site

Less a site as you grow.
$6/montha site
  • The assistant is unlimited on paid sites, with fair use
  • Unlimited clients and builders
Get started

The 21st site and on

However many more.
$4/montha site
  • The assistant is unlimited on paid sites, with fair use
  • Unlimited clients and builders
  • From 25 sites, talk to us about invoicing
Get started
5 sites

$36/month

The first site free.

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.

Hand it over. Get your evenings back.

Free for one site, forever. No card needed.