Eight Months Looking for Someone to Take Over
Pavel Djundik started SteamDB in 2013 as a side project that tracked prices, player counts, and update history across Valve's Steam platform. By this year it had grown into something gaming journalists cited as a statistical source, Steam Deck buyers checked for compatibility notes, and third-party tools quietly built on top of, all while Djundik ran it alone. In January 2026 he began quietly looking for a buyer, not to cash out, but because the job had outgrown what one person could sustain: hosting costs, API rate limits, abuse mitigation, and feature requests kept scaling with traffic, while his available time did not.
In September 2026 he sold SteamDB to Chosen, the company behind Nexus Mods, founded by its CEO Victor Folmann. Djundik described the search as looking for a team that understands what it means to be responsible for something a community depends on, and framed the deal around sustainability rather than an exit. No price was disclosed.
Nobody Signed Anything, Everybody Depended on It
What makes this worth more than a gaming-news footnote is what SteamDB actually was in practice: unpaid, informal infrastructure that a large number of unrelated parties had quietly built workflows around. Nexus Mods itself described the situation as millions of gamers, developers, and publishers relying on a service with no service-level agreement, no succession plan, and no board overseeing what happened if its one maintainer stepped away. There was no contract because there was no vendor, just a person with a website and a growing sense of obligation to everyone using it.
That arrangement is not unusual. It is the default condition of a huge amount of infrastructure the tech industry treats as simply existing: a single maintainer's open-source library, a free API a startup's core product quietly calls thousands of times a day, a community-run database that outlives every other part of a company's original stack. The 2021 left-pad and 2024 xz-utils incidents made the same point about code; SteamDB makes it about a live, publicly used data service.
The Decision Nobody Made Until It Was Forced
Djundik made the responsible choice available to him: spend eight months looking for a steward before burnout forced a worse outcome, a site that degraded, went dark, or sold to whoever paid the most regardless of what they intended to do with it. But the harder decision, the one that never got made, belonged to everyone who built a workflow on top of SteamDB without asking what would happen if he quietly stopped. Nexus Mods now controls data that gaming journalism and third-party tools treat as a reference source, and its own statement that SteamDB needs to make money is a signal, not a threat, that the terms of that dependency can change.
Nexus Mods deserves credit for handling the handover well: no forced account linking, no ads for now, and a public commitment to keep existing free features intact. That is the best-case version of this transition. The uncomfortable question it leaves for any business is not about SteamDB specifically. It is whether the same audit ever happened internally: which free tool, which single-maintainer library, which unofficial API does your own workflow depend on, and what is the actual plan for the day its maintainer burns out.
What to Actually Check This Week
Run a real dependency audit on anything customer-facing or revenue-generating: list every external service or library your stack calls that is maintained by a single person or a team of one to three, with no commercial support contract behind it. For each one, write down what breaks if it disappears with zero notice, and whether a comparable alternative exists that your team could switch to inside a week. If the honest answer for even one entry is that nothing would work and there is no plan, that is not a gaming-industry problem. It is the same unpriced risk that just changed hands at SteamDB, sitting quietly inside a business that has not yet had its own January 2026 moment.
Read next: xPaw Sold SteamDB. Your Dependency Risk Didn't. | GitLab's Critical Flaw Spared SaaS, Hit Self-Hosted
