Admin, reporting & operations
The back office is a client of the API, like everything else.
Dashboard, players, withdrawals, trading, settlement, games, promotions, jackpots, tournaments, campaigns, segments, automations, affiliates, staff, webhooks, billing and the audit log — every screen backed by an operation you can call yourself.
Reporting
Regulatory returns are generated, not assembled
The operator return and the player activity statement are services in the platform. That matters at exam time: a return produced by a code path is reproducible and consistent, and a return produced by a quarterly spreadsheet exercise is neither.
Operator return
Aggregate regulatory reporting generated from the ledger itself, so the numbers in the return and the numbers in the wallet cannot diverge.
Player activity statement
A per-player statement of stakes, wins, deposits and withdrawals — the artefact a regulator or an ombudsman asks for by name during a dispute.
The audit log
Who did what, to which record, when, and why. Back-office writes are captured by default rather than per-endpoint, which is the only version that stays complete.
Running it
Operational surfaces built before they were needed
Health with a scheduler heartbeat
The health endpoint reports degraded when the scheduler stops updating its heartbeat — because the failure that actually hurts is not the API going down loudly, it is the settlement job silently stopping while every page still returns 200.
Webhooks
Outbound webhooks with per-brand configuration, so an operator's own systems react to platform events instead of polling for them.
Platform billing
Plans carry a monthly fee and a revenue share in basis points; invoices are generated monthly against real activity. We bill our own customers through the platform rather than through a spreadsheet.
Publishing
A publish path pushes a brand's static front end to the CDN, which is how a static-export customer site stays a one-action deployment rather than a build pipeline somebody has to own.
What operations does not includeThere is no bundled BI or data-warehouse export beyond the reporting endpoints, no on-call or 24/7 support organisation — Ledgerfield is pre-launch and small — and no uptime figure, because there is no production traffic to measure one from. An operator who needs a contractual SLA today needs a conversation about what we can actually commit to, not a number from a slide.
Ask for the ugly screens.
Anyone can demo a dashboard. Ask to see the audit log, a failed withdrawal, and a settlement that had to be corrected — that is where a back office is actually judged.