Self-hosted dashboards, honestly reviewed. No homelab hype, just what you get when you deploy it.

TL;DR

What it is: A minimalist, MIT-licensed services dashboard — a visual front page for all your self-hosted apps, configured through a single JSON file [README].
Who it’s for: Homelab owners and self-hosters who want a clean, simple link hub for their services without learning YAML or wrangling a complex config system.
Cost: $0 for the software (MIT license). Runs on any VPS or home server alongside your existing stack; no dedicated hardware needed [README].
Key strength: Genuinely plug-and-play. One Docker command, one JSON file, and you have a working dashboard. The v1.0.0 release added a visual editor so you don’t even need to hand-edit JSON [1].
Key weakness: Very early-stage project (160 GitHub stars). No service health monitoring, no Docker auto-discovery, no multi-user auth. If you need more than a styled list of links, you’ll hit the ceiling quickly.

What is Iso

Iso is a self-hosted services dashboard — the kind of page you open in a new tab when you want to get to your Plex server, your Bitwarden vault, or your Gitea instance without memorizing port numbers. It’s a visual launcher for your homelab.

The project was built by Tim (GitHub: coyenn) as a personal homelab tool and open-sourced afterward. The README is candid about this: “Built for my personal homelab — now open-sourced for yours” [README]. That origin story shapes everything about what Iso is and isn’t.

Configuration is entirely through a single config.json file mounted into the container at /config. You define your services as an array of objects — an order number, an icon name, a display label, and a URL. That’s it. The dashboard reads the file and renders your links. There’s no database, no sync service, no accounts system. The entire mental model fits in one read of the README.

Version 1.0.0, announced on r/selfhosted [1], added themes (including the default “amethyst” color scheme), password-based authentication via environment variables, a visual config editor so non-technical users can add services through a UI, and a built-in set of isometric icons. The project also supports four languages out of the box (English, Spanish, French, German) and a search bar wired to your choice of Google, Bing, DuckDuckGo, Startpage, Qwant, Searx, or a custom engine [README].

At 160 GitHub stars as of this review, Iso is a small, early-stage project — not a mature platform.

Why people choose it

The r/selfhosted announcement for v1.0.0 [1] is the only substantial community reaction on record. The reception was positive but mixed, and the author addresses the tension directly.

The main draw is simplicity and design sensibility. Iso’s aesthetic skews toward clean minimalism — isometric icons, smooth page-load animations, and a visual editor that means you don’t need to touch a config file at all after initial setup [1]. For homelab owners who share their dashboard with less technical family members (the post explicitly calls out “non-technical users like friends and family”), this matters more than feature depth [1].

The push back in the thread focused on the tech stack. Several commenters flagged Next.js as heavyweight for what amounts to a static link page. The author acknowledged the criticism but defended the choice [1]. This is a real trade-off: Next.js means the container is larger and startup is slower than a plain HTML dashboard, but it also enables the visual editor and reactive UI without a full frontend build pipeline.

What Iso isn’t competing on: features. It’s not trying to be the most powerful dashboard in the category. The pitch is specifically “plug-and-play” — fast to deploy, easy to configure, easy to hand to someone who isn’t a sysadmin [README][1].

Features

Based on the README and the v1.0.0 release announcement:

Core dashboard:

Service cards with icon, label, and clickable link [README]
Display order control via a numeric order field [README]
Custom dashboard title in the header [README]
Page load animations (togglable) [README]
Custom greeting messages [README]

Visual config editor:

Added in v1.0.0, lets you add and reorder services through a UI [1]
Eliminates the need to hand-edit JSON for day-to-day changes [1]

Icons:

Built-in set of isometric icons [README][1]
Ability to supply your own icon files [README]

Themes:

Color theme support; amethyst is the named default [README]
Multiple themes added in v1.0.0 [1]

Search:

Integrated search bar with built-in support for Google, Bing, DuckDuckGo, Startpage, Qwant, Searx [README]
Custom engine support via a URL template with [q] placeholder [README]
Togglable and configurable placeholder text [README]

Localization:

English, Spanish, French, German (en, es, fr, de) [README]

Authentication:

Password protection via AUTH_SECRET and AUTH_PASSWORD environment variables [README]
Single shared password — no per-user accounts, no roles [README]

Deployment:

Docker image available on Docker Hub (coyann/iso) [README]
Docker Compose support [README]
Config directory mounted as a volume — persists across container updates [README]

What it doesn’t do:

No service health monitoring or uptime checks
No Docker socket integration — services must be manually listed, not auto-discovered
No widgets (CPU usage, weather, RSS feeds, etc.)
No bookmark management
No multi-user authentication

Pricing: what it costs to run

Iso has no SaaS tier and no commercial license — it’s MIT-licensed software you self-host entirely. The cost breakdown:

Software: $0 [README]

Infrastructure: Whatever you’re already running. Iso is a Node.js (Next.js) container that needs maybe 256–512MB RAM. If you’re already running a homelab stack with Plex, Nextcloud, or similar services, Iso adds negligible overhead on the same machine.

If you need dedicated hosting: A $4–6/mo VPS (Hetzner CX11, DigitalOcean Droplet) would be overkill for just a dashboard — you’d run it on the same host as your other services.

The real cost is time: Roughly 10–20 minutes to deploy on a server where Docker is already running. The config.json setup is minimal. The visual editor in v1.0.0 removes even that friction for ongoing changes [1].

Unlike the commercial SaaS alternatives that charge $5–20/month for a “start page” service, Iso (like all the competing open-source dashboards) runs for the price of electricity once deployed.

Deployment reality check

The install path is straightforward:

docker run -d \
  --name iso \
  -p 3000:3000 \
  -e AUTH_SECRET="changeme" \
  -e AUTH_PASSWORD="changeme" \
  -v ./config:/config \
  coyann/iso

Visit http://localhost:3000 and you have a running dashboard [README]. The Docker Compose version adds restart: unless-stopped which is all you need for production use on a homelab [README].

What can trip you up:

The config volume needs to exist before the container starts. If /config is empty on first run, you’ll need to create and populate config.json manually — the visual editor requires the container to be running first.
Authentication is a single shared password. If you expose this to the internet, there’s no account lockout, no 2FA, and no audit trail. For internal homelab use (behind Tailscale or a VPN), this is fine. For a public-facing dashboard, it’s not.
Next.js means the container image is larger than the alternatives. Pull time on a slow connection is noticeable.
The tech stack attracted criticism from the homelab community [1]. Some users prefer minimal footprint (Homer runs on nginx, serving static HTML). If container image size or memory usage is a constraint, Iso isn’t the leanest option.

For a technical user: 5–15 minutes to a working instance. For a non-technical user following the README: 30–60 minutes including figuring out Docker volumes and environment variables.

Pros and cons

Pros

Genuinely simple. Single JSON file, one container, no database, no external services. You can understand the entire system in five minutes [README].
Visual editor. Most dashboard alternatives require YAML or JSON hand-editing for every change. Iso’s v1.0.0 added a UI editor that makes it accessible to non-technical users [1].
MIT licensed. No commercial restrictions, no “fair-code” gotchas — fork it, embed it, do what you want [README].
Multi-language. Four languages included out of the box, which is unusual for a 160-star project [README].
Clean aesthetic. Isometric icons and the amethyst theme give it a distinctive look that stands out from the utilitarian default styling of most homelab dashboards [README][1].
Fast to hand to someone else. The explicit design goal of serving non-technical users (friends, family) is actually achieved — the visual editor means you can set it up and hand it off [1].

Cons

No service health monitoring. You can’t tell at a glance if a service is down. Homarr, Homepage, and Dashy all offer health check integrations. Iso just shows links [README].
No Docker auto-discovery. Every service must be manually added. On a homelab with 20+ containers, this is maintenance overhead [README].
Single-password auth. Fine for a personal homelab, inadequate if you want multiple users with different permissions or any audit trail [README].
Very small community. At 160 stars, Iso is a one-developer project. There’s no plugin ecosystem, limited community support, and no guarantee of longevity. Compare to Homepage (20k+ stars) or Dashy (17k+ stars).
Next.js overhead. Legitimate criticism from the homelab community [1] — the stack is heavier than a simple dashboard warrants. This isn’t fatal, but it’s a real trade-off against alternatives with lighter footprints.
No widgets. If you want to see your NAS storage, current weather, or RSS headlines on the same page as your service links, Iso can’t do that. You’d need a different tool.
Early-stage. v1.0.0 was released relatively recently. The visual editor and themes are new. There will be bugs in features that haven’t had wide production exposure yet [1].

Who should use this / who shouldn’t

Use Iso if:

You want the fastest path from “no dashboard” to “working dashboard” — 15 minutes, one config file, done.
You’re setting up a dashboard for non-technical family members who need to click links, not manage infrastructure.
You value clean visual design over raw features and are happy to sacrifice service health monitoring for simplicity.
You want a dead-simple starting point and are fine migrating later if you outgrow it.

Skip it (pick Homepage) if:

You want service widgets — CPU, memory, weather, Sonarr queue status, media server stats. Homepage has a mature widget ecosystem and 20k+ stars.
You need Docker auto-discovery so new containers appear in your dashboard automatically.
Community support and long-term maintenance guarantees matter to you.

Skip it (pick Homarr) if:

You want the richest feature set: integrations with Radarr, Sonarr, Plex, Jellyfin, Deluge, qBittorrent, and more — all surfaced directly on the dashboard as interactive tiles.
You run a large homelab and want drag-and-drop layout management.

Skip it (pick Homer) if:

Minimal container footprint is a priority — Homer is a static site served by nginx, using a fraction of Iso’s RAM.
You’re comfortable with YAML and just need a fast, dependency-light launcher.

Alternatives worth considering

Homepage (gethomepage.dev) — The current community favorite. YAML configuration, 500+ service integrations with live widgets, Docker auto-discovery, 20k+ stars. More setup friction than Iso, but vastly more capable.
Homarr — Feature-rich, drag-and-drop interface, deep integration with arr-stack services, Docker integration. The best choice if you run Plex/Jellyfin with Sonarr/Radarr.
Dashy — Highly customizable, JSON or YAML config, status monitoring, 17k+ stars. More complex than Iso but considerably more powerful.
Homer — YAML-based, runs on nginx, minimal resource usage. No visual editor, no dynamic features — just a fast, reliable link page. Good if you want the lightest possible footprint.
Flame — Combines a services dashboard with a bookmarks manager. Good for teams that want a shared company intranet portal feel.
Organizr — HTPC-focused, integrates with Plex/Jellyfin for SSO-style tab embedding. Complex setup, powerful if you live in that ecosystem.

For a non-technical homelab owner who just wants to get started quickly, the realistic shortlist is Iso vs Homer vs Homepage. Iso wins on ease of initial setup and visual polish. Homer wins on minimal footprint. Homepage wins on features.

Bottom line

Iso is an honest tool that does exactly what it says: plug it in, list your services, get a clean dashboard. The visual editor and multi-language support make it genuinely accessible to non-technical users, which is rarer than you’d think in the homelab dashboard category. The trade-offs are equally honest — no health monitoring, no auto-discovery, single-password auth, and a 160-star project that may or may not be actively maintained long-term.

If you need a dashboard right now and want the simplest possible path, Iso is a legitimate choice. If you’re building a homelab for the long term and need service health at a glance or Docker integration, spend an extra hour with Homepage instead. Iso is a starting point, not a final destination — and for its target audience, that’s exactly the right pitch.