Ghost for publishers: memberships and newsletters built in

What is Ghost?

Ghost is an open-source publishing platform maintained by the Ghost Foundation. Its repository describes it as independent technology for modern publishing, memberships, subscriptions and newsletters. It is written in JavaScript and runs on Node.js, which sets it apart from the PHP systems that dominate this site’s CMS directory.

The project is MIT-licensed, with copyright held by the Ghost Foundation (2013-2026 in the repository’s licence file). The latest release marked on GitHub on 2026-10-10 was v6.69.0. For the licence’s practical meaning, see our licensing guide.

Who is Ghost best for?

Ghost fits publications whose revenue model is readers: subscriptions, memberships and a newsletter that goes out with each post. A solo journalist, a niche magazine or a small local outlet can run the whole operation from one admin without stitching together a membership plugin, a payment plugin and an email service.

It is a weaker choice if you need a large editorial team with custom permissions, complex taxonomies, many languages on one site or a library of third-party extensions. It also assumes a developer comfortable with Node.js if you self-host. Teams that want a PHP shared-hosting install should look at other profiles.

Three cases show where it lands. A solo journalist or small collective selling a paid newsletter gets the shortest route: the membership documentation describes free and paid members, tiered access and Stripe payments in one product, and states that Ghost takes 0% of revenue. A small local outlet can map its desk onto the Contributor, Author and Editor roles. A larger publisher that already runs a subscription system might use Ghost only as a writing tool and front end, reading content through the API.

The weak cases are the mirror image: sites with little reader revenue, sites that need many custom content types, and organisations that must keep to a PHP-only estate. Before choosing, write down which of your content types are plain articles and which are not. Ghost handles articles and pages well; anything else means a workaround or a different system.

How does Ghost handle the editorial workflow?

The documentation lists five staff roles. Contributors can write posts but cannot publish. Authors can create and publish new posts and tags. Editors can invite, manage and edit authors and contributors. Administrators have full permissions, and the Owner is an admin who cannot be deleted and holds billing access.

That gives a workable pipeline for a small desk: contributors draft, an editor manages the people, and authors publish. What the documentation we read does not describe is custom roles or per-section permissions, so treat the five roles as fixed.

Scheduling works by setting a post’s status to scheduled with a future publication time. The Admin API documentation says that at that time the post is published, any email newsletter is sent and the status changes to published. We could not confirm a revision-history feature from the pages we opened, so check the current help centre if version history matters to you.

What does Ghost offer for SEO, structured data and feeds?

According to Ghost’s SEO help page, each post and page has its own metadata, an XML sitemap is created and updated automatically, structured data is included on all posts and pages, and canonical tags are added. For a news site that means the technical basics need no plugin.

The page does not describe feeds, redirect management or Google News requirements, and we did not verify them. If you run a news publication, check feeds and redirects against the current documentation, and follow Google’s own guidance for Google News eligibility rather than a CMS’s marketing.

Media, multilingual and performance

The documentation pages we opened did not state how Ghost handles multiple languages on one site, image processing or caching, so this profile makes no claims there. If a bilingual or multi-region site is on your list, ask the vendor or test it before committing. Our feature checklist lists the questions to put to any CMS.

Hosting and requirements

Ghost’s documented production stack is Ubuntu 22.04, 24.04 or 26.04 LTS, Node.js 22 LTS, MySQL 8.0 or 8.4 and NGINX, on a server with at least 1 GB of memory, using a non-root user to run ghost commands. The documentation says other setups may work, but this is the stack the vendor supports.

Newsletters add a requirement for self-hosters. The documentation says a bulk mail provider is required to deliver bulk mail reliably, and that Mailgun is the only supported one at present. See our self-hosted guide for the broader trade-offs of running your own server.

Ghost’s own documentation calls Ghost(Pro) its official PaaS, where a fully managed instance can be set up in a couple of clicks.

Extending Ghost

Themes use the Handlebars templating language, with express-hbs adding layouts and partials. For integrations, the Content API is a read-only REST API returning JSON, and webhooks let Ghost POST to a URL you configure when something happens, such as publishing.

Together they make Ghost usable as a headless CMS: the editor and membership system stay in Ghost, and a separate front end renders the pages. We have not verified the size of Ghost’s integration or theme ecosystem, so we do not quote one.

What does Ghost cost?

The software is free under the MIT licence. Self-hosting costs are a server, backups, a Mailgun account for newsletters and developer time.

Ghost(Pro) is the paid route. On 2026-10-10 the pricing page listed Starter at US$15 a month billed yearly (the page’s toggle gives US$18 a month when billed monthly), Publisher at US$29 a month, Business at US$199 a month and a Custom plan. The page builds its prices in the browser, so read them from the live page before relying on them. Member limits and feature differences between plans are on that page too. For the wider picture see our cost guide.

On revenue, the membership documentation states that Ghost takes 0% of what a publication earns. Stripe’s own processing fees are separate and are not covered here.

A realistic budget has four lines: software (nothing, or a Ghost(Pro) plan), email delivery for self-hosters, a person to maintain the server and updates, and a designer or developer for the theme. Managed hosting moves the third line into the subscription, which is the main reason a small team without a sysadmin may prefer it. Self-hosting suits teams that already run Node.js services.

Where does Ghost fall short?

• Narrow permissions. Five fixed staff roles, no custom roles in the documentation we read.
• Mailgun dependency. Self-hosted newsletters need Mailgun; SMTP is not the bulk route.
• Not a PHP stack. If your hosting, developers and agency know PHP, Node.js and MySQL 8 are a new operational skill.
• Unverified areas. We could not confirm from the documentation we opened how Ghost handles multiple languages, revision history, feeds or redirects.
• Prices load client-side. Ghost(Pro) figures need checking on the live page each time.

The verdict for publishers

Ghost is a focused tool. If your publication earns from subscribers and wants posts, members and email in one product, it removes a lot of assembly. The documentation describes a sensible, lean editorial model, and the MIT licence leaves you free to move.

If your newsroom needs layered approvals, many languages or a large extension market, it is the wrong shape. This profile is based on the vendor’s documentation only, not on a test install; see how we test for what we do and do not claim.