THE INFRASTRUCTURE YOUR LAUNCH NUMBERS DON’T SHOW


By Raphael Stange, CEO of Nitrado - the multiplayer infrastructure group behind GameFabric, serving 6 million registered users and studio partners including Bohemia Interactive, Studio Wildcard, Kraken Express, Eleventh Hour Games, and Fenris Creations / CCP Games


I


remember when everyone said the future of multiplayer belonged to the major franchises.


In the early 2010s, it made sense.


Capital unlocked capability: massive marketing budgets and server contracts. Who could compete against the largest IPs in entertainment? But the story has changed. Since 2022, PC playtime outside the top 20 titles has grown 44%.


Playtime for the top 20? Flat. What was obvious a decade ago has been overruled by today’s


reality: multiplayer has flourished in the middle tier. Survival games, co-op sandboxes, extraction shooters. Built by teams of ten who found their audience on Discord and YouTube well before launch. Windrose is the latest proof. Kraken Express, a small studio, shipped


their pirate survival game into Early Access with no large publisher behind them. And yet, they sold 500,000 copies in 48 hours and peaked over 200,000 concurrent players. This is no longer an anomaly. Nitrado caught this tide early on. For us, that means meeting studios


where they’re at, starting conversations not as a provider, but a partner. Nitrado is the preferred dedicated server partner for Windrose and


is embedded in the in-game UI from day one. But I’ll be honest: it wasn’t an easy launch. Time pressure, scaling challenges, you name it. We were in the trenches with Kraken Express, working through it all in real time.


That’s the untold story of viral launches. The line between partner


and provider isn’t about a logo on a page; it’s about being present when 200,000 people show up at once, and your original assumptions go out the door. Every title defining this wave, from Valheim to Palworld, went through these same growing pains. The ones that held their communities had infrastructure relationships built for these moments. Because middle-tier success is uniquely unpredictable, studios that


plan for the median launch are going to keep getting caught by this scaling blind spot – the very moments that define a title’s future. Behind those moments? Private server renters. But there’s a second, more costly blind spot. Most live-service studios treat their official server infrastructure and


their community’s private servers as distinct problems with separate vendors, budgets, and disconnected conversations. I understand why. They feel like separate domains. They’re not. Private server renters are not average users. They run communities,


mod, create tutorials, and host Discords. Their marketing contributions are for free. They stay for years and bring their friends. The retention metrics speak for themselves: this is the most valuable segment of a player base. Yet, most studios have no direct relationship with them at all. Studios that understand this, like Studio Wildcard and Bohemia


Interactive, use a unified model. GameFabric delivers their studio- grade, official infrastructure, while Nitrado and Apex Hosting handle the community side. Same partner, both ends. The result goes beyond cost efficiency: a direct line into the


communities that keep a game alive. Community retention is as vital as acquisition. The math on re-


engaging a lapsed player versus keeping an invested one is not close. Pursuing both through the same infrastructure relationship is an untapped wellspring bubbling in plain sight. The games that win this next cycle won’t just have the best content


pipeline. Their infrastructure strategy will be built around where multiplayer actually lives: in the long tail, the community, and the spaces between updates where the players who matter most are deciding whether to stay.


July/August 2026 MCV/DEVELOP | 41


Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36  |  Page 37  |  Page 38  |  Page 39  |  Page 40  |  Page 41  |  Page 42  |  Page 43  |  Page 44  |  Page 45  |  Page 46  |  Page 47  |  Page 48  |  Page 49  |  Page 50  |  Page 51  |  Page 52  |  Page 53  |  Page 54  |  Page 55  |  Page 56