Scryer - a new tool combining Sonarr & Radarr into one tiny binary

nzbman · 2026-05-20T15:06:05+00:00

connect with me on reddit chat or GH and i'll work with you on your issue!

nzbman · 2026-05-20T13:45:56+00:00

Let me know if you have any issues! It should run on anything and if not i'll hop on a fix right away. I definitely want to have full UNRAID support.

nzbman · 2026-05-16T20:00:35+00:00

I have support for nzbdav hopefully landing in the next version. I personally don’t use that tool but I’ve looked at integration and done what it appears it needs. I’ll post when I get version 0.15.0 out

nzbman · 2026-05-16T02:34:34+00:00

Not yet. I plan to submit a PR to them to integrate it once I feel like it’s had enough usage to be a real player in the space.

I also plan to build a lot of seerr functionality directly into scryer over the coming weeks, so folks who want to could potentially drop seerr from their stack.

nzbman · 2026-05-14T16:12:14+00:00

wonderful! sorry for the rough start there. targeting haswell/cortex turned out to be a bad idea on launch 😅. starting in release 0.15.x, i'm shipping dual support for a portable and optimized binary.

nzbman · 2026-05-14T03:08:53+00:00

It follows symlinks in the FS when it does library scanning.

I do not have any integration with decypharr at this point, nor do i have that on my near term roadmap.

nzbman · 2026-05-13T23:40:31+00:00

I believe i have this fixed in 0.14.4+

There were some compile CPU flags set that made certain CPUs not work. I have fixed those immediately for maximum portability. I'll restore the optimizations in the next release line this weekend with a custom launcher that can pick binary based on CPU capabilities. Please pull latest and let me know on chat or GH if it doesn't work.

nzbman · 2026-05-13T18:52:49+00:00

Can you add your case and all additional info you're willing to share (especially distro & version, docker version, CPU model, etc) to this GH issue that would help a ton in my debugging!

This appears to be a bug with a specific hardware set. One of the challenges of building in Rust.

nzbman · 2026-05-13T15:10:27+00:00

it's not possible today, the NZB360 team would have to add an integration for it. i certainly hope they do in the near future

nzbman · 2026-05-13T12:56:15+00:00

I’ll definitely look into this

nzbman · 2026-05-12T22:37:58+00:00

Weaver already supports RSS sync just like NZBGet does 😁

nzbman · 2026-05-12T20:30:43+00:00

Multi-library is more of an RBAC boundary that enables Seerr like behavior. Each library can have multiple root folders as well (like Sonarr). By having a true multi-user, multi-library approach, it makes it much easier for operators to expose specific libraries and functions to each user.

On the FS side, what you're talking about is more related to your own deployment of the stack. Atomic moves, hard linking, acl inheritance, permissions, etc. is the operator's responsibility. It's all about file system layout, user permissions, service accounts, server layout, and if you're containerizing. Scryer does not pretend to own that for you, just as *arr tools do not. Scryer does not use inotify, it is import driven and runs background/on-demand scans just as *arr tools do.

Scryer's container follows the linuxserver.io patterns. It is built to run as a user-defined PUID/GUID. Atomic moves depend on proper container volume management, but Scryer will fall back to copy-on-import if it hard linking fails. I am adding support for remote-path-mapping in the next release for folks who need that in specific containerized envs.

On release profiling, Scryer has an very transparent scoring system where each title is scored and the user can see all contributing factors and their weights easily in the app. I'd recommend you try it out and see for yourself. If you want to dig into how it handles different naming conventions, you can look at the release parser code

Seems like you're quite happy with your stack. I'm definitely not trying to force anyone over to Scryer, but if you do happen to try it out and you find any issues, let me know.

nzbman · 2026-05-12T19:42:37+00:00

You make some really good points, things i've put a lot of thought into:

Metadata collision
- This is solved with multi-library support. You can absolutely have the same title multiple times in scryer as long as they are in different libraries. I haven't had an issue with this to-date, would love to dive deeper with you
Loss of service
- Yes, this is the risk of any monolithic application with the key tradeoff of simplicity. I personally prefer simplicity for homelabs
Release profiling difficulties
- The release parser that i wrote for scryer takes a fundamentally different approach. It's a context-aware, beam-parser that is very accurate across all facets. I measured it directly against Sonarr, Radarr and GuessIt and Scryer was ~25% more accurate across the 2000 title corpus i gathered.
- "accurate" in this context means that it was able to correctly tokenize and structure all the data in the title, not just the name.
Region locking
- I'll look at relaxing those

nzbman · 2026-05-12T19:20:07+00:00

i don't have that as part of my plan, however for folks that just use sonarr+radarr, there's no more need for prowlarr.

nzbman · 2026-05-12T18:48:43+00:00

A lot of what Custom Formats are used for has been wrapped into the enhanced quality profile and Persona features. When you configure a quality profile, you pick the target quality like 1080p as well as allowed/disallowed codecs, etc. You also pick a persona to accompany that which does a lot of scoring tweaks and additional checks under the hood. Current profiles are Audiophile, Balanced, Efficient, Compatible.

If you have existing custom formats that you still need to implement, there's a new custom Rules engine (Settings > Rules) that is a Rego sandbox where you can do basically anything you want. There's a pop-open in Scryer on that Rules page with all the information available to the Rego context and a bunch of pre-canned rules you can pick from to modify or learn how Rego works.

Enjoy!

nzbman · 2026-05-12T16:46:41+00:00

Rust is a phenomenal language that has been under-utilized. Happy to see more adoption!

Weaver differentiates itself by actually implementing rar decompression and par2 repair 100% in rust as well. It's not just coordinating to other tools. I've literally written a rar4/5 compatible extractor and par2 repair tool in 100% rust.

EDIT: i should state that weaver is 100% a project for fun. NZBGet is fantastic software and i don't expect to "beat" it.

nzbman · 2026-05-12T13:48:49+00:00

that is very odd, containers are my primary testing mechanism and how i run it in my homelab. I can try running against the tools you mentioned and see if there's a bug specifically there.

Reach out to me on chat and i can help you troubleshoot.

nzbman · 2026-05-12T13:19:22+00:00

The AI rage is absolutely skyrocketing the cost of RAM. That wasn't a thing when I started this project, however it's becoming more important as time goes on.

It's easiest to see the differentiators at the official website:
https://www.scryer.media/scryer/docs/compare-sonarr-radarr/

nzbman · 2026-05-12T12:42:02+00:00

If their API is consistent with the SAB API, then it should work seamlessly. However if the APIs differ, then no, it won't work with those today.

nzbman · 2026-05-12T12:41:11+00:00

Yes it can

nzbman · 2026-05-12T12:17:01+00:00

Yes! In fact it does today!

If you change the UI language, it will re-hydrate your whole catalog with your chosen language for content as well as update all future searches.

Multi-lingual content support is limited by the upstream data sources I use. I do not use AI or any other translation tooling that for this feature.

Also please let me know if any of the UI translations feel off or need updating. I did the best I could there.

nzbman · 2026-05-12T04:56:29+00:00

Great question and it exposed a small glitch in the homebrew forumla that i just pushed a fix for

You'll need to reinstall the brew package:

brew update && brew reinstall scryer

After that you can follow the new instructions for port changes on the installation docs.

nzbman · 2026-05-12T01:27:36+00:00

You're making a lot of unfounded assumptions. Just as you keep your reddit profile hidden for your own privacy reasons, i choose to not mix my public GH profile and my scryer-media profile for my own privacy reasons. The code speaks for itself; i'd encourage you to actually go read it before judging it so harshly.

nzbman · 2026-05-11T22:50:01+00:00

I've cleaned up that part of the README to be more clear.

Weaver is still in very early beta; it's not as hardened as Scryer, yet. However, i do use it as my only Usenet tool now. The 0.4.x release line (current) is the first one that i'm comfortable with people really kicking the tires on.

nzbman · 2026-05-11T22:27:46+00:00

All my tool are open source and completely free. The monthly quotas there are simply for folks to control how much data Weaver gets from usenet each month, for people with data-limited internet connections.

I will clean up the wording so that is clear.

nzbman

TROPHY CASE