A Lightweight Server Dashboard That Doesn't Get in Your Way

You've got a VPS humming along somewhere, doing its job, and you'd like to know what it's actually up to. Maybe you've looked at the big monitoring stacks and decided they're more machinery than your little server needs. Or maybe you just want something that looks decent when you open it in a browser tab. That's roughly the gap that dash. (also called dashdot) is trying to fill.

What It Does

dash. is a modern server dashboard built for smaller VPS instances and private servers. It runs on what the README describes as "the latest tech" and is designed with glassmorphism in mind, which is a fancy way of saying the interface leans on translucent, layered panels rather than flat boxes. The project ships with both dark and light modes, so you're covered whether you're checking stats at noon or at 2 a.m.

The practical side of things is straightforward: it's distributed as a Docker image, hosted on DockerHub, and available for both AMD64 and ARM devices. That ARM support matters if you're running something like a Raspberry Pi or an ARM-based cloud instance. Installation is a single docker container run command, and the README points to separate documentation for other installation paths (docker-compose, or building from source) and for configuration options. There's also a live demo you can poke at before committing to anything.

Why It's Cool

• It knows its audience. The README is explicit that this is "intended to be used for smaller VPS and private servers." That's a meaningful scope decision. Plenty of dashboards try to be everything to everyone and end up requiring a metrics pipeline, a database, and an afternoon of YAML wrangling before you see a single graph. dash. seems to aim at the person who just wants a clean view of one machine.

• The install is genuinely short. One Docker command with four flags is about as low-friction as server software gets. The flags themselves (-p for the port, -v /:/mnt/host:ro to mount the host filesystem read-only, --privileged) hint at how it gathers host information, and the README acknowledges this by pointing you to documentation explaining why each flag is needed. That's a good sign—the author isn't hand-waving over the privileged access, they're documenting it.

• ARM support out of the box. A lot of hobbyist and small-scale infrastructure runs on ARM these days, and not every project bothers to publish multi-architecture images. It's a small thing that saves you a build step.

• It's honest about being a work in progress. The developer notice at the bottom of the README explains that the .git history had to be rewritten because of a bloated repository (a combination of yarn's offline mirror and dependabot changes), which wiped out forks created before March 18, 2025. That's an unglamorous detail to include, but it's the kind of transparency you want from a maintainer. It also tells you the project is actively maintained enough to hit that problem in the first place.

• Glassmorphism, for better or worse. Whether you find the aesthetic appealing is a matter of taste, but it does set dash. apart from the utilitarian gray-on-gray dashboards that dominate this space. If you're going to stare at a server panel, it might as well look like someone cared about it.

How to Try It

The fastest path is the Docker command from the README:

docker container run -it \
  -p 80:3001 \
  -v /:/mnt/host:ro \
  --privileged \
  mauricenino/dashdot

A few things worth noting before you run it:

1. The container listens on port 3001 internally, mapped to port 80 on your host in this example. Change the left side of -p 80:3001 if port 80 is taken.
2. The -v /:/mnt/host:ro flag mounts your host's root filesystem into the container in read-only mode, which is how it reads system information. The :ro is important—it can't write back.
3. The --privileged flag grants the container elevated access. The README explicitly says to check the installation docs if you want to understand why each flag is necessary or if you'd prefer a different setup. Worth doing before you deploy this on anything you care about.

If you'd rather use docker-compose or build from source, those options are covered in the installation documentation. Configuration details live in a separate doc. You can see the interface for yourself at the live demo, and the source is at github.com/MauriceNino/dashdot.

Final Thoughts

dash. isn't trying to compete with full observability platforms, and it doesn't pretend to. It's a focused tool for a focused job: giving you a good-looking, low-effort view of a single small server. If that's what you need—and for a lot of hobbyists and small deployments, it is—the Docker one-liner makes it easy to find out whether it fits. The project is open source, contributions are welcome, and there's a Discord if you want to get involved or just ask questions. Give the live demo a look; that'll tell you more in thirty seconds than any writeup can.

Follow @githubprojects for more developer tools and open source projects.