Ghost on any website.

Ghost ships two official APIs in every release since Ghost 2.x: the Content API for public read access and the Admin API for write and member operations. The Content API is documented, versioned, and explicitly designed for embedding Ghost content on third-party sites. You generate a read-only Content API key under Settings, Integrations, Add custom integration in your Ghost admin, paste it into a widget tool, and the tool can fetch posts, tags, authors, and newsletters from your publication. The key is read-only by design, so a widget cannot publish, edit, or delete anything in your Ghost no matter how compromised it gets. Poper uses the Content API exclusively for public posts and the Admin API only for fetching the public-preview HTML of paid member posts when you opt in. Every other Ghost embed path, scraping the rendered HTML, hitting undocumented internal endpoints, or piggybacking on Ghost's RSS feed, is either against the terms of service or fragile when Ghost ships a new version. Since the Content API contract is stable across Ghost 2.x, 3.x, 4.x, and the current 5.x release line, your embed keeps working through every Ghost upgrade automatically. Self-hosted Ghost installs and Ghost(Pro) hosted publications expose the same Content API at the same endpoint paths, so the widget configuration is identical regardless of which hosting model you use.

Ghost added native memberships in Ghost 3.0 and native paid subscriptions powered by Stripe in Ghost 4.0. As of the Ghost 5.x release line, the platform supports unlimited member tiers, monthly and yearly billing, complimentary tiers for VIPs, and gift subscriptions, all without taking a cut of subscription revenue. This is the headline economic difference between Ghost and Substack: Ghost takes 0 percent of paid subscription revenue (you only pay Stripe processing fees), while Substack takes a flat 10 percent on top of Stripe fees. For a publication with 1,000 paid subscribers at $10 per month, that is $1,000 per month that stays with the publisher on Ghost versus going to Substack on the same revenue base. The widget needs to surface this paid-tier model honestly. Public posts render in full inside the embed because they generate no revenue regardless of where they are read. Member-only and paid-tier posts surface a public preview block (the same first-paragraph or two preview that Ghost itself renders to non-members) with a clear member-only badge and a Subscribe to read CTA wired straight to your Ghost member signup page. The signup happens inside Ghost, the Stripe payment runs through your own Stripe account, and the member relationship lives in your own Ghost member database. The widget never breaks the paywall and never attempts to render gated content, which is the only honest pattern for paid Ghost posts.

Ghost is MIT-licensed open-source software that you can self-host for free on your own server or Docker host. The official commercial offering, Ghost(Pro), is managed hosting run by Ghost Foundation themselves, which funds the open-source development. As of 2026, Ghost(Pro) starts around $9 per month for the Starter tier with up to 500 members and includes managed updates, automatic backups, and email delivery via Mailgun. Self-hosted Ghost is free to run but requires you to manage a Node.js server, MySQL database, email delivery service, and ongoing security updates yourself. Both options expose the identical Content API at the same endpoint paths, so a Ghost feed widget works the same way against either. Independent journalists, newsletter founders, and smaller publications usually pick Ghost(Pro) for the managed convenience. B2B SaaS companies running developer blogs, content teams with infrastructure capacity, and paid-membership publications at scale usually pick self-hosted for the cost ceiling and the design freedom. Both ship the same widget integration story. Paste the publication URL, drop in the Content API key, and the embed works regardless of which side of the hosting decision you landed on. This is one of the most under-marketed strengths of Ghost as a platform: the open-source contract means a widget tool that works against Ghost(Pro) automatically works against every self-hosted install too.

Between 2020 and 2026, an outsized share of B2B SaaS companies migrated their marketing blogs from WordPress to Ghost. The pattern shows up clearly across product-led growth companies, developer tools, infrastructure platforms, and design-focused SaaS brands. The reasons are practical rather than ideological. First, Ghost has a clean Markdown editor that engineering and content teams both like, instead of WordPress's Gutenberg block editor that frustrates writers and breaks under custom themes. Second, Ghost ships native multi-author support with author profiles, bylines, and per-author RSS feeds, which is critical for B2B blogs where multiple engineers and marketers contribute. Third, Ghost has built-in newsletter delivery via Mailgun integration, so a single Ghost install replaces the WordPress plus Mailchimp or HubSpot stack with one tool. Fourth, the Content API is genuinely well-designed, which makes it trivial for a marketing engineer to wire Ghost into a Next.js or Astro frontend if the team wants a fully custom site with Ghost as a headless CMS. Fifth, Ghost is open-source and MIT-licensed, which removes the platform-risk concern that makes engineering teams uncomfortable with proprietary closed-source CMSes. The downstream consequence is that a ghost feed widget is increasingly a B2B SaaS marketing tool rather than just an indie blogger tool. Companies running their primary blog on Ghost also want to surface posts on landing pages, product marketing pages, partner pages, and developer documentation sites without setting up the same Ghost theme three times. The widget bridges that gap with one snippet per page.

Ghost supports multiple authors per publication, internal tags, public tags, and an Authors API endpoint that exposes author avatars, names, bios, and per-author RSS feeds. This is exactly the data model a multi-author publication needs, and the widget should respect it. Common patterns: a contributor portfolio page that filters the feed by one author slug, a magazine landing page that filters by a public tag like #features for editor-curated longform, an essays-only block on a personal site that filters by an internal tag like #longform, and a per-newsletter landing page that surfaces issues from one of the publication's newsletters in isolation. Poper handles all of these natively. Filter the feed by tag, author, or newsletter slug at widget configuration time, then embed the snippet anywhere. The widget renders author bylines, tag pills, feature images, excerpts, and read-time estimates from the Content API response, which keeps the embed in lockstep with the source publication. If you publish a new post on Ghost tagged #longform, that post appears on every embed configured to filter by #longform within the next sync cycle, which is hourly on Free, 5 minutes on Pro, and on-demand via Ghost webhook on Business. This is also where the Ghost-versus-Substack-versus-Medium decision starts to favor Ghost for serious editorial operations. Substack is built around the single-author or small-team newsletter model. Medium is built around the individual writer with a publication as a secondary container. Ghost is built around the multi-author publication as the primary unit, with members and paid tiers attached to the publication rather than the individual author. For magazines, B2B blogs, and paid-membership publications with multiple contributors, Ghost is the right CMS and the widget is how you extend that publication onto the rest of your web presence without setting up a custom Ghost theme on every site.