Make games,
not backends.
Leaderboards, multiplayer, saves, economies, live-ops, moderation — the entire backend your game needs, in one import. Turn on everything or just one feature. Point your AI at the docs and it wires itself.
import { createClient } from '@triggair/sdk';
const tg = createClient({ key: 'tg_pk_your_key' });
await tg.login(); // anonymous player
await tg.saves.put('slot1', { level: 4 }); // cloud save
await tg.leaderboards.submit('high', 9000); // leaderboard
const room = await tg.realtime.join('lobby');// multiplayer
tg.track('level_complete'); // analytics Everything a game needs, none of the plumbing
Each feature is one SDK call away and configured from a dashboard — no infrastructure, no servers, no schemas to design.
Leaderboards
Global, daily, or friends-only. Submit a score, read the top — that's the whole integration.
Learn moreCloud saves
Players resume on any device. Conflict-safe, and it keeps working offline.
Learn moreRealtime multiplayer
WebSocket rooms with presence and chat, plus turn-based matches. No servers to run.
Learn moreInstant accounts
Anonymous-first identity — no sign-up wall to build, no auth to babysit.
Learn moreIn-game economy
Currencies, stores, inventories, loot boxes, energy — server-authoritative, so no one cheats.
Learn moreRetention, built in
Daily rewards, quests, battle passes, achievements — the come-back loop, out of the box.
Learn moreChange the game live
Remote config, feature flags with a kill switch, live events — tune it without an app-store release.
Learn moreSafety that ships
Chat + name moderation and age-gating that keep you in the stores. On by default.
Learn moreKnow what's working
DAU, retention, funnels, crashes — rolled up nightly. No data pipeline to build.
Learn moreUse as many or as few features as you like
One import, one key. Start with a leaderboard today, add an economy next month — you never pay in complexity for the features you're not using yet.
Your AI can build the whole thing
Point Cursor, Claude, or any coding agent at /llms.txt. It reads the recipes, calls the MCP tools to set up your game, and runs a one-command self-test to prove it works. Every error even tells it how to fix itself.