About
Built from the parts that are hardest to get right and easiest to fake.
Ledgerfield was not spun out of an operator's tech team and is not a rebrand of an acquired legacy system. It was built API-first, starting from player account management, tenant isolation, two-factor verified against the actual RFC test vectors, and GDPR as code paths rather than policy documents.
Why that ordering
The unglamorous infrastructure is the part that cannot be added later. A bonus engine can be written in a quarter. A tenancy model cannot be retrofitted onto a codebase that has assumed one brand for five years — that is a rewrite wearing a migration's clothes, and it is why several platforms in this market carry the tenancy risk they do.
So the order was: wallet ledger, tenancy, authentication, compliance gates, audit — then sportsbook, casino, CRM and the front-end layer on top. It is a slower-looking first year and a much faster second one.
That ordering shows in the numbers. 2,042 automated tests and over 180,000 assertions, 139 backend domain services, 81 migrations, and 43 front-end widgets each wired to a real backend capability rather than standing in for one.
The nameA ledger is the literal mechanism this platform is built around — an append-only, reconciling record of every movement, with an audit trail over it. It is the word a regulator, an auditor and a finance team already use unprompted. It is a description, not a metaphor.
The candid part
What Ledgerfield is not, in one place
These appear throughout the site next to the features they qualify. They are collected here so nobody has to hunt for them.
Not built, not signed, not heldNo licensed casino content — the in-house titles are uncertified in-house mathematics, and the aggregator protocol is built but no supplier contract is signed. No live payment processor — a real driver implementation exists and is tested, none is connected. No KYC/AML vendor. No GAMSTOP integration. No live dealer. No operating licence in any jurisdiction. No RTS certification, no ISO 27001 audit, no SOC 2, no external penetration test. No operator in production, no traffic, and therefore no uptime figure.
The founding claim is not "we have arrived". It is that the hardest, least visible infrastructure is built and tested, and that everything in the list above is integration work against seams that already exist — not invention from zero. That is a smaller claim than the market usually makes, and it is one that survives contact with your technical due diligence.
FAQ
The questions we actually get asked
Are you licensed to take real-money bets?
No. Ledgerfield holds no gambling operating licence in any jurisdiction. Everything running today is play-money. Taking real-money bets from British consumers would require a Gambling Commission remote operating licence, RTS test-house certification, an ISO/IEC 27001 audit, AML and KYC provision, GAMSTOP integration, age verification and funds protection — none of which we hold or have completed.
Do you have live operators?
No. Ledgerfield is pre-launch. There is no operator in production, no production traffic, and consequently no uptime figure, no customer logo and no case study. We are not going to manufacture any of those, which is why this site has none.
What we do have is seven demo brands running on one instance of the real platform, against the real API, which you can open without an appointment.
Can we use our own front end?
Yes, and it is the path we would recommend if product is your differentiation. The API carries all 308 operations — the operator back office is itself a client of them. Of our seven demo brands, one shares no front-end code with the others at all and runs on the same backend.
One caveat worth knowing up front: system-bet permutation (Trixie through Lucky 63) is expanded in our widget layer rather than the backend, so a bespoke front end reuses that widget or re-implements the combination maths.
How does multi-brand actually isolate data?
The tenant is resolved per request, from an X-Tenant header or the request domain, and every brand-owned table carries a global query scope applied at the model layer. A brand's own staff cannot construct a query that leaves their brand — the scope is applied beneath them rather than by each controller remembering.
Sports fixtures, odds, results and currency rates are deliberately shared platform data, so a second brand does not double your feed cost. Everything a regulator would call customer data is brand-owned.
What does it cost?
£10,000/month flat, plus a configurable GGR revenue share denominated in basis points, invoiced monthly against real platform activity. New brands start on a 30-day trial automatically. There is no per-brand fee and no tier that gates the API or the compliance features.
Ask on the first call and we will give you the basis-point range rather than making you extract it over four meetings.
How long would integration take?
Honestly: we do not know, because we have never integrated an operator, and a vendor quoting you a timeline they have never actually met is guessing with more confidence than we are willing to.
What we can tell you is what the surface is — an OpenAPI 3.1 file describing every operation, generated from the routes — and you can have it before you commit to anything, so your own team can estimate it rather than taking our estimate.
What happens if we want to leave?
Your data is yours and reachable through the same API you integrate against — there is no export process gated behind an account manager, because the export is just the API. We would rather compete on whether the platform is good than on how painful it is to leave, and a platform that has to rely on the latter usually knows something about the former.
Who is behind it?
A small engineering team — small enough that on a technical call you will be talking to the people who wrote the code rather than to a solutions architect relaying questions. That is an advantage during evaluation and a genuine limitation if you need a 24/7 support organisation on day one. Both are true and we would rather say so.
Contact
Request a working demo
The fastest way to evaluate Ledgerfield honestly is to watch it run against its own API. Bring your integration lead and your compliance lead, and bring the questions this site did not answer — the ones specific to your licence conditions, your bonus logic and your brand count.
On the call, we will
Run the test suite from a clean checkout. Hand you the OpenAPI file. Walk the limits state machine, the segmentation fail-safe and the erasure refusal conditions in the code.
And show you
Seven brands on one instance, looking nothing alike, driven from one back office — then tenant isolation separately, in the back office, because the demo brands share a tenant and we would rather say so than let you assume otherwise.
And tell you
If you need certified content and a live PSP next quarter, that we are the wrong choice today. We would rather say it on the first call than the fourth.