On paper, it sounds like the ultimate missing link for anyone trying to manage a self-hosted library without babysitting Docker containers all evening. It targeted the exact friction points I deal with in my setup.

But as I dug into the support threads, the reality looked a lot less polished than the README.

Where the Automation Breaks Down

The core issue right now is a massive headache involving incorrect mount locations inside Sonarr and Radarr. Instead of pointing cleanly to the intended network cache, the container keeps defaulting to a completely wrong nested directory.

When your automation tool cannot accurately talk to your media managers, the whole system collapses into a loop of failed paths and orphaned files. It is a massive net negative for anyone expecting a true set-it-and-forget-it deployment.

You end up spending more time fixing the automation than you would have spent just moving the files manually.

Burning Through the Daily Cap

Even if you manage to wrangle the directory paths into submission, the background behavior of this tool is wildly aggressive. Some users are reporting that the internal cache mode is so relentless it completely swallowed their entire four hundred gigabyte daily allotment in a single afternoon.

My son has some pretty high-bandwidth habits when he gets into a new PC game, but even his heaviest download days do not hold a candle to a misconfigured script eating your network caps alive.

Tech shouldn’t feel like a second full-time job just to keep it from hitting a wall.

The Risk of Stagnant Code

The biggest red flag isn’t even the current configuration bug, but the silence from the development side. The repository has taken on that distinct, eerie quiet that usually signals a project is fading into abandonment. In the self-hosted world, relying on beta software that lacks active maintenance is an absolute gamble because the next minor update to your primary media containers will likely break the integration entirely.

Dead code walking is a liability, not a solution.

Finding the Balance in the Setup

I love tinkering with local-first tools, but there is a fine line between optimization and outright chaos. For now, I am keeping this one out of my production environment and sticking to my existing workflow, even if it requires a few extra clicks. The promise of automated convenience is never worth the price of a broken network path and a drained data limit.

Sometimes the best upgrade you can make is deciding what not to install.