Pillar · Passport

One player, every platform.

Cross-save, cross-progression, cross-platform inventory. Guest → OAuth → account merge, with one identity the whole platform respects. Every other module reads the same player ID.

What you get

Everything a multiplayer game actually needs to launch.

Guest-first onboarding

Players start playing instantly. Promote to a permanent account when they want to; no sign-up wall at the front door.

Account merge that audits

Link Steam, Apple, Google, PSN, Xbox, Nintendo. Merges are reversible, logged, and support handles them from a dashboard.

One ID across every module

Vault grants, Sync presence, Lens cohorts, Stage segments — all keyed to the same player identity.

Platform SDKs as first-class

PSN, Xbox Live, Nintendo Account, Steam, Apple — supported as providers, not left as a future ticket.

Cross-save by construction

Progression and inventory live in the runtime, not on the device. Switch platforms and continue mid-session.

GDPR / DMA-ready by default

Export, delete, and consent endpoints ship with the module. Regulatory asks become a dashboard, not a migration.

Who it's for

Passport fits three kinds of teams.

Technical Director

Ship cross-play without writing identity again

A single player ID the whole backend agrees on — so multiplayer, monetization, and analytics share context out of the box.

Producer

First-party requirements met from day one

PSN, Xbox, and Nintendo integrations live in the module. Cert submissions don't wait on a custom auth service.

Lead Programmer

Account merge that doesn't burn the weekend

When a player links a new platform mid-season, the merge is logged, reversible, and doesn't need a custom migration script.

Under the hood

Passport is one module, used by every other.

Identity is cross-cutting: Sync needs it for presence, Vault for entitlements, Lens for cohorts, Stage for segments. One module, one player ID, every other PlayServ pillar reads from it.

Where Passport fits

Cross-platform continuity as a managed bundle.

Without PlayServ
  • PlayFab covers auth + cloud saves, no first-class inventory merge
  • EOS is viable and free but Epic-centric for entitlements
  • Firebase Auth — no console providers, no cert templates
  • AccelByte — enterprise cross-platform, heavy integration cost
With PlayServ
  • Cross-platform inventory merge bundled in
  • Player-readable conflict-resolution UI
  • Cert-pack templates for Sony TRC / Microsoft XR / Nintendo
  • One ID respected by every PlayServ module

The cert team still owns submission; we compress the prep work so first-party isn't a six-week milestone of its own.

One identity, every platform.

Free up to 1,000 MAU. Upgrade when first-party cert arrives.

© PlayServ Ltd 2026. All rights reserved.
Reg. 10645902 · London N22 8HH, UK
Cookie settings

PlayServ