KeystoneJS logo
Agility CMS logo

From KeystoneJS to Agility CMS

We are the KeystoneJS to Agility CMS migration experts



Challenges with KeystoneJS

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 in KeystoneJS

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 in KeystoneJS

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 in KeystoneJS

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.

Dated admin UI in KeystoneJS

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 in KeystoneJS

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 challenges in KeystoneJS

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.



Benefits of Agility CMS

Key advantages

Agility CMS is one of the few headless CMS platforms that genuinely tries to bridge the gap between developer freedom and editor autonomy. The standout feature is built-in page management, something most headless CMS tools completely ignore. Editors can create and manage pages, control the sitemap, handle SEO fields, and arrange modular components on pages without needing a developer to wire everything up. That alone saves us a ton of back-and-forth on client projects.

The Next.js integration is solid and well-maintained. The SDK handles page routing, preview mode, and image optimization out of the box, and getting a starter site running takes minutes rather than hours. The content modeling interface is intuitive enough that even non-technical clients can understand and extend models without hand-holding, which is rare in the headless space.

Support is genuinely excellent. The team is small enough that you get real humans who know the product inside out, not a ticket queue that disappears into the void. For agencies that need to move fast and hand projects off to client teams, that responsiveness matters. The API request limits are generous too, with high request allowances across all plans, so you're not constantly worrying about overage charges like you would with some competitors.

We also appreciate that Agility takes a pragmatic approach to headless. It doesn't try to be everything, but it does the core CMS job well and stays out of your way when you need to build custom functionality around it.



Page management interface in Agility CMS

Built-in page management

The only headless CMS with native page management. Editors can build and manage pages, control the sitemap, and arrange modular components without developer involvement.

Next.js integration with Agility CMS

Strong Next.js integration

First-class Next.js SDK with automatic preview mode, image optimization, and page routing. Getting a project scaffolded takes minutes, not hours.

Content modeling in Agility CMS

Intuitive content modeling

Visual schema modeler that maps to JSON. Non-technical users can understand and extend content models without needing a developer to walk them through it.

Agility CMS support team

Excellent support team

Small, responsive support team that actually knows the product. You get real answers quickly, not generic ticket responses that take days.

API limits in Agility CMS

Generous API limits

Generous API request allowances across all plans. No surprise overage bills or throttling when traffic spikes, which removes a common headache with usage-based competitors.

SEO management in Agility CMS

Built-in SEO and redirect management

SEO fields, sitemap editing, and URL redirect management are native to the CMS. Editors can handle these without a separate tool or developer intervention.





Get in touch

Book a meeting with us to discuss how we can help or fill out a form to get in touch