Nexus Mods has acquired SteamDB, giving one of PC gaming’s biggest modding platforms ownership of one of Steam’s most widely used tracking and analytics tools. Here’s why the deal happened, what changes for SteamDB, and what it could mean for gamers and mod creators.
Hey, I’m Wizzie. I’ve been gaming since I was five, with a love for MMOs and SciFi that’s only grown since. I run Niteforge as CEO and Editor-in-Chief. Let's talk! wizzie@niteforgestudios.com
Nexus Mods announced on September 2, 2026, that it has acquired SteamDB, bringing two major third party PC gaming platforms under the same ownership.
SteamDB has spent the past 13 years tracking Valve’s Steam ecosystem, while Nexus Mods has become one of the largest platforms for PC game modifications. Both services will continue operating independently, with SteamDB keeping its existing website, branding, and community channels.
The acquisition transfers SteamDB’s ownership and operational responsibility from founder Pavel Djundik to Nexus Mods. Djundik began looking for an acquiring partner in January 2026 after years of running the service largely by himself became increasingly difficult due to burnout and the growing workload.
Nexus Mods will provide SteamDB with infrastructure funding and dedicated engineering support. The arrangement gives the site additional resources while allowing it to continue operating under the SteamDB name and maintaining the service that its existing community knows.
SteamDB is an independent analytics database and tracking platform for Valve’s Steam ecosystem. Pavel Djundik, known online as xPaw, and Martin Benjamins, known as Marlamin, founded the project in 2013.
Djundik’s experience with Valve’s technology goes back to his work in the GoldSrc modding community, where he developed custom plugins for Counter Strike 1.6 community servers.
SteamDB tracks real time concurrent player numbers, historical player peaks, regional pricing, discount histories, backend depot manifests, package updates, and application changes across Steam.
Valve’s public API provides basic store information and user library data, but it does not offer the same level of detailed telemetry. SteamDB collects and organizes much of that additional information automatically, giving users access to historical data that can otherwise be difficult to find.
The site’s backend data has also occasionally led to DMCA notices from publishers. SteamDB does not host game downloads, sell product keys, facilitate piracy, or link to piracy websites. Its purpose is to document information from Steam, including catalog changes recorded through public Steam data and community donated product keys.
Nexus Mods is one of the largest independent platforms for distributing and hosting PC game modifications.
Robin Scott, known online as Dark0ne, founded the site in August 2001 under the name Morrowind Chronicles. It originally served as a dedicated community hub for Bethesda Softworks’ The Elder Scrolls III: Morrowind.
Scott later expanded the site into TESSource and founded TESNexus in 2007. The platform eventually became Nexus Mods as it expanded beyond Bethesda games and began supporting a much wider range of PC titles.
Over more than two decades, Nexus Mods grew to host hundreds of thousands of modifications across thousands of games. The platform now serves tens of millions of registered users and has distributed billions of file downloads. It has also developed its own mod management software, including Vortex.
Nexus Mods went through its own ownership change in June 2025, when Scott sold the company after nearly 24 years as its managing owner.
Scott said the mental strain and anxiety involved in running an enterprise scale community platform alone had contributed to chronic health issues and burnout. Ownership transferred to Chosen, an operating company led by CEO Victor Folmann, known online as Foledinho.
Folmann and his team committed to maintaining Nexus Mods’ open community policies, keeping file downloads accessible, and investing in backend infrastructure and mod management software.
Running SteamDB became increasingly demanding as Steam itself continued to grow.
Martin Benjamins stepped away from regular operations during the project’s early years, leaving Pavel Djundik to maintain and develop the service largely on his own. Over time, Steam generated significantly more data. Steam Direct also brought thousands of new games to the platform each year, increasing the number of depot updates, manifest revisions, and database changes that SteamDB had to track.
The workload eventually became difficult for one person to sustain.
In his September 2, 2026 announcement, Djundik described the physical and mental toll of maintaining the project:
“What started as a hobby project became something I could never have imagined. I always took pride in what kind of a helpful service I was able to create and sustain for all kinds of gamers and, in later years, developers and publishers. With its helpfulness came growth, but that doesn’t come for free. I have always considered SteamDB to be my hobby, but the amount of hours I have worked on it could be considered a full-time job. It was pure passion, and the ever increasing self inflicted workload has taken its toll.”
Djundik also said changes in internet culture contributed to his loss of motivation:
“After COVID and with the rise of AI, the internet we once loved is gone, and with it my passion. I have started experiencing burnout with the project, but I powered through. A few years ago I tried to find someone to continue the project, but I couldn’t find a team that I was confident in, so I decided to keep going by myself. Steam keeps growing, in terms of games, players, and the number of new features being added. It’s hard to keep on top of this alone, and the mental load has only kept increasing, and in good conscience I cannot continue like this.”
Djundik began looking for a company that could take responsibility for SteamDB’s future rather than allowing the service to decline or eventually shut down:
“Running a service like SteamDB is not easy. I wouldn’t be able to live with myself by either just letting the site run as-is and letting it wither, or completely shut it down. In January, I started looking for a worthy partner that could continue the legacy that I had built. This is where Nexus Mods comes in.”
Nexus Mods was ultimately selected because of its own history as a community driven gaming platform and its experience managing a large scale service.
Djundik explained his decision:
“Nexus Mods has been serving gaming communities for more than two decades and, like SteamDB, grew from a passion project into a service relied upon by tens of millions of people. What mattered most to me was finding a team that understands what it means to be responsible for something the community depends on, and that shares my belief in building useful tools for gamers. SteamDB will continue to be SteamDB. The goal is not to change what makes the project special, but to give it the resources, development capacity and long-term stability that I could no longer provide alone. I have full confidence the team will be able to continue improving the project for gamers, developers and publishers alike.”
Victor Folmann, CEO of Nexus Mods and founder of Chosen, described the acquisition as a long term commitment to maintaining SteamDB.
“I founded Chosen to become the kind of long-term owner I wish had existed when I sold my own company, someone who genuinely cares about what has been built, protects what makes it special, and listens to the community that made it possible. SteamDB is exactly the kind of project we want to be a home for. Pavel has spent 13 years building something remarkable that millions of gamers, developers and publishers have come to rely on. We don’t take the responsibility of becoming its next steward lightly.”
Folmann also emphasized the importance of maintaining the trust SteamDB has built with its users.
“Our job isn’t to change what makes SteamDB special. It’s to give it the resources, team and long-term stability it deserves, while building a sustainable foundation that allows us to keep investing in and improving it for many years to come. There will be things we want to improve and new things we want to build, but we’ll do that thoughtfully. SteamDB has earned the trust of its community over more than a decade, and our job is to earn the right to carry that trust forward.”
Nexus Mods also pointed to the similarities between the two platforms in its official announcement:
“Both started as passion projects built by people who wanted to make something useful for PC gamers. Both grew far beyond anything their original creators expected, and both eventually became services that millions of people rely on. SteamDB has also spent more than a decade building trust with its community by giving people useful, transparent information about the games they play. Something it does incredibly well. We think that’s worth protecting, and we’re not interested in changing SteamDB into something it isn’t.”
SteamDB’s data has potential uses beyond player statistics and Steam pricing.
PC modding often depends on specific versions of a game. A mod may work perfectly on one build and break completely after a developer releases an update.
Nexus Mods is a major part of this ecosystem. Players regularly use the platform to build mod lists containing dozens or even hundreds of files, with individual modifications often depending on particular game versions, other mods, script extenders, or supporting tools.
Steam updates can cause problems without much warning. When a developer changes executable files, memory addresses, or other underlying components, script extenders and other tools can stop working. Players may suddenly find that their saves no longer load or that a previously stable mod setup crashes.
Mod authors then have to deal with the fallout.
After an update, creators can receive large numbers of bug reports from players who do not realize their game has changed. Developers and mod authors often have to determine what changed, identify the affected game build, test their modifications against it, and communicate compatibility information to their users.
SteamDB’s historical depot data can help with that process.
Many players primarily know SteamDB for its player count tracking and Steam price history. The platform also maintains years of backend depot information, including internal build numbers, branch updates, and manifest changes processed by Steam.
That historical record gives mod developers a way to identify the exact software environment associated with a particular game version. For compatibility work, having that information available can make it much easier to determine what changed after an update.
Mod authors could benefit from more precise version information tied to their projects.
SteamDB’s depot data could allow mod hosting and management tools to identify the specific game build a modification was designed for. Players could then receive warnings when they are trying to install a mod on an incompatible version.
That would be particularly useful for large projects that require extensive testing after every major game update. A clearer connection between game builds and mod versions could reduce the amount of time creators spend diagnosing compatibility problems.
Players using large mod collections could also benefit.
Nexus Collections can contain hundreds of interconnected files. When a game update changes an important underlying component, the entire collection can stop working until the affected mods are updated.
Historical SteamDB build information could give players clearer compatibility requirements before they begin installing a collection. It could also help identify which game version a collection was originally built around.
Vortex and other mod management tools could eventually use the same information to provide real time warnings.
For example, a player with a heavily modded game could receive a warning when a Steam update is likely to cause compatibility problems. That would give the player the option to pause automatic updates while waiting for mod authors to release fixes.
SteamDB will continue operating as an independent tracking and information platform. It will not become a mod repository, and users will not need a Nexus Mods account to access SteamDB’s pricing histories, player statistics, or other existing features.
The acquisition gives SteamDB access to additional funding, infrastructure, and engineering support while preserving the site’s existing role within the Steam community.
For Nexus Mods, the acquisition also provides access to a large historical dataset that could support future improvements to mod compatibility and management tools. For SteamDB, it provides a larger team and the resources to keep maintaining a service that has become an important part of PC gaming.
The biggest immediate change is therefore behind the scenes. SteamDB remains SteamDB, but Pavel Djundik no longer has to carry the entire workload himself.
LATEST ARTICLES
SUGGESTED FOR YOU
