samuelloranger/labby has 94 GitHub stars and 2 forks. GitHot measured 0 stars in 24 hours and 0 in 7 days. Last checked 2026-11-15 16:30 UTC. Last push 2026-11-05.
What you can do
- Widgets — service monitor, Docker, qBittorrent/Transmission, SABnzbd, AdGuard, Jellyfin, Emby, Plex, Beszel, Radarr, Sonarr, Rawkoon, C411, weather, calendar, speedtest, bookmarks, Reddit, Hacker News
- Live updates — server polls integrations and pushes changes over SSE (no client-side polling)
- Interactive — start/stop containers, pause/resume torrents, toggle AdGuard protection
- Config & credentials — stored in SQLite (config/labby.db), Zod-validated; edit service URLs/keys from the in-app Manage Services page
Measured star growth
- in 24h
- 0
- in 7 days
- 0
- in 15 days
- Update delayed
- in 1 month
- Update delayed
Net star changes over overlapping periods, not daily totals. Missing measurements are left blank. Stars measure attention, not software quality.
About
Self-hosted homelab dashboard: Widgets, live Docker stats, and real-time SSE updates. Built with Svelte + Bun.
Self-hostedREADME.md
Original
Labby

A self-hosted homelab dashboard — lightweight like Glance, interactive like Homarr. One Bun process, one container, config stored in a small SQLite database and editable in-app.
Features
- Widgets — service monitor, Docker, qBittorrent/Transmission, SABnzbd, AdGuard, Jellyfin, Emby, Plex, Beszel, Radarr, Sonarr, Rawkoon, C411, weather, calendar, speedtest, bookmarks, Reddit, Hacker News
- Live updates — server polls integrations and pushes changes over SSE (no client-side polling)
- Interactive — start/stop containers, pause/resume torrents, toggle AdGuard protection
- Config & credentials — stored in SQLite (
config/labby.db), Zod-validated; edit service URLs/keys from the in-app Manage Services page - Theming — named color schemes saved to the DB; no flash on first paint
Security
Login is off by default. Out of the box Labby has no authentication: run it behind a reverse proxy restricted to your LAN or VPN, or protect it with forward-auth at the proxy. Anyone who can reach an unprotected Labby can read status and control integrated services.
Optional OIDC login. Set LABBY_OIDC_ISSUER, LABBY_OIDC_CLIENT_ID, LABBY_OIDC_CLIENT_SECRET and LABBY_URL and Labby requires sign-in through any OpenID Connect provider (Authentik, Authelia, Keycloak, Pocket ID, …). Requires HTTPS. See the security guide for provider setup and the optional email/group allowlist.
Writes sent by another website through your browser (cross-site requests) are always rejected.
Backups (plaintext, including credentials) are written to config/backups/ on the server, never returned in an API response.
Quick start
Labby runs as a single container. Copy docker-compose.yml and start it:
docker compose up -d
services:
labby:
image: ghcr.io/samuelloranger/labby:latest
restart: unless-stopped
ports:
- "8080:8080"
volumes:
- ./config:/app/config
Open http://localhost:8080, then add your service URLs and credentials on the Manage Services page (the Database icon in the header). On first run Labby seeds its SQLite DB (config/labby.db) with a default layout via built-in migrations; everything you configure is stored there, in the mounted config/ volume.
config/must be writable by the user the container runs as. If the DB errors withSQLITE_READONLY, setuser: "<uid>:<gid>"indocker-compose.ymlto match the owner ofconfig/. Without OIDC login configured, keep Labby behind a LAN/VPN reverse proxy (see Security).
Build from source
Requires Bun (curl -fsSL https://bun.sh/install | bash).
bun install && (cd src/web && bun install)
bun run build
bun run start
Configuration
User config lives in the SQLite database. Invalid config shows an error state instead of crashing the server.
Service credentials and per-instance settings (monitor sites, weather location, Docker hosts, download client URLs, etc.) are stored in the integrations table. Dashboard widgets reference an integration by integrationId and only carry display options (title, layout style, max items). Poll cadence is set per integration row (refreshSeconds), not in the dashboard JSON.
Configure everything from the Manage Services page — no .env file or flat env-var keys.
Built-in integrations
Labby ships with a growing collection of integrations for the apps and services that usually live in a homelab:
|
Calendar |
Bookmarks |
Monitor |
Docker |
qBittorrent |
|
Transmission |
SABnzbd |
AdGuard |
Jellyfin |
Emby |
|
Plex |
Beszel |
Radarr |
Sonarr |
Rawkoon |
|
Weather |
Speedtest |
|
Hacker |
Most integrations ask for a base URL and either an API key, token, or username/password. Monitor and bookmarks rows accept lists of sites/links with optional per-item icons; Weather accepts an OpenWeather key plus city or coordinates; Hacker News has no required config.
You can add multiple integrations of the same type (e.g. two Radarr instances) — each gets its own row, poll interval, and SSE channel (int:<id>).
Docker host
The Read host / Write host fields accept either:
- A TCP endpoint —
tcp://host:2375orhttp://host:2375. Docker does not expose this by default; point it at a docker-socket-proxy (recommended — lets you allow reads but deny writes) or at a daemon with the TCP API enabled. - A unix socket —
/var/run/docker.sockorunix:///var/run/docker.sock, mounted into the Labby container. No proxy needed; point both Read host and Write host at the socket.
The socket grants full, root-equivalent control of the Docker daemon (docs). A
:robind mount only makes the socket file read-only on the host — it does not restrict the Docker API, so anything that can reach the socket can still start/stop/delete containers. It is not a read-only connection. If you want true read/write separation (allow status, deny control), use the docker-socket-proxy TCP option above instead and point Write host at a proxy that denies POST. The container must also be able to reach the socket — run Labby as a uid in thedockergroup, or matching the socket's owner.
Icons
The icon field accepts prefixed strings:
| Prefix | Example |
|---|---|
di: |
di:jellyfin — dashboard-icons (vendored at build, CDN fallback) |
sh: |
sh:immich — selfh.st |
lucide: |
lucide:film — built-in line icon |
| URL / path | https://… or /icons/custom.svg |
Refresh intervals
Set poll cadence per integration on the Manage Services page (refreshSeconds; defaults come from the integration type). The browser receives updates via SSE, not its own timers.
Development
bun run dev # API on :8080 (watch mode)
cd src/web && bun run dev # Vite dev server, proxies /api → :8080
bun test
For frontend work, run both dev servers. bun run dev alone does not serve the SPA until you bun run build.
Stack
- Runtime — Bun, TypeScript (strict)
- Backend — Hono (JSON API, static SPA, SSE)
- Frontend — Svelte 5, Vite
- Config — SQLite (
bun:sqlite), Zod validation, automatically seeded via migrations
Support
If Labby is useful to you, consider buying me a coffee ☕ — it keeps the project going.
License
MIT