caboose-ai.io
The lab at the end of the train — a self-hosted playground for things that probably shouldn't be on the internet, carefully put on the internet.
What is this?
A single machine in a home office, rebuilt from a clean slate into a small Kubernetes lab. Everything you can reach under this domain runs there — no cloud compute, no rented servers.
How traffic gets here
The box dials out to Cloudflare and keeps that tunnel open; requests ride back down it. There are no forwarded ports, no inbound firewall holes, and the origin IP isn't in DNS. The only thing listening on the machine's network edge is SSH, from the LAN.
The stack
k3s (single-node Kubernetes) · traefik ingress · cloudflared tunnel connectors · plain YAML manifests, no Helm charts in anger yet. Deployed and wired up with Claude Code.
Status
- checking platform edge → tunnel → traefik → this page
- checking whoami the classic ingress smoke test — echoes what the cluster sees
- checking minecraft Fabric survival server on mc.caboose-ai.io — whitelisted, how to join below
- rebuilding moto-safety-router motorcycle route planner comparing candidate routes on relative estimated risk (Rochester, NY)
Minecraft
mc.caboose-ai.io — Fabric survival on the current Minecraft release, whitelist only. Ask for a spot, then:
On the home LAN — add a server with address 192.168.50.42. That's it.
From anywhere else — the game port rides the same Cloudflare tunnel as this page, so you connect through a small helper. Install cloudflared once, then while you play keep this running:
cloudflared access tcp --hostname mc.caboose-ai.io --url localhost:25565
…and join localhost in Minecraft.