The game
A playable build every two weeks.
- The project in your repository
- Performance measured on target devices
- Automated builds
We build games and the software around them: gameplay in Unity and Unreal Engine, multiplayer servers, accounts, payments, and the content tools a team uses to keep a game alive after launch.
Players see the gameplay, the art and the sound. They don’t see the accounts, matchmaking, servers, payments, analytics and the admin panel the team uses to ship new content every week, until one of them breaks. On launch day it is rarely the game itself that falls over. Usually it is what stands behind it.
We build both sides. Gameplay and prototypes in Unity and Unreal Engine, and the server side and tooling that survive thousands of concurrent players and keep a game alive after launch. We can build a game from start to finish, or join your studio and own a defined part of it.
From the game itself to keeping it running. Take the whole cycle, or the parts your team is missing.
Gameplay, physics, AI opponents, user interface and performance optimisation, so the game runs smoothly on an average device too.
A playable prototype in a couple of weeks, to test the core mechanic before money goes on art and content.
Matchmaking, real-time multiplayer servers, leaderboards, friends and chat, with scaling that survives launch-day load.
Player accounts across platforms, in-app purchases and subscriptions, and analytics that shows where players drop off and what brings them back.
Tools the team uses to run events, offers, balance and player support without shipping a new build to the stores.
Bringing an existing game to a new platform, or joining your team for a defined part of the work, in your repository and your workflow.
The game goes where your players are.
Windows, macOS and Linux, Steam and other stores, keyboard, mouse and controller support.
iOS and Android, touch controls, battery use and performance across devices, and in-app purchases.
Browser games on WebGL with nothing to install, for marketing, learning or a quick test.
Ports to console with the platforms’ certification requirements, and augmented and virtual reality for Meta Quest and mobile.
A game team and a server team working to one plan.
Gameplay, physics and opponents in Unity or Unreal.
Connects the art to the engine and keeps performance right on target devices.
Multiplayer, accounts, payments and leaderboards.
Admin panels and LiveOps tooling for the team.
Playtesting, performance across devices and load tests.
The plan, the priorities and a playable build every two weeks.
Six stages that let you decide at each step whether to continue, change course or stop.
The game’s idea, audience, platforms and engine. A technical plan and an estimate.
The core mechanic, playable with placeholder art. Is it fun?
Content, levels, art and the server side, with a playable build every two weeks.
Bugs, performance across devices, load tests on the servers and a closed beta with real players.
Store reviews, platform certification and a team on call on launch day.
Events, new content, balance and analytics that keep players coming back.
Game engines for the game, and the same mature backend technologies we use across all our projects.
A game that is playable, publishable and manageable after launch.
A playable build every two weeks.
Services that hold up under real load.
The admin panel the team runs the game from.
The game in the stores and on the platforms.
For a new game we start with a prototype, because it is the cheapest way to find out whether the idea holds up. If it does, the prototype grows into production and the team grows with it.
In co-development we join your team: we work in your repository, your workflow and your tools, and own a defined part such as the server side, a port or the tooling. Your studio remains the owner of the game’s creative direction.
Either way there is a playable build every two weeks, and everything that gets made belongs to you.
Studios often have a strong game team and a weak server side. We have both.
A playable prototype shows more than any document and costs less than a failed production.
The servers are load-tested and monitoring is in place before the players arrive.
Code, assets, store accounts and servers are in your name.
Mainly Unity and Unreal Engine, and Godot for smaller and browser-based projects. The engine is chosen by platform, graphical ambition and the team’s skills. If you already have a project, we continue in its engine.
Yes. In co-development we work in your repository with your workflow and tools, owning a defined part: multiplayer, a port, tooling or the backend, for example. Your team stays the owner of the game’s creative direction.
Yes, and it is often a bigger job than the game itself. Player accounts, leaderboards, matchmaking, multiplayer servers, in-app purchases, analytics, and the admin panel the team uses to run content and events. We build it to survive launch-day load.
Yes, and we recommend it. A playable prototype in a couple of weeks shows whether the core mechanic is fun before money goes on art and content. If it is not fun, it is cheaper to find out straight away.
Running the game after launch: events, new content, balance changes, store offers and player support, without shipping a new build to the stores. It needs server-side configuration and tooling that has to be built into the game’s architecture from the start.
Describe your situation in a couple of sentences. We reply within a day.
Prefer to reach us directly?