Game backend for your game
Rudder runs the meta of your game: stores, quests, leaderboards, inventories, remote config and the features only your game has. You install ready modules from the marketplace, add your own modules for the rest, and your LiveOps team runs all of them from one Dashboard.
// A web game buys the starter pack of a store.await rudder.stores.buy({ offer: 'starter' });The call either pays the price and grants the goods, or changes nothing. A retry of the same call never pays twice.
Who reads what
Section titled “Who reads what”| You are | You use | Start with |
|---|---|---|
| A client engineer (Unity, web) | The client SDK and the typed client of your project | Quickstart, Client SDK |
| An engineer who writes game logic | Your own modules, on the Pro plan | Own modules |
| A designer or a LiveOps manager | The Dashboard | Dashboard |
| A coding agent | rudder agent init and the Rudder skill | For AI agents |
What Rudder promises
Section titled “What Rudder promises”- A call changes all or nothing. A function that returns an error leaves the player as it was, and so does a module it called that failed.
- A retry never runs twice. A mutation carries an
Idempotency-Key; the same key gets the same answer and nothing runs a second time. The client SDKs send one for you. - Staging first. Every change goes to staging as a release. Production gets only releases you promote from staging, and you roll either back in one click.
- Every change is in the history. Each call that changed a player is an entry of its history, in the terms of its modules: which field, which balance, which timer.
- Tests behave like production. A module is tested on a laptop, with a clock you move, and behaves the same live.
Read Concepts next for the words these pages use.