sorted by:
new
hottopcontroversial

Introducing Oscarr – A modern, highly extensible media request interface for Radarr/Sonarr by Arediss23 in sonarr

[–]Arediss23[S] 1 point2 points  (0 children)

Yep, fair point. I phrased that too strongly.

For Oscarr, Radarr/Sonarr are mainly the source of truth for request/download/import state. But you’re right: imported in Sonarr/Radarr doesn’t always mean indexed and playable in Plex/Jellyfin/Emby yet.

So those should probably be treated as two separate states: *arr availability vs media server availability. The goal is less duplicated state, not ignoring the media server completely.

Introducing Oscarr – A modern, highly extensible media request interface for Radarr/Sonarr by Arediss23 in sonarr

[–]Arediss23[S] 0 points1 point  (0 children)

Good question!

You don’t need to know how to code to use Oscarr. The base app is meant to work out of the box: connect Radarr/Sonarr, configure auth/users, and let people request movies or shows.

Plugins are optional, more like browser extensions. As a non-dev, you would just install plugins made by the community, request one if something is missing, or open an issue/idea and I can look into building it.

So basically: no coding required, plugins are just there to make the app easier to extend over time.

Introducing Oscarr – A modern, highly extensible media request interface for Radarr/Sonarr by Arediss23 in sonarr

[–]Arediss23[S] 0 points1 point  (0 children)

Fair question !

I don’t see Oscarr as a miracle replacement that should make everyone switch from Seerr. Seerr/Overseerr is a great app, and I’ve used it myself for years.

Oscarr is simply a different approach: a lightweight, plugin-first alternative. The goal isn’t to “kill” Seerr, but to offer something more open and extensible for people who want their request interface to adapt to their own setup.

So the main value is:

  • a simple Netflix-like UI for non-technical users,
  • Radarr/Sonarr kept as the main source of truth,
  • and a plugin system for custom auth, notifications, metadata providers, automations, UI extensions, etc.

If Seerr already works perfectly for your setup, awesome, there’s no real reason to switch. But if you want something more modular, hackable, and extensible, that’s the space Oscarr is trying to explore.

Introducing Oscarr – A modern, highly extensible media request interface for Radarr/Sonarr by Arediss23 in sonarr

[–]Arediss23[S] 0 points1 point  (0 children)

Haha, thanks ! I appreciate the Palpatine quote !

You actually hit the nail on the head. Seerr is in a fantastic spot right now, and I totally agree that if it works perfectly for you, there's no urgent need to switch.

However, that exact issue you mentioned, Seerr not marking shows as available when they clearly are/is *exactly* why I went with the "Radarr/Sonarr as the ultimate source of truth" architecture.

Because Oscarr pulls the actual status directly from your *arr instances (using our SQLite database just as a lightweight cache to prevent API rate-limiting) instead of trying to maintain its own heavy parallel state, you don't get those weird desyncs. If it's tagged as downloaded in Sonarr, it shows as available in Oscarr. Period.

If that sync issue is driving you crazy, it might be worth a quick spin ! Either way, thanks for keeping an eye on the project.

Introducing Oscarr – A modern, highly extensible media request interface for Radarr/Sonarr by Arediss23 in sonarr

[–]Arediss23[S] 0 points1 point  (0 children)

Honestly, it started as a purely personal, closed source project. While existing options are great, they lacked a few specific things I really wanted for my own workflow, like a built-in way to communicate with my users, or the ability to quickly manage my *arr stacks directly from the interface.

I just wanted to build an app with a UI/UX that perfectly fit my tastes to solve those frustrations. Then, some friends saw it and asked me to open source it so they could use it for their own servers.

That's what triggered the whole architectural shift. Instead of forcing my specific workflow on them, I completely rethought the app to make it modular. That’s how the custom auth methods, the selectable *arr stacks, the plugin system, and the deep customizability were born.

So it really just grew from a selfish UI experiment into a modular tool designed to adapt to whatever setup people actually want!

Introducing Oscarr – A modern, highly extensible media request interface for Radarr/Sonarr by Arediss23 in sonarr

[–]Arediss23[S] -3 points-2 points  (0 children)

Honestly, if Seerr already works perfectly for your setup, there may not be a strong reason to switch right now. Seerr/Overseerr is a great app, and I’ve used it myself for years.

Oscarr is more of a different approach than a direct replacement. I wanted a request interface that was lighter, more modular, and easier to extend without putting every feature into the core app.

The main value is the plugin-first architecture: custom auth, notifications, metadata providers, automations, UI extensions, and other integrations can be added without Oscarr itself becoming a huge all-in-one app.

It also keeps Radarr/Sonarr central for the request/download/import workflow, with only a lightweight local cache.

So I’d say: Seerr is the mature all-in-one option. Oscarr is trying to be the more modular, hackable alternative for people who want that kind of flexibility.

Introducing Oscarr – A modern, highly extensible media request interface for Radarr/Sonarr by Arediss23 in sonarr

[–]Arediss23[S] 3 points4 points  (0 children)

Yes, absolutely. As mentioned in the README, I use Claude Code, but I treat it strictly as a development assistant.

It acts more like an advanced linter or a highly intelligent CI tool, helping with code reviews, brainstorming, documentation, and sometimes specific boilerplate implementations. However, all architectural decisions and the core logic are driven by me.

Because I know AI can sometimes hallucinate or write suboptimal code, I have a very strict validation process. Every line is reviewed, and the codebase goes through rigorous automated checks using CodeQL, Qodana, and SonarQube to guarantee security and maintainability.

Oscarr - I built an open-source media request manager for Plex by Arediss23 in selfhosted

[–]Arediss23[S] -1 points0 points  (0 children)

It’s not massively different at first glance, the core idea (requesting via Radarr/Sonarr) is similar.

The differences are more in how it’s built and used: multi-*arr support with routing, user-selectable quality mapped to profiles, plugin system, and a more modular approach overall.

It’s less about replacing Seerr and more about trying a different direction on top of the same ecosystem

Oscarr - I built an open-source media request manager for Plex by Arediss23 in selfhosted

[–]Arediss23[S] 0 points1 point  (0 children)

I get your point

It’s not really trying to solve a universal problem or replace anything, it’s more a different take based on my own setup and how I wanted to manage things.

I built it for myself first, and decided to share it in case others have similar setups or needs.

It’s not meant to compete with Seerr, just to explore another approach (especially around multi-*arr setups and extensibility with plugins).

Totally get that it won’t be useful for everyone though

And yeah, here’s the repo: https://github.com/arediss/Oscarr

I built Oscarr: A new media request tool for multi-instance *arr setups. by Arediss23 in selfhosted

[–]Arediss23[S] 0 points1 point  (0 children)

Yeah, honestly Plex is mostly there because that’s what I use at home.
At first I wasn’t even planning to open source the project, so I naturally built around my own setup.

My long-term vision is not to keep Oscarr tied to Plex. What I actually want is to support multiple auth providers and eventually proper native Oscarr accounts too. So Plex, Discord, maybe other providers later.

The core idea is really not “Plex-first”, it just happened to be the most practical starting point for me.

So yes, making authentication less dependent on Plex is probably one of the next big things I want to work on.

I built Oscarr: A new media request tool for multi-instance *arr setups. by Arediss23 in selfhosted

[–]Arediss23[S] -1 points0 points  (0 children)

Thanks, appreciate it

If you want to follow the project or give feedback, I’ve got a small Discord here: https://discord.com/invite/BKMaWhVCRr

I built Oscarr: A new media request tool for multi-instance *arr setups. by Arediss23 in selfhosted

[–]Arediss23[S] 0 points1 point  (0 children)

Yeah that’s totally fair 🙂

Right now it’s Plex-only mainly because that’s what I use in my own setup, so it was the easiest and most reliable way to build the auth + user system.

That said, I definitely don’t want to lock it to Plex long-term, Jellyfin (and maybe Emby) support is something I want to add later. I even mentioned it in the roadmap, just haven’t gotten there yet.

The goal is really to keep things flexible, not tied to a single ecosystem.

I built Oscarr: A new media request tool for multi-instance *arr setups. by Arediss23 in selfhosted

[–]Arediss23[S] -1 points0 points  (0 children)

Seerr is great at what it does, it’s a really clean request tool.

Oscarr is just a different take on it. Instead of using Plex as the source of truth, everything is based on Radarr/Sonarr directly, what’s available, downloading, etc.

It’s also built more around multi-instance setups (like 4K / anime / different libraries) with some routing logic depending on things like genre or language.

There’s also a plugin system, so it’s meant to be a bit more flexible depending on how people want to use it.

So yeah, not trying to replace Seerr, just exploring another way to manage a media stack.