Wizarr

Open-source user management for Plex, Jellyfin, and Emby — honestly reviewed. What it solves, where it falls short, and whether it’s worth adding to your stack.

TL;DR

• What it is: Open-source (MIT) user invitation and management system for self-hosted media servers — Plex, Jellyfin, Emby, Audiobookshelf, Komga, Kavita, and Romm [README].
• Who it’s for: Anyone running a personal media server for friends or family who is tired of explaining server addresses, app downloads, and access tokens to non-technical users [4].
• Cost savings: Wizarr itself costs $0. You run it on the same VPS or home server your media stack already occupies. The savings are measured in hours, not dollars — specifically the hours you stop spending walking relatives through Plex setup over the phone.
• Key strength: Turns a confusing multi-step onboarding process into a single shareable link. The 2025.5 complete rewrite made it significantly faster and cleaner [2].
• Key weakness: Narrow scope — it does one thing well. If you want full media management, request tracking, or analytics, you still need Overseerr/Jellyseerr on top of it. The project also went through a turbulent period before the 2025.5 relaunch, and long-term maintainability remains a question [2][README].

---

What is Wizarr

Wizarr is an invitation middleware layer for self-hosted media servers. You configure it once, point it at your Plex, Jellyfin, or Emby instance, and from then on adding a new user is a two-step operation: generate an invite link, send it to your friend. They click the link, complete a guided setup flow, and land on your server already configured — apps downloaded, request system explained, Discord joined if you have one [README][4].

The project’s own README states the problem bluntly: “Inviting your Friends/Family to your Plex server is complicated and tedious. It’s also a hard concept for them to get their head around.” [README] That’s exactly the gap Wizarr fills. It doesn’t replace Plex’s user system — it wraps around it with a friendlier front door.

As of this review, Wizarr sits at 2,755 GitHub stars. The project is MIT-licensed and had a notable revival: after going dormant, development relaunched and culminated in the 2025.5 release, described as a complete rewrite starting “back to basics” [2][README]. The primary maintainer (username lubricantjam on Reddit) announced the rewrite directly on r/PleX, framing it as leaving a “chaotic past” behind [2].

Supported media servers as of the 2025.5 release: Plex, Jellyfin, Emby, AudiobookShelf, Komga, Kavita, and Romm [README]. Request system integrations: Overseerr, Ombi, and Jellyseerr [3]. It can also send Discord invites and push notifications via NTFY [2].

---

Why people choose it

The clearest articulation comes from XDA Developers: “Having used Plex for over 7 years now, this is the easiest process I’ve come across yet to add users to my library.” [4] That sentence captures the whole value proposition. The alternative isn’t a paid competitor — it’s manually creating accounts, copying API tokens, and then spending twenty minutes on the phone explaining what a “media server” is to your parents.

The Medium guide [1] positions Wizarr as a “middleware layer between your media server and your users,” which is accurate. It doesn’t manage your media, it manages the door to your media. The TrustPilot-style signal here comes indirectly — ElfHosted, which offers Wizarr as a hosted app in their marketplace, shows strong community reception [3], and the r/PleX thread announcing 2025.5 was met with enthusiasm rather than skepticism [2].

The noted.lol Self Hosted Roundup [5] included Wizarr in its weekly digest of noteworthy new self-hosted projects, which is a reasonable proxy for community interest. The dev.to homelab article [6] doesn’t mention Wizarr by name but describes the exact pain point it solves — non-technical users and complex onboarding — as one of the main friction points in running a personal Plex or Jellyfin stack.

The 2025.5 rewrite matters because it signals the project recovered from whatever caused its previous stagnation. The Reddit post explicitly states: “All existing settings, invites, and users will be automatically migrated if you point the container at your old database.db.” [2] That’s meaningful for anyone who adopted Wizarr before the relaunch and is weighing whether to trust the project long-term.

---

Features

Core invitation system:

• Generate unique invite links per user or group [README][4]
• Optional passphrases, expiration dates, and per-invite user limits [4]
• Automatic account creation on the target media server — no manual steps [README]
• Multi-tiered invitation access (e.g., different library access levels per invite type) [README][2]
• Time-limited memberships with auto-expiry [README][2][3]

Onboarding wizard:

• Guided setup flow for new users: app download instructions, request system walkthrough, custom HTML steps [README][website]
• Pre-invite and post-invite wizard steps you define [README]
• Fully customizable via your own HTML snippets or Markdown [README][2]
• Multi-language UI (Weblate-based translation system) [README]

Integrations:

• Media servers: Plex, Jellyfin, Emby, AudiobookShelf, Komga, Kavita, Romm [README]
• Request systems: Overseerr, Ombi, Jellyseerr [3]
• Discord server invite integration [README][2]
• Notifications via NTFY and Discord [2]

Administration:

• Single dashboard for managing multiple media servers simultaneously [4]
• User list with per-server tracking — see who is tied to which service [4]
• Built-in auto-cleanup: time-limited users are removed automatically when their membership expires [4]
• SSO support (documented as “plug-and-play” in the README, though the asterisk in their own feature list suggests some caveats) [README][website]
• REST API with full OpenAPI/Swagger documentation at /api/docs/ and /api/swagger.json [README]

Coming soon (as of 2025.5):

• Multi-admin support
• Emby guide (the invitation flow, not just access management)
• “Advanced API to make Wizarr incredibly powerful” [2]

---

Pricing: SaaS vs self-hosted math

Wizarr has no SaaS offering and no pricing tiers. It’s MIT-licensed software you run yourself. The cost math is purely infrastructure:

Self-hosting Wizarr:

• Software: $0
• Memory footprint: minimal — it runs comfortably alongside an existing media stack
• Dedicated VPS: not required if you already run Plex or Jellyfin on a home server or NAS
• If you need a new VPS just for the media stack: $4–6/month on Hetzner or Contabo

There is no direct commercial alternative to Wizarr. Plex has its own built-in sharing mechanism, but it doesn’t guide users through onboarding, doesn’t support non-Plex servers, and doesn’t give you invite link controls with expiration or passphrases. ElfHosted offers hosted Wizarr as part of their self-hosting-as-a-service platform [3], but that’s infrastructure hosting, not a Wizarr subscription.

The real cost calculation is time: if you manage a media server for 5–15 people, and each new user onboarding takes you 30–60 minutes of back-and-forth support, eliminating that overhead across a year is the return. Wizarr setup is a one-time investment of 30–90 minutes. After that, new users cost you the time it takes to copy a link.

---

Deployment reality check

What you need:

• Docker (the only supported deployment method — no bare metal instructions in docs)
• Your existing Plex/Jellyfin/Emby API key
• A domain or subdomain with HTTPS if you want external access (Caddy or nginx for reverse proxy)
• The same Linux server or NAS that already runs your media stack

What the install looks like: The official docs point to https://docs.wizarr.dev/getting-started/installation for Docker Compose instructions [README]. The ElfHosted setup guide [3] shows the configuration is straightforward: server name, server type, server URL, API key, and optionally an Overseerr/Ombi URL. That’s the full initial setup for most use cases.

What can go sideways:

The project’s history is the main risk. Wizarr went through a period of dormancy before the 2025.5 relaunch. The Reddit announcement [2] acknowledges a “chaotic past” without specifying what that means — whether it was maintainer burnout, governance problems, or something else is unclear. The rewrite signals recovery, but the project has 2,755 stars and appears to be maintained by a small team. If development stalls again, you’re running unsupported software with access to your media server’s API key.

The SSO feature carries an asterisk in the README’s own feature list [README], suggesting it works but may require additional configuration that isn’t fully plug-and-play for all identity providers. No specifics are documented in the scraped content.

“Multi-admin support” is listed as a coming-soon feature as of 2025.5 [2], which means right now you’re operating with a single admin account. For a family or small group sharing server, that’s fine. For anyone trying to delegate management across multiple people, it’s a real limitation.

The 2025.5 rewrite is recent enough that edge cases and regressions are plausible. The Reddit post explicitly asks for bug reports [2]. If you’re adopting Wizarr now, you’re an early adopter of the new codebase, not a user of battle-tested software.

Realistic time estimate: 30–60 minutes to a working Wizarr instance if you already run Docker and have your media server’s API key handy. Add another 30 minutes if you need to set up a reverse proxy and HTTPS.

---

Pros and Cons

Pros

• Solves a real, specific problem. The onboarding friction for non-technical users on Plex and Jellyfin is genuine, and Wizarr is the cleanest solution that exists for it [4][1].
• MIT license. No usage restrictions, no commercial gating, no fair-code edge cases. Fork it, embed it, run it anywhere [README].
• Multi-server support. Manage Plex, Jellyfin, Emby, and more from a single dashboard — useful if you run separate servers for different content types [4].
• Invite controls that actually matter. Expiration dates, passphrases, user limits, and time-limited memberships are all first-class features, not afterthoughts [README][3][4].
• 2025.5 rewrite is a genuine fresh start. The new version is described as faster, sleeker, and more extensible [2]. Migration from old database is automatic [2].
• REST API with OpenAPI/Swagger docs — unusually well-documented for a project at this maturity level [README].
• Request system integration means users get walked through Overseerr or Ombi during onboarding, not just server access [3][README].

Cons

• Project history is a yellow flag. Development went dormant before the 2025.5 relaunch. Small team, unclear sustainability [2][README].
• No multi-admin support yet — single admin account is the current limit [2].
• SSO has caveats. The asterisk in the README’s own feature list suggests it’s not truly plug-and-play for all configurations [README].
• Narrow scope by design. Wizarr doesn’t replace Overseerr, Jellyseerr, or your media server’s native management. It’s an onboarding layer, nothing more. You still need the full stack [3].
• 2025.5 is a fresh codebase. Being an early adopter means potentially hitting bugs that older versions didn’t have [2].
• No official analytics or reporting. The Medium guide [1] mentions “detailed analytics about your server usage” but this appears to be describing general media server features, not Wizarr-specific functionality — Wizarr’s own documentation doesn’t surface this prominently.
• Community size is modest at 2,755 stars. Fewer contributors means slower bug resolution and less community-tested configurations compared to larger projects.

---

Who should use this / who shouldn’t

Use Wizarr if:

• You run a personal media server (Plex, Jellyfin, Emby) for friends or family and dread adding new users.
• You’ve spent more than one hour in the past month troubleshooting access for someone who “just wants to watch movies.”
• You already run Docker and have a working media stack — Wizarr fits in with minimal additional overhead.
• You want invite links with real controls: expiration, limits, passphrases.
• You run multiple media servers and want a single management interface.

Think twice if:

• You want a mature, battle-tested project with a large team and clear long-term roadmap. The 2025.5 rewrite is promising but recent.
• You need multi-admin support immediately — it’s listed as coming soon, not shipped [2].
• You’re running a more formal setup (paid IPTV service, subscription-based access) where a single admin account and limited SSO coverage creates operational risk.

Skip it entirely if:

• You only share with 1–2 people and manually adding them takes you five minutes. Wizarr’s setup cost won’t pay off.
• You’re on Plex and already satisfied with Plex’s built-in sharing and don’t need guided onboarding.
• Your users are technical enough to follow a README — Wizarr’s value is proportional to how non-technical your audience is.

---

Alternatives worth considering

Plex’s built-in sharing — If you’re Plex-only and your users are somewhat technical, Plex’s native invite system handles the basics. No setup required, no extra container to maintain. What you give up: guided onboarding, invite controls (expiration, limits), and multi-server support.

Jellyfin’s native user management — Similar story. Built-in, no overhead, but no wizard, no invite links with expiration, no guided app download flow. For less technical users, this is where the onboarding pain starts.

Overseerr / Jellyseerr — These are request management tools, not invitation management. They handle “I want to watch X, can you add it?” — a different problem. Wizarr and Overseerr are complementary, not competing: Wizarr handles the door, Overseerr handles requests once users are inside [3].

MediaRequest — A lighter-weight request management alternative. Same relationship to Wizarr as Overseerr: different problem, different tool.

ElfHosted — If self-hosting the infrastructure is the blocker (not the software), ElfHosted offers hosted Wizarr as part of their managed self-hosting platform [3]. You pay for infrastructure management and lose the DIY cost advantage, but eliminate server administration entirely.

There is no direct paid commercial competitor to Wizarr. The space it occupies — media server invitation management — doesn’t have a SaaS equivalent. Your alternative to Wizarr is doing the onboarding manually, not paying for a competing service.

---

Bottom line

Wizarr is a sharp, purpose-built tool that solves exactly one problem: turning “can you add me to your Plex?” into a five-second operation instead of a thirty-minute support call. It does this well, costs nothing, and runs on hardware you already have. The 2025.5 complete rewrite put the project back on solid footing after a period of dormancy, though adopting it now means betting on a recently relaunched codebase with a modest team. For anyone managing a personal media server for more than a handful of non-technical users, that bet is worth taking — the alternative is doing it all manually, and that cost compounds every time you add someone new. If the setup still feels like too much, that’s exactly the deployment work that upready.dev handles for clients.

---

Sources

1. ThamizhElango Natarajan, Medium — “Streamline Your Media Server: A Complete Guide to Wizarr User Management” (Jul 1, 2025). https://thamizhelango.medium.com/streamline-your-media-server-a-complete-guide-to-wizarr-user-management-ad0b009100d7
2. lubricantjam, Reddit r/PleX — “Wizarr 2025.5: A Complete Rewrite | Faster, Sleeker, and More Extensible!”. https://www.reddit.com/r/PleX/comments/1ktmxt3/wizarr_20255_a_complete_rewrite_faster_sleeker/
3. ElfHosted — “Hosted Wizarr - Media Server User Invitation Tool”. https://elfhosted.com/app/wizarr/
4. Dhruv Bhutani, XDA Developers — “4 reasons why this self-hosted app is a must-have for Plex and Jellyfin users” (Jun 29, 2025). https://www.xda-developers.com/4-reasons-why-this-self-hosted-app-is-a-must-have-for-plex-and-jellyfin-users/
5. noted.lol — “Self Hosted Roundup #27”. https://noted.lol/self-hosted-roundup-27/
6. dev.to — “Self-hosting like a final boss: what I actually run on my home lab (and why)”. https://dev.to/dev_tips/self-hosting-like-a-final-boss-what-i-actually-run-on-my-home-lab-and-why-48k1

Primary sources:

• GitHub repository and README: https://github.com/wizarrrr/wizarr (2,755 stars, MIT license)
• Official documentation: https://docs.wizarr.dev