What is Ghost and how does it work?
Ghost combines a publication website, editor, newsletter delivery, membership database, paid subscriptions, analytics, recommendations, and social-web distribution. It is opinionated software: instead of becoming any kind of site through plugins, it tries to make one publishing business unusually coherent.
A writer can publish a post to the web and email, gate it for free or paid members, create tiers, recommend other publications, and export the audience. The hosted Ghost(Pro) service handles the infrastructure; the open-source software can also be self-hosted for teams willing to run it.
The focus is the reason to buy Ghost and the reason not to. A publication does not need to reconcile a page builder, membership plugin, email service, and theme framework. A complex course, forum, store, or application will still need external products.
Ghost standout strengths
Ghost's editor is deliberately quiet. Cards handle images, embeds, calls to action, products, email-only content, and other rich elements without turning every paragraph into a layout project. Writers spend more time on the issue and less on the page builder.
The membership model is unusually direct. Ghost takes 0% of subscription revenue; Stripe processing remains. Free and paid members live in the same system as posts and newsletters, and CSV import/export reduces lock-in. For an established paid newsletter, avoiding a revenue share can justify the subscription quickly.
Performance and SEO are strong out of the box. Clean themes, sensible metadata, canonical controls, sitemaps, structured content, and managed hosting remove a long optimization checklist. Custom themes on Publisher and above allow a publication to look distinct without rewriting the product.
Ghost is also leaning into distribution beyond email. Recommendations and ActivityPub/social-web features give publishers additional discovery paths while the website and member list remain central. Those channels are additive rather than a replacement for an owned audience.
Ghost weaknesses and drawbacks
Starter costs less but excludes the two features many serious publishers expect: paid subscriptions and custom themes. Publisher at $29 per month billed yearly is the realistic entry for a monetized publication, with three staff users and 1,000 members.
Member count, not only paid subscribers, affects Ghost(Pro) tiers. A large free list can therefore raise hosting cost even if revenue is modest. Business is advertised at $199 monthly annually with 15 staff and 10,000 members; larger publications need a quote or self-hosting model.
Stripe is the native payment path. That keeps the product coherent, but creators in unsupported countries or with unusual billing needs have fewer options than a plugin-based platform. Courses, community discussion, and sophisticated marketing automation also require integrations.
Self-hosting is not free Ghost(Pro). The software has no license fee, but the operator must handle the server, updates, backups, CDN, transactional email, bulk delivery, monitoring, and deliverability. Underestimating email operations is the common false economy.
Pricing and total cost
Ghost(Pro) Starter is $18 per month billed yearly for one staff user and 1,000 members, but it excludes custom themes and paid subscriptions. Publisher is $29 for three staff and those features. Business is $199 for 15 staff and 10,000 members. Custom plans handle larger requirements.
Stripe processing, domain, custom development, advanced email services, and external community or course tools may remain. Model cost per total member and per paid subscriber, because list growth can trigger a tier before revenue does.
Do not compare annual promotional prices with month-to-month renewals. Put domain, email, payment processing, apps, templates, add-ons, collaborators, storage, bandwidth, tax tooling, and specialist help into one twelve-month total. Then attach the cost to the constraint it removes. Paying more for reliable checkout or editorial workflow can be rational; paying for dormant features is not.
Review the cancellation and refund language before purchasing. Save the receipt and displayed renewal price, schedule a reminder several weeks before auto-renewal, and use a card or virtual card with clear merchant controls. This is basic vendor management, especially when the domain, audience, and revenue share an account.
Ownership, migration, and business continuity
An export is only meaningful when it contains useful fields. For posts, check URLs, dates, authors, tags, images, captions, and redirects. For members, check email, consent, tier, payment state, source, and cancellation date. Payment credentials usually cannot be moved like a CSV, so a membership migration may require readers to subscribe again.
Use a domain the publisher controls, authenticate sending domains, and take periodic content and audience exports. Platform followers and recommendation traffic are valuable, but they are rented distribution. The durable asset is a reachable audience, a recognizable domain, and an archive that can be reconstructed.
Before a major campaign, test account recovery and invite a second trusted administrator if the plan permits it. Use named accounts rather than shared passwords, enable multi-factor authentication, and remove former contractors promptly. Keep invoices and legal ownership details consistent with the entity that owns the brand.
A migration should run in parallel. Build the destination, import a small sample, compare URLs and metadata, submit a form or order, and monitor both systems before changing DNS. Maintain redirects for old pages and preserve financial records even after the public site moves.
Pricing fit overview
| User type |
Why it can fit |
What to verify |
| Solo creator |
independent publications, newsletters, and paid memberships that value ownership and focus |
Keep one owner for domains, billing, and exports |
| Content-led business |
Publishing is central to the product |
Test URLs, redirects, feeds, email, and bulk editing |
| Seller |
Connect a specialist checkout when native selling is shallow |
Model every fee and perform a refund |
| Agency or team |
Reusable systems can speed delivery |
Check seats, permissions, handoff, and multi-site billing |
| Established brand |
A controlled domain and documented stack preserve continuity |
Avoid Ghost when you need plugin-heavy sites, large free lists with little revenue, native courses/forums, or non-Stripe billing requirements |
Who should use it—and who should skip it
The strongest fit is independent publications, newsletters, and paid memberships that value ownership and focus. These users benefit when the platform's opinionated workflow replaces real work rather than adding another dashboard. Start with the smallest plan that can run the complete transaction or publishing loop, then upgrade because a measured limit appears.
Skip it, or keep it deliberately narrow, for plugin-heavy sites, large free lists with little revenue, native courses/forums, or non-Stripe billing requirements. No amount of template polish repairs a mismatch between the platform's data model and the business. If the first month already depends on several unsupported workarounds, choose the product that treats those requirements as native.
The alternatives are Substack for built-in network distribution; Beehiiv for newsletter growth tooling; WordPress for plugins and site breadth; Medium for algorithmic readership; Memberful for adding memberships to an existing site; Circle for community. Migration cost, audience ownership, payment geography, support quality, and the owner's ability to maintain the system should break close ties.
Ghost review: final verdict
Ghost is the cleanest owned publishing-and-membership stack for writers who want a fast site, email newsletter, paid subscriptions, and 0% platform fees in one focused system. It gives up plugin breadth and beginner-level handholding, and Ghost(Pro) becomes expensive as the team or member count grows.
The sensible buying sequence is a free or monthly test, a real mobile workflow, a support question, and a usable export. Move to annual billing only after the product has survived those checks. The site or shop should remain understandable to the person who operates it and recoverable if the vendor, price, or business changes.
