Welcome to Kraty
Live events, leaderboards, bots, and rewards for game studios. Wire the SDK in once, design live ops in the portal.
Kraty is a live-ops backend for game studios. You wire the SDK into your client once; your design team composes tournaments, races, lobbies, and reward crates from the portal. Bots fill quiet leaderboards so they never look empty. Signed webhooks keep your own backend in sync.
This documentation is for game developers integrating Kraty. If you are evaluating Kraty or pricing it for your team, start at the marketing site.
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 (lobbies visibly fill in over time) or pushed in from your own matchmaker.
Rewards
Fixed bundles, weighted loot tables, openable crates, and rank-scaled prizes, composed visually.
Paid events
Declare a currency + item cost on an event; Kraty debits atomically on start and returns 402 on shortfall.
Platform inventory and wallet
Opt-in per-game player ownership for items and currencies, with auto-deposit, 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.
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. Read Authentication before you ship.
Where to start
Quickstart
Ten minutes from zero to your first live event.
Common integration tasks
IAP fulfilment, daily quests, tournaments, matchmaker handoff, and migration as copy-paste recipes.
Events
The central object: metrics, score formula, schedule, rewards.
Client SDKs
TypeScript, Unity, and Flutter clients for your game.
Authentication
The two-layer key model. Read this before going to production.
Error reference
Every error code Kraty returns, when it fires, and how the SDKs help you handle it.
Reliability
Recovery targets and backup commitments Kraty holds itself to.
REST API conventions
The cross-cutting rules every endpoint follows: versioning, idempotency, rate limits.
How these docs are organized
The sidebar groups pages into three sections:
- Core concepts: the building blocks (events, leaderboards, lobbies, bots, marketplace, rewards). Read these in order if you are new.
- Backend integration: wiring your studio backend (webhooks, settings, player tools).
- Reference: authentication model, error codes, REST API, and language-specific SDK docs.