Everything ran on a gaming laptop sitting on my desk. LaptopLLM. Lid closed, Docker containers running 24/7, agents on cron schedules doing their jobs while I slept.
Then the home internet went out.
What happened
No internet meant no agents, no dashboard, no websites (those were fine on Cloudflare, but everything else), no email engine, no social posting, no prospect research, no health checks. The entire operation sat there on a laptop with a blinking router light.
Single point of failure. The most basic infrastructure mistake. And I made it.
The fix
Migrated production to a Hostinger VPS the next day. KVM 4. Dedicated hosting with dedicated internet. Docker containers, databases, agents, cron jobs, the whole stack moved to a machine in a data center with redundant connectivity.
The gaming laptop that started it all went from my desk to the floor. A black box sitting there as a reminder of where this began.
The current setup
Now I work from a compact NUC-like PC with 3 monitors. That’s the daily workstation. Production infrastructure runs on the VPS.
The separation is cleaner. Dev environment on my desk. Production in a data center. The agents don’t care what I’m doing on my local machine.
The lesson
If you’re running production services from your home network, you have a single point of failure and you’re one ISP hiccup away from losing everything. This isn’t a novel insight. But it’s one thing to know it and another to wake up to it.
The LaptopLLM era was 6 weeks. Long enough to build the whole system. Short enough that the migration wasn’t painful. If I’d waited another month, with more data, more integrations, more dependencies, the move would have been much harder.
Build fast, but don’t get comfortable on infrastructure that can’t handle an internet outage.