01 · Regulatory intelligence
What changed in the rule?
Tracks official and specialist regulatory sources, requirements, effective dates and impact. Best when legal/compliance teams need to understand obligations and change.
Buyer guide · iGaming compliance software
“Compliance software” is not one category.
An operator can buy excellent regulatory intelligence, AML/KYC tooling, safer-gambling operations and affiliate monitoring—and still lack repeatable proof of how a regulated product journey behaved after a release. This guide separates those jobs before you evaluate vendors.
Regulatory intelligence ≠ product QAAML/KYC ≠ browser behaviourEvidence ≠ legal certificationHuman review stays explicit
Four different jobs buyers often group together
The right stack depends on the question you need answered. These categories can complement each other; treating them as substitutes usually creates gaps.
02 · Operational compliance
What happened to a player or case?
KYC, AML, sanctions, safer-gambling and case-management systems evaluate identities, transactions, risk signals and interventions. These are player/account operations.
03 · Affiliate & marketing monitoring
What are partners saying or publishing?
Monitors affiliate sites, search, social, promotions and marketing claims. Strong when third-party promotion is the risk surface.
04 · Executable regulatory QA
What did the live product actually do?
Turns selected observable requirements into bounded browser/product checks, captures technical evidence, records a human review decision and monitors for later regression.
Where Lexsentra fits
You already know the requirement, but Product, QA and Compliance need the same reviewable evidence of the observable product state—and a way to know when it changes later.
You want first value from a URL, then controlled authenticated observation where appropriate, without turning the compliance workflow into a large integration project.
Lexsentra does not replace legal counsel, accredited test-house assurance, formal certification, AML/KYC engines or player-risk decision systems.
Observed, partial and not-observable states stay explicit. Automated evidence is an input to review, not a claim that a regulated product is “certified compliant”.
A practical evaluation matrix
| Question | Regulatory intelligence | AML/KYC/RG operations | Affiliate monitoring | Executable regulatory QA |
|---|---|---|---|---|
| Tracks rule/source changes | Core | Sometimes | Sometimes | Source-linked where mapped to controls |
| Evaluates player/account risk | No | Core | No | No |
| Monitors partner marketing | No | No | Core | No |
| Executes bounded product/browser checks | Usually no | Usually no | Usually no | Core |
| Captures point-in-time product evidence | Requirement evidence | Case/transaction evidence | Marketing evidence | UI/network/screenshot evidence |
| Detects behaviour regression after release | Not the main job | Not the main job | Marketing-change focus | Core |
| Requires human interpretation | Yes | Yes | Yes | Yes—kept explicit |
Category descriptions are functional, not claims that every vendor in a category has or lacks the same capabilities.
Why product QA belongs in the compliance stack
The UK Gambling Commission’s gambling-software guidance asks, among other control questions, who is responsible for product functionality and acceptance testing and who is responsible for quality assurance / regulatory compliance testing. It also distinguishes gambling-software testing from broader business tooling. That makes the handoff from “we know the requirement” to “we tested the product behaviour” an operational responsibility in its own right.
Official UK Gambling Commission guidance: What is gambling software? · See the 30 September RTS 12B evidence checklist
Evaluate the evidence loop, not just the dashboard.
For one UK surface, ask: what requirement is being tested, what exactly is observable, what evidence is retained, what remains inconclusive, who records the review decision, and how a later regression is detected.