I have used both Ghost(Pro) and self-hosted Ghost, so I know the choice isn’t as simple as saying one is better than the other.
I currently self-host a Ghost instance on a DigitalOcean droplet running Ubuntu 24.04, and I’ve also looked closely at what you get with Ghost(Pro).
If you’re trying to decide between Ghost(Pro) vs. self-hosted Ghost, the answer really depends on what you need from your setup.
This isn’t a feature-by-feature comparison, and I’m not going to tell you that Ghost(Pro) is better or that self-hosting is better.
Instead, this is a practical decision guide. When comparing Ghost (Pro) vs. self-hosted Ghost, the three most important factors are security, management, and cost.
Both options are based on the same open-source Ghost software, so the core publishing experience is similar.
The bigger differences are how the platform is hosted, managed, secured, and extended, and which features are available on your plan with Ghost (Pro).
The real difference is simple:
Who is responsible for running the server?
Let's look at each part.
What Is Ghost CMS?
Ghost is an open-source publishing platform built with Node.js. It includes features such as newsletters, memberships, and paid subscriptions out of the box, so you don't need to install separate plugins for them.
The Ghost software is free and released under the MIT license. You can download it and run it on your own server.
What Is Ghost(Pro)?
Ghost(Pro) is the managed hosting service from the Ghost Foundation, the same organization that develops Ghost.
You pay a monthly subscription, and Ghost manages the infrastructure for you. This includes automatic updates, backups, SSL, CDN, security, and email delivery. Ghost(Pro) also includes unlimited email sends on its plans, subject to its fair-use policies.
Your main responsibility is running the publication, creating content, managing members, configuring your publication, and choosing how you want the site to look and work.
The revenue from Ghost(Pro) also helps fund the development of the open-source Ghost project.
What Is Self-Hosted Ghost?
With self-hosting, you run the same Ghost software on a server you manage.
You choose the server, install and configure Ghost, set up SSL and email, and handle backups and updates.
You get more control over the setup, but you also take on more responsibility.
Is Ghost CMS Free?
The Ghost software itself is free and open source, but running it still comes with costs. With self-hosting, there is no license fee, but you need to pay for a server, domain, email, and backups.
With Ghost(Pro), those infrastructure costs are bundled into the subscription.
The important question isn't whether the Ghost software is free. It's whether managing the infrastructure yourself is worth the money and time you save.
Security Handles
Security is one of the clearest differences between Ghost(Pro) and self-hosting.
Ghost(Pro)
With Ghost(Pro), Ghost manages the underlying infrastructure.
Ghost's current platform includes automatic updates, SSL, automated backups, CDN infrastructure, DDoS mitigation, web application firewall protection, brute-force protection, rate limiting, and threat and uptime management.
You don't get SSH access to the underlying server, but you also don't have to maintain that server yourself.
Self-Hosted Ghost
With self-hosted Ghost, security becomes part of your regular maintenance.
You need to keep the operating system, Ghost, database, Node.js, NGINX, and other components updated. You also need to secure SSH access, configure the firewall, maintain SSL, monitor the system, and respond when vulnerabilities or other security issues appear.
This isn't a one-time task. A server that is secure today still needs maintenance tomorrow.
Self-Hosting Isn't Automatically Less Secure
Self-hosting isn't automatically less secure than Ghost(Pro).
A properly configured and regularly maintained server can be secure. The important difference is responsibility.
With Ghost(Pro), Ghost handles much of the infrastructure security for you. With self-hosting, that responsibility sits with you.
Setup and Maintenance
The biggest difference between Ghost(Pro) and self-hosting is simple: who takes care of the server? With Ghost(Pro), Ghost handles the infrastructure. With self-hosting, you do.
Setup
With Ghost(Pro), you can create your site, configure your publication, and start publishing without setting up a server.
With self-hosting, you need to take care of the server, domain, HTTPS, email, backups, security, and monitoring. The initial setup can take a few hours if you're new to Linux server administration.
Self-Hosting Setup Options (Ghost-CLI, Docker Compose)
If you're starting a new self-hosted Ghost installation, the installation method is worth considering. Ghost-CLI is still used for existing Ghost 6 installations, but Ghost is moving toward Docker Compose as the official self-hosting approach for Ghost 7.
Ghost-CLI handles much of the traditional setup, including NGINX and system services.
Docker Compose is better suited to newer Ghost features that require additional services, such as self-hosted analytics and ActivityPub.
So, for a new installation, check the current Ghost documentation instead of following an older Ghost-CLI tutorial.
Email Of Ghost (Transactional, Newsletter)
Ghost uses two types of email. Transactional email covers things like login links, password resets, and member emails. Newsletter email is used to send posts and other bulk emails to members.
For self-hosted Ghost, transactional email can use SMTP or a supported email service. Ghost's native newsletter delivery uses a bulk email provider, with Mailgun as the supported option.
Updates and Backups
With self-hosted Ghost, updates and backups are your responsibility. The exact process depends on whether you're using Ghost-CLI or Docker Compose, but you should always have a backup before major changes.
At a minimum, back up your MySQL database, content/ directory, and Ghost configuration. Ghost(Pro) handles automated backups for you.
Support
Ghost(Pro) gives you support from the Ghost team, while self-hosting means you're responsible for troubleshooting your server and infrastructure.
You can still use Ghost's documentation and community resources, but when something breaks, you have to find and fix the problem.
That is often the biggest difference between managed hosting and running Ghost yourself.
Cost for Ghost(Pro) and GhostSelf-Hosting
Cost is where self-hosting can look like the obvious winner.
Ghost itself is free, so it’s easy to think that running it yourself will always cost less. In practice, it depends on your audience size, email volume, infrastructure, and how much your time is worth.
Ghost(Pro) Pricing
Ghost(Pro) pricing depends mainly on the plan and the size of your audience.
At the time of writing, the yearly-billing prices are $15/month for Starter, $29/month for Publisher, and $199/month for Business. Custom plans are available through sales.
What Does Self-Hosting Actually Cost?
The Ghost software is free, but the infrastructure around it isn't. A typical self-hosted setup may include a VPS, domain, email delivery, backups, and CDN costs.
You also need to account for maintenance, monitoring, security, and troubleshooting.
The cost that's easiest to overlook is your time. If you already manage Linux servers, this may not be a big deal. If you don't, the time spent maintaining the server can quickly become part of the real cost.
Mailgun Pricing
Newsletter delivery is another cost to consider. Ghost's built-in newsletter system currently uses Mailgun for bulk email on self-hosted installations.
Your actual cost depends heavily on how many emails you send, so check the current Mailgun pricing before doing the comparison.
A simple way to estimate the volume is:
Members × newsletters per month = approximate email volume
For example, 5,000 members receiving one newsletter every week means roughly 20,000 emails per month.
When Does Self-Hosting Get Cheaper?
Don't compare only the Ghost(Pro) subscription with the price of a VPS.
At a small scale, the savings from self-hosting may not be enough to justify the extra work. As your audience grows, self-hosting can become more attractive, but email volume can change the calculation significantly.
How Newsletter Frequency Affects Email Costs
Member count alone doesn't tell you the full story.
A publication with 100,000 members sending one newsletter per month sends roughly 100,000 emails. Sending the same newsletter every week increases that to around 400,000 emails.
Same audience. Very different email costs.
That's why it's worth calculating your expected email volume before deciding whether self-hosting is cheaper.
The Real Cost of Self-Hosting
When calculating the cost of self-hosting, include more than the server:
- Server costs
- Email delivery
- Backups
- Additional infrastructure
- Monitoring
- Security maintenance
- Your time
Once you include these, the difference between Ghost(Pro) and self-hosting may be much smaller than the VPS price suggests.
What You Give Up with Ghost(Pro)
The main reason technical teams choose self-hosting is usually control, not just cost.
With Ghost(Pro), you don't manage the underlying server or database. You also have less control over the infrastructure, deployment environment, and server-side services you can run.
But that's also what you're paying for. Ghost(Pro) handles infrastructure, updates, backups, CDN, SSL, security, and email delivery for you.
So the trade-off is simple:
Ghost(Pro) gives you less infrastructure control in exchange for less infrastructure work.
The Third Option: Managed Ghost Hosting From Other Providers
The choice isn't limited to Ghost(Pro) or running everything yourself.
There is also a middle ground: managed third-party Ghost hosting. These providers manage much of the server administration while you still run Ghost outside the official Ghost(Pro) platform.
This can be useful if you want less server work but still want more flexibility than Ghost(Pro) provides.
Why Consider Managed Third-Party Hosting?
A managed host can give you:
- Less server administration
- Managed infrastructure
- Simpler setup
- Different pricing options
- More infrastructure flexibility
It's a reasonable middle ground if you don't want to become a Linux administrator but also don't want to use Ghost(Pro).
The Trade-Off
The main downside is that you're trusting a third-party provider with your infrastructure.
Before choosing one, check what they actually manage, including backups, updates, security, email, server access, migration, support, and outage recovery. Pricing and features can also vary considerably between providers.
Which Should You Choose?
There isn't one right answer for everyone.
The decision mainly comes down to three things:
- How much infrastructure control you need
- How comfortable you are managing servers
- How much time you want to spend maintaining Ghost
Choose Ghost(Pro) If...
Ghost(Pro) is a good fit if you want to focus on writing, publishing, and growing your audience rather than managing infrastructure.
Choose it if you:
- Don't want to manage Linux servers
- Want to launch quickly
- Want managed backups and updates
- Don't want to troubleshoot server problems
- Prefer convenience over infrastructure control
For a smaller publication, the extra cost of managed hosting may be worth it simply to avoid the operational work.
Choose Self-Hosted Ghost If...
Self-hosting makes more sense if you already have Linux and server-management experience.
Choose it if you:
- Need direct server access
- Want control over the filesystem and database
- Need custom infrastructure or integrations
- Already operate Linux servers
- Have specific hosting or data requirements
- Can justify the infrastructure cost
Just don't choose self-hosting because Ghost is free. You're also taking responsibility for everything around it.
Consider Managed Third-Party Hosting If...
A managed third-party host can be a good middle ground if you want a managed server without using Ghost(Pro).
It may make sense if you:
- Don't want to manage Linux yourself
- Want managed infrastructure
- Find Ghost(Pro)'s pricing or features limiting
- Want more infrastructure flexibility
Just make sure you understand exactly what the provider manages and how easy it is to move away later
My Recommendation
For most people, Ghost(Pro) is the easiest place to start. You can get your site online quickly and focus on publishing without worrying about servers, updates, backups, SSL, or email delivery.
As your site grows, the decision may change. If your audience becomes large enough that Ghost(Pro)'s pricing no longer works for you, or you need more control over the server and integrations, self-hosting becomes a more practical option.
You don't need to optimize for a scale you haven't reached yet. Start with what works for you today, and revisit the decision when your audience, email volume, or infrastructure needs give you a real reason to change.
FAQs
Here are answers to some of the most common questions about hosting requirements, costs, customization, security, and switching between the two options.
Ghost Open Source vs. Ghost(Pro): what's the difference?
Same Ghost software. Ghost(Pro) manages the server for you; self-hosting means you manage it yourself.
Can I self-host Ghost anywhere?
Mostly. Ghost officially supports Ubuntu 22.04, 24.04, and 26.04, with Node.js 22, MySQL 8.0 or 8.4, NGINX, systemd, and at least 2GB RAM.
MariaDB, PostgreSQL, and SQLite are not supported for production. Other Linux distributions may work, but they are not officially supported.
How do the costs compare?
Ghost(Pro) mainly charges based on member count and includes unlimited email sending.
Self-hosting has a relatively fixed server cost, but newsletter costs increase with Mailgun usage. For a large audience, sending newsletters frequently can make email your biggest expense.
Can I customize self-hosted Ghost more?
Yes. You have access to the server, filesystem, database, and networking, so you can run custom services and integrations.
With Ghost 6, some features such as self-hosted analytics and ActivityPub require the Docker Compose setup.
Can I use another provider for newsletters?
Not with Ghost's built-in newsletter feature. Mailgun is the supported bulk email provider.
You can use another email service separately, but you lose some of Ghost's built-in newsletter features. Transactional email is different you can use any SMTP provider.
Is self-hosted Ghost secure?
It can be, but security is your responsibility. You need to keep the server, Ghost, database, and other software up to date and properly configured. Ghost(Pro) handles much of this for you.
Can I move from Ghost(Pro) to self-hosted later?
Yes. You can export your content and members and move them to your own server. You'll need to reconnect services such as Stripe and Mailgun, check redirects, and review your theme and configuration. Starting with Ghost(Pro) does not lock you in.
Conclusion
Ghost(Pro) and self-hosted Ghost use the same open-source platform, but the difference comes down to who manages the infrastructure.
Choose Ghost(Pro) if you want to focus on publishing and let Ghost handle the infrastructure.
Choose self-hosting if you have the technical skills and need more control over the server, integrations, or infrastructure.
A managed third-party host can also be a good middle ground if you want less server work without using Ghost(Pro).
For most new sites, starting with Ghost(Pro) is a practical choice. Build your audience, understand your real email and infrastructure needs, and revisit the decision when you have actual numbers.
Move to self-hosting when you have a reason, not simply because a VPS looks cheaper on paper.