Backend Tech: Build or Buy? The Industry Weighs In

Why the Build vs. Buy Debate Matters More Than Ever

Last month, we unveiled the findings of our 'Build Vs. Buy' Report; a landmark survey of 125 senior executives and tech leads at major mobile game studios.

The findings revealed some eye-watering figures, with the cost of each studio's decision to build and maintain their own backend tech coming to a startling $21,662,784.

As well as putting a firm number on this decision for the first time, the idea behind the report was to stimulate discussion among industry leaders.

At Nordic Game 2024, some of those we spoke to were shocked at the size of the $21 million figure, while several told us they thought it was on the low side. One said their company had worked on its in-house backend tech for eight years (at considerably higher expense)!

We also received some "on the record" industry quotes from well-known mobile games industry leaders and Metaplay partners. In this blog, we'll delve into their thoughts and see what can be learned from their words of wisdom.

Why Scalability Should Drive Your Backend Decision

We can't argue against Chris Hong's perspective - it's why we included it on the first page of our report.

Scalability underpins everything we do at Metaplay. A game can become an overnight success, or steadily gain traction over a number of years to eventually reach the charts. Either way, the backend needs to be prepared for both options.

On a resource level, there's no rhyme or reason for a studio to be paying through the nose for a backend which massively over or under serves what they need. Backends should scale in line with success.

As Chris also mentions, there's more to making a game than developing and shipping it. Your backend needs to be prepared for long-term live-service and a steady flow of content to hundreds of thousands or millions of engaged users.

How Live Service Games Need Real-Time Player Understanding

Live service games lend themselves to collaboration between the developer and player.

Look at community chatter surrounding a multiplayer launch, and you'll see frequent discussions about the nerfs and buffs being added to a game. Gamers are keen to discover exploits, and developers must be quick to respond to them.

To achieve this, player behaviour and actions need to be understood on a 1:1 or high-level basis. Using Metaplay, developers can provide OTA (over-the-air) updates to adjust the player experience without resulting in server downtime, key for that all-important retention.

Why Game Studios Should Focus on Games, Not Infrastructure

Three quotes, three studios, one message: game-makers want to make great games, and players want to play them.

For the most part, gamers don't care about the backend technology of a title (and we take no offence to this!). Instead, it's the narrative they'll remember, the engaging gameplay loop that keeps them coming back for more, or that nail-biting multiplayer session with friends.

There is however an exception to this; tech suddenly becomes important to a player when it goes wrong. It's why your server infrastructure and backend need to be reliable and built on strong foundations.

Sure, you could start your backend from scratch but why do this when the tech already exists, and there are great games to be made?

The True Cost of Building Backend Tech In-House

Matt's perspective emphasises something which hasn't always been true in mobile gaming, but now certainly is: every penny counts.

Our research found that the average salary for a backend software engineer comes to $138,864, and, of course, more than one engineer is needed to form a backend team. On average, it takes three years to build a backend with an average of 52 developers needed to do this. Combined, this puts the cost of building internal backend tech at $21,662,784.

It's a staggering amount when backend solutions are readily available. As opposed to the three years it takes to build an internal backend, it takes a matter of weeks to fully integrate the Metaplay Unity SDK (which has been in development for four years). This means games can be developed and brought to market more quickly, with tech that scales as they do.

Why Developer Autonomy Matters for Backend Solutions

The Metaplay team has centuries (literally) of combined experience working in-house at mobile developers and publishers, so we know full well the importance of having autonomy over your project.

From the start, Metaplay has been designed to put developers in control, hosted in the developer's cloud and shipped as source code.

Why Support Quality Makes or Breaks a Backend Partnership

Gabriele's input is true for backend providers, and sage business advice in general.

In our case, we provide a range of support packages that best suit your team's needs. From a Discord community to 24/7 and 1:1 support, Metaplay can be available every step of the way.

The Industry Consensus on Build vs. Buy

Since unveiling the 'Build Vs. Buy' report at Nordic Game, we've enjoyed speaking to tech leads and engineers first-hand to understand their approach to backend tech. You can download the report here.

We're keen to hear your thoughts on the report too - drop us an email at info@metaplay.io.

Build vs. Buy Backend FAQ

How much does it cost to build a game backend in-house?

Our research of 125 senior executives and tech leads found the average cost of building and maintaining in-house backend tech is $21,662,784. This factors in an average of 52 developers working over three years, with backend engineer salaries averaging $138,864.

How long does it take to integrate a third-party game backend?

With solutions like Metaplay, full integration of the Unity SDK takes a matter of weeks rather than the three years typically required to build from scratch. This allows studios to get to market faster with proven, battle-tested technology.

What should I look for in a game backend provider?

Key factors include: scalability (can it grow with your game), programmability (can you customize it fully), source code access (do you maintain control), and support quality (is help available when you need it).

Can I switch from a built backend to a bought solution mid-project?

Yes, though it's easier to start with the right solution. Studios that have built in-house often face painful choices when scaling: rebuild from scratch or patch together temporary fixes. Starting with a scalable, programmable backend avoids this dilemma entirely.