Self-Host Ghost: Blog CMS and Newsletter Platform 2026

TL;DR

Ghost (MIT, ~46K GitHub stars, Node.js) is a modern publishing platform combining a headless CMS, newsletter, and membership/payment system. It's the fastest path to a professional publication. Substack takes 10% of revenue. Ghost self-hosted takes 0% — you bring your own email (Mailgun/Postmark/SES) and payment processor (Stripe). Ghost(Pro) starts at $9/month; self-hosted is free.

Key Takeaways

• Ghost: MIT, ~46K stars, Node.js — blog CMS + newsletter + memberships in one
• Built-in newsletter: Send via SMTP — Mailgun, Postmark, or SES
• Members and paid subscriptions: Stripe integration for paid newsletters/memberships
• Headless CMS: REST API + GraphQL for decoupled frontends
• Performance: ~100ms page loads with built-in image optimization and lazy loading
• Themes: 100+ free themes, or build your own with Handlebars

---

Ghost vs WordPress vs Substack

Feature	Ghost (self-hosted)	WordPress	Substack
License	MIT	GPL 2.0	Proprietary
Cost	Free (hosting + SMTP)	Free (hosting)	Free (10% cut on paid)
Newsletter built-in	Yes	Plugin needed	Yes
Memberships	Yes (Stripe)	Plugin needed	Yes (10% cut)
Revenue cut	0%	0%	10%
CMS editor	Modern (Koenig)	Gutenberg	Basic
API-first	Yes	Yes	No
Setup complexity	Medium	Medium	Zero
GitHub Stars	~46K	~20K	—

---

Part 1: Docker Setup

# docker-compose.yml
services:
  ghost:
    image: ghost:latest
    container_name: ghost
    restart: unless-stopped
    ports:
      - "2368:2368"
    volumes:
      - ghost_content:/var/lib/ghost/content
    environment:
      url: "https://blog.yourdomain.com"
      database__client: mysql
      database__connection__host: mysql
      database__connection__user: ghost
      database__connection__password: "${MYSQL_PASSWORD}"
      database__connection__database: ghost
      mail__transport: SMTP
      mail__options__host: "smtp.mailgun.org"
      mail__options__port: "587"
      mail__options__auth__user: "postmaster@mg.yourdomain.com"
      mail__options__auth__pass: "${MAILGUN_PASSWORD}"
      mail__from: "noreply@yourdomain.com"
    depends_on:
      - mysql

  mysql:
    image: mysql:8.0
    container_name: ghost-mysql
    restart: unless-stopped
    volumes:
      - mysql_data:/var/lib/mysql
    environment:
      MYSQL_ROOT_PASSWORD: "${MYSQL_ROOT_PASSWORD}"
      MYSQL_DATABASE: ghost
      MYSQL_USER: ghost
      MYSQL_PASSWORD: "${MYSQL_PASSWORD}"

volumes:
  ghost_content:
  mysql_data:

docker compose up -d

Visit https://blog.yourdomain.com/ghost → setup wizard.

---

Part 2: HTTPS with Caddy

blog.yourdomain.com {
    reverse_proxy localhost:2368
}

---

Part 3: Initial Setup

1. Visit https://blog.yourdomain.com/ghost
2. Create admin account (email + password)
3. Set up your publication:
   • Name: "My Blog"
   • Description: "Writing about tech and startups"
   • Logo and cover image

---

Part 4: Write and Publish

New Post → Koenig Editor:

Title → Click to write
Subtitle (optional)
Body → Start writing...

Drag-and-drop images
/gallery — image gallery
/code — code block with syntax highlighting
/html — raw HTML embed
/video — video embed
/bookmark — URL card preview
/callout — highlighted callout box

Post Settings (sidebar):

• URL slug
• Publish date (schedule for later)
• Author
• Tags
• SEO: custom meta title/description
• Feature image

---

Part 5: Newsletter Setup

Ghost sends newsletters to your member list via SMTP:

Settings → Email newsletter:

• Confirm SMTP settings (configured in docker-compose.yml)
• From name: "Your Name"
• Reply-to: your email

Send newsletter:

1. Write a post
2. Toggle Email newsletter in the sidebar
3. Select which members receive it: Free, Paid, All
4. Publish sends the post + email to subscribers simultaneously

---

Part 6: Members and Paid Subscriptions

Set up free and paid memberships:

Settings → Members → Enable Members

Free tier: Anyone can sign up for email updates

Paid tier (Stripe):

1. Settings → Stripe → Connect Stripe account
2. Settings → Tiers → Create paid tier
   • Name: "Supporter" or "Premium"
   • Price: $5/month or $50/year
3. Subscribers at paid tier get access to premium content

Gate content: In the post editor → Visibility:

• Public: Everyone (logged in or not)
• Members only: Free subscribers
• Paid members only: Paying subscribers

---

Part 7: Themes

Change your blog's appearance:

Settings → Design → Change Theme → Upload ZIP

Popular free themes:

• Casper: Default, clean and minimal
• Edition: Newsletter-focused
• Source: Developer-friendly, fast
• Download from Ghost Marketplace

Customize Without Code

Settings → Design → Site-wide:

• Navigation menu
• Colors and fonts (theme-specific)
• Homepage layout
• Sidebar widgets

---

Part 8: Headless CMS (API Usage)

Use Ghost as a headless CMS with your own frontend:

# Content API — public, no auth required:
curl "https://blog.yourdomain.com/ghost/api/content/posts/?key=YOUR_CONTENT_API_KEY"

# Get posts:
curl "https://blog.yourdomain.com/ghost/api/content/posts/?key=KEY&include=tags,authors&limit=10"

# Get single post:
curl "https://blog.yourdomain.com/ghost/api/content/posts/slug/my-post-slug/?key=KEY"

// Next.js example:
import GhostContentAPI from '@tryghost/content-api'

const api = new GhostContentAPI({
  url: 'https://blog.yourdomain.com',
  key: process.env.GHOST_CONTENT_API_KEY,
  version: "v5.0"
})

export async function getPosts() {
  return await api.posts.browse({
    include: ['tags', 'authors'],
    limit: 'all'
  })
}

---

Part 9: Custom Domain Email

Use your own domain for newsletter sending:

Mailgun setup:

1. Sign up at mailgun.com → Add sending domain mg.yourdomain.com
2. Add DNS records: MX, TXT (SPF), CNAME (DKIM)
3. In Ghost config: MAILGUN_API_KEY + MAILGUN_DOMAIN

Or use Postmark for better deliverability:

environment:
  mail__options__host: "smtp.postmarkapp.com"
  mail__options__port: "587"
  mail__options__auth__user: "${POSTMARK_API_TOKEN}"
  mail__options__auth__pass: "${POSTMARK_API_TOKEN}"

---

Maintenance

# Update Ghost:
docker compose pull
docker compose up -d

# Backup:
# Ghost content (images, themes):
tar -czf ghost-content-$(date +%Y%m%d).tar.gz \
  $(docker volume inspect ghost_ghost_content --format '{{.Mountpoint}}')

# MySQL database:
docker exec ghost-mysql mysqldump -u ghost -p${MYSQL_PASSWORD} ghost | gzip \
  > ghost-db-$(date +%Y%m%d).sql.gz

# Logs:
docker compose logs -f ghost

# Ghost CLI (if needed):
docker exec ghost ghost doctor
docker exec ghost ghost update

Why Self-Host Ghost?

The case for self-hosting Ghost comes down to three practical factors: data ownership, cost at scale, and operational control.

Data ownership is the fundamental argument. When you use a SaaS version of any tool, your data lives on someone else's infrastructure subject to their terms of service, their security practices, and their business continuity. If the vendor raises prices, gets acquired, changes API limits, or shuts down, you're left scrambling. Self-hosting Ghost means your data and configuration stay on infrastructure you control — whether that's a VPS, a bare metal server, or a home lab.

Cost at scale matters once you move beyond individual use. Most SaaS equivalents charge per user or per data volume. A self-hosted instance on a $10-20/month VPS typically costs less than per-user SaaS pricing for teams of five or more — and the cost doesn't scale linearly with usage. One well-configured server handles dozens of users for a flat monthly fee.

Operational control is the third factor. The Docker Compose configuration above exposes every setting that commercial equivalents often hide behind enterprise plans: custom networking, environment variables, storage backends, and authentication integrations. You decide when to update, how to configure backups, and what access controls to apply.

The honest tradeoff: you're responsible for updates, backups, and availability. For teams running any production workloads, this is familiar territory. For individuals, the learning curve is real but the tooling (Docker, Caddy, automated backups) is well-documented and widely supported.

Server Requirements and Sizing

Before deploying Ghost, assess your server capacity against expected workload.

Minimum viable setup: A 1 vCPU, 1GB RAM VPS with 20GB SSD is sufficient for personal use or small teams. Most consumer VPS providers — Hetzner, DigitalOcean, Linode, Vultr — offer machines in this range for $5-10/month. Hetzner offers excellent price-to-performance for European and US regions.

Recommended production setup: 2 vCPUs with 4GB RAM and 40GB SSD handles most medium deployments without resource contention. This gives Ghost headroom for background tasks, caching, and concurrent users while leaving capacity for other services on the same host.

Storage planning: The Docker volumes in this docker-compose.yml store all persistent Ghost data. Estimate your storage growth rate early — for data-intensive tools, budget for 3-5x your initial estimate. Hetzner Cloud and Vultr both support online volume resizing without stopping your instance.

Operating system: Any modern 64-bit Linux distribution works. Ubuntu 22.04 LTS and Debian 12 are the most commonly tested configurations. Ensure Docker Engine 24.0+ and Docker Compose v2 are installed — verify with docker --version and docker compose version. Avoid Docker Desktop on production Linux servers; it adds virtualization overhead and behaves differently from Docker Engine in ways that cause subtle networking issues.

Network: Only ports 80 and 443 need to be publicly accessible when running behind a reverse proxy. Internal service ports should be bound to localhost only. A minimal UFW firewall that blocks all inbound traffic except SSH, HTTP, and HTTPS is the single most effective security measure for a self-hosted server.

Backup and Disaster Recovery

Running Ghost without a tested backup strategy is an unacceptable availability risk. Docker volumes are not automatically backed up — if you delete a volume or the host fails, data is gone with no recovery path.

What to back up: The named Docker volumes containing Ghost's data (database files, user uploads, application state), your docker-compose.yml and any customized configuration files, and .env files containing secrets.

Backup approach: For simple setups, stop the container, archive the volume contents, then restart. For production environments where stopping causes disruption, use filesystem snapshots or database dump commands (PostgreSQL pg_dump, SQLite .backup, MySQL mysqldump) that produce consistent backups without downtime.

For a complete automated backup workflow that ships snapshots to S3-compatible object storage, see the Restic + Rclone backup guide. Restic handles deduplication and encryption; Rclone handles multi-destination uploads. The same setup works for any Docker volume.

Backup cadence: Daily backups to remote storage are a reasonable baseline for actively used tools. Use a 30-day retention window minimum — long enough to recover from mistakes discovered weeks later. For critical data, extend to 90 days and use a secondary destination.

Restore testing: A backup that has never been restored is a backup you cannot trust. Once a month, restore your Ghost backup to a separate Docker Compose stack on different ports and verify the data is intact. This catches silent backup failures, script errors, and volume permission issues before they matter in a real recovery.

Security Hardening

Self-hosting means you are responsible for Ghost's security posture. The Docker Compose setup provides a functional base; production deployments need additional hardening.

Always use a reverse proxy: Never expose Ghost's internal port directly to the internet. The docker-compose.yml binds to localhost; Caddy or Nginx provides HTTPS termination. Direct HTTP access transmits credentials in plaintext. A reverse proxy also centralizes TLS management, rate limiting, and access logging.

Strong credentials: Change default passwords immediately after first login. For secrets in docker-compose environment variables, generate random values with openssl rand -base64 32 rather than reusing existing passwords.

Firewall configuration:

ufw default deny incoming
ufw allow 22/tcp
ufw allow 80/tcp
ufw allow 443/tcp
ufw enable

Internal service ports (databases, admin panels, internal APIs) should only be reachable from localhost or the Docker network, never directly from the internet.

Network isolation: Docker Compose named networks keep Ghost's services isolated from other containers on the same host. Database containers should not share networks with containers that don't need direct database access.

VPN access for sensitive services: For internal-only tools, restricting access to a VPN adds a strong second layer. Headscale is an open source Tailscale control server that puts your self-hosted stack behind a WireGuard mesh, eliminating public internet exposure for internal tools.

Update discipline: Subscribe to Ghost's GitHub releases page to receive security advisory notifications. Schedule a monthly maintenance window to pull updated images. Running outdated container images is the most common cause of self-hosted service compromises.

Troubleshooting Common Issues

Container exits immediately or won't start

Check logs first — they almost always explain the failure:

docker compose logs -f ghost

Common causes: a missing required environment variable, a port already in use, or a volume permission error. Port conflicts appear as bind: address already in use. Find the conflicting process with ss -tlpn | grep PORT and either stop it or change Ghost's port mapping in docker-compose.yml.

Cannot reach the web interface

Work through this checklist:

1. Confirm the container is running: docker compose ps
2. Test locally on the server: curl -I http://localhost:PORT
3. If local access works but external doesn't, check your firewall: ufw status
4. If using a reverse proxy, verify it's running and the config is valid: caddy validate --config /etc/caddy/Caddyfile

Permission errors on volume mounts

Some containers run as a non-root user. If the Docker volume is owned by root, the container process cannot write to it. Find the volume's host path with docker volume inspect VOLUME_NAME, check the tool's documentation for its expected UID, and apply correct ownership:

chown -R 1000:1000 /var/lib/docker/volumes/your_volume/_data

High resource usage over time

Memory or CPU growing continuously usually indicates unconfigured log rotation, an unbound cache, or accumulated data needing pruning. Check current usage with docker stats ghost. Add resource limits in docker-compose.yml to prevent one container from starving others. For ongoing visibility into resource trends, deploy Prometheus + Grafana or Netdata.

Data disappears after container restart

Data stored in the container's writable layer — rather than a named volume — is lost when the container is removed or recreated. This happens when the volume mount path in docker-compose.yml doesn't match where the application writes data. Verify mount paths against the tool's documentation and correct the mapping. Named volumes persist across container removal; only docker compose down -v deletes them.

Keeping Ghost Updated

Ghost follows a regular release cadence. Staying current matters for security patches and compatibility. The update process with Docker Compose is straightforward:

docker compose pull          # Download updated images
docker compose up -d         # Restart with new images
docker image prune -f        # Remove old image layers (optional)

Read the changelog before major version updates. Some releases include database migrations or breaking configuration changes. For major version bumps, test in a staging environment first — run a copy of the service on different ports with the same volume data to validate the migration before touching production.

Version pinning: For stability, pin to a specific image tag in docker-compose.yml instead of latest. Update deliberately after reviewing the changelog. This trades automatic patch delivery for predictable behavior — the right call for business-critical services.

Post-update verification: After updating, confirm Ghost is functioning correctly. Most services expose a /health endpoint that returns HTTP 200 — curl it from the server or monitor it with your uptime tool.

---

See all open source CMS and publishing tools at OSSAlt.com/alternatives/wordpress.