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

From KeystoneJS to Dato CMS
Key pain points
The biggest challenge with KeystoneJS is that it hands you all the responsibility that a managed CMS would normally handle. Deployment is entirely on you, and the documentation around production hosting, Docker configuration, and scaling is thin. We've seen teams struggle to go from a smooth local development experience to a reliable production setup, especially if they don't have dedicated DevOps support. The admin UI Docker image alone can balloon to over a gigabyte, which is a headache for containerised deployments.
The community around Keystone is significantly smaller than competitors like Strapi or Payload. That means fewer tutorials, fewer plugins, and slower answers when you hit an edge case. The ecosystem of ready-made integrations is almost non-existent, so you'll be building most things from scratch. For an agency working on client projects with deadlines, that time cost adds up quickly.
Content editors also tend to have a harder time with Keystone compared to more polished alternatives. The admin UI is functional but feels utilitarian, and non-technical users often need more onboarding than you'd expect. There's no visual editing, no preview infrastructure, and no real content workflow features like drafts, publishing schedules, or approval chains without building them yourself. If your client's content team needs a CMS they can pick up and run with, Keystone usually isn't the answer.

Deployment complexity
Self-hosting is the only option, and the docs don't hold your hand. Getting Keystone into production requires real infrastructure knowledge, and the large Docker image sizes make it worse.

Small community and ecosystem
Compared to Strapi or even Payload, the community is much smaller. Fewer plugins, fewer tutorials, and slower support when things go wrong.

No built-in content workflows
There are no turnkey drafts, scheduled publishing, or approval chains. Keystone provides field primitives that can be assembled into publishing workflows, but you need to wire them up yourself.

Admin UI feels dated
The admin panel is functional but lacks the polish and UX of modern CMS interfaces. Non-technical editors often find it confusing and need more training.

No visual editing or live preview
There's no way for editors to see content in context before publishing. You'd need to build your own preview infrastructure, which is a significant engineering effort.

Scaling requires significant effort
Running Keystone under high traffic means managing session stores, reverse proxies, and server resources yourself. It doesn't scale as smoothly as cloud-native CMS alternatives.
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.
