AMUD Dashboard

English | Español | Português | Français | Deutsch | Italiano | Русский | 中文 | 日本語 | हिन्दी | 한국어 | العربية

Changelog · Blog · Theme Gallery · Roadmap · Docs · FAQ

What's new in v1.9.5

• Nodes polish — strip hidden until 2+ agents; Settings → Agents / Nodes live table + env snippets
• Theme icon styles — Settings/topbar icons change glyph/style with the theme (not only color)
• Add App CTA — larger primary action vs Settings / Sign Out
• Upgrade docs — Native / Proxmox, Docker, and Unraid steps in every release notes tag

What's new in v1.9.4

• Multi-node agents — one AMUD server, agents on every Proxmox / Unraid / CasaOS / Docker host (Multi-node docs)
• TCP + optional TLS — remote agents over VPN or TLS; UDS stays for co-located installs

Full history: Changelog

Release status (2026-10-04)

Last 5 validated releases (full history: Changelog):

• v1.9.5 (current latest recommended)
• v1.9.4
• v1.9.3
• v1.9.2
• v1.9.1

Do not use: v1.8.6, v1.8.5 (layout), v1.5.5.4, v1.5.6.1, v1.6.1 (withdrawn or broken).

Unify your homelab. A fast, Rust-powered, zero-YAML dashboard with live Proxmox & Docker telemetry, container controls, and integrations for popular self-hosted services — all from the UI. Run one server and optional agents on every host (multi-node).

Unlike legacy dashboards (Heimdall, Homepage, Homarr) that run on heavy runtimes (PHP-FPM, Node.js) and rely on complex nested YAML configuration files, AMUD is written in compiled Rust and persisted entirely in SQLite. Combined, the server and telemetry agent idle at 30–50 MB of RAM (peak ~150 MB with a full integration grid) with sub-millisecond route execution.

Homepage & Homarr parity: AMUD ships integration cache, Homepage YAML import, Custom API widgets, LDAP, per-user boards, Plex/Jellyfin cards, and a growing long-tail catalog — see Comparison.

Architecture & Design Decisions

AMUD Dashboard is split into two native binaries:

1. amud-server: Axum-based web server serving server-rendered HTML (templated via Alpine.js) and managing state via SQLite. One server can accept many agents.
2. amud-agent: Standalone daemon on each homelab host (Proxmox, Unraid, CasaOS, Docker, …). It streams host + container telemetry over UDS (local) or TCP/TLS (remote). See Remote agents / multi-node.

graph TD
    User[Web Browser] -->|HTML / WebSockets| Server[amud-server]
    Server -->|SQLite WAL| DB[(amud.db)]
    AgentLocal[amud-agent Local] -->|UDS| Server
    AgentRemote[amud-agent Remote] -->|TCP or TLS| Server
    AgentLocal -->|HTTPS REST| PVE[Proxmox VE API]
    AgentLocal -->|Unix Socket| Docker[Docker Daemon]
    AgentRemote -->|HTTPS REST| PVE2[Other PVE / Docker]

Technical Stack Justifications

Rust & Axum

• No Runtime Overhead: Compiles directly to native machine code. Eliminates the JVM/V8 startup and heap overhead.
• Concurrent Event Loop (Tokio): Telemetry streams and third-party integrations (AdGuard, Pi-hole, Plex, Home Assistant) poll concurrently on Tokio green threads. Telemetry is serialized once per poll tick and broadcasted to WebSockets using a tokio::sync::watch channel.

SQLite Persistence (rusqlite)

• Zero YAML: Configuration is stored in an embedded SQLite database. Layouts, category tabs, and settings are configured directly via the UI, bypassing YAML syntax headaches.
• Performance: Configured in WAL (Write-Ahead Logging) mode, enabling concurrent reads and low-latency writes without external network overhead.

Direct Telemetry Collection

• Zero Shell Subprocesses: Legacy solutions fork system calls like pvesh or curl every few seconds to grab container stats, resulting in high CPU overhead.
• Natively Networked: amud-agent utilizes hyper and rustls to send native HTTPS REST API calls to Proxmox VE and reads the Docker daemon directly over the UNIX socket via hyperlocal.

Telemetry Configuration

Proxmox VE Integration

Host metrics function automatically. For LXC container monitoring, the agent must be authenticated to the Proxmox VE REST API.

1. Generate API Token

In the Proxmox VE Web UI:

1. Navigate to Datacenter → Permissions → API Tokens.
2. Click Add. Select User (e.g., root@pam) and Token ID (e.g., amud).
3. Uncheck Privilege Separation so the token inherits the user's VM/System audit permissions.
4. Copy the returned Secret key.

2. Pass Token to Agent

Set the environment variable on the host running the agent:

PVE_API_TOKEN=PVEAPIToken=root@pam!amud=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX

Deployment

Docker Compose

For containerized hosts on x86_64/amd64 (combines server and agent communicating over a shared volume for the Unix socket).

ARM64 hosts: Docker images are amd64-only. Use native install or update-amud.sh with release *-arm64 binaries instead.

version: '3.8'

services:
  app:
    image: tradmss/amud-dashboard:latest
    container_name: amud_app
    restart: always
    ports:
      - "8000:8000"
    environment:
      - PORT=8000
      - BIND_ADDR=0.0.0.0
      - DB_PATH=/app/data/amud.db
      - PUID=99
      - PGID=100
      - AMUD_SOCKET_MODE=666
      - AMUD_SOCKET_PATH=/var/run/amud/amud.sock
      - AMUD_AGENT_SECRET=change-me-to-a-long-random-string # MUST match the agent secret below
    cap_drop:
      - ALL
    security_opt:
      - no-new-privileges:true
    volumes:
      - ./data:/app/data
      - amud_run:/var/run/amud

  agent:
    image: tradmss/amud-dashboard:latest
    container_name: amud_agent
    entrypoint: ["/app/amud-agent"]
    restart: always
    environment:
      - AMUD_SOCKET_PATH=/var/run/amud/amud.sock
      - AMUD_AGENT_SECRET=change-me-to-a-long-random-string # MUST match the app secret above
      - AMUD_DOCKER=1 # Auto-enabled when docker.sock is mounted; set 0 to disable
    cap_drop:
      - ALL
    security_opt:
      - no-new-privileges:true
    volumes:
      - amud_run:/var/run/amud
      - /var/run/docker.sock:/var/run/docker.sock:ro

volumes:
  amud_run:
    name: amud_run

Unraid (Community Applications)

Install both apps from Unraid’s Apps tab (they need to talk to each other):

• AMUD Dashboard
• AMUD Agent

Use the same Agent Secret on both. Full guide: Unraid install docs

First-boot permission error? If the dashboard log shows .amud-secrets-key: Permission denied, update to v1.7.2+ and recreate the container, or see troubleshooting and appdata permissions.

Template XML lives in templates/ with ca_profile.xml for Community Applications submission.

Proxmox LXC Autopilot Script

For native installation within a Proxmox VE LXC container (running outside Docker), execute this on your Proxmox VE host:

curl -sSL https://github.com/boubli/AMUD-Dashboard/releases/latest/download/setup-amud.sh | bash

Production Resource Footprint

For developers

Before you push Rust changes, run the same checks as GitHub CI:

# Windows
.\scripts\ci-check.ps1

# Linux / macOS / Git Bash
./scripts/ci-check.sh

Optional: install a pre-push hook with ./scripts/install-git-hooks.sh so cargo fmt failures never reach CI again.

Support & Donation

Bugs and feature requests: GitHub Issues (preferred — tracked per release)
Questions and chat: GitHub Discussions
Docs / troubleshooting: boubli.github.io/AMUD-Dashboard/docs

• GitHub Sponsors
• Donate via Stripe
• Ko-fi