Welcome to Kraty

Kraty is a live-ops backend for game studios. Wire the SDK in once; designers compose tournaments, races, lobbies, and reward crates from the portal. Bots fill quiet leaderboards. Webhooks keep your backend in sync.

What you can build

• Tournaments and races — single-metric or multi-metric, with global, grouped, or per-segment leaderboards.
• Live lobbies — auto-matched with progressive bot fill (so a 4-cap lobby visibly fills over time, not all-at-once after a 30s wait), or pushed in from your own matchmaker.
• Rewards — fixed bundles, weighted loot tables, openable crates, rank-scaled prizes — composed visually.
• Paid events — declare a currency + item cost on an event and Kraty atomically debits on start; insufficient → 402 with a player-friendly message.
• Platform-managed inventory + wallet — opt-in per-game player ownership for items and currencies, with auto-deposit from grants, SDK consume + debit, and an immutable audit ledger.
• Filler bots — composable, deterministic behaviors that look like real players. Browse community bots in the marketplace.
• Signed webhooks — every grant, completion, and lobby state change pushed to your backend, with auto-retry and a circuit breaker for misconfigured endpoints.
• Live leaderboard streams — Server-Sent Events so your UI repaints without polling.
• Zero-trust per-player auth — a leaked SDK key cannot read or spend another player's resources. See Authentication.

Where to start

• New here? Read the Quickstart — ten minutes from zero to your first live event.
• Building a feature? Common integration tasks — IAP fulfilment, daily quests, tournaments, matchmaker handoff, and migration as copy-paste recipes.
• Wiring up an event? Start with Events.
• Integrating from a game client? Jump to the SDKs.
• Securing the integration? Read Authentication — understand the two-layer key model before you ship.
• Handling errors? Error reference lists every code, when it fires, and how the SDKs help you handle it.
• Evaluating Kraty for production? Read Reliability and data durability — the recovery targets and backup commitments Kraty holds itself to.

How the docs are organized

The sidebar groups pages into four sections:

• Core concepts — the building blocks (events, leaderboards, lobbies, bots, marketplace, rewards). Read these in order if you're new.
• Backend integration — wiring your studio backend (webhooks, settings, player tools).
• Reference — Authentication model, error codes, REST API, and language-specific SDK docs.