My Self-Hosting Realizations and Strategy

Introduction

Over time, I've experimented with self-hosting a range of services—particularly Fediverse platforms—and discovered through trial, error, and burnout that not everything that can be self-hosted should be. Here's a reflection on what I've learned, what I’ll keep, and what I’ll let go of.


The Ideal vs. the Reality

I started with the idea that if software is open source and self-hostable, I should host it myself. The promise was enticing:

But the reality is messier:

I learned that freedom includes the freedom to not take on more than I can sustain.


Lessons from Hosting Fediverse Instances

Mastodon

Lemmy, Pixelfed, Mitra, WriteFreely

The Deeper Realization

I don’t need to host the whole Fediverse. Just because it's open source doesn’t mean it belongs on my VPS. I can support the ecosystem by using it, donating to projects and admins, and contributing in ways that fit my energy level.


What I’m Keeping

1. A Minimal Mastodon Instance

2. Email via YunoHost


What I’m Letting Go Of

I’ve tried it. I know what it feels like. I don't owe anyone the labor of a free, open, federated social network just because I can type git clone.


My Current Stack and Strategy

Hosting (on a 8GB RAM / 100GB VPS)

Apps I’ve Removed or Will Avoid:


Personal Philosophy Going Forward

I am hosting intentionally, not exhaustively.

I am not here to perform digital sovereignty, but to practice it with sanity.

I believe in self-hosting when it empowers me, not when it distracts me.

I support open-source projects by using them, donating when I can, and choosing to be part of the network without having to run the entire infrastructure myself.

My server is no longer a playground. It’s a garden. And I’ll tend only what I can care for.