Case Study
View Case StudyTray.ai
Migrating hundreds of thousands of pages, re-platforming and extending for the leading composable AI integration platform

From Contentful to Tina CMS
Last verified:
Key pain points
Contentful is one of those platforms where the bill can catch you off guard. The free tier caps you at 25 content types and 100K API calls, and a single marketing site can blow past both without warning. The next step up is $300 a month, and enterprise pricing often lands in the $50K to $100K+ a year range.
Users on Reddit regularly flag the same thing: tier jumps are forced by hitting one limit, not by needing the bigger feature set. Content model caps alone can push you into a higher plan you don't otherwise need.
The other issue is that Contentful has strong opinions about how content should be modelled, and those opinions aren't always documented. Projects built without that knowledge tend to accumulate performance problems and awkward workarounds. Before writing Contentful off, speak to us, a lot of the pain we see is implementation, not platform.

Pricing climbs fast
Contentful isn't a cheap CMS. Once you pass the free tier's content type or API call limit, you're on the $300/month Lite plan, and enterprise pricing often starts at $50K+ a year.

Complex for non-technical users
Marketers and editors may need a small learning curve before they feel at home. It’s powerful but not always plug-and-play.

Integration dependency
A lot of magic happens through third-party tools. Great for flexibility, but it does mean extra setup instead of getting everything out-of-the-box.

Limited native features
Contentful keeps the core CMS clean and minimal, but that also means more building and configuring to get advanced functionality.

Learning curve for new teams
If your team is moving from a traditional CMS, expect some onboarding time. Structured content is amazing but new for many.

Requires careful management
Because it’s so flexible, projects need good governance. Without it, content models can get messy and harder to maintain over time.
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.
Fill out the form below and we'll get back to you
Join the growing list of successful migrations
Case Study
View Case StudyMigrating hundreds of thousands of pages, re-platforming and extending for the leading composable AI integration platform

Case Study
View Case StudyFrom Sanity overages to instantaneous publishing, we brought Mario Testino into the fast lane, and did it in style.

Case Study
View Case StudyHelping the UAE's most prolific Pay in 4 merchants scale their design system and composable infrastructure.

Case Study
View Case StudyHow we helped the fastest growing online cycling community, push the editorial velocity to new heights.
