Metaplay logo
DemoPricing

FOR CROSS-PLATFORM GAMES

One backend, every platform

A single backend for iOS, Android, Steam, and web with seamless cross-device authentication and save sync.

SupercellTrailmixLessmore GamesMetacoreSuperbloom
Deploy
v2.4.1
BuildReady
Target Platforms
🍎
iOS
Waiting
đŸ€–
Android
Waiting
🎼
Steam
Waiting
🌐
Web
Waiting
Single codebase, multiple platforms0/4 live
01

Why use Metaplay for cross-platform?

Unified player state

Server-authoritative model means player progress lives on the server, not the device.

Automatic cross-device sync when players log in on a new platform.

No more lost save data or device-specific progress islands.

Platform-native features

Social logins for Apple, Google, Facebook, Steam, Game Center, and more.

IAP validation handles Apple App Store, Google Play, and Steam natively.

Account linking with conflict resolution for multi-platform players.

Build once, deploy anywhere

Single C# codebase for client and server logic across all platforms.

Environment configs let you target different builds to different platforms.

WebGL support for browser-based play without a separate backend.

02

Three ways Metaplay helps cross-platform games work better

01

No sync headaches

Player state is server-authoritative. When a player switches devices or platforms, their progress is already there. No manual sync, no cloud save conflicts.

02

Native authentication

Players sign in with their platform identity—Apple ID, Google account, Steam. Metaplay handles the OAuth flows and maps them to your unified player accounts.

03

One IAP system

Server-validated purchases work the same whether players buy on iOS, Android, or Steam. Your game code doesn't need platform-specific payment logic.

03

Features for cross-platform games

01

Social logins

Apple, Google, Facebook, Steam, Game Center, and custom providers.

02

Cross-device sync

Server-authoritative state syncs automatically across all devices.

03

Platform IAP

Unified server validation for App Store, Google Play, and Steam.

04

Steam integration

First-class Steam support with authentication and purchase handling.

05

WebGL support

Unity WebGL builds work with the same Metaplay backend.

06

Account linking

Connect multiple social logins to a single player account.

07

Conflict resolution

Handle cases where the same social login is on multiple accounts.

08

Environment configs

Configure different server endpoints per platform or build type.

09

Multi-region

Deploy globally for low latency and data residency compliance.

04

It couldn't be easier to get started

01

Sign up

Sign up to Metaplay and install the Metaplay SDK. Try a sample project and familiarise yourself with our comprehensive support docs.

02

Start developing

Use our pre-built features to cover all the basics and start developing your game with complete control.

03

Scale and extend

Progressively develop more features and workflows as your game grows and never get held back by your tech.

05
Metaplay has enabled us to scale with very minimal backend work, and our collaboration works well. Whenever we have a question or need to dive under-the-hood, the Metaplay team is always quick to help out.

Juho LyytikÀinen

Tech Lead at Metacore

06

Top frequently asked questions

Player state is stored on the server, not the device. When players log in on a new device—whether through device auth or social login—their account is retrieved from the server with all progress intact. No manual sync or cloud save setup required.

Players can link multiple social logins to one account. If there's a conflict—say, they already have progress on both Google and Apple accounts—Metaplay provides conflict resolution flows so players can choose which account to keep.

Initialize the Steamworks SDK in your Unity project, then enable Steam authentication in Metaplay's runtime options. The SDK handles Steam login and purchase validation automatically. Your game code stays platform-agnostic.

Yes. The Metaplay client SDK supports WebGL builds. You can run browser-based games against the same backend as your native mobile and desktop builds, with the same player accounts and state sync.