One dashboard for your whole homelab.

What Nodvard Deck does

Before Deck changes anything on your servers, it asks you. What it may do without asking is up to you.

Docker with stacks New

Here you see the containers from all your servers together. You edit stacks right in Deck, as text or in a form, or you pull them from a Git repository. You can create networks here too, and save your own Compose files as templates. If you don’t like an update, you go back to the old version. Your stacks from Portainer come along too, and the volumes stay where they are.

More about Docker

Servers and Proxmox

Every server has its own page in Deck. It shows how busy the server is, which services are running and which updates are pending. You start and stop VMs and LXC on Proxmox right here, and the console opens in your browser. Without Proxmox it works just as well.

More about servers

Nodvard Shield

Shield keeps an eye on your Linux servers. It looks for malware with ClamAV, checks the settings with Lynis and flags SSH logins that don’t look like you. You also see which addresses Fail2ban has banned. By default, findings go straight to quarantine, where you can take them out again at any time. If you don’t want that, turn it off.

More about Shield

Backups

Deck checks whether your Proxmox backups actually ran and tells you when one is missing or went wrong.

Apps

Tiles for your services, so you don’t have to remember addresses anymore. Deck finds containers with a web interface by itself.

Integrations

Uptime Kuma, Home Assistant, Plex, Jellyfin, Synology and a few more get a tile in Deck. Many of them are still in beta.

Vault

Deck stores passwords, API tokens and SSH keys encrypted. If you like, every server gets its own key.

Notifications

Anything that’s off somewhere ends up here. It can go to your phone too, via ntfy, Telegram, Discord or others.

Approvals and accounts

Several users with their own roles, and sign-in with two-factor. The log shows who did what and when.

Green light: done. Yellow light: still in beta.

Everything Deck does, in detail

Installed with three commands

All you need is a machine with Docker and Docker Compose. You don’t build anything, the ready-made image comes from GitHub.

mkdir ~/nodvard-deck && cd ~/nodvard-deck
curl -fsSL -o compose.yml https://raw.githubusercontent.com/nodvard/deck/main/deploy/compose.standalone.yml
docker compose up -d

name: nodvard-deck
services:
  nodvard-deck:
    image: ghcr.io/nodvard/deck:latest
    restart: unless-stopped
    ports:
      - "${NODVARD_DECK_PORT:-8080}:8080"
    volumes:
      - nodvard_deck_data:/app/data
      # Optional: a folder for backups, for example on a NAS
      # - ./sicherungen:/backups
    healthcheck: …
volumes:
  nodvard_deck_data:
    name: nodvard-deck-data

Then open http://<your-server>:8080 in your browser. You find the setup code with docker compose logs nodvard-deck. At the end, the assistant asks whether you want to look around with sample data first.

Other ways, including Portainer, Synology or Unraid

Questions, ideas, bugs

If you have a question, come over to Discord. Bugs and ideas can go on GitHub as an issue. I use Deck myself, it runs around the clock in my homelab.

Every version has a changelog on GitHub, for example the one for version 0.13. More than 10,000 automated tests check the code. Please report security issues privately through the security policy.