Developer docs
Connect your game to Rudder
Rudder is a LiveOps layer for games. These docs cover client authentication, remote config, analytics, stores, leaderboards, scenario execution, and realtime sessions through the SDKs that exist in this repository.
Getting started Create a client, sign in with a device identity, load config, and run the first smoke checks. TypeScript SDK Use the browser-first
@rudder/web-sdk package in web games and internal tools. C# SDK Use RudderSdk.Core from Unity or any C# runtime that supplies the required transports. Unity SDK Bootstrap Rudder with a Rudder MonoBehaviour, LiveOpsConfiguration, and Unity platform adapters. Dashboard Manage projects, environments, stores, leaderboards, remote config, and scenarios. Base endpoints
| Endpoint | Production value |
|---|---|
| API URL | https://api.rudder.build |
| Realtime URL | wss://realtime.rudder.build/api/realtime/ws |
| Dashboard | https://app.rudder.build/ |
Integration shape
- Create a project in the Rudder dashboard and copy the project key.
- Initialize the SDK with the project key and production endpoints.
- Authenticate the player with device login before calling protected SDK APIs.
- Load remote config and register handlers for scenario, store, leaderboard, or realtime events.
- Call the SDK from game lifecycle hooks and dispose or disconnect when the session ends.
The first documentation version intentionally covers TypeScript and C# only. Engine-specific wrappers can be added later without changing the public endpoint model.