CATALOGUE PATROL — full-portfolio coverage, on your schedule

Every game on your shelf,
checked on rotation.

Catalogue Patrol sweeps your whole portfolio — or any slice of it — on a configurable rhythm, so the long tail of titles beyond your top earners stays healthy too. Catch silent breaks in games nobody reports until it's already cost you.

Any scale
From 100 titles to your full catalogue
Weekly
Default cadence · fully configurable
Scoped
By provider, release date, or custom list
0
Integration needed
catalogue-patrol · live sweep
!
!
!
SAMPLE · 40 OF 412 TITLES
Catalogue sweep in progress
3 titles failed · 2 degraded · 35 passing — grouped by provider & root cause.
scoped by
Provider Release date Custom list Whole portfolio
how a sweep runs
  1. 01
    define the scope
    portfolio · providers · lists
  2. 02
    rotate through titles
    parallel devices, many geos
  3. 03
    flag what broke
    grouped by provider + fault
what you get
  • every pinned title
    no sampling gaps
  • grouped by root cause
    one ticket, many games
  • weekly portfolio digest
    health trend over time
What Catalogue Patrol does

Full-shelf coverage for the games nobody escalates until it's too late.

Catalogue Patrol rotates through your whole portfolio — or any slice of your catalogue you define — so the long tail of titles doesn't rot silently between releases. Every game gets checked on a cadence you set, with the same real-device, real-geo treatment as your headline titles.

Sweeps whatever scope you pick
Your whole catalogue, specific providers, titles released in the last 30 days, or a hand-picked list. Change the scope anytime.
Real-device check on every title
Every title is opened on your casino, rendered, and spun — not just pinged. The long tail gets the same treatment as your headline earners.
Runs on a cadence you choose
Weekly by default. Tune it daily, bi-weekly, monthly, or on release — per-scope. Catch drift without drowning in noise.
Groups failures by root cause
300 broken games often trace to one provider config. We cluster failures so you escalate one ticket, not three hundred.
Digest, not dashboards to babysit
A portfolio health digest after every sweep: trend, new breaks, recovered titles, grouped evidence bundles — ready to forward.
How it works

Three steps. Define, sweep, digest.

Point Catalogue Patrol at a scope of your choosing. We handle devices, geos, scheduling, clustering, and reporting — you get a digest after every sweep.

01

Define the scope

Pick what to patrol: your entire catalogue, titles from specific providers, games released in a time window, or a custom list. You can run several scopes in parallel, each on its own cadence.

  • Entire portfolio on rotation
  • By provider / aggregator
  • By release date range
  • Any hand-picked title list
02

We sweep, weekly by default

Weekly is the default cadence — adjustable to daily, bi-weekly, monthly, or triggered on release. Each title is loaded, rendered, and spun on real devices from real geos.

  • Parallel execution across many devices
  • Rotate geos per scope
  • Trigger on release or on-demand
03

Get a portfolio digest

After each sweep, a digest lands in your inbox and your tools: what's healthy, what's new-broken, what recovered, grouped by root cause and provider, with evidence bundles ready to forward.

  • Clustered failures by root cause
  • Provider-scoped evidence bundles
  • Webhook / Slack / Teams / Jira
Scope & cadence

You pick what to patrol. We match it to the right cadence.

Run one scope or several at once. Each has a sensible default — all of it adjustable the moment your priorities change.

01
Entire portfolio
Every title in rotation — the baseline sweep.
Default cadence
Weekly default
02
By game provider
All titles from one or more suppliers — post-integration.
Default cadence
Weekly
03
By release window
Anything added in the last N days — post-launch window.
Default cadence
Daily hot period
04
Long tail only
Everything outside your top 50 earners — the silent risk.
Default cadence
Bi-weekly
05
Custom list
Hand-picked titles or compliance audits — your cadence.
Default cadence
On release triggered
Every cadence is a slider, not a contract. Daily, weekly, bi-weekly, monthly, or triggered on your deploy hook — swap any scope's cadence between sweeps. No replatforming. No downtime.
Why you need this

Four reasons the long tail is worth watching.

Top 50 monitoring protects your revenue today. Catalogue Patrol protects your revenue tomorrow — and your audit story whenever the regulator asks.

01
The long tail rots quietly

The game nobody plays this month is the one broken for six.

A title outside your top 50 can sit broken for months — no ticket, no support call, no obvious spike. Then a promo campaign drives traffic to it, and the black screens land in front of exactly the players you paid to acquire.

02
Provider drift at scale

One provider config breaks 200 games at once.

Aggregator rotations, certificate rollovers, SDK bumps — one change upstream can take down an entire catalogue from one supplier. We cluster by root cause so you escalate one ticket, not two hundred.

03
Post-release reality check

Catch what slipped through before the review cycle does.

New build, new deploy, new CDN hash — games that passed on staging can fail in production against your real player's device and region. A release-triggered catalogue sweep closes that gap the same day.

04
Compliance coverage

Prove the whole shelf was exercised, not just the front row.

Regulated markets ask hard questions about operational oversight. A weekly sweep across your whole portfolio produces the audit trail — video, logs, pass/fail history — without any extra work from your team.

What lands in your inbox

A portfolio digest, not a dashboard to babysit.

Every sweep ends with a digest — what broke, what recovered, grouped by root cause. The dashboard is there if you want to drill in, but you rarely have to.

Weekly Catalogue Patrol · Casino C · week 16

412 titles swept · 3 failing · 2 degraded · 407 healthy · +2 recovered vs. last week
● 3 NEW INCIDENTS
State
TitleProviderNote
Failing
Lucky Rush 7 Rainforest Studios Resource 404 — 11 titles affected
Failing
Forest Fortune Rainforest Studios Resource 404 — same root cause
Degraded
Neon Reels 9000 NeonReels Load time 8.4s in DE, edge node flapping
Healthy
Gold Mine Deluxe Pickaxe Gaming Recovered since last sweep
Healthy
Royal Tiger Orient Studio Healthy · 4 weeks green
Incidents grouped by root cause → 1 cluster (Rainforest Studios CDN rollover). One escalation, eleven titles fixed.
Put it on patrol

See your real issues before they cost you.

Get your first results in days — no SDK, no integration, no contract.

Your whole shelf, on rotation

Patrol every game you offer — not just the front row.

A 20-minute demo on your real catalogue. No slides. Just your games, sweeping on our devices.