0 Get started
This is the closest single-capability comparison on the site, because the overlap is real: leaderboards, player progression, an economy, and the plumbing around them. The difference is the same one as everywhere else — a hosted service you call, or a Worker you deploy — but here it decides more, because a game's economy is the one place a vendor outage is a support incident.
Choose LootLocker
When you want a game backend today and never want to operate one.
Leaderboards, progression, currencies, catalogs and player storage, with engine SDKs and a console, ready before you have finished reading their docs. For a small team shipping a game rather than a platform, that is the right trade.
Choose Pithy
When the economy is real money's neighbor.
The ledger is atomic, idempotent and overdraft-safe by database constraint, in your own D1 — and it composes with matchmaking, sessions and rating without any of them calling a service. A payout delivered twice pays once, and you can prove it by reading the schema.
On this capability alone
| Feature | LootLocker | Pithy |
|---|---|---|
Game services | ||
| Leaderboards with closing windows LootLocker: hosted, with a console Pithy: daily through all-time, in plain SQL you can join against your own tables | Yes | Yes |
| Player progression and XP Pithy: XP that only rises, alongside a skill rating that moves both ways | Yes | Yes |
| Skill rating for matchmaking LootLocker: progression, not a rating system Pithy: MMR per pool, and it is what the open queue buckets on | Partial | Yes |
| Matchmaking Pithy: room codes, direct invites, a friend graph and a skill-bucketed queue | Partial | Yes |
| Authoritative multiplayer sessions LootLocker: not the product Pithy: a Durable Object holding state no client can be trusted with | No | Yes |
| Player currency and economy LootLocker: catalogs, currencies, purchases Pithy: a ledger that cannot double-spend: atomic, idempotent, overdraft-safe by CHECK constraint | Yes | Yes |
| Engine SDKs LootLocker: Unity, Unreal and more, maintained Pithy: HTTP and a documented route contract; the Unity path is documented, not packaged | Yes | No |
| Runs in your own account LootLocker: their infrastructure Pithy: your Cloudflare account, your D1, your Durable Objects | No | Yes |
| No vendor in the request path Pithy: there is no service of ours between your player and your game | No | Yes |
The saffron tick marks where Pithy leads — not that the other column is absent. Every claim about LootLocker was checked against their own documentation on 2026-08-25; both products change, and this page is a snapshot rather than a maintained contract.
Where LootLocker wins
A maintained Unity package beats a documented HTTP contract on the first afternoon, and on every afternoon where you would rather be building the game.
Editing a catalog or a leaderboard without a deploy is worth a great deal when the person doing it is not an engineer.
Levels, milestones, achievements and rewards, with opinions already formed. The kit gives you a ledger and a rating and expects you to model the game.
No migrations, no bindings, no provisioning. For a team of two shipping their first title, that is not a small thing.
If you are shipping a game and want a backend to exist, LootLocker will get you there faster. The case for the kit is what happens when the economy matters: a balance that cannot go negative because the database refuses it, a payout that pays once because the ref is a unique row, and no vendor between your player and their currency — with matchmaking, sessions and ratings sharing the same database rather than calling each other.