Multiplayer gaming lobby and real-time scoring for an online gaming startup

Games are one of the biggest audiences online. Newzoo's market research puts the number of players worldwide at well over three billion, and a growing share of them play against each other, not against the computer.

Competitive players are a demanding crowd. They notice a laggy menu, a login that fails, or a score that takes too long to show up, and they notice it right away. When the whole point of playing is to see where you stand, a leaderboard that's a few minutes behind isn't a small bug. It's a reason to leave.

So a gaming community lives or dies on the parts players don't think about until they break: the account, the payment, and the scoreboard.

Gnarcadia, based in Toronto, is building an online gaming community where players compete in a range of multiplayer games and keep one central score across all of them.

That idea puts a lot of weight on the platform in the middle. Players need one place to log in, manage their account, pay, and pick a game. Every game needs to report results back to a shared system. And every player needs to see their exact standing, as it changes, alongside the top scorers across the community.

The hard part is doing all of that at once. Scoring traffic arrives in bursts from many games and many players, payments have to be handled correctly every time, and the whole thing has to stay responsive while it grows. Parts of the system go further than what we describe here, and those stay under NDA.

We built what Gnarcadia called the lobby, the central system every player passes through.

Players sign in there, manage their accounts, and see the games available to them. Payments are part of that account management, through an integration with the AptPay payment gateway. Keeping payments inside the lobby means players never leave the platform to top up or settle, and Gnarcadia keeps one clear record of every account.

The lobby runs on Blazor WebAssembly, so it behaves like an app in the browser. Menus respond instantly, and the client and server share one .NET codebase, which cuts down on the gaps where bugs like to hide.

The piece with the least room for error was the central scoring API.

Every player event across every game flows into it, and scores update the moment the event lands. Each player always knows their exact result, and the list of top scorers is available in real time, not on the next refresh or at the end of the day.

We designed the API for high throughput from the start. A system like this gets its heaviest load at the most visible moments, like the end of a popular match, and that's exactly when players are watching the leaderboard most closely. Planning for those peaks up front costs far less than finding them in production.

We also set up the whole infrastructure on Azure, together with the full DevOps operations around it.

That means environments, deployment pipelines, and the operational setup that lets new versions ship safely and often. For a young company, this matters as much as the code. When releases are automated and repeatable, shipping a new feature stops being a risk to what's already working, and the team can move quickly without betting the platform on every deploy.

In 2024 we delivered the core of the Gnarcadia platform: the lobby players log in to, the payments behind their accounts, the real-time scoring every game reports to, and the Azure infrastructure it all runs on.

Built on .NET and Blazor, with deployment automated from day one, the platform gives Gnarcadia room to add games and players without rebuilding the middle. That's the job a central system like this has to do: stay invisible, stay fast, and keep every score exactly right.