John O'Nolan, Founder of Ghost - the Open Source blogging tool making $7.2m ARR
Ghost founder John O’Nolan explains how a nonprofit, open-source publishing platform built a sustainable hosting business — and why independence is a clearer promise to publishers than source code alone.
John O’Nolan is the founder and CEO of Ghost, the open-source blog and newsletter platform used by Scaling DevTools. At the time of this recording, Ghost was generating more than $7 million in annual recurring revenue.
John describes the growth unlocked by memberships and newsletters, the alignment created by Ghost’s nonprofit structure, the real economics of managed hosting, the trade-offs of decentralization and the smallest possible way to test a new idea.
The Q&A below is experimental — extracted from the episode transcript with AI. If you spot a mistake, let us know at jack@scalingdevtools.com.
What caused Ghost’s biggest period of growth?
Ghost evolved from a blogging platform into infrastructure for people who publish professionally. Adding newsletters, memberships and paid subscriptions coincided with Substack popularizing the format and the creator economy accelerating during the pandemic. That combination produced Ghost’s first real hockey-stick period, and the underlying market continued growing after the initial spike settled.
How do you explain open source to non-developers?
The source code is less persuasive than independence. A publisher on a closed platform can lose reach to an algorithm change, inherit a paywall or watch the product pivot. With Ghost, nobody can take the publication away: a customer can move the same software to another server and continue. People understand that promise most clearly after they have already experienced platform lock-in.
Why is “independence” more prominent than “open source” in Ghost’s marketing?
Most homepage visitors are publishers, not developers, and “open source” can make the product sound technical before they understand its benefit. The primary message therefore focuses on control, independence and the nonprofit mission. Developer documentation, installation guides and GitHub links remain readily available one level deeper, where the audience is actively looking for implementation detail.
How can the entire product be open source while Ghost makes money?
Ghost sells the easiest way to operate the same code. Ghost(Pro) handles frequent upgrades and preconfigures email delivery, payments, image processing and other services, while anyone remains free to self-host. Managed hosting creates predictable recurring revenue and useful margins, making hiring much easier than a business dependent on uneven one-off license sales.
Why would a large company pay instead of self-hosting?
A cheap server stops being the full comparison once the organization needs reliable newsletters, deliverability work, on-call coverage, DDoS protection, payments and integrations. Ghost spreads those systems and vendor volume discounts across many customers; a company rebuilding the equivalent often spends more in specialist salaries alone. Self-hosting still makes sense for a developer with simpler needs, and it uses exactly the same feature set.
How does Ghost’s nonprofit structure align the business and project?
Neither John nor co-founder Hannah owns Ghost; they serve as trustees. The organization earns hosting revenue, pays its team and reinvests any surplus in the mission rather than distributing it to founders, shareholders or investors. Customers can see their subscription funding the software they use, which creates trust that product decisions serve the community instead of preparing an acquisition or maximizing an owner’s payout.
What governance lesson do you take from the WordPress conflict?
Open-source community assets and the venture-backed company should have clean ownership and independent leadership. A foundation could own the project, domains and trademarks, while a commercial company receives explicit rights to operate its service. Separate boards would each have an unambiguous duty. Tangled ownership and overlapping authority make every decision look conflicted, even when individual choices may be defensible.
How does Ghost compete with heavily funded centralized platforms?
Centralized products can deploy instantly, serve users from shared systems, subsidize free plans and pay prominent writers to join. Ghost instead operates thousands of databases and domains, and the modern web’s OAuth, API and observability assumptions make decentralization harder. The advantage appears as publications mature: open architecture permits deeper themes, integrations and customization than a closed shared platform can safely allow.
What would you fund if Ghost suddenly had spare venture-scale money?
I would use a free tier selectively to incubate local news organizations. Advertising’s collapse damaged journalism’s business model, and many communities now lack anyone reporting on the decisions that shape daily life. Reader-funded memberships can restore an incentive to deliver work worth paying for. Extra capital could help new local publications reach the point where that model sustains them.
What is your advice to someone starting a product?
Ship earlier and cut the feature set in half. Ghost’s first MVP was a blog post describing the idea: if nobody had cared, there would have been no reason to spend years building it. Search relentlessly for the smallest artifact that tests demand — perhaps only a tweet — and use the response to earn the next increment of effort.
Links & references
- Ghost ↗
- John O’Nolan’s website ↗
- WordPress and WP Engine explainer ↗
- John O’Nolan on Indie Hackers ↗
- Stratechery ↗
This episode is brought to you by WorkOS.