Unity ended its own Multiplay Game Server Hosting service on March 31, 2026. Multiplay itself did not shut down. Rocket Science Group licensed the software and relaunched Multiplay as an independent service on July 14, 2026. Studios on Unity’s service had to choose between moving to Multiplay under Rocket Science and moving to another provider.
This post covers where things stand now, what the realistic options look like, and what migration actually involves.
What’s still running
Only Unity’s dedicated server hosting service ended. Unity Matchmaker, Relay, Lobby, Distributed Authority, and Netcode for GameObjects are all unaffected and continue to work with third-party hosting providers. Your matchmaking rules, player grouping, and ticket logic don’t need to change — only where your servers run.
Where studios are going
Three paths are seeing the most traction right now.
Rocket Science Group
Rocket Science was founded by members of the original Multiplay team and licensed the software from Unity. Their pitch is continuity: the platform is the same codebase Multiplay ran on. Rocket Science relaunched Multiplay on July 14, 2026 and opened it to new studios.
Rocket Science says Multiplay supports over 60 live clients. What to weigh: as of November 2026 multiplay.com publishes no pricing, no uptime SLA and no self-serve trial, and onboarding starts with a sales conversation. Studios choosing this path swap a Unity contract for a Rocket Science one.
Edgegap
Edgegap has a dedicated Unity plugin and a documented migration path from Multiplay. Self-serve onboarding, 615+ edge locations, pay-per-second pricing. If your team is already comfortable in the Unity editor toolchain, this path has the shortest ramp. Their SDK is optional — see how Gameye compares to Edgegap.
Gameye
Gameye is a dedicated server orchestration platform — in production since 2017, 130M+ sessions orchestrated. API-driven: a single HTTP call starts a session, and Unity Matchmaker routes to it.
The key difference from the other options: Gameye requires no SDK in your game server binary. You remove the Multiplay SDK (IMultiplayService, MultiplayEventCallbacks, ReadyServerForPlayersAsync) and don’t replace it with anything. Your server just starts, listens on its port, and accepts connections.
- $0.07/vCPU/hr on-demand — no egress fees, no bandwidth charges
- 0.5-second session starts — no fleet pre-provisioning
- 21 providers, 200+ datacenters — bare metal + cloud with automatic cross-provider failover
- Game-aware DDoS protection across all providers
- Unity Matchmaker compatible — your matchmaking rules stay unchanged
- Self-serve Developer Trial — no sales call required
What migration actually involves
The technical scope is smaller than it feels right now. Your authoritative game server code, networking stack, Unity Matchmaker configuration, Relay, and Lobby integrations are untouched.
What changes:
- Remove the Multiplay SDK — strip
IMultiplayService,MultiplayEventCallbacks, andReadyServerForPlayersAsyncfrom your server build. With Gameye, there’s no replacement SDK - Containerise your server — if it’s not already in a Docker container, that’s the main new step. Unity’s Dedicated Server build target produces the binary; Docker wraps it
- Replace the allocation call — wherever your backend called Multiplay’s fleet API, replace it with
POST /sessionto Gameye. The response returns host IP and port immediately - Configure in the Admin Panel — set your image, ports, regions, and webhook
Studios have completed this in under two weeks with parallel testing. Step-by-step migration checklist.
Full comparison
For a detailed breakdown of how Gameye compares to the other options — including feature-by-feature tables, pricing, and infrastructure — see:
- Gameye vs Unity Multiplay — full platform comparison
- Unity Multiplay migration options — all three paths compared side by side
- Multiplay to Gameye migration checklist — step-by-step with API examples
Self-serve Developer Trial. No sales call required. Start Building.
Frequently asked questions
Did Unity Multiplay shut down? Unity ended its own Multiplay Game Server Hosting service on March 31, 2026, but Multiplay did not shut down. Rocket Science Group licensed the software and relaunched Multiplay as an independent service on July 14, 2026. Unity Matchmaker, Relay, Lobby, and Distributed Authority continue to work with third-party providers.
Do I need to change my Unity Matchmaker configuration? No. Unity updated Matchmaker to support third-party hosting providers before its service ended. Your matchmaking rules, player grouping, and ticket logic stay unchanged — only the server allocation backend changes.
Does Gameye require an SDK in my Unity game server?
No. Gameye requires no SDK in your game server binary. Remove the Multiplay SDK (IMultiplayService, MultiplayEventCallbacks, ReadyServerForPlayersAsync) and don’t replace it. Your server starts, listens on its port, and accepts connections.
How long does migration from Multiplay to Gameye take? Studios have completed migrations in under two weeks with parallel testing. Gameye’s trial is self-serve. See the step-by-step checklist.