Players and verification
One record per player carrying account state, compliance tier, verification status and the documents behind it.
One portal per casino
Players, staff, games, payments, audit and compliance, branding, domains and settings. One of these per brand, not one console with a brand switcher.
What the portal actually holds
Every panel below is a capture of the running platform, taken from the demo tenants.
Games and the catalogue
Studio visibility, hidden titles and collections, with catalogue coverage kept separate from lobby coverage so you can always see the difference.
Audit and compliance views
Every action by every player, staff member and system in one searchable stream, with the actor, the role, the location and the device attached.
Branding, domains and settings
A complete brand look from two colours, the domain it runs on, and the settings behind both, changed without waiting for a release.
Screenshots are captures of the demo tenants MaxBet and LuckyOni. Every figure on screen is demo data.
Staff join by invite and get exactly the permissions the job needs
A payments reviewer does not inherit the ability to change branding, and a marketing user does not inherit the ability to approve a withdrawal.
Invited by email, scoped by role
A new colleague is added from the portal rather than by raising a ticket with us.
Permissions down to the individual action
A role grants exactly what the job needs and nothing beside it.
Every permission change is itself audited
When a regulator asks who could have done a thing on a given date, the answer is a query rather than an argument.
What an operator changes without a developer
Application to live casino, and every change after launch, without an engineering team on your side.
Change how the brand looks
Colours, logo, layout and page content, previewed in draft and published in one click.
Add or correct a language
Every player-facing string is editable in the portal and publishable without a release, with fallbacks behind it.
Open or close a studio
Turning a studio off removes its titles from the lobby immediately and leaves the integration in place, so the decision is reversible.
Invite a colleague
A staff member joins by email and receives a role scoped to the work they actually do.
The portal, recorded rather than described
Eight walkthroughs taken in the running platform. Nothing here is a mock-up.
Players
Manage the player lifecycle. Account state, compliance tier, verification status and the audit history of every check.
Players: Manage the player lifecycle. Account state, compliance tier, verification status and the audit history of every check.
Questions about running the portal
Every withdrawal goes to a person, with the context already assembled: the player's compliance tier, verification state, deposit history and any screening result, shown next to the amount requested. The reviewer approves, holds or escalates, and the decision joins the audit trail with its reason.
It is deliberately not automatic. Paying out is the irreversible action in a casino. The audit trail then shows the request, the approval, the processing and the payout as separate events.
Yes. Evidence packs are built from the platform wide audit trail and produced from the back office rather than from a database query.
Because the trail records player, staff and system actions in one stream, with the actor, the role, the location and the device attached, assembling the record of one player, one period or one control is a report rather than a project. Your compliance officer can run it without waiting for an engineer to be free.
What this page covers in the feature matrix
Each capability below is a row in the platform index, where its tier sits beside the method and the date behind it. Read the full feature matrix.
Back-office portal
One portal per casino covering players, staff, games, payments, audit and compliance views, branding, domains and settings.
Role-based staff access
Staff join by email invite and receive precisely scoped roles, down to individual permissions.
Dynamic translations
Operators edit and publish translations themselves, with automatic language fallbacks. New languages and copy changes ship without developer support.
Watch the back office before you take our word for it
The demo centre holds the same eight recordings with no form in front of them.
The recordings play without an email address.
