Built for teams that handle real money.
How the platform is put together, and what protects your players, your money and your data. Everything on this page is how the system works today.
Architecture
Protected edge
All traffic passes a protected network edge with attack filtering before it reaches the platform. Application servers accept traffic only from that edge.
One database per brand
Every brand runs on its own database. Staff of one brand can never query another brand's players.
Private management network
Servers are managed only over an encrypted private network; management ports are closed to the internet.
Daily full backups, stored apart
Databases are backed up every day and moved to a separate storage server.
Updates without downtime
A new version is started and warmed up with real requests before traffic moves to it; the previous version stays ready for instant rollback.
Watched around the clock
Automatic watchdogs follow memory, disk, response times and stuck jobs, and alert the team before players notice.
People and data
Permissions down to the action
Every page and endpoint is closed by default. Roles, personal extras and personal denials — a denial always wins.
Personal data masked on the server
Phone, email, ID, IBAN and address are masked before they leave the server for staff without permission. Exports of personal data are refused without it.
Two-factor login
2FA can be enforced for staff; repeated wrong passwords lock the account.
Everything leaves a trail
Admin actions, payment decisions and profile changes are recorded with who, when and what changed — including the old value.
Money and players
Two signatures for large withdrawals
Above a threshold you set, a withdrawal needs approval from two different staff members.
Withdrawal rules and automatic checks
Rules check every withdrawal; automation can approve, but never rejects on its own — a person decides.
Responsible gaming
Limits, time-outs and self-exclusion for players, and KYC review for your team.