SaaS: A Radical Change

After discarding some individual ideas, two friends and I decided to take a different step: we started building Mainhost, a subscription-based hosting service for Minecraft, TeamSpeak, and other platforms we’re still evaluating.

But this time, the goal wasn’t just to launch something quickly. We wanted to truly learn—facing real challenges in architecture, automation, and scalability, as if we were building for production from day one.

We started from scratch. We met on Discord, opened up Excalidraw, and began designing how everything should work: user flows, server creation processes, resource management, potential failure points. Every technical decision raised new questions we had to solve.

Diagram versión 0.1.1

Initially, we thought about using Proxmox to manage the infrastructure. But as we dug deeper into the flexibility and automation we needed, we shifted toward using the Docker Client API. That decision pushed us to learn how to dynamically create containers, manage persistent storage, isolate networks, and ensure stability for each customer’s server.

Along the way, we organized our tasks with GitHub Issues and documented every important decision. Even though we know formal processes like RFCs and ADRs, we chose to move fast, iterating with every step and leaving space to learn from our mistakes.

Beyond the technical challenges, the project is also pushing us to grow as a team: discussing ideas, defending our approaches, giving ground, and improving together.

We’re convinced that the only real way to grow as engineers is by learning through building, facing real problems, and finding creative solutions.

Not building for the sake of building. Not learning because we have to. Learning for the sake of learning.

That’s what Mainhost is today. And that’s what makes every step worth it.