CMS vs Tina · comparison

Norcube CMS vs Tina.io — framework-coupled vs framework-agnostic

Tina.io embeds a React-based visual editor inside your app (Next.js, Astro with their adapter). Norcube CMS is a separate hosted editor that reads any markdown frontmatter, regardless of framework. We diverge on integration depth: Tina goes deep into your codebase; we stay out of it. AI scaffolds your schema on our side; you write Tina's by hand.

No code in your repo Framework-agnostic (any markdown SSG) AI scaffolds the schema
Short verdict

When each wins

  • Pick Tina.io if you want in-place editing rendered by your actual React components (their visual editor renders your Next.js page and lets you click into fields); if you're committed to a Tina-supported framework and welcome the deep integration; if you want the editor to ship with your build, not be a separate hosted service.

  • Pick Norcube CMS if you don't want a Tina SDK / adapter / wrapper in your codebase; if your stack is Hugo / Eleventy / Jekyll / Hexo (Tina has limited or no support there); if you want AI scaffolding instead of writing the schema by hand.

The headline trade: Tina's visual editor is closer to true preview-first editing today (because it renders your actual components), at the cost of significant code in your repo. We ship a clean external editor; preview-first is on the roadmap.

Details

Side-by-side on what matters

Code footprint. Tina lives in your repo — tina/ config dir, @tinacms/cli, adapter packages per framework, route handlers. Norcube CMS is just .norcube/cms/ YAML in your repo; no JS, no adapter, no framework-specific package.

Schema authoring. Both are schema-driven. Tina's schema is TypeScript (tina/config.ts); Norcube's is YAML. Tina expects you to write the schema by hand; Norcube's AI scaffolds it from your existing markdown.

Framework support. Tina officially supports Next.js, Hugo (limited), Remix, Astro (limited). Norcube CMS reads any markdown with YAML / TOML frontmatter — Astro, Hugo, Eleventy, Jekyll, Hexo, Zola, and the long tail. No framework SDK required.

Visual editor model. Tina renders your actual Next.js page and overlays editable regions. Norcube CMS renders typed inputs from the schema in a separate UI. Tina's model is closer to preview-first today; ours catches up when the sandboxed-container preview ships.

Pricing. Tina Cloud has free + paid tiers per project + contributor counts. Norcube CMS is free during the private beta; paid tiers ship at GA without per-seat fees.

Ready when you are

Visual editing without code in your repo

No adapter, no SDK, no framework lock-in. AI scaffolds the schema, the editor reads your existing markdown. Free during the private beta.

Pay as you go No annual lock-ins
No credit card Start building now
Setup in 5 min Any service, any stack
Free tier forever No expiry, no tricks
// tick. tick. tick.
0 ticks since founding