Run it yourself,
or let us run it.
Two models
One codebase.
Two ways to run it.
Model 01 · you run it
Self-hosted
Run it in your own cluster, on your own cloud or hardware, isolated from everyone else.
- Your cluster, your cloud or your hardware
- Physically isolated from everyone else
- Upgrades on your schedule
Model 02 · we run it
Hosted white-label
Multi-tenant by design: each operator has its own brand, games and rules, the licensor console runs the tenants, and Multi-brand adds further brands over one set of players. A managed service run by us is on the roadmap.
- Your brand, your games, your rules
- Region pinning for data residency
- One console for licences, fleet and billing
- Who runs it
- Self-hostedYou, on your own Kubernetes
- Hosted white-labelWe do, on our infrastructure
- Where
- Self-hostedAny cloud or your own hardware
- Hosted white-labelOur clusters, pinned to the region you need
- Isolation
- Self-hostedPhysical: one deployment, yours alone
- Hosted white-labelLogical: every record, actor key and query carries your tenant, and isolation tests prove it
- Brand, games and rules
- Self-hostedYours, set from your back office
- Hosted white-labelYours, set from your back office
- Liquidity
- Self-hostedYour own player pool
- Hosted white-labelYour own pool
- Upgrades
- Self-hostedWhen you choose; servers drain before they stop
- Hosted white-labelRolled out by us, scheduled per operator
Licensor console
Every operator.
One console.
The console is the only component that sees across licensees, through a separate identity realm, and every cross-licensee read is audited with its reason.
Licences and entitlements
A signed licence — modules, markets and their modes, deployments, capacity and commercial terms — decides what each operator runs. The console issues, renews and revokes it, and a licence that ends winds down gently: running games finish and withdrawals always work.
Usage metering
Net gaming revenue is metered from the books by market and mode, the licence's bands applied, into a signed, chained monthly report. The console takes reports in, verifies them and produces statements and an accounting export.
Fleet operations
Each deployment's version, modules, health and capacity from its telemetry, with upgrades scheduled and tracked, and incidents with their severities and service levels.
Risk sharing, opt-in
Licensees who sign a data-sharing agreement exchange hashed indicators through the console; a match raises an integrity alert in the licensee's own queue.
What's included
The whole platform.
Not a starter kit.
How it works
From first look to first hand.
01
Demo
A live walkthrough of the engine, the back office and a running cluster, shaped around your markets and games.
02
Technical deep dive
Your engineers with ours: the protocol, the admin API, the adapters, security and deployment, in as much depth as you need.
03
Pilot
The platform running in your cluster or ours, with your brand, games and rules, tested against your own requirements.
04
Go-live
Your vendors connected, your jurisdictions configured and your rooms open — with us alongside for the launch.
Questions
Before you ask.
Asked and answered.
What does it cost?
There is no price list: what fits depends on the model, your markets and the scale you plan for. Talk to us — a demo is the quickest way to a proposal built around your rooms.
Is the hosted version a different product?
No. Self-hosted and hosted run the same release: a self-hosted deployment is simply one tenant, and what each customer receives is decided by its licence, not by a fork. The platform you evaluate is the platform you run, whichever model you choose.
Who holds the gaming licence?
You do. The operating licence stays with the operator; the platform is built to be configured per jurisdiction and to enforce geofencing. The records, change control and per-market configuration your regulator expects are part of the platform.
Where can we run it ourselves?
AWS, Azure, a budget cloud or bare metal — the same release, step-by-step guides for each. Every workload, probe, autoscaler, disruption budget and network policy in one chart, with ready values for ingress-nginx, AWS ALB, Azure Application Gateway and the Gateway API, and a values file for each in-jurisdiction deployment.
Can we use our own payment, KYC and messaging providers?
Payments, identity, geolocation, sanctions, AML, self-exclusion, messaging and ads behind interfaces with contract tests — swap vendors without touching the game.
Is our data kept apart from other operators' data?
Self-hosted, it never leaves your cluster. Hosted: every aggregate, actor key and query carries the tenant, and two-tenant isolation tests prove one operator can never read another's data. Each operator is pinned to a region; one that needs in-country hosting gets a dedicated cluster from the same charts.
Can our players sit with other operators' players?
Not today: each operator keeps its own pool, on either model. Pooling players from several operators at the same tables, with rake shares settled between them. The design is written; nothing of it is built, and each operator keeps its own pool.
Which games and features are included?
The whole platform: every game, every tournament format, the ledger, the back office and the cloud packaging. Which of them each market offers is your switch, set per operator and per jurisdiction.
Talk to us.
Then see it deal a hand.
Tell us about your markets and your scale, and we will show you the platform running — and how either model would fit.