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

From Tina CMS to Dato CMS
Key pain points
Tina's biggest limitation is that it's fundamentally tied to the React ecosystem. If you want visual editing, you need a React-based framework like Next.js. Basic content editing works with Astro, Hugo, SvelteKit, and others, but the flagship visual experience is React-only. There's been talk of Vue support for years, but nothing has materialised. This is a hard blocker for agencies like us that work across different tech stacks. The platform has also had a notable history: SSW acquired the project in May 2024, and a security breach in late 2024 involved compromised AWS keys via the CI/CD pipeline. These events, combined with the relatively small community, are worth weighing when evaluating Tina for long-term enterprise projects.
On the practical side, developers report frustrating instability in the dev environment. The admin interface can break without any changes to your codebase because it depends on externally loaded assets that update independently. Error handling is weak — forms fail to save silently, and the GraphQL layer doesn't surface errors cleanly. Self-hosting removes the TinaCloud dependency but comes with its own gaps: no search functionality, no Git LFS support, and reference fields can timeout on large collections.
The editing experience, while impressive in demos, can feel fragile in production. Multiple developers have reported losing work in the editor, and features like branch-based editing are locked behind paid tiers. For agencies managing multiple client projects, the React-only constraint and relatively small community (compared to Sanity, Strapi, or Contentful) mean fewer resources, fewer integrations, and more time spent solving problems yourself.

Visual editing limited to React
TinaCMS supports many frameworks including Astro, Hugo, Jekyll, SvelteKit, and Nuxt for basic content editing. However, the visual/inline editing experience, which is Tina's main selling point, only works with React-based frameworks like Next.js.

Unstable development environment
The dev server can break unpredictably because it loads external assets that change independently of your codebase. This makes local development feel unreliable and hard to debug.

Poor error handling and silent failures
Forms can fail to save without any visual indicator, and GraphQL errors aren't surfaced clearly. Losing work without warning is a real risk, especially for content editors.

Branch editing requires paid tier
Multi-branch support isn't available out of the box — it's locked behind the paid editorial workflow feature. You can't test content changes in deploy previews without paying up.

Self-hosting gaps
The self-hosted backend lacks search functionality, Git LFS support, and pagination on reference fields. Large collections can cause network timeouts.

Small ecosystem
Compared to established players like Sanity or Contentful, Tina has a smaller community and fewer plugins. Since the SSW acquisition in May 2024, the project has been actively maintained with regular releases, but the ecosystem is still catching up.
Key advantages
DatoCMS has a low learning curve, clean UI, and a drag-and-drop schema builder that lets teams shape content without a single existential crisis. Editors love it. Developers tolerate it. Everyone gets to ship faster.
The APIs are solid, the media pipeline is excellent, and the multilingual tooling is actually usable. But lto be honest, it’s expensive, and the drag-and-drop approach means it’s not exactly winning awards for flexibility. Still, if you want something that feels polished out of the box and integrates nicely with Next.js, Shopify, and friends, DatoCMS delivers a pretty smooth experience.
User-friendly interface
DatoCMS has a clean, approachable UI that editors can pick up instantly. Little training needed, and teams can publish content without tripping over the system.

Flexible API-based approach
With both GraphQL and REST, you can query content however you prefer. It gives developers freedom to shape data flows without fighting the CMS.

Seamless integration
DatoCMS works smoothly with popular frameworks and tools like Next.js, Gatsby, and Shopify. Plug it in, fetch content, and you’re off.

Efficient data retrieval
The GraphQL API is fast and predictable, making it easy to pull exactly the data you need without overfetching or messy workarounds.

Powerful image tools
Dato handles image optimisation, responsive resizing, and transformations automatically. Your site stays fast without custom pipeline work.

Real-time updates
Content changes sync instantly across environments, giving teams quick feedback and reducing the “save, refresh and hope” cycle.
Book a meeting with us to discuss how we can help or fill out a form to get in touch
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.
