Every Steam owner’s library looks the same after a few years. Hundreds of titles, a handful of completed ones, and a long list of “I will play it later” purchases that keep accumulating in the background. The platform default does not help. The built-in categories are too coarse to organize anything serious, and the recommendation engine is biased toward games you have already started, which is the opposite of what a real backlog manager should do.
Most people try a spreadsheet. The spreadsheet rots. They try a Notion board. The Notion board rots. They try an emulator launcher that does not actually track anything. Eventually they either give up or they find a self-hosted tool that does the bookkeeping for them in the background.
Questarr is one of the cleaner answers to this in 2026. It is part of the same family of tools as Sonarr and Radarr, but for games instead of movies or TV. It pulls metadata from public sources, tracks your play status, supports indexer-based discovery of missing games, and runs entirely on hardware you own. According to the source guide I followed, it tucks neatly into the same Portainer workflow you would use for the rest of the *Arr stack, and that has been my own experience setting it up on a Synology NAS.
If you already run the *Arr stack for movies and TV, the install pattern is going to feel familiar. If you do not, this is a fine place to start, and the value compounds the longer you keep your library sorted.
What “self-hosted” actually buys you here
Honest first disclosure: this is not a privacy tool. Questarr does not hide your library from anyone. What it does is keep your data in a folder you control, on hardware you own, without a subscription that could change next year. That sounds small. It is not.
The practical consequence is that the data outlives the tool. If the maintainer burns out, if IGDB changes their API tier, if Twitch tightens the developer registration flow, the database file on your NAS still has every entry you ever entered. The contract of the tool is small enough that you can fork it, port it, or just keep reading the file from a different tool. That is the actual win of self-hosting this kind of tool, and it is the reason you do it on a NAS instead of paying a subscription for something that could disappear.
Self-hosting also buys you composition. A NAS sitting in your closet already runs Plex, request management, downloads, and probably a half-dozen other containers. Adding a game manager to that mix is one more stack with the same deploy pattern. The mental tax of running it is small, and the value compounds because the rest of your library is already in the same place. According to the source guide I followed, this is the killer feature for people who already run the *Arr stack, and my own experience matches.
Why this is a hard problem to solve well
Game libraries are messier than movie libraries. Movies have a single canonical source (the TMDB/Plex kind of contract), they have a single credit list, and they have one runtime. Games have multiple platforms, multiple editions, regional pricing, DLC that may or may not be included, and a Steam-owned status that does not always line up with reality. The metadata providers have to make peace with all of that, and the indexing layer has to handle the fact that not every game is on every storefront.
Questarr’s approach is to lean on IGDB for the metadata and Steam for the ownership record. That works for most people, but it means the tool inherits the limits of both. IGDB is the better metadata source for indie and niche titles, but it can be slow on day-one releases. Steam sync is reliable for owned games, but it does not see games you own on other storefronts. These are not bugs. They are the price of having a small team build a tool that does not require a paid API tier.
The other hard problem is expectations. People who install a game manager want it to do everything Steam does, plus a thousand things Steam does not. The realistic version of Questarr is narrower. It tracks status, it pulls metadata, it runs on your hardware, and it does not require a subscription. If you want playtime tracking, achievements, and rich social features, you will be disappointed. If you want a quiet, local, well-built tool that helps you decide what to play next, you will be happy.
What the value actually feels like in practice
The first thing I noticed once Questarr was wired up was that the platform default Steam UI stopped being where I went to find something to play. The dashboard has a finished count, a backlog count, and a small group of “now playing” entries. That sounds small, but it changes the loop. Instead of opening Steam and scrolling recommendations, I open Questarr, pick something from the priority list, and play it.
Metadata quality is the second thing. IGDB is the source most modern trackers use, and the box art and critic scores are good enough that the library actually looks like a library. Closing the loop with Steam sync unlocks the third thing, which is that the tool knows what you already own without you telling it.
The fourth thing is more subtle. The fact that the whole thing lives on the NAS means I can keep scraping data even if the upstream landscape shifts. Data in a folder I control, and a contract small enough that I can fork the tool if I have to. That is the actual win of self-hosting this kind of tool, and it is the reason you do it on hardware you own instead of paying a subscription for something that could disappear.
When this is not the right tool to install
Questarr is new. The community is small. The mobile experience is basically non-existent. The documentation is sparse, and the Discord is helpful but does not replace a real docs site. If you want polish on day one, this is not the tool. If you want a self-hosted game manager that respects your privacy and runs on a NAS you already own, this is the cleanest option I have seen in 2026.
The audience for the tool is narrower than the headline suggests. According to the source guide I followed, the people who get the most out of it are the ones who already run the *Arr stack and have a Steam library of more than a hundred games they have not finished. If you have a curated collection of twenty games you actually play, the spreadsheet you already have is probably fine. If you have a sprawling library and you want a private, local, structured way to decide what to play next, the install is worth the afternoon.
Trade-offs
Questarr is for people who have already decided that their game library is worth more than a spreadsheet and a prayer, and who are willing to maintain a small piece of self-hosted infrastructure in exchange for control. The maintenance burden is real but small. The container updates itself when you redeploy the stack. The data lives in a folder you control. The mobile experience is workable but not delightful.
A few things I would tell past me before installing:
- Be honest about whether you want a polished tool or a self-hosted tool, because this is the second one
- If you already run the *Arr stack, this is the natural next step, and the install pattern is the same
- If you do not, treat this as an entry point into the *Arr pattern, and expect a small learning curve
- Plan to spend twenty minutes on the metadata setup, and the rest of the tool clicks together
You do not need every game tracked. You need a system that surfaces what to play next without dragging you sideways into a stranger’s meta. That is what Questarr does well, and that is why it is worth the install if you already have the NAS sitting in the closet.