Hosting: Where Your Digital Property Physically Lives

Every website lives on a physical machine somewhere. A server in a data center in Virginia, or Frankfurt, or Singapore — a real computer with real disks, connected to real power and real network cables. When we talk about hosting, we are talking about where your digital property physically exists, who controls the machine it sits on, and what happens to your work if that relationship changes. Hosting is a sovereignty decision disguised as a technical one.

Why Your Hosting Choice Is a Sovereignty Question

The principle is the same one that applies to every layer of the sovereign stack: can you leave? If your hosting provider changes its terms, raises prices beyond reason, degrades its service, or decides your content violates a policy that did not exist when you signed up — can you take your site and move it somewhere else without losing data, functionality, or your audience? If the answer is yes, you have made a sovereign choice. If the answer is no, you are renting on someone else’s terms regardless of what the marketing page told you.

This is not a theoretical concern. Hosting providers get acquired, shift focus, and change pricing structures. A provider that was ideal for solo builders in 2022 may pivot to enterprise clients by 2026, and the small accounts that built on its infrastructure become afterthoughts. The defense against this is the same defense that applies everywhere in the sovereign stack: choose tools that produce portable outputs, maintain your own backups, and never depend on a single vendor for anything you cannot rebuild elsewhere.

Shared Hosting: The Lowest Rung

Shared hosting is the cheapest entry point. Your site lives on a server alongside dozens or hundreds of other sites, sharing CPU, memory, and disk space. Providers like SiteGround and A2 Hosting offer plans starting at a few dollars per month . For a new site with modest traffic, shared hosting works. It is the studio apartment of the hosting world — small, affordable, and adequate until it is not.

The limitation is the “noisy neighbor” problem. If another site on your shared server experiences a traffic spike or runs a poorly optimized script, your site’s performance suffers. You have no control over who your neighbors are or what they do. Shared hosting also typically offers limited configuration options — you run what the provider gives you, with the settings they choose. For a simple WordPress or Ghost site in its early months, this is a reasonable trade-off. For anything beyond that, the ceiling comes quickly.

The sovereignty assessment: shared hosting is portable. You can generally export your site and move it to another provider. The risk is not lock-in; it is performance and reliability at the margins. Start here if budget is the primary constraint, but plan to graduate.

VPS: The Middle Ground

A Virtual Private Server gives you a dedicated slice of a physical machine. Your allocation of CPU, memory, and storage is yours alone — no noisy neighbors. You get root access to the operating system, which means you can install what you want, configure it how you want, and run it the way you need. Providers like DigitalOcean, Linode (now part of Akamai), Vultr, and Hetzner offer VPS plans starting at $4-7 per month .

The trade-off is responsibility. A VPS is closer to owning your own machine. You handle operating system updates, security patches, firewall configuration, and software maintenance. This is not difficult for someone willing to learn, but it requires a baseline of technical comfort with the command line. For Ghost, DigitalOcean offers a one-click installation image that handles the initial setup. For WordPress, most VPS providers offer similar starting points. The ongoing maintenance — keeping the system updated, monitoring for issues, configuring SSL certificates — is the price of the additional control.

For the sovereign builder who wants meaningful control without the complexity of a full cloud platform, a VPS is the sweet spot. The cost is modest, the control is real, and the portability is excellent. Your site is a set of files and a database; you can back them up and deploy them on any other VPS provider with minimal friction. This is what sovereignty looks like at the infrastructure layer — not free, but affordable, and genuinely yours to move.

Managed Hosting: Delegation Without Surrender

Managed hosting providers handle the server-level work for you. They maintain the operating system, apply security patches, manage backups, optimize performance, and provide support when something breaks. You focus on your content; they focus on keeping the lights on. Ghost Pro is Ghost’s own managed hosting service. For WordPress, providers like Kinsta and WP Engine offer managed environments tuned specifically for WordPress performance .

The cost is higher — Ghost Pro starts at $9/month for a basic plan and scales to $31/month or more depending on traffic and features . Managed WordPress hosting typically starts at $20-35/month for plans that handle meaningful traffic. You are paying for someone else’s expertise and labor, which is a legitimate trade-off if your time is better spent creating than maintaining servers.

The sovereignty question with managed hosting is more nuanced. Ghost Pro, for example, allows full content export and domain portability. If you leave Ghost Pro, you can take your content, your members, and your domain to a self-hosted Ghost instance or another platform entirely. That is a sovereign arrangement — you are delegating maintenance, not surrendering ownership. The test is always the same: can you leave with everything that matters? If yes, managed hosting is delegation, not dependence.

Some managed providers are less portable than others. Any provider that uses proprietary infrastructure, custom configurations that do not translate to standard environments, or that makes export difficult is creating lock-in. Ask before you commit: what does the migration process look like if I leave? If the answer is vague, treat that as a signal.

Cloud Platforms: Power You Probably Do Not Need

AWS, Google Cloud, and Azure offer virtually unlimited flexibility. You can configure precise server specifications, deploy across multiple geographic regions, implement load balancing and auto-scaling, and architect systems that handle millions of requests. For a solo builder running a publishing platform, this is almost certainly overkill.

Cloud platforms are designed for engineering teams building complex applications. The learning curve is steep, the billing is opaque, and the configurations that make sense for a startup with a development team make no sense for a writer with a Ghost site. A misconfigured AWS instance can generate surprising bills; an unused Elastic Load Balancer quietly charges by the hour; a forgotten S3 bucket accrues storage costs that appear small individually but compound over months.

If you have a specific technical need that a VPS or managed host cannot meet — geographic distribution, specific compliance requirements, or an application that demands elastic scaling — cloud platforms exist for exactly that purpose. For everyone else, the simplicity and predictability of a VPS or managed host is the more sovereign choice. Simplicity is not weakness; it is the reduction of unnecessary dependencies and potential failure points.

What to Evaluate Before You Commit

When choosing a host, evaluate five dimensions. First, uptime guarantees. Reputable hosts offer 99.9% or better uptime SLAs. This translates to roughly nine hours of downtime per year. Ask what happens when they miss the guarantee — service credits are standard, but the real question is whether the commitment reflects actual infrastructure investment or just a marketing number.

Second, backup frequency and recovery. How often does the host back up your data? Daily is the minimum standard. How long does recovery take? Can you restore to a specific point in time, or only to the most recent backup? Test this before you need it — a backup you have never restored from is a backup you hope works, not one you know works.

Third, support quality. When your site goes down at midnight, what does the support path look like? Ticket-only support with 24-hour response times is inadequate for a site that generates revenue. Live chat or phone support with technically competent staff is worth the premium. Read reviews from current users, not just the testimonials on the provider’s site.

Fourth, pricing transparency. Hosts that advertise low introductory rates and then triple the price at renewal are not offering a deal; they are offering a bait-and-switch. Look at the renewal price, not the first-year price. Look for hidden costs — SSL certificates, backups, staging environments, and email forwarding are sometimes included and sometimes extra.

Fifth, and most importantly, the ability to migrate. Can you download a complete backup of your site — database, files, configurations — in a standard format that another host can accept? Can you point your domain to a new host without the current host’s cooperation? If you can answer yes to both, the hosting relationship is sovereign. If not, the convenience is not worth the dependency.

Geography and Jurisdiction

Your server’s physical location matters in two ways. The first is speed: data travels at the speed of light, but the speed of light through fiber optic cable across an ocean is still measurable in milliseconds. A server in New York serves a reader in New York faster than a server in Frankfurt does. For most solo builders, choosing a data center in the same broad region as your primary audience is sufficient. If your readers are mostly in North America, host in North America.

The second consideration is jurisdiction. The laws that govern your data depend on where your server lives. A server in Germany is subject to GDPR and German data protection law. A server in the United States is subject to US law, including potential law enforcement access under various statutory frameworks. For most publishers, this distinction matters less than the privacy community suggests — your blog posts are public content, and your subscriber list is governed more by your email provider’s jurisdiction than your hosting provider’s. But if your work touches sensitive topics or your threat model includes state-level adversaries, the jurisdictional question deserves deliberate thought rather than default acceptance.

The Cost Reality

Good hosting for a sovereign builder costs $5-30 per month. On the low end, a DigitalOcean VPS runs a capable Ghost or WordPress site for $6/month. On the higher end, managed hosting with Ghost Pro or a quality WordPress managed host runs $25-35/month. These numbers are real, current operating expenses — but consider them against the alternative. Platform dependency has no monthly invoice, which makes it feel free. The cost is measured in throttled reach, changed terms, lost data, and an audience you can access only as long as the platform permits.

A few dollars a month for infrastructure you control is not an expense. It is the rent on land you functionally own, with the right to leave anytime and take everything with you. That is a deal that no platform will ever offer, because the platform’s business model depends on the opposite arrangement.

Backup Strategy: Trust but Verify

Your host provides backups. Good. Do not rely on them exclusively. Maintain your own backup strategy — a complete copy of your site (database and files) stored somewhere your host cannot touch. A local hard drive, a separate cloud storage account, an encrypted archive on a different provider’s infrastructure. The standard is called the 3-2-1 rule: three copies of your data, on two different types of storage, with one copy off-site. This is the insurance policy that turns a hosting catastrophe from an existential event into a weekend inconvenience.

Test your backups. At least once, take your backup and deploy it on a fresh server. Verify that it works — that the content loads, the database connects, the images display. A backup you have never tested is a hope, not a plan. Sovereignty requires verification, not just intention.

This article is part of the Build Your Own Platform series at SovereignCML.

Related reading: The Platform Stack: What You Need to Own, Ghost vs. WordPress vs. Static Sites: Choosing Your Foundation, Backing Up Everything: Your Insurance Policy