Ghost

Ghost(Pro) is the official managed hosting service operated by the Ghost Foundation; the software itself is open source and can be self-hosted independent of the Foundation.

Ghost's first public release (v0.3.3) shipped via GitHub in October 2013, following a 2013 Kickstarter campaign; the Ghost Foundation nonprofit was established afterward to steward the project.

Ghost(Pro) is managed hosted CMS software; Ghost is also fully open source and self-hostable (see hosting.self_host_option), so it straddles hosted-cms and self-hosted-cms depending on how a customer runs it.

Core Ghost software is open source on GitHub (TryGhost/Ghost) under the MIT license; Ghost(Pro) is the paid managed-hosting product built on that open-source core.

No free Ghost(Pro) hosting tier exists; every managed plan is paid. Ghost the software itself is free to self-host (see hosting.self_host_option), which is a separate path from Ghost(Pro).

Not applicable: Ghost(Pro) has no free plan. Self-hosting Ghost's open-source software is free of licensing cost but requires the customer to provide and manage their own server, which is a materially different offering than a hosted free tier.

Starter plan, billed yearly. Monthly billing (no annual commitment) is higher, around $18/mo for Starter per Ghost's own forum pricing announcement; the yearly-billed page did not surface an explicit monthly-billed figure in this pass.

Publisher plan, billed yearly: 3 staff users, custom themes, 1,000 members, 3 newsletters, 100MB file uploads. Monthly-billed rate is higher than the yearly-equivalent shown here.

Not applicable in the traditional sense: Ghost has no product-catalog ecommerce plan. Its monetization is membership/subscription-based (Stripe-billed recurring tiers), available starting on the Publisher plan ($29/mo yearly); there is no separate 'ecommerce plan' SKU to report.

No evidence of an introductory-vs-renewal price gap; the only pricing lever found is the standard annual-vs-monthly billing discount (annual billing is cheaper per month than paying monthly).

Ghost's own subscription-management help page states plainly: we do not offer refunds. Canceling stops future billing but the current paid period runs out rather than being refunded.

The Ghost editor (Koenig) is a card/block-based rich editor (text, image, gallery, embed, HTML, product, callout cards, etc.) rather than a freeform visual canvas or rigid page-section builder.

Cards (images, galleries, embeds, files, etc.) can be reordered by drag-and-drop within the Koenig editor.

Koenig is a click-to-edit, what-you-see-is-what-you-publish editor for posts and pages.

Post History lets editors access and restore previous versions of a post.

The Ghost editor autosaves drafts as you write.

No official native Ghost mobile app for writing/editing posts was found; Ghost recommends third-party editor integrations (e.g., iA Writer) for mobile drafting rather than shipping its own app.

Content (posts, pages, members) lives in Ghost's database independent of theme files, so switching themes does not rebuild or lose post content; only theme-level design settings can reset if the new theme uses a different name/package.

Editorial judgment: Koenig's card-based writing interface is close to a distraction-free document editor and is quick to pick up for pure content publishing; the curve steepens only if you go into theme code, self-hosting, or custom routing, which are optional for the core writing/newsletter workflow.

Ghost's official theme marketplace lists roughly 280+ themes total: about 20 free official/community themes (including the default Casper) plus 260+ premium themes ($36-$149) from marketplace developers.

Custom fonts can be added via theme code or Code Injection (site header) even where a theme doesn't expose a font picker in settings.

Ghost themes are responsive by default (Handlebars/CSS templates), but Ghost's admin UI does not expose visual breakpoint editing; fine responsive control requires editing theme CSS directly, which is a developer task rather than an in-admin setting.

Custom CSS is added via Code Injection (site header/footer) or by editing/uploading a custom theme. Installing a custom theme on Ghost(Pro) requires the Publisher plan or higher (not available on Starter).

Same mechanism and gating as custom CSS: Code Injection scripts and custom theme code require a Publisher-plan-or-higher Ghost(Pro) subscription to install a custom theme (Starter is locked to the default theme).

No native, admin-configurable animation/interaction builder was found in Ghost's official docs; any motion/animation comes from a theme's own CSS/JS, not an in-product tool.

Settings > Design exposes site-wide brand settings (accent color, logo, cover image, site icon) applied globally across the active theme; deeper design-token control lives in theme code.

Editorial judgment: the admin-only design controls are limited (accent color, logo, a handful of theme-exposed settings), but full Handlebars/CSS theme code is fully open and editable, so flexibility ranges from template-bound (typical non-technical user) to unconstrained (developer editing theme files) depending on skill level.

Ghost(Pro) is Ghost's official managed hosting product, bundling hosting, CDN, SSL, backups, and updates into every plan.

Ghost is fully open source (MIT license) and can be self-hosted on your own server; official docs cover Node.js/MySQL requirements and recommended providers like DigitalOcean.

Ghost(Pro) includes CDN delivery as part of managed hosting on all plans.

Ghost has no official, first-party static-export feature. Static output is achievable only via third-party/community tools (e.g., ghost-static-site-generator) that crawl a running Ghost instance, and doing so breaks dynamic features like membership/paywalls and forms.

May 2026 (2026-05-01), the latest month in the HTTP Archive CWV Technology Report for technology 'Ghost' (74 months of history available, back to Feb 2021). Desktop: 1,896 of 2,992 origins good (63.4%). Mobile: 2,280 of 3,115 origins good (73.2%). Combined pass rate = (1,896 + 2,280) / (2,992 + 3,115) x 100 = 68.4%.

Ghost auto-generates responsive image srcsets and serves optimized formats through its media handling on upload.

Ghost's default Casper theme and image rendering use native lazy loading for content images.

No site-owner-configurable cache-control settings surfaced in Ghost(Pro) plan documentation; CDN/caching behavior on Ghost(Pro) is managed by Ghost, not exposed as an owner-tunable setting. Self-hosted installs can configure caching at the infrastructure layer, but that's outside the hosted product.

Post Settings sidebar has dedicated Meta title and Meta description fields per post/page, falling back to post content if left blank.

Post URL/slug is directly editable in Post Settings.

Native redirects supporting both 301 (permanent) and 302 (temporary) via Settings > Advanced > Labs, managed through an uploadable redirects.yaml (or JSON) file rather than a one-by-one UI form.

Post Settings includes a Canonical URL field to override the automatic canonical, useful for syndicated/guest content.

Not exposed as a settings-panel field; robots.txt is edited by placing a custom robots.txt file at the root of a theme and installing that theme, which on Ghost(Pro) requires the Publisher plan or higher (custom themes are gated below that).

XML sitemaps are auto-generated and auto-updated by Ghost core; no manual configuration needed.

Ghost automatically outputs structured data (schema.org JSON-LD) on posts and pages as part of core SEO handling, alongside auto-generated Open Graph and Twitter Card meta.

Ghost has no native multi-locale content model (a site runs in one publication language at a time), so hreflang tags must be hand-added in theme templates for sites that build their own multilingual URL structure; there's no built-in generator.

Post Settings includes dedicated Facebook (Open Graph) and X/Twitter Card fields (custom image/title/description), falling back to meta title/description if unset.

No native per-post/per-page noindex toggle exists in Ghost's Post Settings sidebar as of this research (confirmed absent from the official post-settings help doc); site-wide noindex is available only via Private Site Mode (password-protects and noindexes the entire site). Per-page noindex is a long-standing community feature request, typically worked around with Code Injection.

Alt text is editable per content image directly in the Koenig editor, plus a dedicated feature_image_alt field for the post's cover/feature image.

Blogging/publishing (Posts) is Ghost's core, purpose-built content engine, not a bolted-on module.

Ghost has exactly two first-class content types, Posts and Pages; there's no admin UI to define arbitrary custom content types/collections with their own fields. Workarounds exist (tag-based 'collections', private #-prefixed tags, custom theme templates) but these are conventions layered on Posts, not a native custom-content-type system.

Tags are native (with public and internal/private # tags); Ghost auto-generates a tag archive for each. There's no separate 'category' taxonomy beyond tags.

Posts have a Publish Date field in Post Settings that can be set in the future to schedule publication.

Post History provides per-post revision access and restore.

Five staff roles (Owner, Administrator, Editor, Author, Contributor) support multiple authors/collaborators per site, gated by plan-level staff-user seat counts on Ghost(Pro) (1 on Starter up to unlimited on Custom).

Ghost auto-generates RSS feeds for every publication out of the box.

The read-only Content API serves published content publicly (posts, pages, tags, authors, tiers, settings), while a separate Admin API (key-authenticated) supports full read-write content management (create/update/delete posts, members, etc.), so full programmatic read-write access exists across the two APIs.

Ghost's native commerce model is membership/subscriptions (Members + Tiers + Stripe), not a physical-product storefront. One-off digital-product sales are not natively supported and require a third-party embed (e.g., Gumroad, Shopify) per Ghost's own help docs.

Ghost natively supports recurring subscription access to gated content (which can include courses/downloads distributed as content), but one-off digital product/download sales are explicitly not natively supported per Ghost's own help docs; publishers are directed to third-party tools like Gumroad or Shopify embeds for one-time digital purchases.

Recurring monthly/yearly paid membership tiers via Stripe are a core, native Ghost feature (available starting on the Publisher Ghost(Pro) plan).

Multiple currencies for member payments are available by enabling the 'Additional payment methods' beta Labs setting, which surfaces additional currencies/methods supported by the creator's own connected Stripe account; not a simple always-on default.

No point-of-sale capability; Ghost is an online publishing/membership platform, not a retail commerce system.

Not applicable/not offered: Ghost has no shopping cart concept (subscriptions are Stripe checkout, not a cart), so there is no native or app-based abandoned-cart recovery feature.

Settings > Advanced > Import/Export downloads all posts, pages, tags, staff users, and settings as a single JSON file; Members can be separately exported to CSV. Full site backup (including images/theme files) for self-hosted or migration purposes uses the Ghost CLI backup command or direct file/database backup rather than the admin export button.

Custom/installed themes can be downloaded as a zip directly from Settings > Design, since themes are just Handlebars/CSS/JS files you own; no proprietary lock on the design layer for paid Ghost(Pro) plans that support custom themes.

Custom domains are the customer's own, connected via standard DNS; Ghost(Pro)'s bundled free .link domain (1-year promo) renews at standard third-party rates thereafter but is still a portable domain, not a Ghost-locked one.

Because Ghost is open-source software, a Ghost(Pro) site's content/theme can be exported and run on self-hosted infrastructure (or another Ghost(Pro)-like host) via the JSON content export plus theme download; this is a materially higher portability ceiling than closed-source hosted builders.

The Admin API provides authenticated, full read-write access to all content and site data; the Content API separately exposes public published content read-only.

Editorial judgment: open-source MIT-licensed core, full JSON content export, downloadable theme files, and a genuine self-hosting escape hatch make Ghost one of the least locked-in hosted platforms in this comparison; the main friction is migrating Stripe-based member/subscription state and any theme customizations, not the platform itself withholding your data or code.

Both a read-only Content API and a read-write Admin API are publicly documented and available on every plan (including self-hosted).

Ghost supports webhooks (configurable via the Admin API/custom integrations) for events like post publish, member creation/subscription changes, etc.

Code Injection (site-wide header/footer, plus per-post header/footer) is available for adding custom scripts/styles; not gated behind a specific Ghost(Pro) plan tier itself, though custom themes (a related but separate capability) are gated to Publisher+.

Ghost-CLI is the official command-line tool for installing, updating, and backing up self-hosted Ghost instances (ghost install, ghost backup, etc.); GScan is an additional official CLI tool for theme compatibility checking.

Official Ghost + Zapier integration (triggers/actions for posts, members, etc.) is listed on Ghost's own integrations page. No official native Make/Integromat listing was confirmed; Make's own site offers a Ghost connector, but that's a Make-side integration rather than one listed as official by Ghost.

No native AI site-generation feature (prompt-to-site) was found in Ghost's official product pages; Ghost's differentiation is manual theme/publishing tooling, not AI-generated design.

No native in-editor AI writing assistant (e.g., AI-drafted copy, rewrite suggestions) is part of Ghost's core product as of this research pass; any AI writing workflow requires an external tool or third-party integration.

No native AI image generation/editing tool found in Ghost's official feature set; the image picker integrates stock photography (Unsplash) but not AI generation.

No native AI-driven SEO audit/assistance feature found; Ghost's SEO strength comes from automatic technical SEO (sitemaps, structured data, meta fields) rather than an AI assistant layer.

Five distinct staff roles (Owner, Administrator, Editor, Author, Contributor) with clearly escalating permissions (Contributors can only draft; Authors can publish their own; Editors can edit/publish everyone's and manage Authors/Contributors; Administrators control all settings/data).

No evidence of real-time simultaneous multi-user editing of the same post found in official docs; Ghost's collaboration model is role-based sequential editing/review (drafts, publish permissions) rather than Google-Docs-style co-editing.

The Contributor/Author/Editor role hierarchy natively enforces a draft-then-approve-and-publish workflow: Contributors and Authors cannot publish others' drafts, only Editors and above can, functioning as a built-in editorial gate without needing a plugin.

Ghost supports draft preview links for reviewing unpublished posts before going live; no dedicated separate staging-site environment (distinct URL/infrastructure mirroring production) is offered on Ghost(Pro) plans in official docs checked.

No native in-editor commenting/annotation feature for staff collaboration on drafts was found in official docs (Ghost does have member-facing comments on published posts, which is a different, public-facing feature, not internal editorial commenting).

No dedicated site activity/audit log feature was found described in Ghost's official Ghost(Pro) plan documentation.

No 24/7 live support commitment found; support is email-based (response-time targets not published in the sources checked) plus asynchronous community forum help.

Editorial judgment: Ghost maintains two well-organized, actively updated documentation sites (docs.ghost.org for developers/self-hosters, ghost.org/help for end users) plus a searchable community forum with responsive staff participation; unusually thorough and current for an open-source project of its size.

No current official member/post count for the Ghost Forum (forum.ghost.org) was found in the sources checked during this research pass; GitHub repo star count (a rough popularity proxy) was not verified via an official source either.

No SOC 2, ISO 27001, or similar formal security certification was found referenced on Ghost's official Trust/Privacy/DPA pages during this research pass; Ghost publishes a GDPR Data Processing Agreement and Privacy Policy but that is not the same as a third-party security certification.

Ghost(Pro) advertises 'daily backups' as part of managed hosting in its own marketing/help content; self-hosted installs must run backups manually via Ghost-CLI's backup command.

Ghost runs a single publication language per site instance; there is no native multi-locale content model (no per-locale posts/pages management in admin). A site's UI strings/theme text can be translated to one target language via locale JSON files, and separate multilingual sites can be simulated with tags/routing conventions, but this is not native multi-language content management. Community/third-party tools (e.g., Weglot, Crowdin, ConveyThis) fill this gap.

No native translation workflow (e.g., linked translated post versions, in-admin translation management) exists; theme/UI string translation uses static locale JSON files edited by a developer, not an editorial translation workflow.

Because Ghost has no native multi-locale content structure, there's no native per-locale URL/hreflang system; hreflang must be hand-built into a custom theme for sites attempting their own multilingual structure.

RTL is achievable by setting the publication locale to an RTL language and having the theme respect the {{@site.locale}} / lang attribute; it's a theme-level implementation detail rather than an automatic platform-wide toggle, but is documented and supported.