Self-Hosted Personal Finance: Firefly III vs Actual Budget for Your Homelab

Of everything people self-host, personal finance data is some of the most sensitive, and also some of the least forgiving if you lose it. A dead media server just means re-ripping or re-downloading. A dead budgeting database with no backup means years of transaction history and categorization work gone with nothing to rebuild it from. That raises the stakes on this pick more than most of the apps already covered on this site, so it’s worth understanding what you’re actually choosing between before you commit to one. ...

November 17, 2026 · 7 min

Self-Hosted Object Storage: Running MinIO for Private S3-Compatible Storage

Every cloud cold storage guide, every rclone walkthrough, half the self-hosted apps in this stack, they all speak the same protocol underneath: S3. Not Amazon specifically, the API that Amazon happened to define first and that everyone else copied because fighting it was pointless. MinIO takes that same API and runs it on drives you own, in a rack you control, with none of the egress bills or account-suspension risk that come with someone else’s bucket. This is that tool on its own terms: what it actually does, how it protects data at the object level instead of the filesystem level, and where it fits (and doesn’t) next to everything else already covered on this site. ...

November 16, 2026 · 7 min

Self-Hosted Calendar and Contacts: Radicale vs Baikal vs Nextcloud for CalDAV and CardDAV

Most self-hosting migrations start with something low-stakes, a media server, a password vault, a note-taking app. Calendar and contacts tend to get put off because the failure mode is scarier: miss an appointment, lose a phone number, and you feel it immediately. But the two protocols behind nearly every calendar and address book app, CalDAV and CardDAV, are open standards, not Google-proprietary, and self-hosting them is one of the more mature corners of the self-hosted world. The question isn’t really “can I do this,” it’s which server to run and whether your devices will actually sync against it without drama. ...

November 13, 2026 · 8 min

Self-Hosted Note-Taking: Joplin vs Standard Notes vs Trilium for Your Personal Knowledge Base

A self-hosted wiki is for infrastructure docs you want someone else (or future you) to be able to find and read. Personal notes are a different job: quick capture, a running journal, half-formed research, the kind of thing you write for yourself and don’t necessarily want structured into a Shelf/Book/Chapter hierarchy before you’ve even finished the thought. Dumping both into the same tool usually works badly, because the features that make a good team wiki (public-ish editing, forced structure, collaboration) are exactly the friction you don’t want when you’re just trying to jot something down before you lose it. Joplin, Standard Notes, and Trilium are the three most commonly self-hosted options for this job, and they land in genuinely different places on structure, security model, and how much they expect from you to run. ...

November 9, 2026 · 7 min

Self-Hosted Wikis: BookStack vs Wiki.js vs Outline for Documenting Your Homelab

Every homelab accumulates knowledge that lives nowhere except the operator’s head: which VLAN the NAS is on, the three commands that fix the thing that breaks every few months, why a particular port got forwarded and whether it’s still needed. That’s fine right up until a drive dies, a service needs rebuilding from scratch, or someone else in the house needs to get the Plex server back online while the usual person is on a plane. A self-hosted wiki is the fix: a place to write procedures, network maps, and inventory down once, searchable, so “how did I set this up” stops being a question only your memory can answer. BookStack, Wiki.js, and Outline are the three most commonly run for this in a homelab context, and they take different enough approaches that picking the right one matters more than it looks like it should. ...

November 5, 2026 · 7 min

Homepage vs Homarr vs Heimdall: Picking a Self-Hosted Dashboard for Your Homelab

At some point every homelab operator ends up with a browser bookmarks folder that’s really a map of their own infrastructure: Sonarr on one port, Proxmox on another, Uptime Kuma somewhere else, each one a separate tab to dig up when you actually need it. That works fine for three or four services. It stops working once you’re running a dozen, especially if anyone else in the house wants to check on something without memorizing 10.0.x.x:port combinations. A self-hosted dashboard solves exactly that problem: one page, usually set as your browser’s homepage or a wall-mounted tablet’s only tab, that links out to everything and optionally shows you live status while it’s at it. Homepage, Homarr, and Heimdall are the three worth seriously considering, and they take meaningfully different approaches to the same job. ...

November 1, 2026 · 7 min

Self-Hosted Team Chat: Matrix vs Rocket.Chat vs Mattermost for Your Homelab

Every few years another wave of people gets tired of a chat platform tightening its terms of service, shutting down a client, or just getting bought by someone they don’t trust, and goes looking for a self-hosted replacement. The three names that always come up are Matrix, Rocket.Chat, and Mattermost. They get lumped together as “self-hosted Slack alternatives,” but they’re not really competing for the same job. Picking wrong means either running something that fights you every day or running something with ten times the operational weight you actually need. ...

October 28, 2026 · 7 min

k3s vs k0s vs MicroK8s: Do You Actually Need Kubernetes in Your Homelab?

Kubernetes shows up in homelab conversations constantly, usually right after someone says “I want to get better at this for work.” That’s a legitimate reason to run it. What’s less legitimate is the assumption that Kubernetes is a natural next step up from Docker Compose the way Compose was a natural next step up from a pile of docker run commands. It isn’t. Compose and Kubernetes solve overlapping problems with very different amounts of machinery, and for a huge share of homelab workloads, Compose (or a UI on top of it, like Portainer or Dockge) is simply the correct tool, not a beginner’s tool you’re supposed to graduate out of. This is about when a lightweight Kubernetes distribution actually pays for itself at home, and when it’s complexity you’re taking on for its own sake. ...

October 24, 2026 · 8 min

Self-Hosting Email: Mailcow vs Mail-in-a-Box, and the Deliverability Problem Nobody Warns You About

Every other service in this stack either works or it doesn’t, and when it doesn’t, you get an error message. Email is different. You can run a flawless mail server, correctly configured down to the last header, and have every message you send quietly vanish into someone else’s spam folder, or get silently dropped before it even gets that far, with zero indication anything went wrong on your end. That one property, failure that’s invisible by default, is why self-hosting email has a reputation as the homelab project that eats the most time for the least reliable payoff. It’s worth understanding why before picking Mailcow or Mail-in-a-Box, because the software choice matters a lot less than most guides make it sound. ...

October 20, 2026 · 7 min

Self-Hosting Paperless-ngx: Turning a Pile of Scanned Paper Into a Searchable Archive

Most homelab stacks start with the fun stuff, media servers, dashboards, maybe a VPN. The boring problem that never goes away is paper: tax documents, insurance paperwork, warranty receipts, kids’ school forms, the occasional letter that actually matters. Paperless-ngx exists to solve exactly that, and it’s one of the few self-hosted apps where the payoff shows up the first week instead of months later. Scan something in, and from then on you can find it by typing a word that appears anywhere in it, not by remembering which folder you filed it under three years ago. ...

October 16, 2026 · 7 min