
I Migrated From Homepage to AMUD Dashboard — What I Lost and Gained
Honest post-Homepage review. GitOps YAML vs browser config. No sugarcoating.
Read article →I ran Homepage for a year. Liked it. Still recommend it for the right person.
Self-hosted dashboards and services
View All Tags
Honest post-Homepage review. GitOps YAML vs browser config. No sugarcoating.
Read article →I ran Homepage for a year. Liked it. Still recommend it for the right person.
Stars, issues, PRs, themes, docs. Homelab projects grow from real users reporting real weird setups.
Read article →AMUD Dashboard isn't a startup. It's a homelab tool I built because I wanted it. But it gets better when other people break it in ways I didn't imagine.
amud.db is your whole config. Copy it. Don't forget .amud-secrets-key if you use encrypted integrations.
Read article →I've seen people maintain elaborate backup scripts for YAML dashboards — git repos, env files, secret sidecars, three different paths.
Dedicated amud system user, /opt/amud layout, systemd units. Lowest overhead if you have a spare NUC.
Read article →Sometimes you have a spare NUC or mini PC that does one job: show the dashboard on a wall and nothing else.
I built AMUD Dashboard so I'm biased. Here's when you'd still pick something else.
Read article →I built AMUD. I'm biased. Here's the honest comparison anyway.
Argon2id passwords, encrypted integration secrets, CSRF, rate limiting — what AMUD Dashboard actually ships with.
Read article →Your dashboard is a map to your entire homelab. Treat it like one.
Two containers, one shared socket volume, AMUD_DOCKER=1 on the agent. Not Proxmox-native but still lean.
Read article →Not everyone runs Proxmox. Some of you are Docker-all-the-way-down and that's fine.
AMUD Dashboard stores your whole dashboard in amud.db. Edit in the browser, backup one file, never debug YAML indentation again.
Read article →I lost a Saturday to a YAML space.
One curl on your Proxmox host provisions an LXC, installs the agent on the hypervisor, and gives you a working dashboard on port 8000.
Read article →Docker is fine. I use it. But wrapping a dashboard — a thing that mostly displays links and polls metrics — inside another network stack on a Proxmox box always felt like wearing two coats indoors.

AMUD Dashboard started because my bookmark portal was eating 150MB of RAM and I was tired of YAML. Here's what I built instead.
Read article →My homelab had the usual problem: twenty services, zero good way to open them.
I tried the usual suspects. Heimdall looked nice until I checked htop and saw PHP-FPM doing absolutely nothing useful while holding ~150MB. Homepage was closer to what I wanted — live widgets, clean UI — but I spent an entire Sunday debugging a YAML indent before I admitted I hate editing config files on disk for something as dumb as "add Jellyfin link."
So I did what any reasonable person with too much free time does: I wrote another dashboard.