Proxmox VE
Hypervisor · bare metalRuns every other box on this page as an isolated container or VM.
Home server · always running
Every service here is named after a god with the right job description. Watch the traffic move through them — including the requests that never make it out.
The simulator
Heimdall is Pi-hole: the resolver that answers every name lookup on the network, and the filter that refuses to answer for ad and tracker domains. Devices at home reach it through the router; devices away reach it through Tailscale — same resolver, same filtering, anywhere. Or switch to the map to see how the whole lab fits together.
What this is
Self-hosting means the software you use every day runs on hardware you control, instead of someone else’s subscription. No account to lose, no pricing change to absorb, no feature moved behind a new tier.
Everything above runs on one box — Jarvis, a refurbished office PC that Proxmox splits into isolated containers and VMs, reachable privately without a single open port. Each service gets its own space, so a bad experiment never takes the others down.
The rack
Each tile is one service, its job in a sentence, and the line it belongs to. Filter by line to see how the lab is grouped.
Runs every other box on this page as an isolated container or VM.
Resolves every name on the network, and refuses to resolve the ad ones.
Publishes one service to the internet without opening a router port.
A full VM where Docker Compose stacks run with their own kernel.
A password manager whose server I own, on a subdomain I own.
Watches for new releases and files them into the library, named correctly.
One disk, mounted into both Kubera and Agni.
Streams the library to any screen in the house, or out of it.
Carries my devices home from anywhere — including their DNS.
Readings are simulated. This site is static and never talks to the server — a public status endpoint would undo the point of a lab with no open ports.