Unity Multiplay Alternative
Multiplay is gone. Here's what comes next.
Unity Multiplay Game Server Hosting shut down March 31, 2026. Studios still need dedicated servers. Here's how Gameye replaces it — and why the Rocket Science handoff didn't work for most teams.
What you're replacing
- Dedicated server fleet management
- Global region coverage
- Fleet management dashboard
- Multiplay SDK (
IMultiplayService) - Server build upload and deployment
- Dedicated server fleet management
- Global region coverage
- API-driven orchestration dashboard
- Session API (single POST replaces Multiplay SDK call)
- Sub-second session starts, no egress fees
- Provider-agnostic: bare metal + cloud
Why most studios didn't go to Rocket Science
Rocket Science was positioned as the natural migration path when Unity announced the Multiplay shutdown. In practice, adoption has been limited. Pricing remains largely unpublished. The company is newly independent, with no track record as a standalone game server platform. Studios that needed to move fast — and most did — chose an established alternative with transparent pricing, a public SLA, and documented integrations.
That's not a knock on Rocket Science. It's just the reality of what studios need when a platform shuts down on a fixed date: a clear migration path, a published price, and a provider with a history of keeping servers running.
Key facts about Gameye
What migration involves
Four technical changes. Everything else stays the same.
Replace the host allocation call
One POST request to the Gameye Session API replaces the Multiplay fleet allocation request. Same data, different endpoint.
Remove the Multiplay SDK
Strip IMultiplayService from your dedicated server build. Gameye does not require a server-side SDK — session lifecycle is managed via the API.
Containerise your server
If you're not already using Docker, this is the main new step. Gameye runs containerised dedicated servers. Most studios complete this in a day or two.
Connect Unity Matchmaker to Gameye
Deploy Gameye's Unity Matchmaker Cloud Code module via the UGS CLI — takes around 15 minutes. Your matchmaking rules, queues, and ticket logic are unchanged.
Works with your Unity stack
- ✓ Unity Matchmaker — now supports third-party hosting providers natively
- ✓ Unity Relay — unaffected, no changes required
- ✓ Unity Lobby — unaffected, no changes required
- ✓ Netcode for GameObjects — unaffected, no changes required
- ✓ Unity 6.x — fully compatible
Frequently asked questions
What happened to Unity Multiplay?
Unity shut down the Multiplay Game Server Hosting service on March 31, 2026. Studios were given advance notice and needed to migrate to an alternative dedicated server hosting platform.
Why didn't most studios move to Rocket Science after the Multiplay shutdown?
Rocket Science was positioned as the handoff partner, but adoption has been limited. Pricing remains largely unpublished and the company is newly independent with no established track record as a standalone game server platform. Studios that needed to move quickly chose alternatives with transparent pricing, a public SLA, and documented integrations.
How long does migration from Unity Multiplay to Gameye take?
Most studios complete the core migration in one to two days. The main new step is containerizing your server with Docker if you weren't already doing so. The host allocation call, Multiplay SDK removal, and Matchmaker config update are straightforward changes.
Do I need to replace Unity Matchmaker when I move to Gameye?
No. Unity Matchmaker natively supports third-party hosting providers. You update the matchmaker configuration to point to Gameye as the hosting provider — no custom matchmaking code is required.
Does Gameye work with Unity Relay and Unity Lobby?
Yes. Unity Relay and Unity Lobby are unaffected by the hosting provider change. Your game logic, networking code, and other Unity services remain unchanged when migrating dedicated server hosting to Gameye.
Sandbox access provisioned within 24 hours.
Get your environment running today. No sales call required to start.