Game development

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.

A game is software too

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.

What we do

Game development services

From the game itself to keeping it running. Take the whole cycle, or the parts your team is missing.

  1. 01

    Gameplay engineering

    Gameplay, physics, AI opponents, user interface and performance optimisation, so the game runs smoothly on an average device too.

  2. 02

    Prototyping

    A playable prototype in a couple of weeks, to test the core mechanic before money goes on art and content.

  3. 03

    Multiplayer and servers

    Matchmaking, real-time multiplayer servers, leaderboards, friends and chat, with scaling that survives launch-day load.

  4. 04

    Accounts, payments and analytics

    Player accounts across platforms, in-app purchases and subscriptions, and analytics that shows where players drop off and what brings them back.

  5. 05

    Back-office tools and LiveOps

    Tools the team uses to run events, offers, balance and player support without shipping a new build to the stores.

  6. 06

    Porting and co-development

    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.

Platforms

The game goes where your players are.

Team

Who works on your project

A game team and a server team working to one plan.

Process

How a game gets made

Six stages that let you decide at each step whether to continue, change course or stop.

01

Discovery

The game’s idea, audience, platforms and engine. A technical plan and an estimate.

Stack

Tech stack

Game engines for the game, and the same mature backend technologies we use across all our projects.

What you get

What you get

A game that is playable, publishable and manageable after launch.

The game

A playable build every two weeks.

  • The project in your repository
  • Performance measured on target devices
  • Automated builds

Server side

Services that hold up under real load.

  • Accounts, multiplayer and leaderboards
  • A load test before launch
  • Monitoring and alerting

Tools

The admin panel the team runs the game from.

  • Events, offers and balance
  • Player support and moderation
  • An analytics dashboard

Launch

The game in the stores and on the platforms.

  • Store and platform requirements met
  • Accounts and keys in your name
  • On call on launch day
Working together

How we work with a studio

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.

Why choose Techbaltics

  • Game and backend in one team

    Studios often have a strong game team and a weak server side. We have both.

  • A prototype before a promise

    A playable prototype shows more than any document and costs less than a failed production.

  • Ready for launch day

    The servers are load-tested and monitoring is in place before the players arrive.

  • All of it is yours

    Code, assets, store accounts and servers are in your name.

Frequently asked questions

Which game engines do you work with?

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.

Can you join our existing studio?

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.

Do you build the server side too?

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.

Do you prototype before full production?

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.

What does LiveOps mean?

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.

Related services

Let’s talk about it.

Describe your situation in a couple of sentences. We reply within a day.

  • We read your message and reply by email within a day.
  • We clarify the details by email. Would you rather talk? Say so and we will call.
  • A written proposal: scope, approach, timeline and price.

Prefer to reach us directly?

By sending this form you agree that we store your message in order to reply to it.

Send an enquiry