Self-Hosted Ghost or Ghost(Pro)? The Crossover, Worked Out

Ghost is unusual in offering the same product twice: once as MIT-licensed software you can run on any server, and once as a managed service starting at $18 a month billed yearly. Identical software. Wildly different prices. That makes it one of the few genuine build-or-buy decisions in publishing, and it is worth doing the arithmetic properly rather than reaching for the obvious answer.

The obvious answer, incidentally, is wrong in both directions depending on who is asking.

The two bills, side by side

Ghost(Pro) publishes its rates openly. Starter is $18 a month billed yearly — $216 for the year — covering one staff user and up to 1,000 members. Publisher is $29 a month billed yearly, $348 annually, with three staff users. Business is $199 a month billed yearly, $2,388 for the year. Paying month to month costs more on every tier. Starter caps at 1,000 members rather than scaling; Publisher and Business rise in price as your member count grows.

Self-hosted Ghost costs whatever your server costs. Ghost’s own installation documentation asks for an Ubuntu machine with at least 1GB of memory, and the official CLI does most of the setup. Small instances at commodity providers sit in the range of a few dollars a month, which puts the annual server bill somewhere around $60 to $90 for a personal blog.

On paper, then: roughly $70 a year against $216. A saving of about $146, or around 68%.

Now the part the paper does not show.

What self-hosting actually costs

The server is the cheap part. The recurring obligations are these.

Updates. Ghost ships releases regularly, including security releases. Applying them is a command, and the command is easy. Noticing that you need to run it is the work, and it never stops being your job.

Backups that have been tested. A backup nobody has ever restored is a hypothesis. The moment you urgently need the database back is a poor moment to find out that the procedure has a step missing.

TLS certificates. Automated renewal handles this until the day it does not, and when it fails your site goes from working to alarming in the space of one browser warning.

Transactional email. This is the one that surprises people. Ghost sends member signup confirmations, password resets and newsletters. Delivering those reliably from your own infrastructure means configuring a mail provider and getting the authentication records right. Get it wrong and members silently never receive the confirmation, which looks exactly like nobody signing up.

The standing obligation. Above all of it sits the thing that does not appear on any invoice: the low-level awareness that a machine somewhere is yours to look after, and that if it stops, nobody else is going to notice.

Where the crossover really falls

Call it four hours a year for a well-behaved single-author install once it is set up — checking updates, verifying a backup, dealing with the occasional surprise. Setup itself is a half-day if you have done it before and a full day if you have not.

At four hours a year to save $146, you are being paid about $36 an hour to administer a server. For a student, a hobbyist or anyone who enjoys this work, that is a perfectly good rate and self-hosting is the right call. For a working professional whose time bills at considerably more than that, it is a straightforwardly bad trade — you are doing sysadmin work at a discount to your own rate, on infrastructure that fails at inconvenient moments.

Self-hosting is cheap in money and expensive in attention. Managed hosting is the reverse.

Which means the real question is not “what does it cost” but “what is scarce for you”. If money is scarce and time is not, self-host. If time is scarce and $216 is not, do not. The arithmetic is almost never close once you frame it that way, and this same scarcity test decides most of the choices in our best blogging platforms guide.

Three cases where self-hosting is clearly right

You are technical and this is not work to you. If you already run servers, adding one more is marginal effort and the saving is real.

You need control the managed service does not offer. Custom integrations, unusual data residency requirements, a configuration Ghost(Pro) does not expose. If you have a genuine requirement of this kind you already know it.

The blog has no revenue and no deadline. A hobby project that goes down for six hours on a Tuesday has lost nothing. Apply a different standard to anything people pay for.

Three cases where managed is clearly right

The blog earns money. Downtime and undelivered member emails have a price, and it is higher than the hosting difference. Pay someone whose job it is.

You have a business to run. Every hour spent on a mail authentication record is an hour not spent on the thing that actually generates your income.

You do not want the standing obligation. This is a legitimate and underrated reason. Some people find infrastructure interesting; most do not, and choosing not to own a problem is a valid use of $216.

The migration you can always make later

The best feature of this decision is that it is reversible, which is a consequence of both paths running identical software.

Moving from self-hosted to Ghost(Pro) means exporting your content and importing it into the managed service. Moving the other way works the same. Neither is a platform migration in the painful sense — you are changing where the software runs, not what software you are running. Themes come across. The admin interface is the same interface. Your URLs can be preserved.

That is worth more than it sounds. On most platforms, the decision you make at the start is one you live with or pay dearly to reverse. On Ghost, “start cheap and move when it matters” is a genuinely available strategy rather than a comforting thing people say.

What this desk would do

Start self-hosted if you are comfortable in a terminal and the blog is yours alone. You will learn something, you will save $146 a year, and the exit is easy if you tire of it.

Start on Ghost(Pro) if the blog has a commercial purpose, if you have members who expect their email to arrive, or if the sentence “check whether the backup restores” makes you want to lie down. The full assessment of both paths is in our Ghost review.

And if $216 a year is the binding constraint and self-hosting is not appealing either, the honest answer is that Ghost may simply be the wrong platform for now. There are cheaper places to write, and moving to Ghost later is one of the easier migrations you will ever make.