# Ghost to KeystoneJS migration > How to migrate from Ghost to KeystoneJS, with a side-by-side comparison and FAQs. --- ## Source: Ghost - **Type:** headless - **Official site:** https://ghost.org - **Pricing:** https://ghost.org/pricing - **Last reviewed:** 2026-08-05 ## Key advantages Ghost is genuinely great if all you want is a fast, clean, no-nonsense blogging machine. It keeps things beautifully simple: a slick Markdown editor, zero clutter, and performance scores so good they’ll make WordPress users cry into their PHP logs. If your plan is "just publish content," Ghost actually gets out of your way and lets you do that. The built-in memberships and payments system is also a win. You can slap a paywall on your content, charge people to read your mediocre hot takes, and do it all without duct-taping together 12 plugins. For solo creators, small publications, and anyone who wants a simple writing-first experience, Ghost delivers exactly what it promises and nothing you didn’t ask for. ### Lightweight JSON API Ghost’s API is fast, predictable, and doesn’t make you fight a schema just to fetch a title. It’s perfect for JAMStack setups where you want speed without ceremony. Pull content, ship pages, move on with your life. ### Intuitive Markdown editor If you enjoy writing without 19 toolbars screaming at you, Ghost’s Markdown editor is bliss. Clean, distraction-free, and actually enjoyable to use. ### Built-in membership system Memberships, paywalls, and subscriptions come built in, no plugin Frankenstein required. Hook up Stripe and you’re basically running your own mini-Substack in minutes. ### SEO-friendly defaults Ghost ships with fast performance, clean URLs, structured data, and proper metadata, without needing an SEO plugin the size of a small country. Most sites hit solid scores straight out of the box. ### Native subscription support You don’t need 3 SaaS tools duct-taped together to run a newsletter. Ghost handles email delivery, subscriber lists, and automated posts natively. ### Easy theme customization Themes are simple to tweak thanks to Ghost’s handlebars-based templates. If you know basic HTML/CSS, you can make it look exactly how you want without fighting a visual builder from 2011. ## Key pain points Ghost is great until you need it to do anything more than "post blog, send newsletter, and beg readers for $5/month." The moment you step outside that happy path, the whole thing starts feeling painfully bare-bones. There’s no real visual builder, no serious content modeling, and the plugin ecosystem is basically "good luck, build it yourself." Hosted plans get expensive fast once memberships grow, and self-hosting turns into a weekend-killing DevOps hobby nobody asked for. If you need anything beyond a clean blog with a paywall, Ghost will politely tap out and tell you to write less ambitious content. ### Blogging-centric feature set Ghost is brilliant for blogs… and very "meh" for anything else. If you need complex content models, workflows, or enterprise-level flexibility, you’ll hit a wall quickly. ### Sparse plugin marketplace There’s no real ecosystem to lean on. Anything outside the basics usually means rolling up your sleeves and writing code yourself. ### No visual page builder If you were hoping to drag, drop, and magically design pages, Ghost politely says "no." Everything beyond basic layouts needs theme edits. ### Custom coding required Even simple enhancements often require Handlebars or API work. Non-technical teams will run out of road fast. ### Limited content modeling You get posts and pages, that’s pretty much the deal. Anything beyond that is a workaround, not a first-class feature. ### Lacks multi-site support Running multiple sites under one instance isn’t Ghost’s thing. If you’re scaling across regions or brands, you’ll feel boxed in. ## 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 ### Does Ghost need a developer to maintain it? If you're self-hosting, yes. Ghost runs on Node.js and requires regular updates, database maintenance (MySQL), and server monitoring. Major version upgrades can break themes and integrations, and someone technical needs to handle those. Ghost 6, for example, raised the minimum Node.js to v22 and removed API behaviour like ?limit=all that older themes and custom integrations relied on. On Ghost Pro, maintenance is handled for you, but customisation still requires a developer. Custom themes use Handlebars templating, and anything beyond basic styling means editing theme files and redeploying. If your team is purely non-technical and you want to go beyond Ghost's default themes, you'll need developer support on an ongoing basis. ### How much does Ghost CMS really cost beyond the "free" open source version? Ghost is free to self-host, but "free" is misleading. You'll need a VPS ($5-$20/month minimum), someone to handle server maintenance, security updates, SSL certificates, and backups. That's either your time or a developer's hourly rate. Realistically, self-hosted Ghost costs $50-$200/month in labour and infrastructure for a small team. Ghost's managed hosting (Ghost Pro) starts at $18/month for the Starter plan (1,000 members), jumps to $29/month for Publisher, and scales to $199/month for the Business tier (10,000 members). Once your membership list grows past a few thousand, costs climb fast. We've seen publishers hit $300+/month on Ghost Pro before questioning whether the platform still made sense for them. ### When should you migrate away from Ghost? Ghost hits its ceiling when you need more than blog posts and newsletters. If you're trying to build landing pages, manage structured content across multiple page types, run an ecommerce store, or handle multi-language content, Ghost wasn't designed for any of that. We've migrated publishers off Ghost when they outgrew the "blog plus newsletter" model and needed a real content platform. The migration itself is painless. Ghost's JSON API makes content extraction simple, and posts map cleanly to markdown. The typical timeline is 4-6 weeks to move content into a headless CMS and rebuild the frontend. ### Can Ghost handle a site with more than just a blog? Barely. Ghost gives you two content types, posts and pages, and that's it. There's no custom content modelling, no relational fields, no structured data beyond tags and authors. You can hack together something with custom routes and internal tags, but it's brittle and hard to maintain. If you need case studies, service pages, team directories, or any structured content beyond articles, you're fighting the platform. Ghost is excellent at what it does. It just doesn't do very much. For sites that need a blog alongside other content types, a headless CMS gives you the flexibility Ghost intentionally leaves out.