A buyer pays for operations, not code exclusivity. Ghost describes a cycle in which free software creates demand for the managed platform, which funds more free software (About). The product grew toward publisher revenue. The retrospective explains the move beyond editing into memberships and subscriptions, including custom paid tiers and audience segmentation (Ghost 5.0). Ownership is part of the offer. Ghost says its nonprofit constitution prevents a sale and reinvests all revenue. That is its stated governance structure, not our legal audit (About).

Ghost: free software, paid hosting, nonprofit ownership

Q: What didn't work for Ghost, and what are the risks?

Slow execution was real. Ghost says it took three years before it could hire more product engineers for new ideas, then another two to build the membership beta (Ghost 5.0). Open source is not automatically a business. The paid hosting layer is the monetization mechanism; the existence of free users alone does not establish demand for it. See [RethinkDB](/case-studies/rethinkdb) for the opposite company outcome. Dashboard totals and retrospective claims come from Ghost itself. Run rate is not profit, and installs are not paying customers (About).

Key takeaways

Founded in April 2013; the foundation says it cannot be bought or sold.
Its live dashboard showed roughly $11.1M annual run rate when checked on 7 November 2026; this is company-reported, not audited here.
Memberships were a slow, revenue-funded expansion, not an overnight creator-economy pivot.

What it is

Ghost is an open-source publishing platform for websites, newsletters and paid memberships. The free software attracts publishers; customers who want a managed service pay for Ghost(Pro), funding the foundation and further development (Ghost About).

Timeline

April 2013: John O’Nolan and Hannah Wolfe founded Ghost. Its first prototype was released on April 29, according to the later product retrospective (About, Ghost 5.0).
2015: Ghost says it had three product engineers, $36k MRR and no other funding. It mapped out a broader publishing business rather than competing only as a blog editor (Ghost 5.0).
2022: the Ghost 5.0 retrospective described about $5M annual revenue and expanded paid tiers, newsletters and audience tools. These are historical company figures, not current revenue (Ghost 5.0).
Checked 7 November 2026: its live dashboard displayed $11,136,975 annual run rate and 30,377 active customers. These are company-reported snapshots and can change (About).

Why it worked

A buyer pays for operations, not code exclusivity. Ghost describes a cycle in which free software creates demand for the managed platform, which funds more free software (About).
The product grew toward publisher revenue. The retrospective explains the move beyond editing into memberships and subscriptions, including custom paid tiers and audience segmentation (Ghost 5.0).
Ownership is part of the offer. Ghost says its nonprofit constitution prevents a sale and reinvests all revenue. That is its stated governance structure, not our legal audit (About).

What to learn

Identify the recurring operational job that customers would rather outsource than self-host.
Fund adjacent capabilities from demonstrated demand instead of copying a fashionable competitor.
Explain what your ownership structure means for customers. Compare this continuity promise with Skiff’s acquisition and sunset.

Risks and what didn't work

Slow execution was real. Ghost says it took three years before it could hire more product engineers for new ideas, then another two to build the membership beta (Ghost 5.0).
Open source is not automatically a business. The paid hosting layer is the monetization mechanism; the existence of free users alone does not establish demand for it. See RethinkDB for the opposite company outcome.
Dashboard totals and retrospective claims come from Ghost itself. Run rate is not profit, and installs are not paying customers (About).

FAQ

Short answers drawn from the sections above.

What is Ghost?

Why did Ghost work?

A buyer pays for operations, not code exclusivity. Ghost describes a cycle in which free software creates demand for the managed platform, which funds more free software (About).
The product grew toward publisher revenue. The retrospective explains the move beyond editing into memberships and subscriptions, including custom paid tiers and audience segmentation (Ghost 5.0).
Ownership is part of the offer. Ghost says its nonprofit constitution prevents a sale and reinvests all revenue. That is its stated governance structure, not our legal audit (About).

What can indie builders learn from Ghost?

Identify the recurring operational job that customers would rather outsource than self-host.
Fund adjacent capabilities from demonstrated demand instead of copying a fashionable competitor.
Explain what your ownership structure means for customers. Compare this continuity promise with Skiff’s acquisition and sunset.

What didn't work for Ghost, and what are the risks?

Slow execution was real. Ghost says it took three years before it could hire more product engineers for new ideas, then another two to build the membership beta (Ghost 5.0).
Open source is not automatically a business. The paid hosting layer is the monetization mechanism; the existence of free users alone does not establish demand for it. See RethinkDB for the opposite company outcome.
Dashboard totals and retrospective claims come from Ghost itself. Run rate is not profit, and installs are not paying customers (About).

Sources

Every link cited above, in order of first use.

1.Ghost About (ghost.org)
2.Ghost 5.0 (ghost.org)