Migrate from Unity Multiplay

import { Aside } from ‘@astrojs/starlight/components’;

Overview

Migrating from Multiplay to Gameye involves replacing the server hosting layer underneath your existing Unity stack. Your game logic, networking model, matchmaking rules, and client connection flow don’t change.

Key difference: Gameye requires no SDK in your game server binary. Remove the Multiplay SDK and don’t replace it.

For a detailed step-by-step checklist with code examples and API reference, see the full migration guide on gameye.com:

Unity Multiplay to Gameye Migration Checklist →

What changes

Remove the Multiplay SDK — strip IMultiplayService, MultiplayEventCallbacks, and ReadyServerForPlayersAsync() from your server build. Gameye requires no replacement SDK.
Containerise your server — build a Linux Dedicated Server, package in Docker, push to Docker Hub.
Configure in Admin Panel — set your image name, ports, networking mode, and regions.
Replace the allocation call — wherever your backend called Multiplay’s fleet API, call POST /session on the Gameye API instead.

What stays the same

Unity Matchmaker (rules, queues, ticket logic)
Unity Relay
Unity Lobby
Netcode for GameObjects
Your authoritative server logic
Client connection flow

Quick reference

Multiplay concept	Gameye equivalent
Fleet / server profile	Application (Admin Panel)
Server allocation API	`POST /session`
Server deallocation	`DELETE /session/{id}` or TTL expiry
`IMultiplayService` SDK	Not needed
`ReadyServerForPlayersAsync()`	Not needed — Gameye checks port availability
Server logs	Admin Panel + log streaming API
Fleet scaling rules	Managed by Gameye — or configure warm pools
Regions	Available locations