TinaCMS is an open-source, Git-backed headless CMS for teams whose websites already live in Markdown, MDX, and JSON. Instead of a proprietary database, content stays in files beside your code, and editors change it through a visual editing interface on the site's own /admin route, with every save committed back to Git.[1][2]
Quick verdict
Teams with Markdown-driven sites who want editors working visually without giving up Git will get the most from TinaCMS. Its Apache-2.0 core edits Markdown, MDX, and JSON through a live preview with every save committed to version control, self-hosted or on TinaCloud from $0. The price is framework and Node.js ownership plus paid tiers for SSO and advanced governance, so non-technical teams should choose a hosted SaaS CMS instead. If your developers live in React and your content lives in Git, start with the free tier and evaluate Team or Enterprise separately.[1][2][3]
Key features
Visual editing with live preview: React sites get real-time on-page editing so content editors see changes as visitors will.[1]
Git-backed Markdown, MDX, and JSON storage: no database to manage, with content in plain files versioned by Git.[1][2]
Commits on every save: editor changes in the /admin route are committed back to your Git repository for review.[1]
Queryable GraphQL content API: the backend serves file content with filtering, searching, and pagination.[1][2]
Content modelling in code: collections defined in tina/config.ts shape the editing experience for each content type.[1]
Local-files development mode: developers can run TinaCMS against local files for a fast feedback loop.[1]
Pluggable self-hosted backend: replaceable auth provider, database adapter, and Git provider deploy to Vercel, Netlify, or any Node.js serverless environment.[1]
Editorial workflow on paid cloud plans: structured review and approval plus shareable drafts for non-technical publishing teams.[1][2]
Who will love it
Docs and marketing-site teams on Markdown: writers get a friendly editor while developers keep content as versioned files.[1][2]
React and Next.js shops: visual editing, framework starters, and serverless deployment fit that stack directly.[1][2]
Organizations wanting to own their content: GitHub-backed storage with pull-request review keeps every change auditable.[1][2]
Who should avoid it
Non-technical teams with no developers: setup, backend configuration, and hosting need framework and Node.js skills, so a hosted SaaS CMS serves them better.[1][2]
Buyers needing SSO or advanced governance on day one: SSO, custom roles, and the API sit on the Enterprise tier, not the free core.[1]
Teams wanting every cloud feature while self-hosting: the docs state some TinaCloud features are unavailable in self-hosted setups.[1]
Switching and coexistence
Strapi teams wanting database-driven modelling: Strapi builds REST and GraphQL APIs from a no-code content-type builder, so TinaCMS trades that for Git-native file content with visual editing.[1]
Proprietary-database lock-in is the stated thing to leave: the docs name WordPress, Contentful, and Sanity as the databases TinaCMS does not lock you into.[1]
Questions worth asking
How much does TinaCMS cost per month?
The self-hosted core is free under the Apache-2.0 license, so the license itself costs 0 dollars; you still pay for hosting, database, and operations. Managed TinaCloud starts at $0 for the Free plan with 2 users, then $24 per project per month for Team, $41 for Team Plus, and $249 for Business, all billed annually with monthly options. Enterprise is custom-priced. Prices checked October 13, 2026, in USD.[1][2]
Can you self-host TinaCMS?
Yes. The self-hosting docs describe running the TinaCMS backend on your own stack with your own database, authentication, and Git integration, exposing a GraphQL endpoint from a Node.js serverless function. Start from the Next.js self-hosted starter for Vercel or wire the auth provider, database adapter, and Git provider into your own setup. Note that some TinaCloud features are unavailable when self-hosting.[1][2]
Does TinaCMS support single sign-on?
SSO exists but only on the Enterprise plan, alongside GitHub Enterprise support, custom roles, and a custom editorial workflow. Free, Team, Team Plus, and Business plans list no SSO, so teams needing single sign-on should budget for the Enterprise tier.[1]
Should I choose TinaCMS or Strapi?
Choose TinaCMS if your content already lives in Git as Markdown or MDX and your editors want visual, on-page editing with pull-request review. Choose Strapi if you want a database-backed CMS where editors model content types in a no-code builder served over REST and GraphQL. Both are open-source and self-hostable, so the deciding factor is Git-native file content versus database-driven content modelling.[1][2]
Sources and editorial review
Source research. Reviewed on October 13, 2026. Written by Sanjib Sah. AI assisted; reviewed by a human editor.
We have not run or tested this product.
- TinaCMS homepage: open-source headless CMS with visual editor
official · Observed October 13, 2026
tina.io presents TinaCMS as the open-source headless CMS with a visual editor for Markdown; nav covers TinaCMS, TinaDocs, TinaCloud pricing and enterprise, editorial workflow, quickstart via npx create-tina-app, and a v4 roadmap post.
- TinaCMS documentation: what is TinaCMS
official · Observed October 13, 2026
Docs define TinaCMS as an open-source Git-backed headless CMS: no proprietary database, content as Markdown/MDX/JSON in Git, queryable content API with filtering/search/pagination, TinaCloud hosted backend, self-hosted option, /admin route editing with commits back to Git, tinacms init setup, local-files dev mode and tina/config.ts collection modelling.
- TinaCMS plans and pricing
official · Observed October 13, 2026
TinaCloud pricing in USD: Free $0 forever with 2 users and 2 roles; Team $24/project/month with 3 users; Team Plus $41 with 5 users plus editorial workflow; Business $249 with 20 users, 3 roles beta and API beta; Enterprise custom with SSO, GitHub Enterprise support, custom editorial workflow and API.
- TinaCMS self-hosting documentation
official · Observed October 13, 2026
Self-hosting docs: run the TinaCMS backend on your own stack with own database, authentication and Git integration; GraphQL endpoint compatible with Node.js serverless environments; Next.js starter deployable to Vercel; modules for auth provider (Auth.js default), database adapter (MongoDB, Postgres) and Git provider; some features unavailable versus TinaCloud.
- About TinaCMS: the Git and Markdown CMS
official · Observed October 13, 2026
About page: TinaCMS is a developer-friendly, fully open-source CMS powered by Git and Markdown with live previews, real-time editing, GitHub integration, no database to manage, local development and content in .md files with pull-request review via the editorial workflow.
- tinacms/tinacms LICENSE
official · Observed October 13, 2026
Repository LICENSE is the Apache License Version 2.0 with copyright and patent grants for reproduction, derivative works and distribution.
- tinacms/tinacms GitHub repository
official · Observed October 13, 2026
Canonical repository tinacms/tinacms describes TinaCMS as the leading open-source headless CMS supporting Markdown and visual editing with content stored in the user's own GitHub repo.
- tinacms/tinacms root package manifest
official · Observed October 13, 2026
Repository root manifest shows a pnpm/turbo TypeScript monorepo requiring Node 22 or 24 with React 18 packages, vitest and vite tooling.
Compared with these products
No explicit proprietary baseline is recorded.