The Sovereign Creator Stack: A Complete Setup Guide

This is the article where philosophy becomes infrastructure. We have spent this series arguing that you should own your platform, explaining what the pieces are, and comparing the options. Now we assemble the whole thing, from zero to a functioning sovereign publishing platform, in a single guide. The complete setup takes a few hours and costs between fifteen and fifty dollars a month depending on your choices. By the end, you will have a domain you own, a site you control, an email system that reaches your audience directly, analytics that respect your visitors’ privacy, payment processing that keeps the revenue relationship between you and your readers, and a backup system that ensures none of it can be lost to a single point of failure.

Why This Matters for Sovereignty

The sovereign creator stack is the digital equivalent of Thoreau’s cabin. It is not the most luxurious option. It is not the most convenient option. It is the option that belongs to you. Every component is something you can take with you if any single provider changes terms, raises prices, or disappears. Every layer passes the ownership test we established earlier in this series: can you move it without losing data or functionality? If yes, you own it. If no, you are renting.

The stack we recommend here reflects the proportional posture of this site. We are not recommending the maximum — a self-hosted server cluster with custom-built CMS software running on hardware you physically control. That setup exists, and for some builders it is appropriate. For most sovereign creators, it is disproportionate to the actual threat. The stack we recommend is the practical middle: sufficient sovereignty without unnecessary complexity. You own the critical layers. You can migrate any component. You are not dependent on any single provider. And the whole thing can be assembled in a weekend.

How It Works

Step 1: Register your domain. Your domain is the deed to your digital property. Register it through a registrar that does not bundle hosting — this prevents lock-in. Recommended registrars: Cloudflare Registrar (at-cost pricing, no markup), Namecheap (reliable, well-established), or Porkbun (straightforward, competitive pricing). Choose a .com if possible. Keep it short, memorable, and relevant to your work. Enable WHOIS privacy protection — there is no reason for your home address to appear in a public database. Enable auto-renewal immediately. Domain expiration is a preventable catastrophe that should never happen to a deliberate builder. Cost: approximately $10-15 per year.

Step 2: Choose and set up hosting.This is where your site physically lives. For most sovereign creators, two paths make sense. The first is Ghost Pro — Ghost’s managed hosting service — which handles server maintenance, updates, and security for you. You focus on publishing; they handle the infrastructure. Plans start at $9 per month for the Starter tier and run to $31 per month for the Business tier . The second path is self-hosting Ghost on a VPS from DigitalOcean, Hetzner, or Vultr. A $6/month droplet on DigitalOcean is sufficient for most solo sites, and Ghost provides a one-click installation image that simplifies setup considerably. Self-hosting gives you more control at the cost of more maintenance responsibility. If you are comfortable with a command line, self-hosting is the more sovereign option. If you are not, Ghost Pro is the proportional choice — you still own your content and can export it at any time.

Step 3: Install and configure your CMS. If you chose Ghost Pro, the setup wizard walks you through the initial configuration: site title, description, your author profile, and basic design settings. If you self-hosted, the Ghost one-click install on DigitalOcean provisions a functioning Ghost instance. Either way, spend time with the design settings. Choose a theme that reflects your publishing style — Ghost’s default Casper theme is clean and functional. Customize the navigation, set up your publication icon and cover image, and configure your site description for search engines. This is the front door of your digital property. Make it intentional.

Step 4: Configure DNS. Point your domain to your hosting. If you are using Cloudflare as both your registrar and your DNS provider, this is straightforward — add an A record pointing to your server’s IP address. If your registrar and DNS provider are different, update the nameservers at your registrar to point to your DNS provider. Configure SSL using Let’s Encrypt — Ghost’s setup handles this automatically in most cases, and your hosting provider likely automates it as well. SSL is not optional; it encrypts the connection between your visitors and your site, and search engines penalize sites without it. The DNS configuration takes ten to thirty minutes, and most of that is waiting for propagation.

Step 5: Set up email infrastructure.Your site needs to send emails — welcome messages to new subscribers, newsletter editions, password resets, membership confirmations. Ghost uses a transactional email provider for this. The recommended options are Mailgun (the most commonly used with Ghost, with a free tier of up to 1,000 emails per month ) or Postmark (known for excellent deliverability). Configure SPF, DKIM, and DMARC records for your domain. These are DNS records that authenticate your emails and tell receiving servers that messages from your domain are legitimate. Without them, your emails are far more likely to land in spam folders. Ghost’s documentation provides specific instructions for each email provider, and the process takes roughly thirty minutes.

Step 6: Install privacy-respecting analytics. You need to understand who visits your site and what content performs. You do not need to feed the surveillance machine to get this understanding. Recommended options: Plausible Analytics (lightweight, EU-hosted, GDPR-compliant, approximately $9/month) or Umami (open-source, self-hostable on the same VPS as your Ghost instance, free). Both provide the data you actually need — page views, traffic sources, top content, geographic distribution, device types — without cookies, without cross-site tracking, and without consent banners. Installation is a single script tag added to your Ghost site’s code injection settings. Ten minutes, start to finish.

Step 7: Connect payment processing.If you plan to offer paid memberships — and we recommend it for most sovereign creators — connect Stripe to your Ghost site. Create a Stripe account if you do not have one. In Ghost’s membership settings, connect your Stripe account and configure your pricing tiers. A common starting structure: a free tier (anyone can subscribe to your email newsletter), a paid tier at $7-10/month or $70-100/year (access to premium content plus the newsletter), and optionally a higher tier for additional access. Stripe’s transaction fee is 2.9% plus 30 cents per transaction — compare this to Substack’s 10% or Patreon’s 8-12%, and the sovereignty math becomes clear.

Step 8: Verify Google Search Console. Google Search Console is free, it is separate from Google Analytics, and it provides data about how your site appears in search results that you cannot get anywhere else. Verify your site ownership (several methods are available; the DNS TXT record method is the most reliable), then submit your XML sitemap. Ghost generates a sitemap automatically at yourdomain.com/sitemap.xml. Submitting it tells Google’s crawlers where to find your content and how often it changes. This is a one-time setup that takes five minutes and pays dividends for as long as your site exists.

Step 9: Configure backups. If you are on Ghost Pro, Ghost handles server-level backups. Supplement this with your own regular JSON exports (Settings > Labs > Export) stored in cloud storage you control. If you are self-hosting, enable automated snapshots through your hosting provider (DigitalOcean offers weekly snapshots for 20% of the droplet cost) and configure your own backup to off-site storage — Backblaze B2, a personal S3 bucket, or even a local external drive. Back up your email list separately. Test your restoration process. The backup article in this series covers this in full.

Step 10: Publish your first content and send your first email. Your sovereign platform is live. Publish something. It does not need to be perfect. It needs to be present — a signal to search engines that your site is active, to potential subscribers that there is substance here, and to yourself that this is no longer theory. Send your first newsletter edition to whatever list you have, even if that list is five people. The system is built. The practice begins now.

The Proportional Response

The total cost of this stack ranges from approximately $15 per month (self-hosted Ghost on a $6 VPS, Umami analytics self-hosted, Mailgun free tier) to approximately $50 per month (Ghost Pro Business tier, Plausible analytics, Mailgun paid tier). The one-time time investment is a few hours — realistically, a Saturday afternoon. The ongoing maintenance is minimal: weekly content publication, monthly CMS and plugin updates (if self-hosting), quarterly backup testing, and annual domain renewal verification.

This is not free. The platforms you are leaving — Medium, Substack, WordPress.com — were free because you were the product, or because they took a cut of your revenue, or both. The sovereign stack costs money because you are the customer, not the product. Fifteen to fifty dollars a month is the rent on your digital property. It is a fraction of what most people pay for streaming services they barely use, and it buys something those services never will: ownership.

One caution about scope. This guide gives you the complete minimum viable sovereign stack. It does not give you every feature, every optimization, or every integration that exists. Resist the temptation to add complexity before you need it. Start with this stack. Publish on it. Build an audience on it. Add features — a community forum, a course platform, an additional payment option — only when the need is clear and the audience is present. Premature optimization is the enemy of actually shipping, and the builder who spends three months perfecting their stack before publishing a word has mistaken preparation for progress.

What to Watch For

Pricing on the services mentioned here changes. Ghost Pro, Stripe, Mailgun, Plausible — all of them may adjust their pricing between when this article is written and when you read it. Check current pricing before committing. The principles do not change with the prices: own your domain, host your site on infrastructure you can leave, send email through services that let you export your list, and measure your audience without surveilling them.

The technical steps in this guide assume a basic comfort with web interfaces — creating accounts, configuring settings, copying and pasting code snippets. If you have ever set up a social media profile or configured an email account, you have the technical skill required. If any individual step feels beyond your ability, Ghost’s documentation and community forum are genuinely helpful, and the self-hosting community around DigitalOcean’s tutorials is one of the best on the internet.

The stack described here is not permanent. It is sovereign specifically because it is portable. If Ghost changes direction and no longer serves your needs, your content exports to JSON and your subscribers export to CSV. If DigitalOcean raises prices beyond what is reasonable, your server image moves to Hetzner or Vultr. If Stripe becomes problematic, alternative payment processors exist. Every layer can be replaced without starting over. That is sovereignty in practice: not the absence of providers, but the absence of dependency on any single one.

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