Self-hosted media request management, honestly reviewed. No marketing fluff, just what you get when you run a Plex server for six people and they all want different things.

TL;DR

What it is: Self-hosted media request portal for Plex, Emby, and Jellyfin — your users browse, click “request,” and the content appears on your server without you getting a 2am text [README][1].
Who it’s for: Anyone running a shared media server for family or friends who needs a civilized way to handle content requests without becoming a personal help desk. Not really aimed at founders escaping SaaS — this solves a specific homelab problem [README][5].
Cost savings: Ombi itself is free (GPL-2.0). Managed hosting through services like ElfHosted exists for those who don’t want to run their own server [1]. The real savings pitch is elsewhere: one self-hosted media server shared across a household vs. five people each paying $15–20/mo for streaming services.
Key strength: First-mover advantage and breadth — one of the few request tools that natively supports Plex, Emby, and Jellyfin, plus mobile apps for both iOS and Android. It’s the OG in this niche [README].
Key weakness: Overseerr has largely taken over the Plex-specific use case with a more modern codebase and faster-moving development. Ombi is in a defensive position and showing its age in parts [5].

What is Ombi

Ombi solves a specific problem: you’ve built a Plex, Emby, or Jellyfin server and shared it with family or friends, and now you’re the de facto on-call content coordinator. Someone wants the new season of something, another person wants a movie they saw reviewed somewhere, and none of them know how Sonarr works or why they shouldn’t just text you.

Ombi sits in front of your media stack and gives your users a clean portal where they can search for movies, TV shows, and music, click “request,” and let automation handle the rest. The request flows from Ombi into Sonarr (for TV) or Radarr (for movies) or Lidarr (for music), which downloads the content, your media server picks it up, and the person who asked gets a notification when it’s available [README].

The project was started by Jamie Rees (GitHub handle: tidusjar) and has picked up 270+ contributors over its lifetime. It sits at 4,066 GitHub stars under a GPL-2.0 license, available on GitHub at https://github.com/ombi-app/ombi and at the official site http://ombi.io.

The pitch from the README: “Want a Movie or TV Show on Plex/Emby/Jellyfin? Use Ombi!” The website goes with “Your Media, On Demand.” Both are accurate. This is a utility tool that does what it says on the tin.

Why people choose it

The honest answer is that most people who choose Ombi in 2026 are either migrating from an older setup, running Emby or Jellyfin (where Overseerr has historically had weaker support), or already deep in an Ombi configuration they don’t want to relearn.

That said, there are genuine reasons to choose it:

It’s the one that supports everything. Ombi works with Plex, Emby, and Jellyfin. For a long time, competing tools like Overseerr were Plex-only, which made Ombi the default choice for anyone running Emby or Jellyfin. That gap has narrowed — Jellyseerr now covers Jellyfin — but Ombi still has the broadest native media server support [README][1].

Mobile apps exist and are real. Both iOS (App Store) and Android (Google Play) apps ship as part of the project. In a category full of “responsive web app and that’s fine,” native apps are a differentiator for households where family members are browsing from phones [README].

It plays well with Organizr. Organizr is the dashboard-for-dashboards that homelab enthusiasts use to unify their apps under one URL. Ombi has documented SSO integration with Organizr, meaning your users can log in once and access Ombi alongside their other self-hosted tools without managing separate credentials [2].

Managed hosting exists if self-hosting is the blocker. ElfHosted offers hosted Ombi as part of their FOSS hosting platform, which means you can run Ombi without owning a server or touching Docker. They describe it as a 7-day trial option, which lowers the barrier to experimenting [1].

The honest counter-position: Overseerr has eaten significant market share among Plex users specifically. If your entire stack is Plex-first and you’re starting fresh, the community will often point you toward Overseerr for its more polished UI and more active current development. Ombi is not a bad choice — but it’s no longer the default recommendation for new setups [5].

Features

Based on the README and website:

Core request flow:

Users can request movies, TV shows (entire series, by season, or individual episodes), and music [README]
Shows existing content on your server — users can see if something is already available before requesting [README]
Will show if a title is already being monitored by Sonarr/Radarr even if not yet downloaded [README]
Optional admin approval step before requests are automatically forwarded to download tools [website]

Integration stack:

Media servers: Plex, Emby, Jellyfin [README][1]
Download automation: Sonarr, Radarr, Lidarr, CouchPotato, SickRage [README][website]
Automatic status updates when content is added to your server [README]

User management:

Syncs user accounts from your Plex or Emby server — no need for people to create new credentials [README][website]
Local accounts also supported [README]
Configurable per-user request limits and auto-approval rules [README]

Notifications:

Per-user customizable notifications [README]
Multiple notification channels (email, push, and others via webhook) [website]

UI and access:

Responsive web UI [README]
Native iOS app (App Store) and Android app (Google Play) [README]
Localization via Crowdin — community-translated into multiple languages [README]
Landing page with server availability status and custom downtime notices [README]

SSO and integrations:

Organizr SSO integration documented and maintained [2]
API key-based access for integration with other tools [2]

Pricing: SaaS vs self-hosted math

Ombi has no SaaS tier. There is no subscription, no cloud version, no per-user pricing. The software is GPL-2.0 and the only question is where you run it.

Self-hosted (the standard path):

Software: $0
Server: $0 if you’re running it on the same box as Plex/Emby (which most people do)
If you need a separate VPS: $5–10/mo on Hetzner, Contabo, or similar

Managed hosting (ElfHosted):

ElfHosted hosts Ombi as part of their self-hosted app platform, with a 7-day trial [1]
This makes sense if you want Ombi without managing a server yourself, and you’re already using ElfHosted for Plex or Arr* apps
Specific ElfHosted pricing for Ombi as a standalone add-on was not available at time of writing — check their current pricing at elfhosted.com

The real cost context: Ombi doesn’t replace a SaaS subscription — it replaces a manual workflow. The actual savings calculus here is at the media server level, not at Ombi itself. A household of five people paying Netflix ($15–23/mo), Disney+ ($8–14/mo), and one or two other streaming services is spending $60–150+/mo collectively. A single self-hosted Plex server with Ombi handling requests and Sonarr/Radarr handling acquisition runs on a $10–25/mo VPS or an existing home server. That’s the cost comparison Ombi enables, not a direct Ombi-vs-paid-tool comparison.

Deployment reality check

Ombi runs on Windows, macOS, Linux, and Docker. The Docker path (via the linuxserver/ombi image) is the most common and what most guides use [README][5].

What you need:

An existing Plex, Emby, or Jellyfin server (Ombi is a companion, not a standalone system)
A Linux host or VPS with Docker installed
A reverse proxy (Caddy or nginx) if you want HTTPS and a clean URL
Optionally, a working Sonarr/Radarr/Lidarr stack if you want requests to flow into automated downloading

What the setup actually looks like: The SimpleHomelab Docker media server guide lists Ombi as part of a 150+ app stack, suggesting it integrates cleanly into a broader homelab environment without being the difficult piece [5]. The install is a standard Docker Compose block — nothing more involved than any other app in the Arr stack.

Reverse proxy setup: The official docs at docs.ombi.app include reverse proxy configuration examples, which is important for HTTPS and clean subdomain access (e.g., requests.yourdomain.com) [README][2]. The Organizr SSO docs recommend using either a subdomain (ombi.domain.com) or a directory path (domain.com/ombi) depending on your proxy setup [2].

Known rough edges:

If you’re running Ombi behind Organizr with SSO, you need specific settings enabled in Ombi’s user management for the Plex user type sync to work correctly — the Organizr docs flag this explicitly [2].
The project’s GitHub shows active CI builds but the third-party review coverage is thin compared to newer tools, which may reflect that the active user base has partially shifted toward Overseerr for new installations.
Third-party review depth for Ombi specifically is lower than for comparable tools — most homelab guides treat it as part of a stack rather than something that warrants dedicated long-form coverage [5].

Realistic setup time: 30–45 minutes for someone who has already stood up a Plex server and deployed one or two other Docker containers. Under 2 hours even if Docker Compose is new to you and you’re following a guide.

Pros and Cons

Pros

Broadest media server support. Plex, Emby, and Jellyfin all natively supported — one of the few tools in this category that doesn’t force you to choose [README][1].
Native mobile apps. Real iOS and Android apps, not just a PWA or responsive web page. Matters for household adoption [README].
Handles the full request lifecycle. Checks if content already exists, flags if it’s being monitored, forwards to download automation, notifies on availability [README].
Organizr SSO integration. First-class documented support for single sign-on via Organizr, useful for unified homelab dashboards [2].
Works on every platform. Windows, macOS, Linux, Docker — not just Linux-first like some tools [README][website].
Managed hosting option. ElfHosted offers hosted Ombi for users who want the capability without the server management [1].
GPL-2.0 licensed. Source is open, you can audit it, fork it, and modify it for personal use [README].
Grandma-friendly is literally how the README describes it — the request flow is designed for non-technical household members, not homelabbers [README].

Cons

Overseerr has surpassed it for Plex users. If your server is Plex and you’re starting fresh, the current community consensus leans Overseerr for its cleaner UI and more active development pace [5].
GPL-2.0 is more restrictive than MIT. You can’t embed Ombi in a commercial product or redistribute it as part of a paid service without complying with the full GPL terms. For personal homelabbing this doesn’t matter. For building a product on top of it, it’s a constraint [README].
No cloud/SaaS tier. Entirely self-hosted — there’s no “just click and go” option without setting up your own server or using a third-party managed host like ElfHosted [1].
Thin third-party review coverage. Searching for in-depth independent reviews of Ombi specifically turns up mostly passing mentions in broader media server setup guides, not dedicated evaluations. Draw your own conclusions about the current activity level [5].
Category leader status is contested. For a long time Ombi was the default. That default has shifted in parts of the community, particularly for Plex-first setups.
Dependent on your existing stack. Ombi alone does nothing — you need Plex/Emby/Jellyfin plus ideally Sonarr/Radarr. It’s infrastructure middleware, not a standalone product [README].

Who should use this / who shouldn’t

Use Ombi if:

You run a media server for family or friends and want to stop being the person everyone texts to ask for new content.
Your media server is Emby or Jellyfin (where Ombi’s multi-platform support is a genuine differentiator).
You already have Ombi deployed and it’s working — there’s no burning reason to migrate to Overseerr unless you need specific features it lacks.
You want native iOS and Android apps for your household’s request workflow.
You’re comfortable with Docker or willing to follow a guide.

Skip it (pick Overseerr instead) if:

You’re running a Plex-only setup and starting fresh — Overseerr is the current community default for Plex, has a more modern UI, and is under faster active development [5].
You prioritize a polished, contemporary interface over broad media server compatibility.

Skip it (pick Jellyseerr instead) if:

You’re exclusively Jellyfin-based — Jellyseerr is a fork of Overseerr specifically rebuilt for Jellyfin and is the typical recommendation for Jellyfin-first setups.

Skip it entirely if:

You’re the only user of your media server. The request workflow adds zero value if you’re requesting content for yourself — just use Sonarr and Radarr directly.
You don’t already have or plan to build a self-hosted media server. Ombi requires one.

Alternatives worth considering

Overseerr — The current default recommendation for Plex setups. Cleaner, more modern UI, more active development. Plex-focused historically, now with basic Jellyfin support. The obvious comparison point for most users [5].
Jellyseerr — Fork of Overseerr rebuilt specifically for Jellyfin. If your stack is Jellyfin-only, this is the most common recommendation.
Petio — A request manager in the same category; the Organizr docs reference it as an SSO option alongside Ombi and Overseerr [2]. Less widely used and appears to have lower activity than either Ombi or Overseerr.
Requestrr — Discord-bot-based request handling. Interesting if your household already lives in Discord and you want requests to flow through there rather than a web portal.
Manual workflow — If you have fewer than three or four users and they’re technically capable, just giving them read access to Radarr/Sonarr is an option. Ombi adds value at scale, not necessarily for a two-person setup.

Bottom line

Ombi built the category. It was the first media request tool most homelab media server operators deployed, and it solved a real problem — the endless stream of text messages from family members who want content added to your Plex server. It still does that job. GPL-2.0, free to self-host, native mobile apps, and compatibility with Plex, Emby, and Jellyfin in one package are genuine strengths.

The honest caveat is that the landscape has shifted. Overseerr and Jellyseerr have taken significant mindshare, particularly for Plex-focused setups. If you’re building a new media server stack today, benchmark both Ombi and Overseerr before committing — the decision mostly comes down to which media server you’re running and which UI you prefer after 15 minutes of poking at a demo. If you’re already running Ombi and it works, there’s no urgent reason to migrate.

Sources

ElfHosted Documentation — Hosted Ombi: Media Request & Discovery Platform (ElfHosted). https://docs.elfhosted.com/app/ombi/
Organizr Documentation — Ombi SSO (Organizr). https://docs.organizr.app/features/sso/ombi-sso
Organizr Documentation — Overseerr SSO (Organizr — referenced for alternative comparison). https://docs.organizr.app/features/sso/overseerr-sso
Track Awesome List — Awesome Piracy updates Apr 2020 (TrackAwesomeList). https://www.trackawesomelist.com/2020/15/
Anand — UDMS Part 14: Kickass Docker Media Server with 150+ Apps (SimpleHomelab). https://www.simplehomelab.com/udms-14-docker-media-server/

Primary sources:

GitHub repository and README: https://github.com/ombi-app/ombi (4,066 stars, GPL-2.0 license)
Official website: https://ombi.io
Official documentation: https://docs.ombi.app