I'm a Senior Systems Administrator. I manage enterprise infrastructure for a living — HPE blade servers, storage arrays, Elasticsearch clusters, the works. I know how to evaluate tools professionally.
And yet, for my homelab and personal projects, I kept paying for SaaS tools that did 80% of what I needed, locked my data behind someone else's API, and would disappear or change their pricing whenever they felt like it.
So I stopped. And built my own.
This is what I learned.
The SaaS trap for self-hosters
If you run a homelab or manage Docker containers at home, you've probably felt this. The tools that exist are either:
- Too enterprise (Portainer Business, Rancher) — overkill for a home setup, expensive
- Too basic (Portainer CE) — missing features you actually want
- Too opinionated — built for someone else's workflow, not yours
- Too fragile — dependent on a company that might pivot or shut down
The alternative — building your own — used to mean weeks of work for something barely functional. A weekend project that turns into a month-long rabbit hole.
That calculus has changed.
What I built instead
I built NEXUS Ecosystem — a modular suite of self-hosted Docker management tools. Six services, all open source, all running on my own hardware.
| Tool | What it does | Port |
|---|---|---|
| NEXUS | Container management, stacks, terminal | 9090 |
| Watcher | Image update detection | 9091 |
| Pulse | Uptime monitoring | 9092 |
| Security | Port & vulnerability audit | 9093 |
| Notify | Multi-channel alerts | 9094 |
| Hub | SSO + central dashboard | 9095 |
Stack: React 18 + Vite + Node.js + Express + Socket.io. No Tailwind. CSS custom properties. Lucide icons. Docker.
I built this in my spare time, as a solo developer, while working a full-time job.
Why self-hosting wins for this use case
Control over data. My container state, my metrics, my alert history — none of it leaves my network. When I use Portainer Cloud or any hosted dashboard, I'm sending data about my infrastructure to a third party. For a homelab, that's acceptable. For anything sensitive, it's not.
No pricing surprises. SaaS tools change their pricing. Features move to paid tiers. Free plans get sunset. I've been burned by this more than once. A self-hosted tool costs what it costs to run — electricity and a bit of RAM.
It does exactly what I need. Not more, not less. Every feature in NEXUS exists because I wanted it. There's no bloat from features built for enterprise customers I'm not. The UI is exactly how I want to work.
I understand every layer. When something breaks in a SaaS tool, I'm at the mercy of their support queue. When something breaks in my own tool, I fix it. I know the codebase. I know where the logs are. I know what the health endpoint returns.
The part that changed: building it no longer takes months
This is the real shift.
A year ago, building a full ecosystem like this — six services with SSO, event-driven automation, real-time metrics, a design system — would have taken me months of evenings and weekends. Realistically, I might have abandoned it after the second service.
With Claude Code, I built the core of this in weeks. Not because it wrote perfect code that I rubber-stamped. Because it handled the scaffolding, the boilerplate, the consistent patterns across services — the parts that are necessary but not interesting — while I focused on architecture, decisions, and what the thing should actually do.
A recent session: I needed two new services (Security and Notify) created from scratch and integrated into the Hub. I wrote a detailed prompt, hit enter, and went to write some LinkedIn posts. 29 minutes later, both services were built, integrated, and passing health checks.
That's not magic. That's a real shift in what a solo developer can ship.
What self-hosting still costs you
I want to be honest about this because most "build your own" articles aren't.
Time investment upfront. Even with AI assistance, building something well takes time. You have to design it, make decisions, review the output, test it. It's not zero effort.
Maintenance responsibility. When a dependency has a security vulnerability, that's on you. When Docker changes an API, you need to update your code. SaaS handles this silently; self-hosted doesn't.
No support team. If something breaks at 2am, the support team is you. For a homelab this is fine. For anything production-critical, think carefully.
Initial learning curve. Understanding Docker networking, volume mounts, health checks, reverse proxies — if you don't already know this, there's a learning investment before you even write a line of application code.
Who this makes sense for
Self-hosting your own tools is the right call when:
- You have the technical skills to maintain what you build
- The data is sensitive enough that you don't want it on someone else's servers
- You want to learn — building tools is one of the best ways to understand how they work
- The existing SaaS options don't fit your workflow
- You want full control over features and roadmap
It's the wrong call when:
- You need the tool to be production-critical and reliable from day one
- You don't have time to maintain it
- A good SaaS option already exists at a price that makes sense
The open source angle
Everything I build, I publish. Docker Hub, GitHub, MIT license.
This isn't altruism — it's consistency. If I'm going to argue that you shouldn't depend on closed platforms, I should practice what I preach. Publishing your tools forces you to write documentation, think about usability for someone who isn't you, and maintain a standard of quality you'd be comfortable showing publicly.
It also means other people can run it, improve it, and point out when something is broken in a way you didn't test.
The philosophy underneath
The self-hosting movement is growing because the value proposition of SaaS is weakening. Prices are going up. Features are fragmenting into tiers. Data portability is getting harder. And the tools to build your own are getting dramatically better.
I'm not anti-SaaS. I use SaaS tools every day. But there's a category of tool — the one that runs your infrastructure, monitors your systems, manages your containers — where owning the stack is worth it.
You understand it better. You control it completely. And increasingly, building it yourself is within reach.
NEXUS Ecosystem is open source and actively developed.
- GitHub: github.com/Alvarito1983
- Docker Hub: hub.docker.com/u/afraguas1983
Top comments (0)