Which is better, Substack or Ghost?
Substack vs Ghost for developers: list ownership, exports, APIs, themes, a fee break-even example and what self-hosting costs in ops.
Neither is better in general, but they optimize for different things. Substack is better if you want zero ops and a built-in audience: you write, it handles sending, payments and a network of readers who already live inside its app. Ghost is better if you care about owning the stack, paying a flat price instead of a percentage, and controlling the front end and the data through code. For a developer who already has an audience, or plans to monetize seriously, Ghost usually wins on the numbers. For someone who wants to start writing tonight and find readers inside a network, Substack usually wins on friction.
The honest tie-breaker is a number you can compute yourself: how many paying subscribers you expect, and what a flat plan costs against a percentage. I'll show that math with a worked example, then cover exports, APIs, themes, discovery, self-hosting and migration, with five other options alongside.
Disclosure: I work on VeloCMS, which is one of the seven options I compare near the end, with its weaknesses listed like everyone else's. Most of this piece is about Substack and Ghost.
Last verified: November 14, 2026.
Every price and feature claim sits on a vendor page I opened that day, linked in Sources. One limit: Substack's help center returned a 403 to my fetcher, so for Substack I leaned on its fee page, its public blog posts and Ghost's migration guide. Where a claim rests on less than a primary page, I say so.
Who owns the subscriber list, and how do you get it out?
Both platforms say you own your list. The practical question is what "own" means when you're standing at the exit with a laptop.
On Substack, the subscriber export is a CSV. Substack's own subscriber dashboard guide describes clicking an Export button, optionally scoping the export to a filtered list, then downloading the file. Ghost's migration guide, which is the other half of this story, also tells you to create a full content export in Substack's settings (a zip) and to download a free-subscriber CSV and a paid-subscriber CSV separately. So three artifacts leave Substack: your posts, your free list, your paid list.
Ghost works the other way around, and it's the more complete export of the two. In Ghost Admin you open the Import/Export settings and pick the Export tab. The help page lists a single zip containing your content and settings as JSON, members as CSV (with labels, custom fields and subscription status), post analytics as CSV, every installed theme including any custom code, and your routes and redirects files. Media files are included only on Ghost(Pro); on a self-hosted install you copy them from the server yourself. Ghost(Pro) emails you a download link that lasts seven days; self-hosted downloads immediately.
Notice what that implies for a developer. A Ghost export includes the theme and the redirect rules, so you can re-host your exact templates elsewhere. A Substack export has posts and lists, and you rebuild the presentation.
Paid subscriber data is the open question. Ghost's export page says the members file carries labels, custom fields and subscription state, and doesn't say whether Stripe customer IDs are in it. Ghost's member import page does list a stripe_customer_id column (a Stripe customer ID, or auto to let Ghost match by email against your connected Stripe account), so a Stripe-linked move is a supported path in the other direction. The Ghost migration docs have you connect the same Stripe account you used on Substack before importing paid members, which is the real portability lever. If your payments sit in a Stripe account you control, moving is a data-mapping job. If they don't, you're asking a platform to cooperate.
What do the fees look like, and where is the break-even?
Here's where the two models diverge, and where a developer's instinct to compute something pays off.
Substack's fee page says writers keep 90% of their revenue minus credit card fees. So Substack takes 10%, and card processing comes out of your share on top. Ghost's pricing page lists a 0% transaction fee on every plan that supports paid subscriptions, and notes that payment processor fees still apply. Ghost's flat price replaces Substack's percentage, so the comparison reduces to one inequality: is 10% of your monthly paid revenue larger than the flat plan?
Stripe's cut applies to both, so it cancels out of the comparison. A Stripe support page states that standard card payments are 2.9% plus 0.30 USD in the US (Stripe's own pricing page served me UK rates when I fetched it, and rates vary by country, so check yours). The shape matters at small prices: on an $8 monthly charge that's about $0.53, roughly 6.7%, while on an $80 annual charge it's about $2.62, roughly 3.3%. The fixed 30 cents punishes cheap monthly plans on every Stripe-based platform.
Now the worked example. This is an assumption, not a benchmark: a paid tier at $8 a month, and Ghost(Pro)'s Publisher plan, which the pricing page lists at $29 a month billed yearly (that's $348 a year). Substack's 10% of $8 is $0.80 per paying subscriber per month. Divide $29 by $0.80 and you get 36.25, so you break even at 37 paying subscribers. At 36 paying subscribers Substack costs you $345.60 a year, a little under $348. At 37 it costs $355.20, a little over. After that, every additional subscriber widens the gap in Ghost's favor.
Scale it up. At 500 paying subscribers, Substack's cut is $400 a month, against $29 for the flat plan. The catch: the Publisher plan shows 1,000 members, free subscribers included, so the break-even holds only while your total list stays inside that cap. At 2,000 paying readers the cut would be $1,600 a month, but I couldn't read a price for that size off the page text, so I won't invent one. Check ghost.org/pricing. (It also shows conflicting member figures for the Business plan between its card and its comparison section.)
Self-hosted Ghost changes the equation again. Ghost takes no cut and charges no license fee, so your costs are a server, a bulk-mail provider and your own hours. Plug them into the same formula:
break-even paying subs = ceil(monthly flat cost / (0.10 x monthly price))
Assume $40 a month all in (a made-up figure; price your own VPS and mail volume) and the answer at $8 is 50 paying subscribers. Value your hours at a real rate and the number climbs fast, which is the part developers tend to under-count.
Two more flat-price data points. beehiiv's pricing page lists a Lite plan from $49 a month billed annually at up to 1,000 subscribers, with a 0% platform fee on paid subscriptions, and the price rises with list size. At $8 a month that breaks even against Substack at 62 paying subscribers. VeloCMS's pricing page lists Pro at $9 a month (or $86.40 billed yearly) with a membership paywall at 0% platform fee, which puts the break-even at 12 paying subscribers, with the caps covered below.
One small cost people forget: Substack's announcement for custom domains says a one-time $50 fee per publication unlocks the feature, after which you can add and remove domains at no extra charge. That's separate from buying the domain.
Does either platform have an API I can build on?
This is the cleanest technical split. Ghost is an API product first. Substack, as far as I can verify, isn't.
Ghost has two APIs, and the pricing page ties them to plans. The Content API is read-only, authenticated with a key passed as a query parameter, and the docs say that key is safe to use in browsers because it only exposes public data. It's how you run headless Ghost: render posts, pages, tags, authors and tiers from any front end. The pricing page lists the Content API on every Ghost(Pro) plan, including Starter.
The Admin API is the write side. The docs say everything Ghost Admin can do is possible through it. You create a custom integration in Ghost Admin to get an id and secret, then you generate short-lived JSON Web Tokens from them (the payload's expiry can be at most five minutes after issue) and send them in an Authorization header. Posts, pages, tags, labels and webhooks have full create, edit and delete, tiers, newsletters and offers support create and edit, and members can be browsed, read, added and edited. Themes can be uploaded and activated, images uploaded. Keys must stay server-side. On Ghost(Pro), the Admin API, webhooks and custom integrations are listed from Publisher up; Starter doesn't have them.
Webhooks cover the lifecycle events you'd want to react to: site changes, post and page events including published, scheduled and unpublished, tag attach and detach, and member added, edited and deleted. You add a target URL and a trigger in the integrations screen, Ghost POSTs a JSON body, and any 2xx response counts as success. That's enough to sync members into a CRM or rebuild a static front end on publish.
Substack is a different story. The official surface I could verify is its Developer API terms of use, which describe returning only information creators have made publicly visible on their profiles: things like name, social URLs, total subscriber count and bestseller status. That's profile metadata, not publishing, and not your subscribers or posts. I found no documented official API for writing posts, reading your list or receiving subscription events. Third-party sources describe unofficial endpoints and scrapers, which Substack doesn't support and I wouldn't build on. For automation, plan around CSV exports and email, not webhooks.
The others vary. Buttondown's docs describe an API meant to cover essentially every object in the product, with subscribers and sending as the examples. beehiiv's pricing page lists "API and integrations" on its Free plan and webhooks among the Pro plan's features, so check its comparison table for per-plan limits before you build on it. VeloCMS's pricing page lists API access at 10,000 calls a day on Pro, 100,000 on Business and uncapped on Agency.
How much control do you have over the front end?
Ghost themes are Handlebars templates, served by Express, and the theme docs say Ghost runs express-hbs so you get layouts and partials. There's a validator called GScan that checks a theme for errors and deprecations, available on a web page and as a CLI (npm install -g gscan, then gscan /path/to/theme). Upload a theme zip in Ghost Admin and the same validation runs; a fatal error prevents the theme from being used. Because the Admin API can upload and activate themes, you can put theme deployment in CI.
Plan gates matter. Ghost(Pro)'s Starter plan is listed with only the built-in default theme, and custom and marketplace themes start at Publisher. Self-hosted has no such gate. And if Handlebars isn't your idea of a good time, the headless route lets you ignore the theme layer and build the public site in any framework, calling the Content API.
Substack is the opposite deal: you configure, you don't template. Its own posts describe a website editor with themes, homepage layouts, colors and fonts, and none of the pages I read mention custom code, HTML or templating. I couldn't find a Substack page that documents uploading your own templates, so treat it as a settings-driven product. That conclusion is my inference from the absence, not a quote. That's a feature if you want your newsletter to look right in ten minutes. It's a limit if you want a specific information architecture, structured data, or an unusual page type.
This ties to search. With Ghost themes you decide what lands in the head: titles, canonical tags, structured data. Whether that ranks better is a different question and I haven't measured it, but the control is real. On Substack you work with what the platform exposes. If organic search is a primary channel, template access is worth real weight.
Which one helps readers find you?
Here Substack earns its reputation, and I'd be doing you a disservice to wave it away.
Substack's recommendations feature, per its own announcement, lets writers directly endorse each other's publications. Recommended publications appear to readers after they subscribe, the post says it isn't algorithmic, and recommended writers are notified and encouraged to recommend back. Notes, per Substack's post, is a space for short-form posts inside the app, and the same post says that having worthy posts shared widely has historically been one of the major ways writers find growth on Substack, with restacking as the sharing tool. The Notes post adds that Notes lives in Substack's mobile apps as well as on the web. None of that exists outside Substack's network, and it's the strongest argument for the platform.
Ghost has been building toward a response. Its Recommendations feature is cross-promotion between publishers: you add a site in the Growth settings and the pop-up appears when a new member signs up. Ghost's help page labels it a beta and doesn't say whether self-hosted installs get it, though the pricing page lists it on every Ghost(Pro) plan, so verify before you plan around it on your own server. Its social web feature, built on ActivityPub, gives a site a public handle that people on other open social platforms can follow, and posts get shared automatically. The help page says it is currently in beta, lists missing features (no reporting or muting of people yet, no video attachments on notes), and requires a custom domain that isn't a subdirectory. That page doesn't mention self-hosting, but Ghost's Docker install docs do: new installs use Ghost's hosted ActivityPub service by default, free for self-hosters up to 2,000 followers, 2,000 following and 100 interactions a day, and that page is itself marked preview. So Ghost's discovery story is real but young: an open network you can join, not a closed one that sends you traffic. If your growth plan is being found through Substack's feed, Substack is the practical call. If it's search, social, talks or an existing audience, ownership matters more.
What does self-hosting Ghost actually take?
Ghost is open source under the MIT license, according to its GitHub repository, and the Ghost home page says it is independent and funded 100% by its users, with a Non-Profit Foundation badge in the footer. That makes self-hosting legitimate and free of license fees. It doesn't make it free of work.
The Ubuntu install guide lists Ubuntu 22.04, 24.04 or 26.04, a supported Node.js version, MySQL 8.0 or 8.4, at least 1 GB of memory, NGINX, systemd and a domain with a DNS A record pointing at the server. The configuration docs list MySQL as the default database and SQLite as an alternative. For email, the same docs say Mailgun is optional for transactional mail but required for bulk mail, so sending newsletters to members means setting up a bulk-mail provider on top of the server. Transactional mail goes through SMTP.
Add the unglamorous parts: backups (media on a self-hosted install isn't in the admin export), OS, Node and Ghost upgrades, TLS renewal, monitoring and deliverability. If your newsletter lands in spam on a Tuesday, you're the postmaster. Ghost(Pro) removes that burden.
My unscientific rule: if your realistic monthly maintenance hours, priced at your own rate, exceed a month of Ghost(Pro), pay Ghost and keep your weekends. If you enjoy running servers, or need data in a specific jurisdiction, self-host.
How do you migrate between them?
Substack to Ghost is well documented, because Ghost wants the traffic. The docs describe a migrator in Import/Export settings: enter your public Substack URL, upload the zip from a Substack export, upload the free-subscriber CSV, then, for paid members, connect Stripe first (the same Stripe account used on Substack) and upload the paid-subscriber CSV. Review the counts, then import. Two follow-ups from that same page are worth copying into your plan. First, Substack will keep taking its 10% on existing paid subscriptions, and Ghost's guide points you to concierge@ghost.org if you want help getting those payment fees removed. Second, if you used a custom domain on Substack, you need redirects in Ghost to prevent broken links: Substack puts /p/ in public post URLs while Ghost uses it for post previews, so the docs give a redirect rule for your redirects.yaml that excludes UUID-style preview paths.
Ghost to Substack is the direction I can't document from a primary source, since Substack's help pages wouldn't load for me. Check Substack's import docs for what carries over, particularly paid subscribers, before you commit.
The general pattern holds either way: export content, export the list, keep payments in your own Stripe account, and set redirects before you flip DNS. Compare the export's member count with your dashboard, since third-party guides report mismatches.
How do the seven options compare?
Each entry has the same shape: what it is, price signals from its own page, one strength and one weakness. Prices are as listed on the vendor pages on the verification date.
Substack
A hosted newsletter and publishing platform with a built-in reader network.
- Price signal: writers keep 90% of revenue minus card fees; a one-time $50 custom domain fee per publication.
- Strength: discovery through recommendations, Notes and the app; nothing to run.
- Weakness: a percentage cut that scales with success, limited customization, and no documented official API for posts or subscribers.
- Source: https://substack.com/going-paid
Ghost(Pro)
Ghost's official managed hosting.
- Price signal: Starter $18, Publisher $29, Business $199 a month, all billed yearly; 0% transaction fee on plans with paid subscriptions.
- Strength: Content API on every plan, Admin API and webhooks from Publisher, custom themes from Publisher.
- Weakness: Starter has no paid subscriptions, no custom themes and no Admin API; member caps push you up the price ladder.
- Source: https://ghost.org/pricing/
Self-hosted Ghost
The same open-source software on your own server.
- Price signal: no license fee; you pay for the server, a bulk-mail provider and your time.
- Strength: full control and no platform cut.
- Weakness: you run everything, including backups, upgrades and mail deliverability.
- Source: https://docs.ghost.org/install/ubuntu
beehiiv
A hosted newsletter platform.
- Price signal: Free to 2,500 subscribers with no paid subscriptions; Lite from $49 a month billed annually; Pro from $95; 0% platform fee on paid plans.
- Strength: a free tier with API access and a growth-oriented product.
- Weakness: price rises with list size, and the paid-subscription feature is not on Free.
- Source: https://www.beehiiv.com/pricing
Buttondown
A hosted newsletter service with a developer-friendly API.
- Price signal: free for the first 100 subscribers; add-ons such as paid subscriptions are an extra $9 a month; the base price above 100 isn't shown as text on the page.
- Strength: an API meant to cover its whole product.
- Weakness: add-on pricing makes the true cost harder to estimate, and custom-domain archives are a $29 add-on.
- Source: https://buttondown.com/pricing
WordPress with Jetpack Newsletter
A newsletter bolted onto the WordPress ecosystem.
- Price signal: fees on paid subscriptions range from 10% on the Free plan to 2% on the Complete plan, plus Stripe fees.
- Strength: you can use WordPress's theme and plugin ecosystem, and the page lists CSV import of existing subscribers.
- Weakness: paid-subscription fees are highest on the Free plan, and you'd be running WordPress as well. A separate Jetpack support page does document a CSV subscriber export.
- Source: https://jetpack.com/newsletter/
VeloCMS
A hosted blog platform from the company I work for, with newsletter, membership and a store.
- Price signal: Pro $9 a month or $86.40 billed yearly; 14-day trial with a card required unless you have a cardless trial code; no free plan; 0% platform fee on membership.
- Strength: API access, newsletter, membership and e-commerce on the same plan.
- Weakness: it's managed SaaS only, with no self-hosted install; Pro caps newsletter subscribers at 5,000; and, as my own disclosure-biased opinion rather than a measured fact, it is the newest product on this list, so weigh its public track record against the older tools yourself.
- Source: https://velocms.org/pricing
When is Substack the better choice?
Pick Substack when speed and audience matter more than control. If you've never run a newsletter, a polished editor and a send button beat debugging a mail pipeline. It's the lowest-risk way to test whether a paid newsletter can work at all: the break-even math says the percentage is the cheaper model until you reach a few dozen paying subscribers.
When is Ghost the better choice?
Pick Ghost when you can already describe your business in numbers. With hundreds of paying subscribers, the flat-versus-percentage math favors Ghost by a wide margin. If you want your own templates, structured data and API-driven automation, Ghost gives you hooks Substack doesn't. And if you may leave someday, a documented export of content, members, themes and redirects is a safer place to build. The cost is operational: Handlebars for custom themes, and sysadmin duty if you self-host.
Who is each option best for?
- Substack: writers who want built-in discovery, no ops, and are happy to pay a percentage for it.
- Ghost(Pro): publishers who want Ghost's code-level control and flat pricing without running servers.
- Self-hosted Ghost: developers who enjoy ops, want maximum control, or have data-residency needs.
- beehiiv: newsletter operators who want a growth-focused hosted tool with a free entry tier.
- Buttondown: developers who want a small, scriptable service and are fine with add-on pricing.
- WordPress with Jetpack: people already on WordPress who want a newsletter without a second platform.
- VeloCMS: bloggers who want newsletter, membership and a store on one hosted plan. It isn't the pick if you need to self-host or want a free tier.
FAQ
Is Ghost cheaper than Substack?
At scale, yes; at the start, no. In the example above, Ghost(Pro) Publisher beats Substack once you pass 37 paying subscribers at $8 a month. Below that, Substack costs less.
Can I export my subscribers from Substack?
Yes. Substack's dashboard guide describes a CSV export, and Ghost's migration guide has you download separate free and paid subscriber files plus a content export.
Does Substack have an API?
Not one I could verify for publishing or subscribers. Its Developer API terms describe only public creator profile data.
Do I need Mailgun to self-host Ghost?
Ghost's configuration docs say Mailgun is optional for transactional email but required for bulk mail, so plan on a bulk-mail provider.
Can I keep my Stripe customers if I move?
Ghost's migration guide has you connect the same Stripe account you used on Substack before importing paid members, so keep that account under your control.
Is Ghost's ActivityPub support finished?
No. Its help page says the feature is currently in beta and lists missing features. Ghost's Docker install docs say new self-hosted installs use Ghost's hosted ActivityPub service by default, with free-tier limits, and mark that page as a preview.
Sources
- Substack fees: https://substack.com/going-paid
- Substack custom domain announcement: https://on.substack.com/p/new-add-a-custom-domain-to-your-substack
- Substack subscriber dashboard guide: https://on.substack.com/p/subscriber-dashboard-guide
- Substack recommendations: https://on.substack.com/p/recommendations
- Substack Notes: https://on.substack.com/p/notes
- Substack website customization: https://on.substack.com/p/themes-search
- Substack Developer API terms: https://substack.com/api-tos
- Ghost pricing: https://ghost.org/pricing/
- Ghost home page: https://ghost.org/
- Ghost exports: https://ghost.org/help/exports/
- Ghost recommendations: https://ghost.org/help/recommendations/
- Ghost social web: https://ghost.org/help/social-web/
- Ghost Content API: https://docs.ghost.org/content-api
- Ghost Admin API: https://docs.ghost.org/admin-api
- Ghost webhooks: https://docs.ghost.org/webhooks
- Ghost themes: https://docs.ghost.org/themes
- Ghost configuration: https://docs.ghost.org/config
- Ghost Ubuntu install: https://docs.ghost.org/install/ubuntu
- Ghost Docker install (ActivityPub on self-hosted): https://docs.ghost.org/install/docker
- Ghost member import columns: https://ghost.org/help/import-members/
- Ghost Substack migration: https://docs.ghost.org/migration/substack/
- Ghost on GitHub: https://github.com/TryGhost/Ghost
- Stripe US card fee: https://support.stripe.com/questions/manually-entered-card-payments
- Stripe pricing (UK page served to my fetcher): https://stripe.com/pricing
- beehiiv pricing: https://www.beehiiv.com/pricing
- Buttondown pricing: https://buttondown.com/pricing
- Buttondown API: https://docs.buttondown.com/api-introduction
- Jetpack Newsletter: https://jetpack.com/newsletter/
- Jetpack subscriber export: https://jetpack.com/support/newsletter/export-subscribers/
- VeloCMS pricing: https://velocms.org/pricing
- VeloCMS tech stack: https://velocms.org/tech-stack
About the author
- Building VeloCMS.org , A fast multilingual CMS for blogs and online stores. I write about headless CMS, Next.js, SEO and moving off WordPress and Shopify.
Comments
Join the discussionNo comments yet. Be the first to comment.