Lastboard

Yes. Lastboard is free and open source under the Apache License 2.0. You can read, run, fork and self-host it however you like, and the licence explicitly reserves only the names and logos.

Run the single static Go binary directly on Linux (amd64 or arm64) with the one-line install script, or use the Docker image. Data lives in a single SQLite file, so there is no separate database to set up and no configuration file to write — the first run is a three-step wizard in the browser.

Very little. It is one static binary with a pure-Go SQLite driver and no CGO, and the frontend ships zero runtime JavaScript dependencies. It runs comfortably on a Raspberry Pi or a 512 MB LXC container.

Yes. It runs behind Nginx, Traefik, Caddy, Cloudflare or Pangolin. Enable the TRUST_PROXY option so rate limiting and the login lockout see the real client IP, and set TRUST_PROXY_HOPS if more than one proxy sits in front.

Yes. Lastboard imports Homepage services.yaml and bookmarks.yaml and Dashy conf.yml, creating new dashboards without touching or overwriting what you already have, and telling you how many items it will create before it creates any.

Yes. Enable 24/7 monitoring and a server-side scheduler probes every bookmarked service on a 1 to 30 minute interval, recording 30 days of status, latency and outages — and alerting you through ntfy, Gotify or a webhook when something goes down and again when it recovers.

No. Monitoring is part of Lastboard: the same bookmark you click to open a service is the thing being monitored, so there is nothing to configure twice and no second container to run.

Yes. Lastboard lists containers from the local socket, from remote TCP or TLS daemons, or through the Lastboard Agent, shows their live CPU and memory, and lets an administrator start, stop and restart them. The agent means you never have to expose the Docker socket on the network.

It reads a Proxmox VE host with an API token and shows node load, storage fullness and every virtual machine and container, each tied to the bookmark it serves so a stopped machine names the service it takes with it. Start and shutdown are optional, only on the hypervisors you connected, and never offered for a node.

No. There is no telemetry, no analytics and no account. Icons you pick are downloaded once and then served from your own server, so loading your dashboard does not tell a public CDN your address or which services you run. The only request Lastboard makes on its own is the update check, and it goes straight to our own Forgejo.

It is built for it: passwords hashed with Argon2id, HMAC-signed session cookies, CSRF plus a Sec-Fetch-Site check, a strict Content-Security-Policy with a per-request nonce, rate limiting with a login lockout, signed releases verified with Ed25519, and optional unprivileged execution. It is still self-hosted software — put it behind HTTPS.

Yes. Each account gets its own dashboards, preferences, avatar and password. Each account also has its own monitoring and alert channel and its own Proxmox connections. There is exactly one administrator — the account created by the setup wizard — who holds the server-wide settings: users, backups and updates.

Yes. Lastboard renders a simplified, touch-friendly layout on phones, with visibility and ordering set independently of the desktop grid. It also installs as an app on Android, iOS and the desktop.

Twenty, all hand-translated: Arabic, Bengali, Chinese, Dutch, English, Farsi, French, German, Greek, Hindi, Indonesian, Italian, Japanese, Korean, Polish, Portuguese, Russian, Spanish, Turkish and Urdu — with full right-to-left layout for Arabic, Farsi and Urdu.

An administrator can update from the web interface: Lastboard downloads the release, verifies its Ed25519 signature and checksum, installs it and restarts, showing each step as it happens and putting the old binary back if the swap fails. Docker and native installs can also be updated the usual way.