I Help Enterprises Move to Azure for a Living. And I Self-Host Everything Personal.
This isn’t hypocrisy. It’s risk assessment.
The same analytical thinking I apply to enterprise cloud migrations – vendor lock-in analysis, disaster recovery planning, multi-vendor strategy – tells me that concentrating my personal digital life in the hands of a few hyperscalers creates unnecessary risk. Not paranoia. Risk.
I’ve architected Microsoft 365 rollouts, built Azure Landing Zones, and made the business case for cloud adoption dozens of times. I understand the value proposition. I also understand the trade-offs that enterprise procurement teams accept but individuals shouldn’t.
Career Context: This thinking – DR planning, concentration risk, multi-vendor strategy, exit planning – is exactly what separates infrastructure engineers (£50-60k) from solutions architects (£70-90k). Learning to self-host isn’t just about privacy. It’s about developing architect-level thinking.
The Nuanced Position
Let me be clear about what this series is and isn’t.
This is NOT:
- Anti-cloud propaganda
- Paranoid prepper content
- A suggestion to abandon professional cloud tools
- Unrealistic advice to self-host everything
This IS:
- Professional risk assessment applied to personal infrastructure
- The same multi-vendor thinking enterprises pay £800/day consultants for
- Practical sovereignty that works for busy professionals
- Skills that translate directly to enterprise architecture roles
The goal isn’t to eliminate cloud from your life. It’s to have optionality. To not be completely dependent on any single provider’s terms of service, account review algorithms, or pricing changes.
The Tiered Approach
Digital sovereignty isn’t all-or-nothing. Think of it in tiers:
| Tier | Strategy | Effort | Sovereignty Level |
|---|---|---|---|
| Tier 1 | Cloud backup – local copies of all cloud data | Low (automated exports) | Data portability |
| Tier 2 | Parallel systems – self-hosted running alongside cloud | Medium (setup + maintenance) | Immediate failover capability |
| Tier 3 | Self-hosted primary – cloud as backup | Higher (operational responsibility) | Full control, cloud insurance |
Most professionals should aim for Tier 1 minimum, Tier 2 for critical services. Tier 3 is for those who want the operational experience or have specific privacy requirements.
The architect’s view: This is exactly how enterprises think about multi-cloud and hybrid strategies. “What happens if AWS goes down?” “What’s our Azure exit strategy?” “How quickly can we recover from a provider incident?” The fact that you’re asking these questions about your personal infrastructure demonstrates enterprise-level thinking.
The Series
Each article covers a specific aspect of personal digital sovereignty – the why, the how, and the career skills you’re building along the way.
Foundation
The convergence of platform risks, real examples of account termination, and a framework for thinking about personal infrastructure decisions. Not anti-cloud – just anti-concentration-risk.
Critical Infrastructure
Your email is your digital identity anchor. The spectrum from Gmail to self-hosted, when each makes sense, and how to reduce your dependency on free services that monetise your data.
Practical Implementation
From zero to working Nextcloud instance. Docker setup, SSL, proper database backend, and backup automation. The practical implementation that replaces Google Drive, Dropbox, and iCloud.
Coming Soon
This series is actively expanding. Future articles will cover:
- Password Management Sovereignty – Self-hosted Vaultwarden vs. cloud password managers
- Photo Library Independence – Immich, PhotoPrism, and escaping Google Photos lock-in
- Home DNS and Ad Blocking – Pi-hole, AdGuard Home, and network-level control
- VPN Sovereignty – Wireguard, Tailscale, and secure remote access to your infrastructure
- Backup Strategy Deep Dive – The 3-2-1 rule implemented properly with Restic, Borg, and offsite replication
- Family Digital Sovereignty – Protecting those who can’t protect themselves
Reality check: Self-hosting isn’t free. It costs time, electricity, and requires ongoing maintenance. The question isn’t “is self-hosting better?” It’s “what’s the right balance of control, convenience, and cost for your specific situation?” This series helps you make that assessment professionally.
Who This Series Is For
This series is written for a specific audience:
- Cloud professionals who understand enterprise infrastructure but want personal control
- Technical climbers who want to develop architect-level thinking
- Privacy-conscious professionals who aren’t ready to go full prepper
- Homelab enthusiasts looking for purpose beyond “because I can”
- Parents in tech who want to protect family data without paranoia
If you’re looking for anti-technology screeds or bunker mentality content, you won’t find it here. This is professional risk assessment applied to personal infrastructure.
The Career Angle
Beyond the personal benefits, self-hosting develops skills that directly translate to enterprise roles:
- Disaster recovery planning – What’s your RTO/RPO for personal data?
- Multi-vendor strategy – Avoiding lock-in, maintaining portability
- Capacity planning – Storage growth, performance monitoring
- Security hardening – SSL, firewalls, access control, updates
- Documentation discipline – If you can’t document your homelab, you can’t document enterprise infrastructure
Every self-hosting project in this series includes the enterprise parallel and interview talking points. You’re not just building personal infrastructure – you’re building a portfolio that demonstrates operational thinking.
Start Here
New to the concept? Start with Why Self-Host in 2026? for the philosophical and practical foundation.
Ready to build? The Nextcloud Build Guide gets you from zero to working personal cloud in an afternoon.
Concerned about a specific service? Email Sovereignty tackles the most critical piece of personal infrastructure.
Related Learning Paths
Self-hosting skills build on foundational infrastructure knowledge:
- Linux Fundamentals – Command-line skills for managing self-hosted services (12 guides)
- Homelab Guides – Hardware selection and infrastructure setup
- Azure Fundamentals – Understand what you’re complementing