Substack vs Ghost

Ghost is MIT-licensed and can run on your own server or on Ghost(Pro), and the comparison page lists memberships, paid subscriptions and newsletters as built in without extra plugins. The gains matter most when your paid revenue is large enough that a percentage share becomes a meaningful line item, when you need your own domain and design, or when you want the member relationship and billing records under your control.

• No transaction fee on subscriptions: Ghost's comparison page says it takes no transaction fee on paid subscriptions, though Stripe processing fees still apply. This matters most when subscription revenue is high enough that a revenue share outweighs hosting costs.
• Own domain and design: You control the theme, URL structure and site layout. This matters if your publication is part of a wider brand or must follow an internal style or accessibility standard.
• Member and Stripe ownership: Your member list and subscription records sit in your Ghost instance, and payments run through your own Stripe account. This matters if you may change platforms later or need direct access to billing data.
• Independent organisation: Ghost describes itself as an independent non-profit that reinvests its revenue into the product. This matters if vendor direction and pricing stability affect your planning.
• Open-source code: Ghost's MIT license lets you inspect and modify the software. This matters if you have engineers who need to extend the platform.

Before you commit, confirm current Stripe fees for your country and card mix, and ask Ghost(Pro) or your hosting provider for the exact plan limits that apply to your member count.

Substack's network gives writers discovery tools that a self-hosted Ghost site does not supply. Readers find publications through recommendations, browsing and cross-links between writers, and the platform handles the reader-facing experience without extra setup. This matters most for new publications that have no existing audience and no marketing budget.

• Built-in discovery: Substack's recommendations and network features expose your publication to readers who did not search for you. Ghost has no equivalent directory, so this reach must come from your own channels.
• Hosted reader experience: Substack handles hosting, the reader app and email delivery without your involvement. With Ghost you run or contract for these functions.
• Simple paid setup: Paid subscriptions work from the start with limited configuration. Ghost also includes this, but you configure Stripe, tiers and pricing yourself.
• Archive visibility: Substack hosts your archive on its network, which can be found through its search. A Ghost archive is indexed only through your own site and search engines.
• Community features: Substack offers comment and chat features tied to its network. Ghost's comment and engagement features differ, so confirm what your audience needs.

This loss matters most when your growth depends on new readers finding you through the network rather than through search, social channels or other writers.

The discovery you give up can be replaced, though it takes ongoing effort and no single tactic matches the network's reach. Most publishers combine several channels: cross-posting excerpts to other platforms, asking established writers for recommendations, and running referral programs that reward existing subscribers for bringing in new readers. Ghost supports sending content to other media through its Content API, which helps you build the feeds and excerpts you publish elsewhere.

• Cross-posting excerpts: Publish summaries on social platforms or other newsletters with links back to the full post on your Ghost site. Track clicks to see which channels produce subscribers.
• Referral and recommendation swaps: Trade recommendations with writers who cover adjacent topics. Ask them to mention your publication in their own issues.
• Referral incentives: Offer existing members a reason to share, such as a free month or extra content. Check how your Ghost setup tracks referrals before you promise a reward.
• Search optimisation: Structure posts with clear titles, descriptions and internal links so search engines index your archive well. Ghost gives you control over metadata in its admin.
• Migration of existing readers: Use the Substack export and Ghost's migration path to bring your current subscribers across, then announce the move to them directly.

Before you rely on any channel, measure the subscriber sources for at least a few issues, since the right mix depends on your niche and audience.

The trade-off depends on your audience size, how much of your income comes from paid subscriptions, and whether you have time or staff to run the site. Ghost suits publishers who want brand control and direct ownership of members and billing. Staying on Substack suits writers who depend on network discovery and want no hosting duties. The decision is rarely permanent, since your export and migration options stay available either way.

• Revenue-led publishers: If paid subscriptions carry most of your income, the absence of a transaction fee on Ghost deserves close comparison with your Stripe costs and hosting bill.
• Brand-led publishers: Organisations with an established domain, design rules or internal approval processes gain the most from owning the site.
• Discovery-led writers: Newer writers who rely on the network for growth may find the loss of recommendations costly until they build their own audience.
• Hybrid approach: Some publishers keep a Substack presence for discovery while running a Ghost site for members, though you must manage two audiences carefully.
• Operational capacity: Self-hosting requires someone to maintain the server, backups and updates. Ghost(Pro) moves that work to the vendor for a fee.

Before deciding, model your own numbers with an honest estimate of how much of your growth currently comes from Substack's network.

A writer or small publisher without operations staff usually gets the most from Ghost(Pro), the hosted version run by the Ghost team. Ghost(Pro) is priced by staff users and member count on the published pricing page, so the monthly cost is predictable and the hosting, upgrades and backups are handled by the vendor. Self-hosting shifts those tasks to the publisher, who would also need to keep a Node.js runtime, MySQL, NGINX and email delivery current.

• Operating effort: Ghost(Pro) requires no server work. A self-hosted install needs regular upgrades, backups and monitoring, which one person may not have time for during a launch.
• What you control: Design, domain, content, members and Stripe connection are yours in both models. Server access, hosting region and upgrade timing are only yours when you self-host.
• Plan tiers: Ghost(Pro) limits staff users and members by plan, so growth can move you to a higher tier. Check the current limits on the pricing page before you choose.
• Analytics: Ghost's Ubuntu install guide says Ghost-CLI installs do not support web analytics, so a self-hosted site that needs analytics requires a separate Docker Compose setup.
• Confirm with the vendor: Ask where Ghost(Pro) hosts data, how backups and exports work, and what support response terms apply on your plan.

Before you choose hosted, confirm the export path you would need if you leave, because the migration works in both directions only if your content and member data can be exported.

A publisher with one or more in-house engineers can run self-hosted Ghost on a server they manage. The Ubuntu install guide lists supported versions of Ubuntu, Node.js, MySQL, NGINX and systemd, and installation runs through Ghost-CLI. Ghost publishes frequent minor releases, so the engineer needs a routine for applying them, testing the site and rolling back if needed. The cost is mostly staff time, server hosting and email delivery, and these recur every month.

• Operating effort: Expect ongoing work for OS patching, database backups, TLS renewal, Node.js and MySQL upgrades, and monitoring. Most of this is recurring rather than a one-time setup.
• What you control: Hosting provider, region, database, backup schedule, custom integrations and the Content API keys you create in Ghost Admin.
• Analytics and extras: If you need web analytics or the ActivityPub service, plan for the separate Docker Compose install that Ghost documents.
• Migration and plugins: Ghost's WordPress migration docs list custom post types and most content-restriction plugins as items that do not migrate, so check those before you leave a WordPress site.
• Confirm with the vendor and provider: Ask Ghost which versions of its supporting software are current for your release, and confirm your hosting provider's support terms for the server.

If your engineer cannot commit to regular upgrades, the hosted option is the more reliable choice, even for a technical team.

A regulated organization, such as a bank, health provider or public body that publishes member or customer communications, often needs the publication to run in an environment it controls. Self-hosted Ghost can run in the organization's own cloud account or data center, with its own database, backups, access controls and logging. Ghost(Pro) may be suitable if its hosting location and support terms meet the organization's data residency and vendor risk requirements, but that must be confirmed in writing. Self-hosting shifts more of the security and compliance work to the organization, and this work should be scoped before the decision is made.

• Operating effort: Plan for change control, patch windows, access reviews, backup testing and incident handling in the same way as other internal web applications.
• What you control: Network placement, identity and access to Ghost Admin, encryption settings, backup retention, log retention and the Stripe account configuration.
• Data flows: Map where member data, emails and payment data travel, including the email delivery provider and Stripe, because those parties are separate from the Ghost hosting decision.
• Vendor terms: Ask Ghost(Pro) for hosting location, subprocessors, data processing terms, support hours and breach notification commitments.
• Evidence: Independent auditors and certification bodies assess controls. DeployOpen prepares systems, controls and evidence for those assessments but does not issue audit reports or certifications.

Do not select an operating model until your compliance lead has confirmed the hosting location, support terms and data processing terms in writing.