Overview

TraLa is a dashboard for services published through Traefik. Instead of maintaining a bookmarks page by hand, you give TraLa the address of your Traefik API and it discovers the HTTP routers it finds there, then renders them as a grid of icon tiles grouped by tag. The result is a live start page that keeps up with your stack automatically: deploy a new container with a Traefik label set, and it appears on the dashboard without an edit.

It is a single container with a web interface, written for the common self-hosted pattern of Traefik in front of a handful of services, and it scales to an aggregator for several Traefik hosts at once. The project is MIT licensed and available in English, German, Dutch and French.

Key Features

• Automatic discovery: reads HTTP routers straight from the Traefik API and lists them, so the dashboard is always in sync with what the proxy is serving.
• Icon auto-detection: resolves service icons through selfh.st/icons, which removes most of the manual per-service artwork.
• Smart grouping: groups services by their Traefik tags, letting you arrange the dashboard into sections such as media, network or observability from labels alone.
• Multi-host: aggregates services from several Traefik instances into one page, useful when you run more than one Docker host.
• Manual services: adds custom entries for links that Traefik does not manage, so everything you use still lives on one page.
• Light and dark themes: follows the operating system preference automatically.
• Multi-architecture images: published for amd64 and arm64, which covers both a desktop-class server and a Raspberry Pi.
• Translations: community languages managed through Weblate, with English, German, Dutch and French already available.

Why Use It

The usual home server start page is a hand-written HTML file or a YAML list that slowly drifts out of date. Because TraLa takes its inventory from Traefik itself, the list cannot drift: whatever the proxy routes is what the page shows. That makes it a good fit for anyone who already labels containers for Traefik and would rather not maintain a second source of truth for the same information.

Common Use Cases

• Home lab start page: one link that opens everything Traefik fronts, with icons already resolved.
• Catalogue across hosts: a single view of services scattered over two or three Docker machines.
• Shared with the household: a friendly grid for people who do not want to remember ports and subdomains.
• Discovering forgotten services: browsing the auto-built list often turns up containers still running that nobody remembers deploying.

Running It

TraLa is distributed as a container image (ghcr.io/dannybouwers/trala). The minimum configuration is a single environment variable pointing at your Traefik API, for example TRAEFIK_API_HOST=http://traefik:8080; grouping, icons, manual services, multi-host aggregation and search are covered in the documentation at trala.fyi. It is designed to sit behind the same Traefik instance it reads, which keeps the dashboard on a private network.