A homelab made building a SaaS feel natural for me, because by the time I started ReviewMix I had already spent years running servers at home: DNS, certificates, firewalls, backups and monitoring. The homelab did not teach me to write software. It taught me the operational half of a SaaS, the part that keeps a product online, at a stage when a mistake cost an evening rather than a customer.
How does running a homelab help you build a SaaS?
Running a homelab helps you build a SaaS by teaching the infrastructure skills a product needs before the stakes are real. Every self-hosted service at home involves the same chores a production app does: a domain that resolves, a certificate that renews, a reverse proxy that routes traffic, a backup that can be restored, and something that tells you when a service is down.
The most useful thing it teaches is humility about backups. A backup that has never been restored is a hope, not a backup, and the homelab is where that became a habit. ReviewMix's development database backups were restore-tested in July 2026 before they were trusted.
What the homelab is
The homelab is a single Proxmox VE server on a low-power mini PC with an Intel Core i3-1315U processor and 32 GB of RAM. It is shared-purpose: home automation, media, a camera recorder and ReviewMix development all run on it, in Docker containers and LXC guests.
In front of it sits an OPNsense firewall with Unbound for DNS. None of it is exotic. It is a modest machine that has been run carefully for years, which is exactly why it was a comfortable place to start a product.
What moved straight across to ReviewMix
Several homelab habits moved straight across to ReviewMix with almost no change:
- Docker and containers. Running each service in its own container was routine before ReviewMix, so the production app as a container was not new.
- A self-hosted deploy platform. ReviewMix deploys with Coolify, a self-hosted platform similar to the Docker dashboards I already used at home. A push to the main branch is the deploy.
- Reverse proxy and TLS. Routing several services behind one proxy with automatic certificates was a solved problem.
- Restore-tested backups. The rule that a backup is only real once restored came from home.
- Self-hosted monitoring. ReviewMix uses self-hosted uptime monitoring and self-hosted error tracking, the same kind of tools a homelab already depends on.
Knowing this layer meant the AI agents that write ReviewMix's code could be checked on infrastructure work by someone who had made the same mistakes by hand. The rest of the toolset is in the tools and framework behind ReviewMix.
Where the homelab stops and production starts
The homelab stops at development: ReviewMix's production app and its database run on Hetzner servers in Germany, not at home. Development, testing and experiments happen there; customers use the production servers.
One link connects the two. Production sends its error reports through a WireGuard tunnel to the error tracker running on the homelab.
Keeping that line sharp matters. A home connection and a home power supply are fine for a development machine and wrong for a product people rely on.
What a homelab does not teach
A homelab does not teach application code, product decisions or how to find customers. It made servers familiar, but writing ReviewMix still needed AI agents and a strict review process, and deciding what ReviewMix should be still needed a marketer's view of the buyer.
That is the honest limit of the advantage. The homelab covered the servers; everything else, from the data model to the first customer, was new. The wider story of building ReviewMix without a developer background is in how a marketer built a SaaS without coding.
