There's a point in any industry when the pipes stop being just pipes. The systems built to carry content from one place to another start deciding which content gets carried, on what terms and in what order. At that point, infrastructure isn't only supporting the market. In practical terms, it is the market.
Online gaming reached that point some time ago. It's worth being honest about what that means for the people building games and the people offering them to players.
From connection to curation
Distribution infrastructure in online gaming started with a simple job: connect games to operators, so neither side had to build every connection by hand. That job was valuable, and it still is.
But a layer that sits between a large number of games and a large number of operators naturally gathers influence. It sets the onboarding requirements for new suppliers. Its commercial terms shape which studios can afford to join. Its lobby tools and default catalogues affect what operators see first. Its integration roadmap decides which features are practical to ship.
None of this requires bad intent. It's simply what happens when one layer becomes the route that almost everything has to take.
What it means for studios
For a studio, the practical effect is that getting a game in front of players often depends on satisfying the infrastructure first. Catalogue expectations, integration standards, commercial thresholds and onboarding queues all come before a single operator has had the chance to look at the game.
Established suppliers with large catalogues and long track records get through comfortably. Newer and smaller studios often don't. Their games aren't necessarily worse. The gate was simply designed around a different kind of supplier.
Studios respond rationally. Some sign with larger publishers to borrow their distribution. Some design games to fit what the route to market already rewards. Some stop at a single market because the next one is out of reach. Each is a sensible business choice, and each makes the industry a little less varied.
Over time that shapes the whole industry. When distribution is hard for new creators to get, fewer new creators try, and the range of games players see gets narrower.
What it means for operators
Operators feel the same pull from the other direction. Their catalogue is largely shaped by what's available through the connections they already have. Bringing in a studio outside those connections is a project, so most don't bother, even when that studio's games would suit their players well.
That leaves many operators competing with similar libraries and trying to stand out through bonuses and promotions rather than content. It's an expensive way to build a distinctive brand.
There's a quieter effect too. When an operator's content decisions are mostly made by what its connections offer, it loses some of the direct relationship with the creators behind its best games. Asking for an exclusive, a custom version or an early release gets harder when there's no direct line to the studio. The catalogue is wide, but it isn't really the operator's own.
Why it happens without anyone intending it
It's worth stressing that this story doesn't need a villain. Infrastructure providers set onboarding standards because they carry real risk: a badly built game or a non-compliant supplier can cause problems for every operator on the network. Commercial minimums exist because integrating and supporting a supplier costs money. Default catalogues exist because operators ask for them.
Every one of those choices is defensible. The combined effect is still a route to market that favours suppliers who are already large. That's the nature of infrastructure at scale. Its defaults quietly become the industry's defaults, which is exactly why the defaults deserve attention.
What neutral infrastructure should look like
None of this is an argument against aggregation or shared infrastructure. The industry needs both. It's an argument about what they should optimise for. We think infrastructure works best when it behaves more like a road than a gatekeeper, and a few principles follow from that.
- Access based on whether a game meets the technical and regulatory standard, not on the size of the studio behind it.
- Terms that work for small catalogues as well as large ones.
- Operators choosing what they carry, rather than inheriting a default library.
- The platform improving the route for everyone, instead of competing with the content that travels along it.
Principles like these are easy to write down and harder to hold on to as a business grows. That's precisely why they need to be deliberate choices rather than good intentions.
Supply creates demand
There's a commercial case here as well as a principled one. More creators produce more games. More games make a catalogue more interesting to operators. More operators mean more distribution for creators, which attracts more creators. Infrastructure that narrows the entrance weakens that loop. Infrastructure that widens it makes the loop stronger for everyone in it.
Where Raise fits
That loop is how we think about Raise. Raise Engine gives creators, from established studios to first-time teams, the infrastructure to build and launch games. Raise Portal gives operators streamlined access to that growing catalogue through a single integration layer. The platform's job is to keep the route open and make it shorter, not to decide in advance which games deserve to travel on it.
Infrastructure will always shape the industry around it. The real choice is whether it shapes it narrower or wider.
.gif)
