# Kontent.ai to KeystoneJS migration > How to migrate from Kontent.ai to KeystoneJS, with a side-by-side comparison and FAQs. --- ## Source: Kontent.ai - **Type:** headless - **Official site:** https://kontent.ai - **Pricing:** https://kontent.ai/pricing - **Last reviewed:** 2026-08-03 ## Key advantages Calling your CMS "Kontent dot ai" is a brilliant way to convince people you’ve built an AI-powered future. And to be fair, the platform does have a clean editor, strong workflow tools, and a respectable multi-channel setup. It's perfect for the kind of company that has more infosec members than it does have devs. But calling yourself an AI platform doesn’t mean you’re built like one. Real AI-driven CMS platforms start at the foundation with structured content, flexible modeling, real-time indexing, and an architecture that doesn’t panic the moment you try something complex. Sanity doesn’t even market itself as "AI-first," but it’s been ahead of the curve for years. They shipped an embedding index before "AI CMS" was a pitch deck buzzword. We even built one of the first AI search tools on top of it. So yes, Kontent.ai is great. If you want a polished interface and enterprise workflows, go for it. And if you’re dead-set on building your website there, talk to us first. We’ll walk you through it and maybe even find a better way before you spend six months discovering the limits yourself. ### Intuitive content management You shouldn’t need a week of onboarding to publish a paragraph. Kontent.ai nails this with a clean interface that doesn’t punish you for being a marketer instead of a developer. ### Flexible content modeling Build content the way your brain works. Modular, structured, reusable. No dev intervention every time marketing decides "we need one more field." ### Strong API-first architecture The APIs are predictable, well-documented, and don’t require wild workarounds. Everything connects the way it should and developers stay happy too. ### Tech stack integration React, Vue, Angular, or whatever framework you’re obsessed with this week, Kontent.ai plays nice with all of them and keeps deployments smooth. ### Advanced image transformations You can resize, crop, and optimize visuals without leaving the CMS. Think of it as an in-house designer that doesn’t complain about aspect ratios. ### Real-time collaboration Writers, editors, and developers can work together without stepping on each other’s commits. Instant updates, fewer Slack messages, and zero "who overwrote my draft?" moments. ## Key pain points We've always been known to talk trash about WordPress, Framer and especially Prismic. It's fun and theraputic but truth be told Kontent.ai deserves it's fair share of aggro. Pricing is hidden behind "book a demo" and their vague "price calculator". Basic features require developer elbow grease, and replacing a single image gives you a brand-new URL like it’s 2009. At scale, the API rate limits and bare-bones taxonomy start to feel less "enterprise" and more "please slow down, you’re scaring the CMS." If you’re absolutely set on using Kontent.ai, give us a shout. We’ll try to make it work… or find you something that won’t make your content team cry into their spreadsheets. ### Hidden pricing model Kontent.ai loves a "contact sales" button. Great if you're an enterprise with a procurement department, not so great if you're just trying to budget a project. Until you get a quote, you’re basically guessing. ### Complex initial setup requirements The platform is polished, but the setup isn’t plug-and-play. Getting projects wired correctly, especially when it comes to multi-channel setup, usually requires a developer, documentation, and a quiet room to scream into. ### Missing out-of-box preview system Unlike most modern CMS platforms, there's no native live preview. You have to build a custom preview pipeline, which adds effort, cost, and another item to the dev team’s already depressing backlog. ### Asset replacement URL issues Swap an image or file, and Kontent.ai generates a new URL, which means link rot and cleanup duties no one asked for. Publishing teams feel this pain the fastest. ### API rate limiting constraints API-first is great until you hit the rate limit. 100 requests per second is fine for small sites, but high-traffic apps need careful caching or extra infrastructure to avoid bottlenecks ### Limited Management API coverage The Management API doesn’t expose every UI action, so automation hits a ceiling. Some tasks still require clicking through the interface, which defeats half the point of going headless. ## Target: KeystoneJS - **Type:** headless - **Official site:** https://keystonejs.com - **Last reviewed:** 2026-07-28 ## Key advantages KeystoneJS is one of those tools that really clicks if your team thinks in code. It's a schema-driven, open-source headless CMS built on Node.js, and the developer experience is genuinely good. You define your content models in TypeScript, Keystone generates a GraphQL API and an admin UI for you, and you're off. There's very little magic or abstraction hiding what's happening under the hood, which we appreciate when building complex projects for clients. The Prisma ORM integration is a real highlight. Automatic migration generation, type-safe database access, and support for PostgreSQL, MySQL, and SQLite mean you're not fighting your data layer. If you've ever had to wrangle a CMS into supporting a non-trivial relational content model, you'll understand why this matters. Keystone lets you express those relationships cleanly and query them with a proper GraphQL API. The document field editor is also worth mentioning. It's one of the more thoughtful rich text implementations we've seen in a headless CMS. You can embed custom React components directly into the editor, which means content teams can work with your actual design system components rather than generic blocks. For teams that care about structured content, Keystone gives you real tools to enforce it. Where Keystone really shines is in projects where the development team wants full ownership of the stack. There's no vendor lock-in, no proprietary query language, and no surprise pricing tiers. If you want a CMS that feels like a well-designed library rather than a platform, Keystone delivers on that promise. ### Schema-as-code with full TypeScript support Define your entire content model in TypeScript with strong type inference throughout. The schema drives everything from the database to the admin UI to the GraphQL API. ### Automatic GraphQL API generation Every content type you define automatically gets a full CRUD GraphQL API with filtering, pagination, and relationship resolution. No manual endpoint wiring needed. ### Prisma-powered database layer Built on Prisma ORM with automatic migration generation and type-safe queries. Supports PostgreSQL, MySQL, and SQLite out of the box. ### Flexible document field editor The rich text editor supports custom embedded components that map to your design system, giving content editors structured authoring without sacrificing flexibility. ### Granular access control Fine-grained, field-level access control defined in code. You can write custom logic for create, read, update, and delete operations per field or per list. ### Fully open source with no vendor lock-in MIT licensed with no paid tiers or proprietary features gated behind a subscription. You own the entire stack and can host it wherever you want. ## 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. ## Frequently asked questions ### What happens to image URLs when you replace assets in Kontent.ai? This is a genuine pain point. Every time you replace an image or file in Kontent.ai, the platform generates a completely new URL. That means any hardcoded references, cached versions, or external links to the old asset break instantly. For content teams publishing at scale, this creates a maintenance burden. You need to update every place the old URL was referenced, or accept broken images. Most CMS platforms handle asset replacement by keeping the same URL and invalidating the cache. Kontent.ai's approach feels like an oversight that hasn't been fixed. If you're managing hundreds of assets, this adds real friction to daily editorial work. ### What's involved in migrating away from Kontent.ai? The content extraction itself is clean. Kontent.ai's Delivery API and Management API let you pull content items and assets programmatically. The challenges are schema translation and workflow replication. Kontent.ai's content types map to their own structure, and converting those to another CMS's schema requires careful field-by-field mapping, especially for linked items and modular content. If you've built custom workflow states and approval chains, those need to be recreated in the target platform. Plan for 6-10 weeks depending on the number of content types, locales, and workflow complexity. The API rate limit of 100 requests per second can also slow down bulk exports for large content libraries.