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 Contentstack
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
Contentstack is one of the more polished enterprise headless CMS platforms. It has API-first, composable, and loaded with the usual DXP buzzwords. It actually backs some of it up. The workflows are strong, role-based approvals are genuinely helpful for large editorial teams, and the visual builder plus modular blocks give marketers enough power to ship pages without pinging developers every 30 seconds. Its omnichannel delivery, multi-region CDNs, and fast APIs make it a solid fit for global brands with heavy traffic and complex localisation needs.
But this is firmly in enterprise territory. We generally don’t recommend platforms in the “DXP with 47 whitepapers” category, but if you must pick one, Contentstack at least has a smoother developer experience than most. The composable architecture is well thought out, integrations behave predictably, and the SDKs play nicely with modern frameworks like Next.js. If you're a Fortune-500-sized team and want help figuring out whether this is the right bet, or want a modern alternative instead, get in touch.

Enterprise-grade composable architecture
Built for large teams shipping across markets. The stack scales fast, stays stable under heavy traffic, and doesn’t crumble the moment your marketing team schedules a global launch.

Advanced workflow and approvals
Contentstack’s workflow engine handles multi-step approvals, roles, and governance without duct tape. Perfect for teams that need structure instead of Slack chaos.

Multi-region CDN delivery
Your content gets pushed worldwide through edge CDNs, keeping delivery fast even when your customers are nowhere near your servers.

API-first microservices design
Developers get flexibility without wrestling with legacy monolith logic with REST, GraphQL, and webhooks.

Extensive React/Next.js SDKs
Strong developer tooling means faster builds and fewer hours wasted writing boilerplate just to fetch and render content.

MACH-compliant infrastructure
Fully modular, cloud-native, and replaceable in parts. Plays nicely inside modern composable stacks instead of dragging you back to 2010.
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.
