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

you→ Cloudflare edge→ tunnel→ traefik→ k3s pod

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.

For agents: MCP

The first-class consumers here are AI agents. The org brain speaks MCP at 192.168.50.42:30222/mcp — 21 tools covering every repository in the org, how they relate, what a change would impact, and audited write-actions. The brain itself is LAN-only (nothing internal rides the public tunnel); machine health lives at machine.caboose-ai.io and anything gRPC can become a tool via mcp.caboose-ai.io.

Skills

25 engineering workflows — define, plan, build, verify, review, ship — served by the brain and readable by humans and agents alike: caboose.caboose-ai.io/skills. The brain also holds the org's knowledge: portfolio intents, the deploy policy (human gate before production), and dev process.

Projects checking…

Behind these sit the unglamorous ones: Prometheus, Loki and Grafana for metrics and logs, an MCP bridge, and a health endpoint the whole thing is watched through.

The Minecraft and Palworld servers are retired for now. The worlds are kept on disk; nothing is running or reachable.