Homer vs Organizr

Editor take

Pick Homer for a light static page. Choose Organizr only for embedded services behind a login.

Editor

Pros and cons

Each app's own strengths and weaknesses, plus the specs where Homer and Organizr differ.

Homer

Pros

  • Single YAML config file
  • Static, very light page
  • Fuzzy search and shortcuts
  • Installable as a PWA
  • Multi-page layouts

Cons

  • No Docker status by default
  • Login left to a proxy
  • Themes need custom CSS

Organizr

Pros

  • Tabs embed your own services
  • Per-group tab permissions
  • Login with Plex or LDAP
  • Nginx auth_request support
  • Themes and custom icons

Cons

  • No release since 2019
  • Iframes blocked by some apps
  • Site and wiki still unfinished

Homer vs Organizr: specs side by side

Every spec for both apps in one table. Values in bold are where one app has the edge, and amber ones are worth a second look before you install.

Spec
PriceFreeFree
LicenceApache-2.0GPL-3.0
Web UIYesYes
DockerYesYes
Tech stackVuePHP
Docker Containers1 (app only)1 (app only)
DatabasenoneSQLite
Architecturex86 + ARMx86 + ARM

Common questions

Does Homer have a login?

No. It leaves authentication to a reverse proxy; Organizr has its own login and groups.

Which handles Docker status?

Neither does much: Homer needs extra setup and Organizr embeds the service's own page.

Sources: Homer docs and Organizr docs. Versions checked: Homer 26.08.3.

Updated