Git-based CMS
Siteshare vs TinaCMS
Both keep content in your Git repository. TinaCMS gives editors forms and click-to-field editing on collections you model; Siteshare lets them change the site by talking to it, without a schema.
| Question | Siteshare | TinaCMS |
|---|---|---|
| What it is | An editor at the client's own site, /edit, on the site you built | An open-source, Git-backed headless CMS with an editor at /admin |
| How someone edits | Chat, select or draw on the real site; double-click to type | Forms in a sidebar; visual editing with click-to-field where wired up |
| Setup in your code | None: a GitHub App on the repository | A schema in tina/config.ts, plus useTina and tinaField for visual editing |
| Where content lives | Your repository | Your repository (Markdown, MDX, JSON) |
| Before it goes live | A draft, a build check on a clean copy, then one commit on main | Each save is a commit; an editorial workflow on paid plans |
| AI | An assistant per site, built in | Listed as coming soon on the pricing page |
| 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 | Free (2 users), Team $24, Team Plus $41, Business $249 a month, per project |
The difference: a schema, or none
TinaCMS starts from a content model. You describe collections and fields in tina/config.ts, and editors get forms for exactly those fields, with click-to-field editing where you wire it up with useTina and tinaField. That is precise and predictable, and it is work: every editable part has to be modelled first.
Siteshare starts from the site as it is. There is no schema. The client points at a heading, a photo or a whole section, or just says what should change, and the assistant edits the code where that text or image actually lives, including texts inside components that no CMS field reaches.
Safety before speed
In TinaCMS each save is a commit. In Siteshare every change is a draft first; publishing builds the exact files on a clean copy, and only a site that builds gets one commit on main. Clients also have a level: by default they change text and images, and anything beyond waits for your approval.
Price
Tina charges per project, with seats per plan. Siteshare charges per site, less a site as you grow, with clients and builders without limit.
When TinaCMS is the better choice
- You want structured, typed content with collections and GraphQL queries.
- Editors should fill well-defined fields, like blog posts or product entries.
- You want an open-source CMS you can self-host.
Questions
Can I use TinaCMS and Siteshare on the same site?
Yes. They both work through your repository: Tina for the collections you modelled, Siteshare for everything else on the page, such as texts inside components.
Does Siteshare need a content model like Tina's collections?
No. The assistant reads your components and changes them the way you wrote them, so texts inside an .astro or .tsx component are editable too.
Hand it over. Get your evenings back.
Free for one site, forever. No card needed.