Dashy: A Self-Hosted Dashboard with Real-Time Status Monitoring for Your Homelab

If you run a homelab, you know the pain of juggling a dozen different services, each with its own URL, login, and uptime quirks. You could bookmark everything, sure. But wouldn't it be nicer to have a single, customizable dashboard where you can see at a glance if your Plex server is alive, your Pi-hole is blocking ads, or your NAS is feeling moody?

That's exactly what Dashy does. It's an open-source, self-hosted dashboard that not only organizes your apps and links, but also gives you real-time status monitoring. Think of it as a homepage for your infrastructure, minus the clutter.

What It Does

Dashy is a static, client-side app that you run via Docker or just drop into a web server. You define your services in a simple YAML or JSON config file, and Dashy renders them as interactive cards. Each card can show an icon, a description, and a live status indicator. Green means healthy. Red means something is on fire (or just offline). It's that simple.

The real magic is in how it monitors those services. Dashy can ping endpoints directly from the browser, so you know instantly if something went down, without needing Nagios or a separate alerting suite. It's not trying to replace your monitoring stack, but it gives you a quick, visual health check for your day-to-day services.

Why It's Cool

Dashy has a few features that set it apart from other dashboards:

Real-time status checks. Most dashboard projects just show a list of links. Dashy pings each service on a configurable interval. If your Jellyfin server crashes during a movie night, you'll see the red dot before your family complains.

Customizable to the extreme. You can choose from multiple layouts, themes, and icon sets (Font Awesome, Simple Icons, or even custom SVG). You can also group apps into sections, add markdown content, or even embed iframes. It's flexible enough to be a personal start page or a team ops dashboard.

No database needed. Everything is in a YAML file. This makes backups trivial. Just copy that one file, and your entire dashboard configuration is safe. It also means you can version control it with Git if you're that organized.

Offline mode and privacy. Dashy runs entirely in your browser. No telemetry, no external calls (unless you're pinging external services). If your router decides to take a nap, the dashboard still loads from your local server.

Accessibility and performance. It's built with modern frontend practices, so it's fast, responsive, and keyboard-navigable. You can even set up a password via a simple hash, no need for a full auth backend.

Use cases? Homelab operators love it for monitoring Docker containers, media servers, and VPNs. Some folks run it as a team internal dashboard for intranet links and service status. Others just use it as a better browser new tab page.

How to Try It

The easiest way to test Dashy is with Docker.

docker run -d \
  -p 8080:80 \
  -v /path/to/conf.yml:/app/public/conf.yml \
  lissy93/dashy

Replace /path/to/conf.yml with your own config file. If you don't have one yet, the repo has a sample to start from. Once the container is running, open http://localhost:8080 in your browser.

If you'd rather not Docker, you can also:

• Use the cloud demo hosted at the online demo.
• Deploy with docker-compose, k8s, or even a git clone and npm run build if you're old school.

For a full config guide, check the docs. It's well written, which is refreshing for a project this size.

Final Thoughts

Dashy is one of those projects you set up in ten minutes and wonder how you lived without it. It's not trying to be the next Grafana or a full monitoring solution. It's just a clean, fast, and highly customizable dashboard that tells you whether your stuff is working. And sometimes that's exactly what you need.

For devs running side projects or homelabs, Dashy is a no brainer. Drop it behind your nginx, point it at your internal services, and you've got a single pane of glass for your digital empire. No SaaS, no subscriptions, no bullshit.

Give it a spin. Your future self (the one chasing down why your Sonarr isn't connecting) will thank you.

Follow @githubprojects for more dev-focused open source finds.