Start with the foundation of a player experience.

 Bring player sign-in, backend rules, and configurable settings together as you build your game’s first connected workflow.
Review integrationExplore products
01 Authentication
02 Cloud Script
03 Remote Config
Contextual draft · Release status, supported versions, and limits await owner review. authenticate a player, retrieve supported settings, invoke backend logic, and read or update a gameplay value.

Workflow to evaluate

Authenticate a player
Step 1: pending
Retrieve supported settings
Step 2: pending
Invoke backend logic
Step 3: pending
And read or update a gameplay value.
Step 4: pending

Your game team’s responsibilities

 Design client UX, game rules, permissions, and error recovery. Simulation, game-server hosting, moderation, and fulfillment are separate responsibilities unless explicitly included in a confirmed integration.

Service building blocks

 Explore what each service contributes to this workflow, then review its integration requirements.
SERVICE 1

Authentication

 Give every player a way into your game. Explore Authentication
SERVICE 2

Cloud Script

 Run game logic behind your player experience. Explore Cloud Script
SERVICE 3

Remote Config

 Adjust game settings between releases. Explore Remote Config
SERVICE 4

Stats

 Track the numbers that define player progress. Explore Stats

Before implementation

 Validate access and supported versions for every required service. Test the workflow with failure, reconnection, and authorization cases before using it in your game.
YOUR NEXT CHAPTER STARTS HERE

Build the backend for your next game.

 Explore the services and plan your first player experience.
Create GameIntegration overview