How it works

This is how the patrol plays.

What happens in one run, the evidence it leaves behind, and the few things we need from you.

One run, step by step.

The patrol is a loop of short runs. Here is what happens in every single one.

  1. 1Sign in like a playerPlayPatrol logs in with real user credentials, just like a real player.
  2. 2Pick the next targetThe game, flow or bet that is due in this cycle.
  3. 3Play it for realSpins the reels, places bets and follows the journey a player would.
  4. 4Judge the screenComputer vision reads what actually renders: did it load, play and pay out?
  5. 5Record everythingVideo, screenshots, console logs and network traces. On every run.
  6. 6Classify the runOK or FAIL, with the cause in plain words.
  7. 7DeliverA fail fires an alert with a forwardable run page. Clean runs land in your dashboard.
PlayPatrol Agent in action

Real steps. Real screenshots. Real verification.

1Login
Step 1: Login
✓ OK
2Open Lobby
Step 2: Open Lobby
✓ OK
3Launch Game
Step 3: Launch Game
✓ OK
4Play & Verify
Step 4: Play & Verify
✓ OK
5AI Verification
Step 5: AI Verification
✕ FAIL
6Result
Step 6: Result
✓ OK
Fail
detected
Balance mismatchExpected: €125.00Actual: €100.00
View full run
VideoScreenshotsLogs
Recorded run of a failing game session.
00:24 / 00:35
PlayPatrol DashboardLast 24h
Tests today12,645
Passed12,125
Failed520
Success rate95.9%
Recent failuresView all failures →
  • Book of DeadBalance mismatch2 min agoView run
  • Sweet BonanzaGame freeze8 min agoView run
  • Legacy of DeadBonus not triggered15 min agoView run
24/7Non-stop monitoring
100%Real player journeys
Every run recordedVideo, logs, screenshots
SecondsFrom issue to alert

No test scripts to write or maintain. The standard patrol library configures itself to your games and flows. When a title changes, the patrol adapts.

You get the facts, not surprises.Every run. Every game. Every time.

Here is a real one.

Inside every run page: video of the full run · annotated screenshots · network traces · root cause + reproduction steps.

Delivered where you work:

And a dashboard with trends.

Zero to get value. More only ever adds.

Level 0: a URLThe quickest way to start.
You give
A link and a list of titles. No account, no integration.
The patrol can check
From day one, the patrol checks that every game and flow you list opens, loads and plays at all.
Level 1: a test accountRecommended. This is where the patrol does its best work.
You give
A login and password for a test user, with test money we never withdraw.
The patrol can check
How your product really behaves for a signed-in player with a balance: bets, bonuses and cashout journeys included.
Never real money. Never a real withdrawal.
Level 2: a source of truthFor advanced needs. Often custom work, built together by your team and ours.
You give
Any source of truth you can share: a list of expected games, a dictionary, an endpoint. By mail or by API.
The patrol can check
The patrol checks the screen against it: games that should be live are live, translations match the dictionary, and what your backend promises is what players get.

Setup and maintenance are on us. No level is ever a condition to start.

We go everywhere. We touch almost nothing.

Where the patrol plays

Real devices in every market you operate in. Every combination of geo, language and currency, played the way a local player would.

Any geo on demand: a country, a US state, a Canadian province, a German Land. Don't see your market? We add new geos in days, not quarters.

What it never touches
  • Real money: the patrol plays only on the test funds in its account. There is nothing we could withdraw or cash out.
  • Your codebase or your full math model: you share what a test needs, nothing more.
  • Player data: the patrol plays its own test account and nothing else.

Built by createIT: in software since 2004, in iGaming since 2015.

About PlayPatrol & createIT →

Questions your team will ask.

How do you handle false positives?

Every finding carries the video of the exact run. A human can verify a flag in seconds, so alerts stay actionable instead of noisy.

How often do you run?

Cadence is yours to set, per scope. Each core patrol has its own default: daily for casino titles, every 48 hours across operator networks, around the clock for sportsbook builds. You can tighten it for the titles or events that matter most. Alerts fire the moment a run fails.

What happens when you find an issue?

An alert fires the moment a run fails: e-mail, Slack, Teams and more. Every alert links a forwardable run page with the video, the logs and the cause in plain words.

Will the patrol pollute my analytics or RG controls?

Runs use test accounts you control and flag, so sessions can be excluded from analytics and player-protection tooling on your side.

What about the credentials you hold?

A login for a test user with virtual funds and limited access. Never real money, never a real withdrawal, never player data.

Which technologies do you support?

Any technology that renders on screen. HTML5, Unity and native are everyday examples: if players can see it, PlayPatrol can play it. New games join the patrol without custom scripting.

How does the patrol learn a game it has never seen?

Our models have played thousands of games and recognise the spin button, the reels and the balance on titles they meet for the first time. When a game is unusual enough to need teaching, our engineers handle that on our side.

What if a game provider tries to block automation?

Some try. So far their measures have slowed the patrol down, never stopped it. If a provider ever blocks us for good, you hear it from us first, not from a gap in your reports.

Can you play from the exact jurisdiction a licence covers?

Yes. Runs go through real local egress in the jurisdiction you name: a US state, a Canadian province, a German Land. If a market is missing, we add it on demand.

Start patrolling your games.

A link and a list of titles is enough. Your first report comes from the very first run.