DEMO TENANTOperator-side data (staff, contacts, calendar, training, grants, complaints, SAR, four-eyes reviews) is illustrative — not a real Greentube record. Connector output, evidence-ledger anchors, RFC 3161 timestamps, Postgres RLS, regulator-source ingestion and LLM extractions are the real machine. Rows marked demo are seeded fixtures.
Georg Gubo
MGA · UKGC · ADM · RO-ONJN · SK-MFSR · DGOJ · GGL · SPI · NJ-DGE · MI-MGCB · PA-PGCB

Game compliance

Cross-reference between currently-offered games and regulator-approved whitelists · OP-GREENTUBE— API /operators/OP-GREENTUBE/game-compliance/exceptions?jurisdiction=sk-mfsr returned 400
Jurisdiction:allmgaukgcadmro-onjnsk-mfsrdgojgglspinj-dgemi-mgcbpa-pgcb
Offerings scanned
0
across SK-MFSR
Unapproved
0
offered without regulator approval
Cert invalid / expired
0
missing or expired test-house cert
Cert expiring (30d)
0
ramp re-test now
Certs on file
0
—
Exceptions (0)Cert calendar (0)

Exceptions (0)

No game offerings on file yet — the daily catalog sync populates this once a PAM is connected.

How this works

KURAL syncs your PAM's game catalog daily into OperatorGameOffering. The regulator whitelists (UKGC RTS-tested games, MGA approved-supplier list, ...) populate GameJurisdictionApproval. The cross-reference engine flags any (offering, jurisdiction) pair without a corresponding approval as unapproved, missing/expired cert as cert_invalid, and certs expiring within 30 days as cert_expiring_soon. High/critical exceptions auto-route to your Jira project via the existing ticketing bridge.