The book explains how a small k3s home lab stays up, backed up and boring. The three recipes are that same lab's monitoring, storage and backups as tested Flux manifests. Read it, then deploy it. Made for people who want the why and the YAML, and would rather not type either from scratch. What's in it Versions, each the product's current download: the book 1.2.0; monitoring 1.1.0, S3 + static sites 1.2.0, backups 1.2.0. The book: Self-Hosting Everything on a Three-Node k3s Cluster, 12 chapters, PDF + EPUB. Every chapter is something that runs, with the mistakes left in. Monitoring: Prometheus, Grafana, Loki, probes and seven email alerts in about 1.5 GiB of RAM. S3 + static sites: Garage with buckets and keys in one file, nginx, and a Cloudflare tunnel with zero open ports. Backups: MariaDB, Postgres to any minute and S3, with restore tests every week and an optional copy of the cluster's own state. Why together Chapters 6 and 7 are the story behind the monitoring and backups recipes, and chapter 5 is the S3 one. The book tells you why each setting is there, including the ones I got wrong first, and the recipes save you from typing them. It costs €9 less than the Starter Pack and the book bought separately. How it was tested ✅ Each recipe deployed from an empty VM following its README, on x86_64 and again on arm64 ✅ Backups: five recovery drills, including a point-in-time Postgres restore and a full cluster-state rollback ✅ Every number in the book comes from a real run Is it for you? Yes, if you run k3s on one to a few small nodes, or want to, and like knowing why things are set up the way they are. No, if you need high availability across machines: the lab is three VMs on one physical box. Losing one node is covered (chapter 11, and tested three-node options in the monitoring and S3 recipes). Losing the box is what the backups are for.