Case study
View case studyJamb
We rebuilt Jamb on Sanity and Next.js, merging two legacy PHP sites into one calm catalogue without losing the SEO equity their antique and reproduction collections had built up.

From Agility CMS to Tina CMS
Last verified:
Key pain points
The pricing is the elephant in the room. Starting at $1,249/month for the lowest tier, Agility is significantly more expensive than most headless CMS competitors. For smaller agencies or startups, that's a hard sell when platforms like Sanity or Contentful offer free tiers and more gradual scaling. If a client needs template customizations beyond what's available, those changes often require going through Agility's team at additional cost, which can slow things down.
The editor experience, while better than most headless CMS tools, still has rough edges. The content preview has a noticeable delay which frustrates editors used to real-time feedback. Component nesting can feel limited when building complex layouts, and creating unique page designs sometimes requires creating an excessive number of components as workarounds. The initial setup and configuration is also more involved than the marketing suggests, particularly for teams coming from traditional CMS platforms.
The ecosystem and community are noticeably smaller than competitors like Contentful or Sanity. There's less community-generated content, fewer third-party plugins, and Stack Overflow coverage is thin. When you hit an edge case, you're more reliant on the support team than community knowledge. The platform also lacks JSON field support in content models, which limits some advanced use cases that other headless CMS tools handle natively.

Expensive entry point
Starting at $1,425/month (billed annually) with no free tier, it's one of the priciest headless CMS options. Hard to justify for smaller projects or clients with lean budgets.

Slow content preview
Agility's own product page now markets 'Real-time Content Preview.' Whether the implementation matches the marketing claim should be validated with an active instance, but the vendor no longer positions preview as a lagging feature.

Steep initial setup
Despite marketing claims of simplicity, the initial configuration requires significant effort. Advanced features and custom setups demand real technical expertise.

Limited component nesting
Building complex, deeply nested layouts can feel restrictive. You often end up creating numerous individual components as workarounds for unique page designs.

Small community and ecosystem
Far fewer plugins, community resources, and Stack Overflow answers compared to Contentful or Sanity. When you hit edge cases, you're mostly on your own.

Missing JSON field support
No native JSON datatype in content models, which limits flexibility for advanced structured data use cases that other headless CMS platforms handle easily.
Key advantages
Tina CMS has a genuinely compelling core idea: real-time visual editing backed by Git. Instead of your content living in some opaque database, every change becomes a Git commit. For developer teams that already live in Git, this feels natural. The local development workflow is solid too — you can iterate on schema and content simultaneously, merge everything in a single commit, and keep your content pipeline tightly coupled with your codebase. That's a meaningful advantage over CMS platforms that treat content as a completely separate concern.
The inline editing experience is where Tina really shines. Content editors can see their changes in context on the actual live site, which dramatically reduces the feedback loop between "I changed something" and "here's what it looks like." For marketing teams and content creators who are tired of editing fields in a dashboard and then previewing on a separate URL, this is a breath of fresh air. It bridges the gap between developer-friendly and editor-friendly in a way that most headless CMS platforms don't even attempt.
Since going fully open-source under Apache 2.0 and being acquired by SSW, the self-hosting story has improved significantly. You can run your own backend with your own database and auth, which gives you more control than relying on TinaCloud. If you're building a Next.js or React-based project and want a CMS that lives close to your code, Tina is worth serious consideration. If you want help evaluating whether Tina fits your stack, or you're looking at alternatives, we're happy to chat.

Real-time visual editing
Editors can make changes directly on the live site with instant visual feedback. This is genuinely one of the best inline editing experiences in the headless CMS space.

Git-backed content workflow
Every content change becomes a Git commit, so your content versioning, branching, and collaboration all flow through the same tools your developers already use.

Schema defined in code
Content models are defined in your codebase alongside your components, keeping your content structure and frontend tightly aligned and version-controlled.

Strong local development experience
You can develop locally with full CMS functionality, iterate on schema and content together, and push everything in a single commit. No cloud dependency during development.

Markdown and MDX support
Tina works natively with markdown and MDX files, making it a natural fit for documentation sites, blogs, and any project that already uses file-based content.

Fully open-source and self-hostable
The entire backend is open-source under Apache 2.0. You can self-host with your own database, auth, and Git provider, giving you full control over your content infrastructure.
Tell us what you're building. We reply within one working day — Jono or someone on the team picks up every message personally.
Join the growing list of successful migrations