Build My Homelab is a self-paced Build Path from spare machine to a private home server you actually understand: real apps for your home and family, safe remote access, backups you have restored with your own hands — with your own AI agent doing the building, and not a single open port. When it's running, you own more than apps: a foundation for everything you build next.
Search "home server" and fifteen minutes later you're deep in Proxmox versus Ubuntu, contradicting r/homelab threads, and security warnings from people who forgot what starting feels like. And AI will confidently hand a port-forwarding answer to someone who has never tested a backup.
The problem isn't missing information. It's overload — with no order, no context, and no safety net.
Build My Homelab is built by Ilan Kushnir — the maker behind KWS Rack, the printed 10-inch rack system — out of a home server that runs for real, every day:
"AI can build you tools shockingly fast now. But a tool with nowhere to live stays a demo. Your home server is where those tools become part of your life."
These are real, daily uses — not a promise that everything takes ten minutes. Each one is a station on the path you'll walk yourself.
Home Assistant with backups and private remote access — automations that survive a power cut, not a fragile late-night install.
A folder of files turned into a real service: music and movies at home and on the road, without renting yet another interface.
Instead of another year of a paid generic app — a tool built for exactly how Ilan trains, running from his own server.
A task board that matches how Ilan thinks — instead of bending his work into someone else's template.
Signing workflows on open-source, DocuSeal-style tools. For some workflows that's enough, cheaper, and fully yours.
The lab lives in the printed rack Ilan designed. Same philosophy throughout: built deliberately, documented, made to grow.
Not promises — workloads. These five run at Ilan's home as you read this, and each one replaced an app, a subscription, or a compromise.
Walk through all five — don't skip. Each takes ten seconds.
Ilan built Pumpy with Claude Code, and it runs from this very server — for him, his friends and his family. It works better for him than any generic fitness app for the simplest reason: it was built around exactly how he trains — and when his needs change, the app changes the same week.
See Pumpy live ↗Home Assistant runs the lights, the door lock, the electric blinds and the TV — alongside the routers, access points and a mesh of sensors and automations. And because the brain lives at home, not in a cloud, it keeps working even when the internet doesn't.
Media, photos, documents, bookmarks, file sync — the self-hosted world has a serious app for almost anything. One home server runs a surprising number of them at once, and each one retires another monthly subscription.
Browse the catalog — selfh.st/apps ↗Ilan's personal kanban. Built around exactly how he plans his work — and wired to his AI agent, so tasks get added, sorted and closed as part of the conversation, not in yet another form.
The one that changes everything: Ilan's personal agents — Hermes and Astra — run from this server, connected to his projects, his tools, his task board and a long-term memory. Not a cloud chatbot with amnesia — a partner that knows the house it lives in.
This is where the path leads ↓This is the whole point of the path: not "learn Linux" — end up with things like these, running quietly at your place.
Docker, Linux and networking are just the building materials. These are the rooms they become:
There are thousands of self-hosted apps — which is exactly where beginners get lost. The internet already offers infinite comparison. This path sells its absence: it picks the next win with you, for your goals.
Nobody actually wants Docker. You want a quiet path through the chaos, and something real running at home.
Not video chapters, not articles. One build loop, repeating from the first lesson to the last upgrade:
Why this step matters — one mental model, one diagram, two minutes.
A recommended default with its reasons. Not ten options — one, and why.
A ready prompt card for your agent, with context, boundaries and warnings.
One check you can see with your own eyes: it works, or it doesn't.
A field or two in your Server Passport. Your server stays documented, always.
A capability you didn't have yesterday, stated plainly.
Exactly one clear step forward. Not a menu. No getting lost.
And from Next — back to Brief. That's how a server gets built: loop after loop, no dangerous leaps.
Not a dry syllabus, not a deadline — a build map. Every stage ends in something you can see and feel, nothing risky unlocks early, and the pace is set by your goals, hardware and time.
A sane hardware choice for your budget, Ubuntu Server or Proxmox installed to match your profile, and your AI agent wired into the process.
An ordinary machine became a breathing server. You SSH into it from across the room.Docker Compose done properly, a management UI that doesn't scare you, and your first apps per your Blueprint — media, smart home, or a personal tool.
Something that used to live in the cloud, or in chaos, now runs at your place — and you understand how.A dashboard as the front door, internal names instead of IP addresses, and Tailscale — private access from your phone, anywhere in the world.
You opened your dashboard from a coffee shop. Without touching a single router port.A cockpit that shows everything is alive, real backups, a full restore drill, and a security review that shows exactly what's exposed and what isn't.
You broke it on purpose. You brought it back yourself. From that moment — it's truly yours.A domain, reverse proxy, HTTPS, and deliberately publishing one service to people you chose. Serious, orderly — and only for those who truly need it.
Locked until: restore drill passed + clean security reviewA home AI agent, a personal-apps lab, a physical lab around KWS Rack. Your first server is the beginning, not the end.
Unlock after finishing the first pathThe onboarding questionnaire learns what excites you, how much experience you have, and what hardware is already lying around — then generates your KWS Blueprint: a personal build plan with a system path, first apps, your first win, and an honest "not yet" list.
Which one sounds most like you? Click to swap the plan:
Every stage ships a prompt card written for your agent: with your server's context, the current stage's boundaries, and what must never be pasted. Copy it, run it, come back and verify the result.
Works with Claude Code, Codex, ChatGPT and any similar agent — you bring the one you already use.
You are my build companion for setting up Tailscale on my home server. ## Context - OS: Ubuntu Server LTS (fresh install, updated) - Apps run with Docker Compose under /opt/kws/stacks - My dashboard (Homepage) works on the local network - I am a beginner: explain every command in one sentence before I run it ## Goal Reach my dashboard from my phone, away from home, privately. ## Hard rules 1. Do NOT suggest port forwarding or exposing anything to the internet. 2. Do NOT ask me for passwords, keys, or tokens. If a login is needed, tell me to complete it myself in the browser. 3. One step at a time. After each step, tell me exactly how to verify it worked before we continue. Start by checking what we need to install, and wait for my output.
Beginners don't read warnings — they follow the path in front of them. So on this path you physically cannot reach a risky step before its conditions are met. Three gates keep the order:
Before any risky command — formatting a disk, changing a firewall, deleting — the agent is instructed to stop until you explain in one sentence what the command does. You never run what you can't explain.
Built into every prompt card on the path.
Advanced growth stages stay locked until a full restore drill has passed. Not "backups configured" — you actually restored, with your own hands.
If the server replaces part of your life, it must be restorable.
Exposing a service to the internet unlocks only when every condition is met. Try it yourself:
The gate is locked. On the core path, not one port ever opens — and that's exactly the point.
Great question — and you genuinely should ask it, a lot. This path is built around your agent, not against it. But a good answer and a build path are two different things:
In short: your agent builds. The path gives it context, boundaries and sequence — and gives you the confidence that you're never one step from an unrecoverable mistake.
Build My Homelab opens with a small first group, and this waitlist is literally how its timing and size get decided. Joining costs nothing and commits you to nothing — and if you're not sure yet, there's a place right here to just ask.
Honestly: there's no fake "3 spots left" here. The first group is small because real guidance doesn't scale with a button — and your signup is a real vote for what opens first.
No. Build My Homelab is a separate product — a guided Build Path from the same maker. KWS Rack stays exactly where it lives, and nothing about its published files changes. A printed rack is a beautiful home for your server, and the path includes an optional physical-lab stage — but on day one, a shelf works just as well.
No. You need technical curiosity and the willingness to run a command after it's been explained to you in one sentence. The path teaches each concept exactly when you need it — not in an intro lecture. If you've ever written code, managed a technical product, or set up a smart home, you have more than enough.
For most people: a used or new mini PC, or a computer already lying around. The Blueprint questionnaire recommends a hardware path for your budget and goals — including "don't buy anything yet, start with what you have". No hardware at all? There's a supported VPS path. A server closet is not required, promise.
Neither do we. On the core path, not a single router port is opened — remote access runs through Tailscale only, private and encrypted. Public exposure is an optional stage, locked behind a passed restore drill and a security review, meant only for people who truly need to publish something.
Full transparency, so you don't find out midway:
"Not yet" always means "not now, and here's why" — never a locked door without an explanation.
Better to say it here than after you sign up. This path isn't for you if:
If one of those is you — you'd likely be disappointed, and we'd rather save us both the time.
You work with the agent you already have: Claude Code, Codex, ChatGPT or similar. Stage 0 of the path includes an agent-readiness check before anything else. The prompt cards are written to work in any capable agent, not just one.
English. The lessons, the Blueprint and every prompt card are written in English — agents are most precise with English infrastructure prompts, so that's also what you'll paste into yours. A Hebrew edition exists from the earliest pilot and may return later, but the path launches in English.
Every stage has an escape lane: a Stuck Report template that produces an orderly failure report — what you expected, what happened, and the relevant log with secrets stripped — ready to paste into your agent or send to support. Getting stuck is part of learning; staying stuck isn't.
Early in the path you build a backup and run a full restore drill — you break it on purpose and bring it back. After that, a mistake isn't a disaster, just another lap of the loop. Genuinely risky stages simply don't unlock before that safety net exists.
