Ghost Self-Hosted

Open-source publishing and membership CMS with documented customer-operated Linode and DigitalOcean deployments.

6 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

What lands where

  1. Supplied by

    Vendor or project

    Official Ghost-CLI production installation on Linode or Ghost Marketplace Droplet on DigitalOcean

  2. Operated by

    Your team

    Customer manages the Linode server or DigitalOcean Droplet, operating system, MySQL, reverse proxy, TLS, mail, storage, backups, monitoring and Ghost upgrades.

Deployment boundaries by provider

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodOfficial Ghost-CLI production installation on Linode or Ghost Marketplace Droplet on DigitalOcean
InfrastructureServers / containers
Ghost runs as a long-lived Node.js service with MySQL, proxy, mail and persistent content dependencies on a customer Linode or DigitalOcean Droplet.
Licensing modelOpen Source / Open Core
The Ghost application is MIT-licensed. Ghost(Pro) hosting and third-party themes, integrations or services have separate terms.
LicenseMIT

Buyer diligence

Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.

How to read these facts

Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.

5 of 12 fields researched (42%) · 3 documented · 2 unresolved. Evidence coverage is not a feature score.

Single sign-on
Not confirmedEvidence and scope for Single sign-on

The native Members documentation describes passwordless email-link/JWT sign-in. This does not establish a supported corporate SAML/OIDC federation path for staff or publication members in the listed self-hosted core. Confirm the exact identity surface and supported integration before treating this as enterprise SSO.

Ghost self-hosted member authentication; staff and external federation are separate questions · Source ↗ · Self-hosting configuration and service boundaries ↗ · Reviewed 2026-11-20

Sources checked — unresolved · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

The official ghost-docker repository supplies the Docker Compose deployment for Ghost, MySQL and Caddy, with optional ActivityPub and analytics services. The guide labels this tooling preview; Tinybird-backed analytics and external mail have separate configuration and service boundaries.

Official Ghost 6 Docker tooling preview; not a hardened HA baseline · Source ↗ · Deployment artifact ↗ (Moving repository; use compatible pinned application/service versions) · Reviewed 2026-11-20

Documented · Editor reviewed.

Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing

The supported production stack requires at least 1 GB memory, Ubuntu LTS, Node.js LTS, MySQL, NGINX, systemd and a non-root user. This is a minimum prerequisite, not a capacity guarantee; size mail, media, backups and traffic separately.

Ghost supported self-hosting stack checked 2026-11-16 · Source ↗ · Reviewed 2026-11-16

Documented · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

Ghost core is distributed under the MIT license. Ghost(Pro) hosting, paid publication services, mail delivery, optional analytics dependencies and third-party deployment packages are separate from the core software terms.

Upstream Ghost software license; not a Ghost(Pro) subscription or infrastructure quote · Source ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

Operating cost estimate
Not confirmedEvidence and scope for Operating cost estimate

Worked infrastructure subtotal: one Regular Basic DigitalOcean Droplet (1 GiB RAM, 1 vCPU, 25 GiB SSD) at the published USD 6 monthly cap, plus Basic weekly backups at 20%, gives USD 7.20/month. This is a rate illustration, not a complete operating-cost estimate or capacity recommendation. It excludes mail, domain, extra storage/transfer, monitoring, support, tax and operator labor.

Illustrative standard-rate month for Ghost self-hosting; select an available region and test capacity. No discounts or free credits assumed; rates checked 2026-11-16. · Source ↗ · DigitalOcean Basic backup plan percentages ↗ · Ghost supported production stack and minimum memory ↗ · Reviewed 2026-11-16

Sources checked — unresolved · Editor reviewed.

Show all fields (7 not researched)
Marketplace delivery
Not researched Supply a public source.
Cloud commitment eligibility
Not researched Supply a public source.
SCIM provisioning
Not researched Supply a public source.
Compliance attestations
Not researched Supply a public source.
Security controls
Not researched Supply a public source.
Air-gapped operation
Not researched Supply a public source.
Release snapshot / cadence
Not researched Supply a public source.

Scope & considerations

This entry covers self-hosted Ghost, not Ghost(Pro). The official Linode guide requires a secured Ubuntu server and hands ongoing software maintenance to the customer. Verify the current supported Node.js, MySQL and Ubuntu versions before installation.

Community & maintenance

Ghost release v6.77.0 was published on November 11, 2026, and the public contributor history records sustained upstream participation. This evidence applies to the open-source application, not to Ghost(Pro) hosting or paid support.

Category fit

Content management & CMS
Provides a self-hosted publishing CMS for websites, memberships, newsletters and structured editorial content.

Compare within Content management & CMS

  • ApostropheCMSCustomer-operated content management and website application framework.
    • Heroku
    Customer-operated · Open Source / Open Core
  • Cockpit CMSSelf-hosted structured content and API management application.
    • Railway
    Customer-operated · Open Source / Open Core
  • Confluence Data CenterCommercial self-managed Confluence edition for enterprise collaboration and knowledge management. New Data Center subscriptions are restricted to eligible existing Atlassian customers.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • CrafterCMSSelf-hosted content authoring and delivery platform.
    • AWS
    Customer-operated · Open Source / Open Core
  • Directus Self-HostedSelf-hosted content and data management with APIs over your SQL database.
    • Railway
    Customer-operated · Source Available
  • dotCMS Cloud AnywhereVendor-operated content platform deployed into a customer cloud account.
    • AWS
    • Azure
    • Google Cloud
    Vendor-operated BYOC · Commercial Only
  • DrupalOpen-source content management system for building and operating websites.
    • AWS
    Customer-operated · Open Source / Open Core
  • GravSelf-hosted flat-file content management system.
    • AWS
    • DigitalOcean
    • Linode
    • Vultr
    • Hostinger
    • LumaDock
    Customer-operated · Open Source / Open Core

Showing 8 of 25 other listings in Content management & CMS. These products address related workflows; read their category-fit notes before comparing scope. See all of Content management & CMS →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • Official Ghost production deployment on Linode ↗ · Linode

      Vendor / upstream documentation · Reviewed 2026-11-15. Vendor support commitment: not assessed; confirm the selected release and contract.

      Ghost provides an official production guide that starts with a customer-configured and secured Linode Ubuntu server and installs Ghost through Ghost-CLI.

    • Official Ghost production deployment on DigitalOcean ↗ · DigitalOcean

      Vendor / upstream documentation · Reviewed 2026-11-15. Vendor support commitment: not assessed; confirm the selected release and contract.

      Ghost documents creating its Marketplace Droplet in the customer DigitalOcean account, connecting by SSH and completing Ghost-CLI, domain, TLS and mail configuration. Confirm the image and upstream runtime versions before production.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked
  5. Community & maintenance evidenceChecked

Suggest a correction · Back to directory