See the whole market as it plays.
Live play from every operator and game provider, every casino floor and every game, watched by alert rules that put what matters in front of the right officer the same day.
Market monitoring
AlertsMonitoring officer
Payout below approved levelGames · approved 94.0%, as played 90.8%
NewExcluded players playingPlayer protection · matched by player token
NewWins larger than the bet allowsRevenue · tax at stake USD 9,660
LateWebsite not on the licenceMarket · m•••••n-win.club
Case openLive feedthe tape moves only when bets arrive
The problem
By the time a report arrives, the play is over.
A game paying out below the level it was approved at. A casino floor that didn't send its count. A website added without telling anyone. An excluded player back at the tables. Each one is visible in the data the day it happens.
Read a month later from a report, it's history. Read as it plays, it's something an officer can still act on.
How it works
From a bet to the right officer.
- 01The data arrivesOperators and game providers send play as it happens, over secured APIs. Casino floors send their daily counts.
- 02It's matched to the registerEach bet is tied to a licensed operator, a known website and an approved game.
- 03Alert rules runReady-made rules and your own, within the limits your office sets.
- 04An officer actsThe alert lands in the right in-tray, and becomes a case when it's a breach.
What's included
Online, on the floor, and on the operator's own site.
Live feedThe market as a trading floor: stakes, payouts, players' money and the tax they're building. A feed that goes quiet is flagged.
Alert rulesA library of rules, plus your own: drafted, tried out quietly on real data, then approved before they go live.
Casino floorsPremises, daily table counts, the machine register, and officers' own counts on the floor.
Games registerEvery game and its approved payout, matched to the feed. Unrecognised games are listed, not lost.
WebsitesSites an operator never put on its licence, and unlicensed networks, taken to blocking.
Test playYour officers bet on an operator's site with test accounts, and their bets are checked against the feed.
Used by
For the officers who watch the market.
Monitoring officersWatch the live feed and work the alerts in their in-tray.
InspectorsRecord their own counts and observations on the casino floor.
Compliance managersDecide which rules run, approve new ones and keep watch over the rest.
FAQ
About market monitoring.
How soon does play show up?
As soon as the operators' feeds send it. The live feed moves only when bets arrive, so a feed that goes quiet stands out.
Can we write our own alert rules?
Yes. A rule starts as a draft, is tried out quietly on real data so you can see what it would catch, and goes live once it's approved. Administrators can step in on any rule.
What happens when a game pays out less than it should?
The games register holds each game's approved payout. When the payout as played falls below it, an alert goes to the officer who looks after games.
Does it cover land-based casinos?
Yes. Each premises sends its daily table counts and keeps its machine register on the record, and inspectors can record their own counts to compare.
How do operators send their data?
Over secured APIs. Only senders your office has whitelisted can connect, and traffic passes through Cloudflare before it reaches the platform.
Watch your own market for three months.A pilot on your operators' own feeds.
Ask about a pilot