Self-hosted Ghost vs Ghost(Pro): costs and maintenance
Compare self-hosted Ghost with Ghost(Pro), including email delivery, annual billing, backups, analytics, maintenance, and who should choose each route.
Advertising disclosure: We earn commissions when you shop through the DigitalOcean links below. Links to Ghost(Pro) and Mailgun are ordinary links. The recommendation depends on the work and responsibility you want to take on.
Choose Ghost(Pro) if you want to run a publication and have the hosting, updates, and email service managed for you. Consider self-hosted Ghost when you need direct server access and will operate the stack yourself. A DigitalOcean Droplet is one place to run it.
For a newsletter, the server price is only part of the bill. Self-hosted Ghost needs bulk email delivery, a recovery process, and somebody responsible for keeping the service working. Those costs can remove an apparent price advantage before you send the first issue.
This guide separates a small web publication from a newsletter with paying members. It uses current documentation and explicit cost examples, not a hands-on performance test. Prices were checked on October 2, 2026 in US dollars; tax, currency conversion, and optional services are additional.
Decide which job you are buying help with
| Need | Start by considering | Main trade-off |
|---|---|---|
| A small publication with an email newsletter and no server operator | Ghost(Pro) Starter, if its feature limits fit | Limited customization and no paid subscriptions on Starter |
| Paid memberships, custom themes, or a publication team | Ghost(Pro) Publisher or an appropriate higher plan | Subscription price changes with the plan and audience size |
| Direct SSH and database access, custom infrastructure, or changes to the server | Self-hosted Ghost | You own installation, security, updates, delivery configuration, and recovery |
| A full online shop or a site built around WordPress plugins | Reassess Ghost before choosing its host | Hosting does not change the application's purpose |
Owning the server can be a good technical decision. It is less convincing when the only reason is a low compute line and nobody has agreed to maintain it.
Read the Ghost(Pro) billing term correctly
At the 1,000-member selection, the live Ghost(Pro) pricing page showed these plans:
| Plan | Monthly billing | Annual billing shown as a monthly equivalent | Annual payment |
|---|---|---|---|
| Starter | $18/month | $15/month | $180/year |
| Publisher | $35/month | $29/month | $348/year |
Starter does not include paid subscriptions or custom themes. Publisher includes those features and three staff users. Select your expected member count before comparing prices; these figures are not quotes for a larger list.
Hosting, newsletter delivery, backups, and platform maintenance are part of the managed offer. Payment-processor fees still apply when collecting money from readers. A plan advertised at a monthly equivalent but billed yearly requires the annual payment, not twelve optional monthly payments.
See the subscription management guide for billing changes and cancellation. Keep your own export before leaving a provider. Do not treat a promotional period as the ongoing cost.
Build a self-hosted budget without hiding the extras
Take a current compute quote for a configuration that suits the chosen installation method. Record the backup plan's separate quote as well. Minimum software requirements do not establish capacity for your publication.
Use this worksheet instead of comparing a server's starting rate with a complete publishing service:
| Recurring item | Web publication | Newsletter publication |
|---|---|---|
| Compute | Selected server quote | Selected server quote |
| Backups and recovery storage | Chosen plan and off-server copies | Chosen plan and off-server copies |
| Transactional email | Needed for staff and member account messages | Needed alongside bulk delivery |
| Bulk newsletter delivery | Only if you send newsletters | Current plan for the expected send volume |
| Domain and renewal | Registrar's actual charge | Registrar's actual charge |
| Extra services | CDN, analytics, and other services you choose | Same, accounting for features already included elsewhere |
| Administration | Maintenance and recovery work | Maintenance, recovery, and delivery operations |
Add the monthly recurring items, convert annual charges to monthly equivalents, and keep one-off setup work separate. Then compare the result with the managed plan that has the features you need. Keep taxes, payment processing, currency conversion, and overages visible rather than calling the infrastructure subtotal the whole bill.
A newsletter sent four times to 1,000 recipients produces about 4,000 deliveries before signup messages, staff mail, retries, or other sends. A daily issue to the same list is closer to 30,000 deliveries in a 30-day month. Price sends, not just subscribers.
At the Mailgun Basic rate discussed below, bulk email alone adds $15 per month to an eligible self-hosted configuration. That makes the current compute and backup quotes meaningful: add those costs before deciding whether self-hosting improves your budget. It still does not buy the same managed services as Ghost(Pro).
Check the selected server's billing model
Older installation examples may show retired rates. Use the actual selected configuration and current estimate.
Bundled CPU billing has a 672-hour monthly cap; v5 configurations do not. Price v5 against actual calendar-month hours and its selected resources. Destroying an unwanted Droplet ends its compute billing; powering it off does not.
Email has two separate configuration paths
Ghost distinguishes newsletters from account mail. For self-hosted installations, the current newsletter documentation supports Mailgun for bulk sending. Ordinary SMTP configuration does not configure the newsletter service. Member login links, password resets, and staff invitations use transactional mail instead.
Mailgun's current pricing lists Basic at $15 per month with 10,000 sends and no daily sending limit. Its entry tier has a 100-email daily cap, which does not cover a single issue to 1,000 recipients. Check the provider's live plan and account approval requirements rather than relying on an older email allowance quoted in another guide.
There is also a DigitalOcean-specific setup issue. Its Droplet limits block SMTP ports 25, 465, and 587. Ghost's DigitalOcean installation guide currently recommends port 2525 for Mailgun transactional SMTP. For another provider, verify its supported port and Ghost configuration. Bulk Mailgun sending uses a separate API configuration.
Before inviting readers, verify the sending domain and test a staff invitation, a member login link, a password reset, and a newsletter to a small consenting test list. Check the received messages and unsubscribe path. A page that loads over HTTPS is not proof that email works.
Check the installation's actual feature boundary
The current Ghost-CLI Ubuntu installation guide requires at least 1 GB RAM, a supported Node.js version, MySQL, NGINX, systemd, and a registered domain. Supported combinations change, so follow that guide as a whole rather than assembling an installation from old snippets. SQLite is not the production database choice for this route.
The same documentation says Ghost-CLI installations do not support Ghost's native web analytics. Fully self-hosting the social-web service or web analytics requires the separate Docker Compose route. A standard Ghost-CLI Droplet should therefore not be described as including every feature of a Ghost(Pro) plan.
The hosting guide explains the additional services and current limits. It also notes that Ghost is not designed to be clustered or sharded across several application servers. Do not buy multiple Droplets expecting a supported scale-out configuration without revisiting the architecture.
If you need the newer services, confirm their deployment status, dependencies, operational requirements, and complete cost before committing. Adding them later can change both the server budget and the maintenance work.
When to choose the DigitalOcean route
Self-hosted Ghost is worth considering when you need direct infrastructure control, already have a capable operator, and are comfortable keeping mail delivery and recovery working separately. It can also suit a web-focused publication whose requirements are deliberately narrower than a managed newsletter platform.
Before creating a Droplet, write down the chosen install method, the selected plan, the mail provider, the backup destination, and who handles updates. If those decisions are settled, use the DigitalOcean button below to review the configuration and current charges. It is an affiliate link.
If the goal is to publish and send newsletters with less infrastructure work, compare Ghost(Pro)'s plans directly. There is no requirement to buy a Droplet first.
Prove recovery before moving members
A backup is useful only if you know what it contains and can restore it. Ghost's update guide describes its CLI update and backup workflow. Also preserve the configuration and external service details you would need to rebuild the whole service, protecting credentials separately from a public repository.
Use an isolated restore test. Prevent the restored copy from sending newsletters, charging customers, or running production integrations. Verify representative posts, images, themes, redirects, member records, and the configuration you depend on. Record how long the recovery took and what needed manual work.
For an existing publication, identify everything that must move before changing DNS. Ghost's migration guide for moving from self-hosting to Ghost(Pro) is a useful inventory of content, images, themes, routes, and redirects; it is not a complete reverse-migration procedure. If you are leaving Ghost(Pro), request the necessary exports and confirm the self-hosted destination steps separately. Keep content URLs stable where possible. For paid memberships, account and subscription continuity need explicit checks; successfully importing posts is not enough.
Plan a final content and member-data sync, a cutover window, and a way back. Keep the former installation until the publication owner has checked the new site and accepted the migration. Do not cancel the old service as the first migration step.
Budget for the next update as well as the launch
A self-hosted publication needs regular attention to operating-system packages, the supported Node.js and database versions, Ghost releases, disk space, certificates, and delivery failures. Read release notes before a major upgrade and make a recoverable copy first. If there is no maintenance window or operator, use that as evidence in favor of managed hosting.
Keep a short operating record with the domain owner, billing accounts, recovery location, last successful restore, and a secure reference to the required credentials. Add an external monitor if a missed outage would matter. The separate website monitoring guide covers that part of the job.
For a newsletter-led business, Ghost(Pro) is the stronger default when its limits fit. For a technical operator with a concrete need for control, DigitalOcean remains a reasonable self-hosting option. The right purchase follows the operating plan.
Review notes
Checked October 2, 2026 against the linked primary sources. Ghost(Pro) prices were verified in the live pricing selector after switching billing terms; the page animates its figures during the transition. The budget worksheet leaves account-specific charges to the live quotes and names the additional costs to include. No server, email-delivery, migration, performance, or restore test was run for this article.