SteamDB, the unofficial database for Valve's PC game distribution platform Steam, has been acquired by Chosen, the parent company of Nexus Mods, the largest mod distribution platform. Both sides announced the deal on September 2, 2026. Co-founder Pavel Djundik, who has handled almost all development and maintenance since the site launched in 2013, cited burnout tied to the platform's rapid growth and a changing internet, and said he could no longer keep running it alone. Under the acquisition, SteamDB will keep its independent brand and remain free to use, while gaining development resources and infrastructure from Nexus Mods. One of the most important pieces of infrastructure in PC gaming, long reliant on volunteer effort and donations, has reached a turning point in its 13th year: the need for an organizational footing that can sustain it.
Thirteen years of solo operation and the limits of a changing internet
SteamDB was launched in 2013 by Pavel Djundik and Marlamin as a hobby project. Thanks to its precise tracking of concurrent player counts, price history, package contents and more, it grew into an essential tool not only for ordinary gamers but also for developers, publishers and the press. As the site gained influence, however, the workload soared. Marlamin eventually stepped back from day-to-day operations, and Djundik became the sole person holding the whole system together.
What strained operations most was the explosive growth of Steam itself. With well over 10,000 new games registered each year, frequent sales and a steady stream of new features, maintaining and monitoring the database had far outgrown what one person could handle in their spare time. On top of that, changes in the internet over recent years added to Djundik's mental burden. In his statement, he said that the pandemic and the rise of AI had eroded the atmosphere of the internet he once loved, and that his passion for the project faded with it. Faced with growing mental strain, he concluded in good conscience that he could not keep running it alone.
Djundik had looked for a successor a few years earlier but failed to find a team he could trust, so he carried on by himself. Yet he could neither let the site decline through neglect nor shut it down completely. In January 2026, he began searching for an organization to which he could entrust what he had built. The result was the transfer of the business to Chosen, the parent company of Nexus Mods.
Tackling "patch breakage" in modding through data integration
The acquisition means more than simply covering server costs. Nexus Mods had a clear technical motive for bringing SteamDB under its roof: resolving the biggest structural problem that PC game modding has long faced.
The thing that most often breaks a PC game's mod setup is an official update to the game itself. Many mods are built for a specific game version, so even a minor patch of a few dozen megabytes can cause prerequisite script extenders and related mods to stop working all at once. A game that ran fine the day before suddenly refusing to launch is a routine source of friction for mod users.
Solving this requires historical file-composition data from Steam's distribution system. On Steam, a game's executables and assets are stored in units called "depots," and each build's file composition and hash values are recorded in a "manifest." Once an official update is delivered, access to old manifests and depots becomes extremely difficult. Nexus Mods had tried to collect Steam game data on its own, but tracking down previous-version data right after an update was hard.
SteamDB, by contrast, holds a vast back catalog covering 13 years of file-update history, including builds, manifests and depots. Nexus Mods has said it plans to link this database with its mod manager Vortex and its web platform. Through this technical integration, it aims to deliver features such as the following:
- Accurate detection of the game version installed on a user's PC
- Advance verification of whether a mod a user is about to install is compatible with the current game build
- Early warnings about the risk of mod breakage when a game update is released
- Support for "version pinning," letting users stay on a stable earlier version and keep playing
- Integrity checks against clean game files using data SteamDB has already collected
Furthermore, in Nexus Mods' "Collections" feature (shared lists that bundle multiple mods and their installation settings), recommended game build numbers could be linked precisely as metadata. Users would no longer need to hunt for this information manually in forum posts or description text. SteamDB's data assets stand to drive progress in automating and stabilizing the mod environment.
Monetization boundaries and community wariness
With the change in operating structure, what users are watching most closely is the commercialization of the service and any changes to its terms of use. SteamDB, which had been sustained by donations and Steam keys contributed by volunteers, now faces unavoidable cost increases as it becomes an organization.
In its official FAQ, Nexus Mods frankly acknowledged that "SteamDB needs to generate revenue." Staffing a full-time engineering team and providing infrastructure and security that can withstand growing traffic over the long term requires a corresponding flow of funds.
Nexus Mods and Chosen, however, have explicitly ruled out commercialization that would undermine the site's integrity. The promises made to the community boil down to the following four points:
- No display ads or programmatic ads will be introduced on the site
- Existing features and data currently available for free will not be placed behind a paywall
- Users will not be forced to create a Nexus Mods account or log in to view data
- Users' personal data will not be sold to third parties
The alternatives under consideration are low-intrusion revenue models such as partnerships with publishers and affiliate links when games are purchased through SteamDB. As for securing the Steam keys needed to analyze game files, Nexus Mods will move away from relying solely on volunteer donations and will directly fund purchases to widen coverage.
Even with these promises on the table, some in the community remain cautious. Chosen and Nexus Mods have a history of causing considerable friction with users and creators during past platform overhauls. Nexus Mods previously restricted "permanent file deletion by mod authors" in the name of maintaining the integrity of the Collections feature, drawing fierce backlash from some prominent mod creators. The forced migration from the long-beloved Nexus Mod Manager to Vortex, the redesign of the site, and discussions about introducing age verification in response to UK regulations have also stirred debate.
Among users, there is lingering concern that even if independence and free access are promised at first, lock-in and feature restrictions could creep in as operating costs grow. Because the project is changing its banner from a volunteer-run labor of goodwill to a business under a corporate parent, the community's trust will be proven not by words but by future operating practices.
The end of volunteer-dependent game infrastructure, and what to watch next
What this acquisition highlights is a structural strain in the vastly expanded PC gaming ecosystem. Now that Steam's distribution volume has reached tens of billions of dollars a year and tens of millions of people around the world access it simultaneously, entrusting the surrounding infrastructure that supports its analysis and convenience to one individual's volunteer spirit was untenable from the start.
As it happens, the buyer, Nexus Mods, has experienced exactly the same pain. Nexus Mods founder Robin Scott also closed the chapter on 23 years of running the site because of serious health concerns and excessive stress, selling the business to Chosen in June 2025. The "long devotion by passionate individuals" that supported early PC gaming culture is reaching its limits one after another, as platforms have grown enormous and the internet has become harsher.
The path SteamDB has chosen is a realistic outcome for avoiding the service's disappearance. Djundik will support a smooth transition over the next several months and will then be relieved of the heavy burden.
The next thing to check is how the stated promises take shape in practice. In the near term, the several-month transition period will test whether existing browser extensions and the principle of keeping the API non-proprietary are maintained. In the medium to long term, the benchmark will be at what stage SteamDB's build and manifest tracking is integrated into Nexus Mods' mod-management platform, and whether it reaches users as an effective patch-breakage countermeasure. Whether the most important record keeper in PC gaming can protect its transparency and neutrality while taking on corporate capital and discipline is the real question.