Seven vendors down to one.
Sofia leads engineering at a small mobile F2P studio. Since GameSparks shut down, the backend is Firebase + RevenueCat + a bespoke game server + three other services glued together. One refund bug bounces across three dashboards. Here's the month she consolidates.
Mobile F2P team consolidating off GameSparks, Photon, Firebase, RevenueCat, and Amplitude into a single event bus.
Inventory the stack
Sofia maps everything the game touches: Firebase Auth, Firebase Realtime DB, RevenueCat, a custom receipt-validation service, Amplitude, a bespoke game server on Fargate, and a Zendesk webhook for refunds. Seven services, three people who understand the glue, one on-call rotation.
The discovery call with PlayServ maps each service onto a module. Seven vendors compress into one runtime.
Identity and payments first
Passport takes over authentication — guest → OAuth → account merge, including the legacy Firebase UIDs imported in one migration script. Vault replaces the receipt-validation service; the refund webhook now fires from one place instead of three.
Config, economy, analytics
Pulse replaces Firebase Remote Config and adds segment targeting the old stack never had. Market takes over the in-game store logic previously smeared across three services. Lens ingests alongside Amplitude for the first month — the team verifies parity before switching off the legacy pipeline.
Game server joins the platform
The Fargate game server moves to Edge as a bring-your-own container — same binary, new scheduler. Matchmaking logic that used to live in a Lambda now lives in Canvas. Zendesk still handles support tickets, but the refund workflow runs end-to-end inside PlayServ and emits a single signal Lens correlates with player cohort.
Turn off the old stack
Firebase, RevenueCat, the custom validator, the Lambda, Amplitude — all deprecated in the codebase. The last piece to go is a quarterly reminder in the calendar to renew the Firebase billing plan. Sofia cancels it.
“We had a stack diagram that took up a whole wall. We now have one vendor, one dashboard, and a wall we can paint.”
GameSparks shut down years ago; Firebase and RevenueCat are alive but billed separately. PlayServ replaces all three plus the bespoke game-server glue that usually sits between them. Identity, payments, economy, config, and analytics share one event bus — so a refund in Vault is visible to Lens without a custom pipeline.
Bring the stack diagram.
Seven vendors, three glue services, one on-call. We'll show you the same picture on one runtime.