Homelab.
A self-hosted stack on bare metal — no cloud VM, no managed anything. One box called Friday runs the media, documents, photos, AI memory, and automation that used to be a pile of SaaS subscriptions.
The box.
One physical machine, not a cluster — everything above runs on a single host.
Friday is a single bare-metal server — no VMs, no Kubernetes, no cloud instance underneath it. Fedora Linux (Server Edition) on a 4-core i3-class CPU, 15GB of RAM, and a 118GB root volume.
Everything is orchestrated with Docker Compose — each service is its own compose stack, started independently so a failure in one doesn't take the others down. No shared VM, no single point of failure across the stack.
The box stays up for weeks at a stretch between reboots, running quietly in the background — the proof-rail numbers above are read live off the hardware, not a spec sheet.
Why self-host.
Own the hardware, own the data, skip the per-seat pricing.
Everything here runs on hardware I own, on a network I control. No vendor lock-in, no per-seat pricing, nothing leaves the premises unless it's explicitly tunneled out.
Immich replaces Google Photos. Jellyfin-class media tools replace Netflix. Document management replaces filing cabinets and Dropbox. A reverse tunnel handles public ingress — no open inbound ports.
Running cost is electricity plus internet — a small fraction of the equivalent SaaS bundle, and the data never leaves the building.
Network shape.
Public ingress only through a reverse tunnel. No open inbound ports, no exposed admin panels.
DNS-level ad/tracker blocking runs for every device on the internal network · Private LAN clients (phones, laptops, TV, IoT) reach services only through the local network — never exposed directly.
Stack.
11 containers running right now, grouped by what they do.
- Caddyreverse proxy, automatic TLS
- AdGuard Homenetwork-wide DNS, ad & tracker blocking
- Cloudflare Tunnelpublic ingress with zero open ports
- Portainercontainer fleet management UI
- Stremiostreaming client service
- PinchflatYouTube channel archiving
- ImmichGoogle Photos replacement — server, ML tagging, DB
- Documents & knowledgePaperless (document archive), Kiwix (offline wiki mirrors), Obsidian notes — personal filing cabinet replacement.
- AI & automationHoncho (AI long-term memory), a Discord bot, and an internal AI-agent platform — the layer Jarvis and other agents run on.
- Smart home & authHome Assistant for automation, Authentik for single sign-on in front of internal dashboards.
- Monitoring & dashboardsBeszel (server metrics) and Glance (status dashboard) — brought up when checking in on the box.
- Music & 3D printingNavidrome (personal music streaming) and a Bambu Lab printer manager for job tracking.
These run as compose stacks rather than 24/7 — brought up when in active use to keep the always-on footprint small on a 4-core box.
Operations.
How the box stays alive without someone babysitting it.
Automated backups — compose configs and service data are snapshotted on a schedule, so a bad update or disk failure doesn't mean starting from zero.
Self-restart — containers run with restart policies; a crashed service comes back on its own instead of staying down until someone notices.
AI-assisted maintenance — routine upkeep (dependency bumps, log review, health checks, this very page) is handled by an in-house AI chief-of-staff running on the box itself, not a human SRE on call.
Physical hardware.
Bambu Lab A1
3D printer on the local network, used for homelab mounts, brackets, and print jobs. Dashboard →