Self-hosted service organization, honestly reviewed. No marketing fluff — just what you actually get when you run a dozen services and need to stop memorizing ports.

TL;DR

What it is: A self-hosted, PHP-based dashboard that wraps all your homelab services into tabbed iFrames behind a single URL, with user management and authentication baked in [3][4].
Who it’s for: Homelab operators and HTPC enthusiasts who run Plex, Sonarr, Radarr, Home Assistant, Portainer, and a dozen other services and are tired of maintaining a browser bookmark folder that nobody else in the house can use [1][3].
Cost: Free. GPL-3.0 licensed. Runs in Docker on whatever server you’re already running [README].
Key strength: iFrame tab management with per-user access control — a feature combination that simpler dashboards like Homer and Flame deliberately don’t have [1][5].
Key weakness: The project feels stalled. The official site says “will be refreshed soon,” the wiki says “will be updated soon,” the last stable release is from 2019, and at least one comparison review author actively chose not to evaluate it for that reason [6][README].

What is Organizr

Organizr is a PHP web application that acts as a front door for a homelab. Instead of bookmarking http://192.168.1.10:8989 for Sonarr, http://192.168.1.10:32400 for Plex, and another eight URLs for everything else, you set up Organizr once and access everything through tabs on a single page — something like http://organizr.yourdomain.com [3].

The core mechanic is the Tab Editor. You add services as tabs with one of three modes: iFrame (the service loads inside Organizr), New Window (opens a browser tab), or Internal (for Organizr’s own built-in pages). Most self-hosted services that run on a web port can be embedded as iFrames. Those that don’t play well with iFrames — typically anything with strict X-Frame-Options headers — fall back to the new window mode, and Organizr has a “Test Tab” button that detects and recommends the correct setting automatically [3].

What separates Organizr from simpler bookmark aggregators is the user and access control layer. You can create user accounts, assign them to groups, and make individual tabs visible only to specific groups. This means your spouse can see Plex but not Portainer; your friends can see the shared media library but not your router admin panel. Guests get their own reduced view. Authentication can be handled by Organizr’s own login system or delegated to an external provider — Plex, Emby, or LDAP [README][4].

The project lives at GitHub under causefx/Organizr, carries a GPL-3.0 license, and shows 5,714 stars and 94 contributors. Docker pulls on the official image are substantial, suggesting a large installed base despite the project’s quiet public presence [README].

Why people choose it

The Reddit thread [1] captures the honest sentiment: someone who cycled through Homer → Heimdall → Dashy → Organizr and stopped at Organizr because it was “the most complete solution.” The specific reasons that come up in that thread and in the HomeTechHacker review [3] cluster around two things: iFrame support and user access tiers.

Homer and Flame are fast, clean, and simple — but they’re link launchers. They open services in new tabs. Every service gets its own browser tab, you’re constantly context-switching, and there’s no concept of “this person can see these links, that person can see those.” For a solo operator who just wants quick navigation, Homer is plenty. For someone running a shared household media setup or a multi-user lab, Organizr’s tab management model is genuinely different [5][1].

Dashy is closer competition — it has per-user access, status monitoring, and workspace views. But several users in the r/selfhosted community land on Organizr specifically because of iFrame embedding: watching Plex, checking Sonarr’s download queue, and glancing at Grafana metrics without leaving the Organizr window [1][5].

The HomeTechHacker review [3] makes a pragmatic point: Organizr is not “just a bookmark organizer.” The homepage customization, where you can embed widgets showing Emby’s currently playing, recent additions, and other service-specific data pulled via API tokens, turns it from a navigation panel into an actual dashboard. That layer of integration is where simpler alternatives fall short.

The blackvoid.club review [6] is worth citing honestly, because the author explicitly chose not to evaluate Organizr — putting it in a list alongside Homer and Muximux as tools that are “just not my cup of tea.” The reasoning isn’t elaborated, but the choice signals something: for users who prioritize visual minimalism and simplicity over features, Organizr’s density can feel like too much.

Features

Core tab engine:

iFrame, new window, and internal tab types per service [3]
“Test Tab” button auto-detects if a service supports iFrame embedding [3]
Quick access tabs via URL hash — organizr.example.com/#Sonarr jumps directly [README]
Split-screen support for two tabs side-by-side [4]
Keyboard shortcuts for tab navigation [README][4]
Pin/unpin sidebar, fullscreen mode [README]
Set a default page on launch [README]

User and access management:

Unlimited user groups with per-tab visibility controls [README]
Three default user classes: admin, user, guest [4]
Registration passwords to control who can create accounts [README]
Login with Organizr credentials, Plex, Emby, LDAP, or sFTP [README][4]
Multiple login provider support (e.g. Plex OR LDAP) [README]
User management console for creating, deleting, and promoting accounts [README]

Security integrations:

Nginx auth_request support — use Organizr as an auth proxy for other services [README][4]
Fail2ban integration for brute-force protection [README]
Login log viewer for auditing access attempts [README][4]

Customization:

Full theming with color palette access [README][4]
Upload custom icons or use built-in icons for popular services [3]
Add your own logo or site name to the top bar [README]
Additional language support: EN, DE, ES, FR, IT, NL [4]
Gravatar support for user avatars [README]

Homepage widgets:

Per-service homepage items (Emby, Plex, etc.) showing currently playing, recent media, etc. [3]
Requires API tokens from each connected service [3]

Pricing: self-hosted vs. the alternative

There is no SaaS version of Organizr. The software is free, GPL-3.0, runs in Docker, and costs nothing beyond the server you’re already running other services on [README].

The honest cost comparison here is time and complexity rather than dollars. The real-money version of this problem is paying for something like Cloudflare Access or a commercial reverse proxy dashboard product to front your homelab — or accepting that nobody in your household will ever use your self-hosted tools because the URLs are incomprehensible.

If you’re running a $6–10/month Hetzner or Contabo VPS as a homelab server, Organizr adds zero marginal cost. If you’re hosting locally on a home server, it’s the same: no license fees, no usage tiers, no premium-gated features [README][4].

The only “cost” worth naming: the Nginx auth_request integration, if you choose to configure it, gates access to all your other services through Organizr’s auth system. This means Organizr is now in the critical path — if it goes down, your auth proxy goes with it. That’s a configuration choice, not a requirement, but it’s worth understanding before you build the setup [README][3].

Deployment reality check

Docker installation is straightforward. The README’s example command is three parameters: a volume for config, a port mapping, and PUID/PGID for file permissions [README]:

docker create \
  --name=organizr \
  -v /path/to/config:/config \
  -e PGID=1000 -e PUID=1000 \
  -p 8080:80 \
  organizr/organizr

The HomeTechHacker review [3] walks through the post-install setup: create an admin user, set a database name and hash key for password storage, then start adding tabs. The tab editor is visual. The setup for a basic multi-service dashboard is described as “pretty straightforward.”

What can go sideways:

First, iFrames. Not every service will embed cleanly. Services that set X-Frame-Options: DENY or Content-Security-Policy: frame-ancestors 'none' will refuse to load inside Organizr’s iFrame. The “Test Tab” detection helps, but you’ll hit this with things like Bitwarden’s web vault, some router admin panels, and services that have hardened their headers. You either configure those services to allow your Organizr domain, or you fall back to new window mode [3].

Second, Nginx auth_request integration requires nginx configuration changes that aren’t beginner-friendly. The wiki covers it, but the wiki itself carries a “will be updated soon” warning that has apparently been there for a while [README].

Third, the project’s maintenance velocity. The GitHub history shows 4,230 commits but the last formal release dates from February 2019, with a warning that update before that date was required to keep v1 working. The v2-master branch has seen commits since, but the development cadence is slow, and the official documentation site openly signals it’s out of date [README]. For a tool that sits in front of your entire homelab setup, betting on a project with stalled public momentum is a real consideration.

Realistic install time: 20–45 minutes for someone comfortable with Docker who already has a reverse proxy running. For someone deploying Docker for the first time, add another hour or two for the surrounding infrastructure.

Pros and cons

Pros

iFrame tab management. The distinguishing feature. Services load inside Organizr — no context switching to new browser tabs. For an active monitoring workflow (watching Sonarr + Grafana + Portainer simultaneously), this changes how you actually use your homelab [1][3].
Per-user access tiers. Share your homelab with family or friends without exposing the admin surface. This is missing or vestigial in Homer, Flame, and most simpler alternatives [README][4][5].
LDAP/Plex/Emby authentication. If you’re already running one of these, you get SSO into Organizr without maintaining a separate user database [README][4].
Nginx auth_request proxy. Organizr can serve as an authentication gateway for services that don’t have their own login, protecting them with a single auth layer [README][3].
Genuinely free. GPL-3.0, no premium tier, no features gated behind a commercial license [README].
Large installed base. Docker image pull numbers and r/selfhosted activity suggest a large community with solved problems and working configurations [1][README].

Cons

Maintenance pace is slow. Last stable release 2019. Official site and wiki openly marked as out-of-date. A tool that sits in the critical auth path of your lab needs active maintenance to stay trustworthy [6][README].
iFrame limitations are real. Hardened modern services refuse iFrame embedding. You’ll spend time configuring headers or accepting that some tabs open in new windows anyway [3].
PHP dependency. Running a PHP app in Docker is fine, but it’s a heavier runtime than static dashboard alternatives. Not a dealbreaker, but notable when Homer serves similar link-launching functionality as a static HTML file [README][5].
Setup complexity relative to alternatives. Flame and Homer are genuinely simpler to configure. If you don’t need user groups and auth proxying, that complexity is overhead, not value [5][6].
Not for visual minimalists. The feature density reads as clutter to some users. At least one reviewer explicitly passed on evaluating it for this reason [6].
Homepage widget setup requires API tokens and service-specific config. The dashboard homepage isn’t plug-and-play — you need to get Emby/Plex API keys and wire them in [3].

Who should use this / who shouldn’t

Use Organizr if:

You run 5+ self-hosted services and want them accessible through one URL with one login.
You have multiple users (family, lab partners) who need different access levels — guests see media, admins see infrastructure.
You want services to load inside the browser window rather than constantly spawning new tabs.
You’re already running Plex or Emby and want to delegate authentication to them rather than maintaining separate accounts.
You want an auth proxy layer via Nginx auth_request to protect services that don’t have their own login.

Skip it (use Homer or Dashy instead) if:

You’re a solo operator who just wants a clean list of links to click.
You prioritize visual simplicity and low maintenance over features.
You’re setting up a quick homelab for the first time and want something that works in 10 minutes.

Skip it (use Dashy instead) if:

You want status monitoring, uptime checking, and service health widgets in a more actively maintained project with a modern UI.

Approach with caution if:

You’re planning to use the Nginx auth_request integration on a production setup — you’re betting uptime on a project with slow maintenance.
You need reliable documentation — the wiki being self-described as out-of-date is a real friction point when things break.

Alternatives worth considering

Homer — Static HTML, YAML config, dead simple, zero user management. The right choice if you’re a solo user who wants quick links without complexity [5].
Heimdall — Closer to Organizr in age and popularity. Application tiles with built-in app types for enhanced display. Less feature-dense than Organizr; no iFrame tabs [6][5].
Dashy — Actively maintained, more polished UI, status monitoring, SSO support, workspace view. Probably the strongest alternative today for most users [5].
Flame — Minimal, Docker-integrated auto-discovery of services via container labels, fast to set up [5][6].
Homarr — Newer entrant with a drag-and-drop tile editor, service integrations, active development. Has been gaining ground in r/selfhosted as a more modern option.
Muximux — Similar iFrame-based approach, but effectively abandoned. Organizr is the better version of this idea [6].

For a non-technical user being set up by someone else, Heimdall or Dashy are more accessible. For a power user who specifically needs iFrame tabs and user group access control, Organizr remains the only option that combines both — even accounting for its maintenance pace.

Bottom line

Organizr solves a real problem that simpler dashboards don’t: multiple users, different access levels, and services that load inside the window instead of spawning new tabs. For the homelab operator who has outgrown “a folder of bookmarks” and needs to share a curated view of their infrastructure with non-technical household members, the feature combination is unique. The trade-off is real — a project with slow maintenance, self-described outdated docs, and a 2019 last release timestamp is not where you want a critical auth gateway to live. If you use the tab navigation without the Nginx auth_request integration, that risk is lower. If you’re wiring it into your entire service auth chain, the maintenance story deserves honest weight in your decision.

For the audience this tool targets — homelab operators building out HTPC setups around Plex, Sonarr, and a fleet of related services — Organizr has the right features. The question is whether the development velocity gives you enough confidence to build on it. Check the GitHub commit dates against your tolerance for running something that might not get patched when PHP or Docker changes underneath it.