Is Ghost a headless CMS or a publishing platform?
Ghost is both. It is an open source publishing platform with built-in memberships, paid subscriptions and email newsletters, and it also exposes a read-only Content API that any frontend can call. You can run the Ghost theme layer as is, or use Ghost only as the editor and data store behind a Next.js or Astro site. As of October 2026 the vendor sells managed hosting as Ghost(Pro) and also publishes the source code for self-hosting.
If your business is the audience (a newsletter, a media site, a paid community), Ghost gives you the subscription machinery without a plugin stack. If your business is a product with a marketing site, it usually does too much in one direction and too little in another.
Who Ghost suits
Ghost fits a small editorial team that publishes often and wants members to pay for it. It also fits a SaaS company that wants a fast blog and changelog under its own domain, or a publisher leaving WordPress who is tired of maintaining plugins for email and paywalls.
It is a weaker fit for sites built from many page types, landing pages with modular sections, or deep relations between content. Ghost models posts, pages, tags and authors well. It does not give you a free-form content type builder.
What it costs to own
Ghost(Pro) lists Starter at $18 per month, Publisher at $29 and Business at $199, billed yearly, as of October 2026 on ghost.org/pricing. The Content API is on every plan. Webhooks, the Admin API and automation tools are not on Starter, which matters if you plan to rebuild a frontend on publish events. Self-hosting removes the licence fee and adds server upkeep, backups and mail delivery setup.
Our own cost drivers are the number of templates, the member and payment flows, the volume of content to import and how many redirects the move needs. We scope those after a short audit.
When we would pick something else
- Many content types, relations or localized landing pages: Strapi or Payload model that better.
- Visual page building for marketers: Storyblok.
- Enterprise governance and several brands: Contentful.
Our guide to the best open source headless CMS platforms compares them against Ghost side by side.
What we build on Ghost
- Custom Handlebars themes that keep Ghost’s rendering, with performance budgets and structured data for articles.
- A Next.js or Astro site reading the Content API, with webhooks triggering rebuilds or revalidation, and a preview route for drafts.
- Tier design, Stripe setup, gated content rules and paywall behavior tested across devices.
- Sending domain authentication, segmentation and a sign-up experience that does not hurt page speed.
- Analytics, CRM sync and automation through the Admin API and webhooks.
- Posts, authors, tags and images imported by script, with a redirect map so rankings survive. Our WordPress to headless CMS migration page describes the method, and the migration checklist lists what we verify before cutover.
How a Ghost project runs
We begin with a content and URL inventory: what ranks today, which posts earn links, and which membership tiers exist. Then we settle the architecture decision, theme or decoupled frontend, because it changes every later estimate. A theme ships faster and keeps Ghost’s built-in member pages. A decoupled site gives design freedom but means we rebuild login, paywall and preview behavior ourselves.
Staging comes next, with a copy of real posts and a test Stripe account, so editors can try publishing and sending a newsletter before launch. After cutover we watch indexing, email deliverability and page speed for the first weeks.
If you need an engineer rather than a project team, see how to hire a Ghost developer. For the wider decision, start from our headless CMS hub.
