# Siteshare

> Siteshare lets a web builder and their client build a website together, with AI instead of a CMS. The client is used to a CMS (WordPress, or Contentful at work); with Siteshare they skip it and change the site the builder made directly, by chatting, pointing at it or typing on the page, and permissions per client keep them from breaking it. The builder keeps building in the same code with their own AI. The client opens their own site at /edit, says what should change, and sees it in a preview. Publishing builds the site on a clean copy first and puts one commit on the builder's main branch on GitHub; the builder's own host deploys it. Siteshare does not host sites and needs no CMS.

## What it works 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. PHP, Ruby and Python are not supported.
- Any host that deploys from the main branch, such as Cloudflare, Netlify, Vercel or GitHub Pages.

## How a builder starts
1. Sign up at https://app.siteshare.dev/sign-in and connect GitHub (a GitHub App, on the repositories you choose).
2. Add a site. Siteshare starts it in a sandbox of its own and checks that it builds.
3. Invite a client by email. They sign in at their own site, at /edit, with a code from their email.

## Pricing (a price per site that drops as the team grows; VAT is added where it applies)
- Your first site: free, forever, without a card.
- The 2nd to 5th site: $9 a site a month or $90 a year (ten months for twelve), in the EU €9 or €90.
- The 6th to 20th site: $6 a site a month or $60 a year (ten months for twelve), in the EU €6 or €60.
- The 21st site and on: $4 a site a month or $40 a year (ten months for twelve), in the EU €4 or €40.
- For example 5 sites $36 a month, 10 sites $66, 20 sites $126. No plan to choose.
- Unlimited clients and builders. The assistant is unlimited on paid sites with fair use; the free site has about 30 assistant changes a month. Running 25+ client sites: talk to us.

## Pages
- [Product](https://siteshare.dev/product): the editor, publishing, history, what a client may change, security.
- [The editor](https://siteshare.dev/product/editor): chat, select, draw and browse on the real site; typing on the page; photos.
- [Publishing](https://siteshare.dev/product/publishing): the draft, the checks and the build before anything goes live; History and Restore.
- [Access and approvals](https://siteshare.dev/product/access): four levels per client, what stays protected, approvals, your team.
- [Under the hood](https://siteshare.dev/product/how-it-works): every part and where it runs, one change from chat to live, and measured load times per kind of site.
- [For clients](https://siteshare.dev/for-clients): the page a builder sends to a client.
- [Pricing](https://siteshare.dev/pricing)
- [Everything on one page](https://siteshare.dev/llms-full.txt)

## Who it's for
- [You built it for a friend. Let them run it.](https://siteshare.dev/for/hobby-builders): Built a site for a friend, a club or your partner's studio with AI? Let them change it themselves, for free: one site, one editor, no CMS.
- [Build fast. Hand over without a CMS.](https://siteshare.dev/for/freelancers): Build client sites fast with AI and hand them over without a CMS. Clients change texts, photos and pages; you keep the code. Five sites for $36 a month.
- [Stop selling hours for typo fixes.](https://siteshare.dev/for/marketing-agencies): Stop selling hours for typo fixes. Hand every client site over with Siteshare: clients edit by talking, your team keeps the code. 20 sites for $126 a month.
- [One way to hand over every site you build.](https://siteshare.dev/for/web-agencies): Many client sites, many stacks, one handover. Next.js, Astro, SvelteKit and more on GitHub, any host. Clients edit by talking; every publish is checked.
- [Campaign sites that change until the last day.](https://siteshare.dev/for/production-companies): Many campaign and event sites with short lives and late changes. Let the client's team edit them by talking, until the last day, without a CMS per site.
- [Developers build it. Marketing runs it.](https://siteshare.dev/for/marketing-teams): Developers build the company site in code; marketing changes it by talking. Drafts, approval for design changes, history and a log of every publish.
- [Landing pages in minutes, not sprints.](https://siteshare.dev/for/founders): Your site was built with Lovable, v0 or Claude Code and lives on GitHub. Add landing pages and change copy by talking to it, without waiting for a developer.

## Compared with other tools
- [Siteshare vs TinaCMS](https://siteshare.dev/compare/tinacms): TinaCMS gives editors forms and click-to-field editing on a schema you define. Siteshare lets clients change any part of the site by talking, with no schema.
- [Siteshare vs Decap CMS](https://siteshare.dev/compare/decap): Decap CMS is a free, open-source form editor on fields you configure. Siteshare lets clients change the real site by talking or pointing, without a config.
- [Siteshare vs Pages CMS](https://siteshare.dev/compare/pages-cms): Pages CMS is a free, open-source editor for content you describe in .pages.yml. Siteshare edits the site as your AI built it, nothing to describe.
- [Siteshare vs Decap Turbo](https://siteshare.dev/compare/decap-turbo): Decap Turbo hosts the open-source Decap CMS: auth, users and speed, priced per site and per seat. Siteshare counts only sites and needs no fields.
- [Siteshare vs CloudCannon](https://siteshare.dev/compare/cloudcannon): CloudCannon gives editors visual editing on regions you mark up and config you write, priced per user. Siteshare edits the site as built, priced per site.
- [Siteshare vs Sanity](https://siteshare.dev/compare/sanity): Sanity is a content platform with Studio, visual editing and AI for builds on its APIs. Siteshare adds an editor to the site you have, content stays in Git.
- [Siteshare vs Storyblok](https://siteshare.dev/compare/storyblok): Storyblok is a headless CMS with a visual editor: content in its cloud, blocks you define, an SDK in your code. Siteshare edits the code of the site you built.
- [Siteshare vs Payload](https://siteshare.dev/compare/payload): Payload is an open-source CMS and Next.js framework: collections in code, an admin panel, content in your database. Siteshare edits the site as you built it.
- [Siteshare vs Netlify Agent Runners](https://siteshare.dev/compare/netlify): Netlify Agent Runners lets team members prompt an AI agent to change a Netlify site. Siteshare gives clients an editor at their own site, on any host.
- [Siteshare vs CMS Brew](https://siteshare.dev/compare/cms-brew): Both let clients edit a site in Git by chatting, at the same price. CMS Brew keeps them to content values; Siteshare goes further, with your approval.
- [Siteshare vs CMS Chat](https://siteshare.dev/compare/cms-chat): CMS Chat and Siteshare both let clients edit a site in Git by chatting. The differences: drafts and a build check, selecting and drawing, and a free plan.
- [Siteshare vs Fimo](https://siteshare.dev/compare/fimo): Fimo is a platform for AI-built sites with hosting, a content layer and AI agents. Siteshare adds an editor to the site you built and leaves hosting to you.
- [Siteshare vs Lovable](https://siteshare.dev/compare/lovable): Lovable builds apps and sites from a prompt. To let a client change one, they join your workspace and use your credits. Siteshare gives them their own editor.
- [Siteshare vs v0](https://siteshare.dev/compare/v0): v0 builds and changes Next.js apps by chat, with a paid seat per collaborator and hosting on Vercel. Siteshare gives clients a free editor on any host.
- [Siteshare vs Bolt](https://siteshare.dev/compare/bolt): Bolt builds sites and apps by chat and hosts them on bolt.host. Siteshare gives the client a site is handed over to an editor of their own, on any host.

## Guides
- [The best CMS for Astro in 2026](https://siteshare.dev/guides/best-cms-for-astro): Ten ways to let editors change an Astro site in 2026, from free Git-based editors to headless platforms, with prices, setup and limits, checked October 2026.
- [The best CMS for Next.js in 2026](https://siteshare.dev/guides/best-cms-for-nextjs): Ten ways to let editors change a Next.js site in 2026: Git-based editors, headless platforms and visual builders, with prices and limits, checked October 2026.
- [WordPress alternatives for client sites](https://siteshare.dev/guides/wordpress-alternatives): Eight alternatives to WordPress for agencies and freelancers who hand sites over to clients: how clients edit, what it costs per client, and who owns the code.
- [How to let a client edit a site you built with AI](https://siteshare.dev/guides/let-a-client-edit-an-ai-built-site): You built the site with Claude Code, Cursor, Lovable or v0. Six ways to let your client change it themselves, and a handover checklist that keeps the code safe.
- [Do I need a CMS for my client's website?](https://siteshare.dev/guides/do-i-need-a-cms): Often not. If the content lives in the site's own code and goes to one website, an editor on the site is enough. When a CMS is the better choice, and why.
- [How to let a client edit a site you built with Claude Code](https://siteshare.dev/guides/client-edits-a-claude-code-site): Your site is code in a repository. Push it to GitHub, connect it to Siteshare, and invite your client: they edit the real site with a chat, you keep building.
- [How to let a client edit a site you built with Cursor](https://siteshare.dev/guides/client-edits-a-cursor-site): A site built in Cursor is code in a repository. Connect that repository on GitHub to Siteshare and your client edits the real site with a chat.
- [How to let a client edit a site you built with Lovable](https://siteshare.dev/guides/client-edits-a-lovable-site): Sync the Lovable project to GitHub, host it from there, and connect it to Siteshare. Your client edits without access to your Lovable workspace.
- [How to let a client edit a site you built with Codex](https://siteshare.dev/guides/client-edits-a-codex-site): Codex works on your GitHub repository. Connect that repository to Siteshare and your client edits the real site with a chat, while Codex keeps opening PRs.
- [How to let a client edit a site you built with v0](https://siteshare.dev/guides/client-edits-a-v0-site): Connect the v0 project to GitHub and to Siteshare. Your client edits the real Next.js site without a v0 seat, and Vercel builds what they publish.
- [How to let a client edit a site you built with Bolt](https://siteshare.dev/guides/client-edits-a-bolt-site): Sync the Bolt project to GitHub, host it from there, and connect it to Siteshare. Your client edits without a Bolt account or your tokens.
- [Cloudflare + Siteshare](https://siteshare.dev/guides/cloudflare-and-siteshare): Keep the site on Cloudflare. Your client edits it in Siteshare, and Publish is one commit on main that Cloudflare builds and takes live.
- [Netlify + Siteshare](https://siteshare.dev/guides/netlify-and-siteshare): Keep the site on Netlify. Your client edits it in Siteshare, and Publish is one commit on main that Netlify builds and takes live, without a Netlify seat.
- [Vercel + Siteshare](https://siteshare.dev/guides/vercel-and-siteshare): Keep the site on Vercel. Your client edits it in Siteshare without a Vercel seat or a headless CMS, and Publish is one commit on main that Vercel deploys.
- [Let clients edit a Next.js site without a CMS](https://siteshare.dev/guides/edit-a-nextjs-site-without-a-cms): Your client changes texts and images in a Next.js site where they are, in JSX or MDX. No schema, no headless CMS, and route handlers stay yours.
- [Let clients edit an Astro site without a CMS](https://siteshare.dev/guides/edit-an-astro-site-without-a-cms): Your client edits the real Astro site: texts in .astro pages and components, and entries in content collections. No CMS, no schema to describe twice.
- [Let clients edit a SvelteKit site without a CMS](https://siteshare.dev/guides/edit-a-sveltekit-site-without-a-cms): Your client edits texts in +page.svelte files and components on the real site. Server files, hooks and settings stay protected by default.
- [Let clients edit a Nuxt site without a CMS](https://siteshare.dev/guides/edit-a-nuxt-site-without-a-cms): Your client edits the real Nuxt site: texts in .vue pages and components, and Markdown in Nuxt Content. The server/ folder stays yours.
- [Let clients edit an Eleventy site without a CMS](https://siteshare.dev/guides/edit-an-eleventy-site-without-a-cms): Your client edits the Markdown and templates of an Eleventy site on the real site, with drafts and a build check. No Decap config to write.
- [Let clients edit a Hugo site without a CMS](https://siteshare.dev/guides/edit-a-hugo-site-without-a-cms): Your client edits the Markdown in content/ of a Hugo site on the real site, with drafts and a build check. A theme in themes/ works; Hugo Modules don't yet.
- [Let clients edit a plain HTML site without a CMS](https://siteshare.dev/guides/edit-a-plain-html-site-without-a-cms): A site of plain HTML files can't have a CMS without a rebuild. With Siteshare your client edits the HTML itself, with drafts and your approval for scripts.

## Docs
For builders, their clients and their AI coding assistant; every page also as plain Markdown.

### Start here
- [How it works](https://siteshare.dev/docs/how-it-works.md): What Siteshare does, where your site lives, and what happens from question to live site.
- [Getting started](https://siteshare.dev/docs/getting-started.md): Connect GitHub, add a site, check its settings and invite your client.
- [Supported sites](https://siteshare.dev/docs/supported-sites.md): Which sites Siteshare can run, and what to change when one is refused.

### For builders
- [Inviting clients and access](https://siteshare.dev/docs/inviting-clients.md): Invite a client, how they sign in, and changing or removing access.
- [What your clients can change](https://siteshare.dev/docs/client-steps.md): The four steps, what is protected by default, and approvals.
- [Approvals](https://siteshare.dev/docs/approvals.md): What happens when a client asks for more than their step, and how you decide.
- [Your team](https://siteshare.dev/docs/your-team.md): Builders, owners, and the owner of each site.
- [Plans and billing](https://siteshare.dev/docs/plans-and-billing.md): A price per site that drops as you grow, the assistant per site, failed payments and invoices.
- [Publishing and your repository](https://siteshare.dev/docs/publishing.md): The draft branch, what a publication puts on main, and what never happens.

### For your clients
- [Editing your site](https://siteshare.dev/docs/editing-your-site.md): Open your site, find your way around, and nothing goes live until you say so.
- [Chat, Browse, Select and Draw](https://siteshare.dev/docs/chat-select-draw.md): The four ways to say what should change.
- [Text and photos](https://siteshare.dev/docs/text-and-photos.md): Type on the page, replace a photo, and add new ones.
- [Publish](https://siteshare.dev/docs/publish.md): What happens when you publish, and what to do when it can't go ahead.
- [History and Restore](https://siteshare.dev/docs/history-and-restore.md): Look at earlier versions and bring one back.
- [When your builder needs to help](https://siteshare.dev/docs/builder-help.md): Your access, asking for more, and what only your builder changes.

### Reference
- [admin.json](https://siteshare.dev/docs/admin-json.md): Every field of a site's settings file, with examples and defaults.
- [For AI coding assistants](https://siteshare.dev/docs/ai-assistants.md): The link to hand a site to a client, what to tell your assistant, and admin.json.