Ghost has carved a specific position in the publishing-platform market as the editorial-first, members-and-payments-integrated, nonprofit-foundation-owned alternative to Substack and Beehiiv on the newsletter side and to WordPress on the blog side. The platform is genuinely good at what it does and the right tool for a specific shape of publication. The honest comparison covers where the platform earns its subscription and where publications have outgrown what Ghost is structurally built to do.
What Ghost is good at
Three things Ghost does materially better than the alternatives. The editorial pipeline is the cleanest in the publishing-platform space — the writing interface, the publication workflow, the editorial-team collaboration, the SEO defaults all work without configuration. The members-and-Stripe integration is genuinely operational — paid newsletters, member-only content gating, recurring subscriptions, member-tier management — all built natively rather than bolted-on. The nonprofit-foundation ownership matters to a values-driven audience that explicitly chooses Ghost over Substack for the governance.
What Ghost is not good at
Three things Ghost does worse than a custom build. Commercial-services functionality — service pages, location pages, booking flows, custom commercial schema are not what Ghost is built for, and publications that have grown commercial alongside their editorial output hit the wall fast. Schema depth — Ghost emits decent Article schema by default but does not expose Service-with-Offer, regulated-industry propertyValue, multi-Person team schema or the deeper editorial-content schema (citation arrays, mentions, audience entities) that lifts ranking on commercial-intent queries. Customisation flexibility — Ghost themes constrain front-end customisation in ways that suit publications but limit publications-with-commercial-elements.
When Ghost is the right answer
Two scenarios where staying on Ghost is the better call. First: pure paid newsletter publication where Members and Stripe are the operational core. Ghost(Pro) Creator at £25/month is the right price for the right tooling, and the platform-managed runtime means no infrastructure work. Second: publication actively chosen on values grounds — Ghost’s open-source foundation, no-tracking commitment, editorial-first design philosophy. For publishers who have made the explicit choice, the platform earns its position.
When the migration is overdue
Three patterns that point to migration. The publication has grown commercial functionality — service pages, location pages, consulting offerings, e-commerce — that Ghost is not built for, and the workarounds are clumsy. The schema and SEO depth needs have outgrown what Ghost exposes — Service-with-Offer schema, regulated-industry propertyValue, AI-crawler fields. The subscription stack has reached complexity Ghost Members does not support cleanly — multi-tier subscriptions, gift subscriptions with custom terms, geographic-tier pricing, complex coupon logic.
The Ghost-as-CMS hybrid pattern
For publications wanting Ghost’s editorial pipeline alongside custom commercial functionality, the hybrid pattern works well. Keep Ghost as the editorial backend (writers continue in Ghost Admin), render the public site in Next.js or similar using Ghost’s Content API to pull articles, build commercial pages and custom functionality in the front-end framework outside Ghost. The editorial workflow stays untouched; the commercial and custom layers gain full flexibility. We have built this pattern for several publications outgrowing Ghost without wanting to disrupt the editorial team.
The migration sequence
Same overall shape as other CMS migrations. Full crawl of the existing Ghost site for URL inventory. Content export via Ghost Admin API (every post, every page, every tag, every member). Ghost Members data exported with subscription status and Stripe customer IDs for subscription continuity. Schema rewrite with the depth Ghost does not expose. URL preservation where the existing structure makes sense; redirect map for any URL changes. Stripe subscriptions migrate by transferring customers rather than re-billing. Search Console handover. Day 7, 14, 30 health checks.
The cost comparison
Ghost(Pro) Creator: $31/month annual = ~£300/year. Plus Mailgun for transactional email at typical $35/month. Plus Stripe at standard rates. Five-year all-in: ~£1,500-£2,000. Same-day Growth tier + Stripe direct + transactional email via Resend or Postmark: £899 + £180/year hosting × 4 = ~£1,619 across five years. Cost is genuinely close; performance, ownership, customisation flexibility and schema depth are the actual decision drivers.