Ghost ships RSS out of the box because its architecture treats the feed and the email as parallel pipes, not alternatives.

Two Outputs, One Canonical Source

Every Ghost publication — whether hosted on Ghost's infrastructure or self-deployed on a private server — generates a public RSS feed automatically at /rss. No plugin, no toggle, no opt-in. The feed appears the moment a site exists. That design choice is a position: distribution should not require permission from a platform, and no single channel should own the relationship between a publisher and a reader.

Two adults at adjacent desks in a small office, both with monitors showing feed-reader and terminal windows
Newsletter operations run small. The ten per cent buys billing, sending, and the deliverability nobody wants to run themselves.Photo: Kampus Production / Pexels
Adult leaning over a laptop showing a Feedly unread list several hundred items long, desk lamp casting warm light on the screen
A laptop, a newspaper and a pair of headphones on one desk. Three delivery routes for the same reporting, and only one of them is a feed.Photo: Beyzanur K. / Pexels

Ghost's architecture routes the same post object to both outputs simultaneously. A piece published in Ghost's editor travels to email subscribers via Ghost's built-in delivery infrastructure and to feed readers via the RSS endpoint, with the same content and at the same moment. Neither channel is subordinate. This mirrors the POSSE principle — publish on your own site, syndicate elsewhere — though Ghost operationalises it at the infrastructure layer rather than leaving it as a workflow practice.

The Ghost Foundation, a non-profit based in Singapore, governs the project. That structure insulates the roadmap from the revenue pressures that push venture-backed newsletter platforms toward consolidation and lock-in. John O'Nolan co-founded Ghost in 2013 following a Kickstarter campaign, and the Foundation model has remained intact since. Because Ghost is open-source under the MIT licence, the feed behaviour is not a feature a future owner can deprecate by policy decision — it lives in code that anyone can fork.

From the record

Architecture at a glance

  • Ghost post objectthe single content unit that routes simultaneously to email and RSS
  • /rss endpointgenerated automatically on every Ghost installation, no configuration required
  • MIT licencemeans feed behaviour cannot be removed by a future owner without a public fork

The contrast with Substack is instructive. Substack provides an RSS feed, but its business logic points toward its own reader product, which surfaces content inside a walled garden. Ghost's defaults point outward. The feed is not a concession to power users; it is the architecture's statement about what a publishing tool is for.

In a landscape where platforms increasingly route content through proprietary algorithms, a CMS that generates a syndication feed by default is making a claim about who controls distribution. Ghost's answer is the publisher.