Built for the parts of iGaming that get audited
The iGaming platform built API-first — every operation, not a subset.
Ledgerfield is player account management, a sportsbook, a casino engine, a bonus and CRM stack and a compliance layer for licensed operators — exposed as 308 API operations across 268 documented paths, with no console-only pocket of functionality waiting to be discovered six months into integration.
Seven operator brands are running on one instance of this platform right now, in play money — dark and light, casino-led and coupon-led, one of them monochrome — and you can click into any of them without an appointment.
- Automated tests
- 2,042all passing
- API operations
- 308/ 268 paths
- Domain services
- 139/ 81 migrations
- Platform status
- checking…
Why this shape
The incumbents were built console-first. That build order shows.
BetConstruct, SoftSwiss, EveryMatrix, Playtech, Digitain — each was shaped in an era when the back office was the product and the API, where one existed at all, was added on top afterwards. Operators feel that in exactly two places during an evaluation: a CTO's team finds functionality the console can do that the API can't, and a compliance team inherits a tenancy model retrofitted onto a codebase years after the multi-brand claim was already being sold.
Ledgerfield reverses the order. The operator back office is a client of the same operations your own front end, mobile app or internal tooling would call. That isn't a design preference stated for its own sake — it is why a Head of Product can commit to a real go-live date instead of a "should be possible" one, and why a Head of Compliance can point a regulator at a code path instead of a policy document.
Differentiator 01
API-first architecture — 100% surface, not a subset
308 operations across 268 documented paths. That is not a curated public API sitting in front of a larger admin-only system; it is the whole platform. The documentation is auto-generated — an OpenAPI 3.1 specification regenerated on every route change, describing what the code does today rather than what it did last quarter.
A real domain underneath
139 backend domain services, 66 models and 81 migrations — a wallet ledger, an odds and settlement engine, a bonus engine, compliance gates and an audit log. Not a thin wrapper over somebody else's platform.
Every feature has a front end
43 production front-end widgets, each wired to a real backend capability. There is no feature that exists only as an admin screen with no way to put it in front of a player.
Docs that cannot drift
The OpenAPI spec is generated from the routes themselves on every change. There is no separate documentation effort for it to fall behind — a route that exists is a route that is documented.
Check this one firstAsk us for the OpenAPI file and diff it against the routes. We will hand you both. An API surface is the single easiest vendor claim to verify and the single most expensive one to get wrong — so verify it before you read anything else on this site.
Differentiator 02
Compliance enforced in the code path, not bolted on
The test a Head of Compliance actually applies is not whether a policy document describes the right behaviour. It is whether the system is architecturally capable of the wrong one.
Consent is structural
Campaign automation is filtered through marketing-consent and self-exclusion checks by construction. There is no code path that routes a campaign to a player who withdrew consent — it is not a rule a marketing coordinator has to remember.
Segmentation fails safe
9 CRM segmentation rule types, combined with AND. If the engine meets a rule type it does not recognise, it excludes every player from that segment — a deliberate fail-safe rather than an accidental pay-everyone default.
Exposure is checked live
Sportsbook liability is not a nightly batch. The sweep re-checks every 5 minutes, and markets suspend at kick-off without waiting for a human to remember.
Differentiator 03
Multi-tenant by design, audited rather than assumed
One codebase serves every brand. The active brand is resolved per request and brand-owned tables carry a global query scope, so a brand's own staff can only ever reach their own data. That distinction matters because a tenancy bug in this category is not a UI glitch — it is a data breach with a regulator's name on the incident report.
10 skin presets
A skin is the visual layer only. The brand underneath it is what tenant-ownership security actually isolates — re-theming is a setting, not a deployment.
4 interface locales
The interface is translated into English, Spanish, German and French — navigation and interface labels. Promotional copy remains English-only, and we are not going to describe that as anything more than it is.
Live in seven brands today
BetBeavers, Kestrel Sports, Chinchón, Lumo, Pulsar, Ludgate & Co. and AXIS all run against one API and one deployment, sharing one odds feed. They demonstrate front-end independence rather than tenancy — the demo brands deliberately share a tenant, so a balance follows you between them. Isolation is the back-office story, and it is a separate one.
Differentiator 04
A build culture where every claim has a passing test
2,042 automated tests / over 180,000 assertions, all passing. That is the baseline, not the headline. Claims that carry money or compliance weight are held to a tighter standard than "we wrote a test for it".
Two-factor, verified against the specification
RFC 6238 TOTP is checked against the official Appendix B test vectors from the specification itself, then cross-checked a second time against an independent Python implementation — not merely against our own code's idea of what RFC 6238 should produce.
RTP solved, never typed
Every one of the in-house slot titles has its return-to-player calculated by a solver from the real paytable. No RTP figure on this platform was hand-entered, because a hand-entered RTP is a number nobody ever checks again.
Stated plainly, in the same breathThose titles are in-house mathematics awaiting test-house certification. They are not certified content today, and "calibrated" is not a word we are using to obscure that. Licensed casino content is a supplier contract we have not signed — the seamless-wallet protocol an aggregator plugs into is built and tested, which is a different claim and a smaller one.
What we are not going to claim
No customer list. Here is what you can verify instead.
Ledgerfield is pre-launch. There is no production customer base, no operator logo to put on this page, and no uptime figure to quote, because there is no production traffic to measure one from. We are not going to manufacture a testimonial to fill that gap — we would rather tell you exactly what does exist and let you check it.
WHAT EXISTS
A test suite you can run yourself
2,042 tests and over 180,000 assertions, executed against the actual codebase. We will run it in front of you, from a clean checkout, on the call.
WHAT EXISTS
A specification that regenerates
OpenAPI 3.1, rebuilt on every route change. What you read is what the code does today, because there is no manual step where the two could diverge.
WHAT DOES NOT
A live payment processor
The PSP driver contract is built and tested end-to-end against a mock driver. Connecting a real processor is an implementation against that contract, not a rebuild — but it is not connected, and a mock is not an integration.
WHAT DOES NOT
An operating licence
Ledgerfield holds no gambling licence in any jurisdiction. Today it is a play-money platform. Nothing on this site implies otherwise, and any page that seemed to would be a page we would fix.
The offerInstead of a reference list: the same test suite, the same auto-generated specification and the same solver output that we looked at. Bring your integration lead and your compliance lead, and bring the questions this site did not answer.
Go deeper
The whole platform, one section at a time
Sportsbook & trading
Bet builder correlation pricing, system bets from Trixie to Lucky 63, live settlement with a defined grace window, and a liability sweep every 5 minutes.
How the book worksCasino & aggregation
31 in-house engines with HMAC-SHA256 provable fairness, solver-calculated RTP, tournaments and jackpots — plus a seamless-wallet protocol for licensed content.
How the games workCRM, bonuses & affiliates
9 segmentation rule types with fail-safe exclusion, automation journeys, a bonus engine with real wagering allocation, and affiliate attribution.
How growth worksCompliance & safer gambling
Limits with cooling-off, reality checks, self-exclusion that cannot be lifted early, affordability signals, markers of harm, GDPR export and erasure as code paths.
How the gates workMulti-brand & tenancy
Per-request tenant resolution, a global query scope on every brand-owned table, an audited staff permission model, and a one-command brand launch.
How isolation worksDevelopers & the API
308 operations, OpenAPI 3.1 regenerated on every route change, bearer auth, webhooks, and a public API for an operator's own tooling.
Read the surfaceEvaluate it honestly — against its own API, not a slide deck.
Bring your integration lead, your compliance lead, and the questions this site did not answer: the ones specific to your licence conditions, your bonus logic, your brand count. Commercially, Ledgerfield runs on the Growth plan — £10,000/month flat plus a configurable GGR revenue share in basis points, with new brands starting on a 30-day trial automatically.