Git-based CMS
Siteshare vs CloudCannon
Both keep content in your Git repository. CloudCannon gives editors visual editing on the regions you mark up, plus content and data editors, set up in a cloudcannon.config file; it charges per user, not per site. Siteshare edits the site as your AI built it, with no config, and charges per site with clients unlimited.
| Question | Siteshare | CloudCannon |
|---|---|---|
| What it is | An editor at the client's own site, /edit, on the site you built | A Git-based CMS with visual, content and data editors |
| How someone edits | Chat, select or draw on the real site; double-click to type | On the page in Editable Regions, or in forms |
| Setup in your code | None: a GitHub App on the repository | A cloudcannon.config file and Editable Regions in your templates |
| Where content lives | Your repository | Your repository |
| What a client may change | Four levels per client; anything above waits for your approval | What you configure and mark as editable |
| Price | Free for 1 site, then $9 a site a month, down to $4 as you grow (5 sites $36, 20 sites $126); clients and builders unlimited | Standard $55 a month with 3 users, Team $350 with 15; $10 a month per extra user; sites unlimited |
Marked up, or found
CloudCannon’s visual editing works on what you prepare: you add Editable Regions to your templates and describe collections in a config file. That gives editors a precise, predictable interface, and it is work you do per site.
Siteshare starts from the site as it is. Your client points at a heading or a photo, or says what should change, and the assistant edits the code where it lives. Nothing is marked up first, which suits a site you built with AI and want to hand over the same day.
Price per user, or per site
CloudCannon’s plans count users, with unlimited sites. Siteshare charges per site, less a site as you grow, with unlimited clients and builders. If your client’s whole team should be able to edit, a price per site doesn’t grow with them.
When CloudCannon is the better choice
- You run many static sites and want one fixed, field-level editing interface for all of them.
- Your editors are a small, steady team, so a price per user works out cheaper than per site.
- You want content and data editors with fields you define, next to visual editing.
Questions
Is CloudCannon cheaper than Siteshare?
It depends on what you count. CloudCannon charges per user and not per site, so many sites with a few editors is cheap. Siteshare charges per site and not per person, so a site where the client invites colleagues costs the same.
Do I have to mark up my templates for Siteshare?
No. Siteshare finds the text where it is, including inside components, without regions or config.
Hand it over. Get your evenings back.
Free for one site, forever. No card needed.