ENGINEERING · 2026-06-17

Unity Multiplay is shutting down:
how to migrate your multiplayer backend in 2026.

By Alexander Strandberg · Founder, Aevs

Unity ended Multiplay Game Server Hosting in March 2026. If your game depends on Multiplay for dedicated server orchestration, you need to migrate. The good news: the alternatives are mature and the migration path is straightforward — provided you validate the new backend before cutting over production traffic.

This guide covers what happened, your main alternatives, how to evaluate them, and — critically — how to verify your replacement works before players see it.

What happened to Unity Multiplay?

Unity Gaming Services announced the end of Multiplay Game Server Hosting (rebranded as Unity Game Server Hosting) effective March 2026. Studios using Multiplay for fleet management, server allocation, and matchmaking integration needed to migrate. Unity recommended its own Relay and Lobby services for certain topologies, but neither covers the dedicated server hosting use case that Multiplay served — leaving studios running persistent authoritative servers needing a third-party replacement.

The shutdown follows a broader pattern of Unity's fragmented service offerings. Multiplay was acquired by Unity in 2020 alongside Vivox (voice) and ChilliConnect (backend). GameSparks (acquired from Amazon) was sunset in 2023. Studios that built on these managed services have repeatedly found themselves migrating, often under time pressure.

Unity Multiplay alternatives: comparison table

How to evaluate a Multiplay replacement

Not all alternatives are equivalent for all game types. Evaluate on five axes:

How to validate your backend before migrating

The most common migration failure mode: the new provider works correctly in isolation, but breaks under the specific interaction patterns of your game's topology. Session management, matchmaking callbacks, and reconnect logic all behave slightly differently across providers. These differences only surface when the full stack is exercised together.

The safest migration path runs a declarative validation plan against the new provider in an isolated sandbox before touching production. Write the plan first, against Multiplay, while it still works — it becomes your baseline. Then run the same plan against the replacement. If the plan passes on the replacement, the migration is behaviorally equivalent.

Example: migration validation plan

export default {
  id: 'multiplay-migration-smoke',
  steps: [
    // 1. Server allocation
    { type: 'http', method: 'POST', path: '/v1/servers/allocate',
      body: { region: 'eu-west', gameMode: '5v5' },
      assert: { status: 'allocated' } },

    // 2. Match assignment callback fires within 5s
    { type: 'wait', condition: 'server.status === "ready"',
      timeout: 5_000 },

    // 3. Player can connect and session persists
    { type: 'http', method: 'POST', path: '/v1/session/join',
      body: { playerId: 'p1', serverId: '{{server.id}}' } },

    { type: 'wait', condition: 'session.connected === true',
      timeout: 3_000 },

    // 4. Reconnect flow works
    { type: 'http', method: 'POST', path: '/v1/session/disconnect',
      body: { playerId: 'p1' } },
    { type: 'http', method: 'POST', path: '/v1/session/reconnect',
      body: { playerId: 'p1', serverId: '{{server.id}}' },
      assert: { reconnected: true } },
  ],
}

This plan covers the four scenarios that most commonly break in migrations: allocation success, callback latency, initial session establishment, and reconnect. It takes under 30 minutes to write and can be run on any provider with an HTTP API.

Step-by-step migration guide

Frequently asked questions

Can I migrate without rewriting my game code?

It depends on how deeply you used the Multiplay SDK. Standard server allocation and deallocation calls have direct equivalents in all major alternatives. Multiplay-specific features — custom fleet configuration scripts, the Multiplay QoS system, or the Unity Dashboard fleet management API — will require provider-specific replacements.

What about Unity Relay and Lobby — can I use those instead of dedicated servers?

Unity Relay (P2P relay through Unity's network) and Unity Lobby are viable for games that do not require authoritative dedicated servers — typically turn-based games, casual titles, or games where latency requirements are relaxed. For real-time competitive games (FPS, MOBA, battle royale) that require authoritative server-side physics and anti-cheat, dedicated servers remain the only viable architecture. Relay is not a substitute.

How do I know when my migration validation is complete enough?

Your validation plan is complete when it covers the failure modes that would be visible to players: failed matchmaking, broken reconnect, and session state loss under concurrent load. A useful heuristic: if your plan passes and a player then reports one of those failures in production, the plan has a gap. Start with allocation, session, and reconnect — add more steps when you hit production issues.