Game-protection platform

Integrity,
measured.

Edge and probability, measured for every bet on the table. So your shift knows what the tables are actually doing.

INPUTShoe ledgerINPUTHand logINPUTSide-bet CSVSTATISTICAL ENGINE01Player / house edge02Pair-wise wager ρ03Composition-edge drift04Plain-English summary05Evidence packOUTPUTFlagged sessionsOUTPUTReport PDFOUTPUTNetwork graph
Every bet on the table

Main game, every side bet, every player — one session.

Two paradigms of proof

Outcomes vs expectation. Wagers vs edge. Both watched in parallel.

Composition-dependent side bets

The bets counters can't mentally count. Where advantage play hides.

Any equipment, any brand

Manual entry, CSV, or paste. No hardware lock-in.

Three ways to watch a table

What your team is actually watching for.

01

Outcome integrity

Did the table pay out what probability says it should? Every outcome — pocket, shoe, side bet — compared to theoretical, with confidence intervals.

02

Wager–edge correlation

Does the bet size track the edge? A silent pattern hardware misses and mental counting can't catch on composition-dependent side bets.

03

Player-network intelligence

Pull any player into a graph. See shared sessions, tables, tags, and operator links. Attach events, notes, and locations. Investigate networks without leaving the app.

Side bets

Composition-dependent side bets.

Every card entered, every hand reconciled against composition. Edge–wager correlation per player catches the bets that rise when the edge does — the advantage play mental counting can't scale to.

BJ-12 · Perfect Pairs · 30 hands
Edge curve vs player wagers
P-14 tracks edge
+1%0−1.5%HOUSE EDGE$0$1501HAND #30
EDGE
P-07 WAGER
P-14 WAGER
Baccarat

Shoe integrity, coup by coup.

Running player and banker edge against theoretical over the life of a shoe. Composition drift and side-bet edge exposure, surfaced before the session closes. Big Road, Bead Plate, and derived roads reconcile to the stats.

BAC-03 · 8-deck shoe · 60 coups
Running z-score across the shoe
P-31 crossed alarm
REVIEWALARMCRITICAL+20−1−2−3−4Z-SCORE1COUP60
P-22
P-07
P-31
Wheel Bias

Roulette wheel integrity.

Per-pocket hit frequency vs chance, chi-squared goodness-of-fit, and a PDF report maintenance can act on. Hardware-agnostic.

Wheel 7 · 14 days · 3,742 spins
Per-pocket z-score radar
Pocket 17 flagged
091726z=0±2±3
WITHIN TOLERANCE
REVIEW
FLAGGED
Shipping next
Dragon Bonus (Baccarat)Super 6 / Tiger (Baccarat)Dragon 7 / Panda 8 (Baccarat)Player-winnings paradigm (Roulette)Signed evidence packs (compliance)
How it works

Enter, analyse, investigate.

One flow, three products. The shift enters what it sees, the platform measures it against chance, and the evidence comes out the other side.

01
Enter
Manual hand entry, batch paste, or CSV/XLSX import. Per hand for Pairs, per coup for Baccarat, per spin for Wheel Bias. Players are operator-defined codes — no names required.
02
Analyse
Dashboards compute live as data flows. Edge curves, running z-score, per-pocket frequencies, composition tracking, road plates. Every readout carries a Wilson 95% confidence interval.
03
Investigate & export
When something trips a threshold, the player-network graph pulls a thread across sessions. Out: PDF reports and CSV.
Get started

See what your tables
actually did.