Turn-Based Game Server Options in 2026: An Honest Comparison for Indie Developers

Building multiplayer functionality for turn-based games has always been a challenge for indie developers. The core tension remains the same: how do you balance development speed against the need for authoritative control, cheat protection, and proper handling of hidden game state?

The Four Paths Forward

Based on the current landscape in 2026, indie developers essentially have four distinct approaches to choose from:

Custom Backend - Building everything from scratch using Node.js, Go, or similar technologies with a database and WebSockets. This gives you complete control but requires significant engineering effort and ongoing maintenance.

Per-Match Servers - Spawning dedicated headless game instances for each match using engines like Unity Netcode, Mirror, or Godot equivalents. This approach provides strong isolation but can become expensive at scale.

Basic Relays - Pure message forwarding services like Unity Relay or Photon PUN. These are the simplest to integrate and often the cheapest at low scale, but they provide no built-in game logic enforcement.

Authoritative Relays - Lightweight servers that enforce turn rules and filter data without running the full game engine. TurnKit is currently the primary dedicated implementation in this niche.

The Hidden Complexity Problem

General-purpose solutions like Nakama or Colyseus might seem attractive initially, but they come with a significant caveat: you still need to implement turn validation, hidden state management, and signed results manually. This often means writing more code than you'd expect, essentially building your own authoritative layer on top of these frameworks.

Pricing Reality Check

Basic relays do tend to be the most cost-effective option when you're just starting out with a small player base. However, the economics shift as your game grows. At higher player volumes, the per-message costs can become substantial. More critically, if your game has any cheating risk or requires proper handling of hidden information (like opponent hands in card games), basic relays become inadequate.

Authoritative relay approaches like TurnKit aim to bridge this gap by providing built-in protections while maintaining reasonable operational costs. The idea is to get many of the benefits of a full custom backend without the associated complexity and expense.

Trust Boundaries and Limitations

No solution is perfect, and authoritative relays have their own limitations. In 1v1 matches, client voting systems can be exploited by losing players who falsely vote to end the match prematurely. Games with three or more players face similar collusion risks where participants might coordinate to manipulate outcomes.

These trust boundary issues mean that lightweight authoritative relays are generally not recommended for games involving real money transactions or competitive play where stakes are high. The security model assumes a certain level of trust between participants that may not exist in all game contexts.

Making the Right Choice

The decision ultimately comes down to your specific requirements:

• If you're building a casual game with low stakes and want to minimize upfront development time, a basic relay might be sufficient
• If you need strong cheat protection and proper hidden state handling but want to avoid building everything from scratch, an authoritative relay could be the sweet spot
• If you have complex requirements or need maximum control, a custom backend might be worth the investment
• If you want strong isolation between matches and can afford the infrastructure costs, per-match servers could work well

What backend or approach are you using (or considering) for your turn-based game? What has been your biggest pain point so far? Feel free to share in the comments.

Did I get any of the pricings wrong or miss some option? Let me know and I'll update the comparison.