HobbySky gives hobbyists real network infrastructure — VMs, firewalls, subnets, load balancers, and public IPs — without the enterprise price tag or the enterprise headaches.
See what's coming ↓Running a homelab is one of the best ways to learn networking, DevOps, and systems administration. But hardware is noisy, power is expensive, and your ISP doesn't hand out clean public IPs.
HobbySky gives you a slice of real cloud infrastructure that works exactly like a homelab — spin up VMs, carve out subnets, set firewall rules, expose services behind a load balancer — all from a browser, all without racking a single server.
Our goal: make the kind of infrastructure that normally costs thousands per month accessible to the people who build things for the love of it.
Full control over your environment without worrying about hardware failures or power cuts.
No locked-down managed services. Run whatever OS, whatever software, however you like.
Proper subnets, firewall rules, NAT, and public IPs — not toy abstractions.
Spin up to 16 VMs per user. Choose your OS, and start playing. Your machines, your rules — no managed runtimes, no restrictions.
Define ingress and egress rules at the subnet level. Block, allow — full control over what traffic flows where.
Create multiple private subnets and isolate workloads from each other. Run a trusted internal network alongside a DMZ — just like a real homelab.
Every project gets a public IP. NAT rules let you expose exactly the services you want, keeping everything else tucked safely behind the firewall. Choose to load balance or expose directly — it's up to you.
Distribute traffic across your VMs with a built-in load balancer. Run HA setups, blue/green deployments, or just spread the load on your game server.
Persistent volumes, managed DNS, VPN tunnels, and monitoring are on the roadmap. HobbySky is being built in the open — your feedback shapes what ships next.
See the roadmap →Got a container ready to go? Upload a Docker image tarball or provide an image reference from a registry like GitHub Container Registry. HobbySky will spin it up on our k3s cluster and put a load balancer in front. You manage your own DNS: point an A record to our hosting IP and tell us the hostname so we can route it to your app.
Explore the website hosting roadmap →Upload a saved image as a .tar file, or point us to a registry image:
ghcr.io/your-name/your-app:latest HobbySky will deploy your container to our Kubernetes cluster. You bring the app; we manage the cluster.
Create a DNS A record pointing to the hosting IP we provide, then send us the hostname
—for example, app.yourdomain.com. We'll add that hostname to the load balancer
and route traffic to your container. Your DNS stays with your own provider.
We're a small team of hobbyists who got tired of paying enterprise prices for homelab-style tinkering. So we're building the cloud platform we always wanted. Follow our progress on the blog — we'll be sharing updates and behind-the-scenes as we go.