Responsible gaming
that actually works.
Deposit limits. Self-exclusion. Risk monitoring. Affordability. National registry checks. Virtus delivers the player-protection stack as a single REST API — available today in seven European markets — so your engineers can stop building compliance tooling and start building product.
No commitment. We'll reach out when early access opens.
Available today in seven European markets.
We only list markets where operators can use Virtus right now, without waiting on any supplier licence or software approval on our side. Where a market requires one, it's on the roadmap — not on this list.
NetherlandsGermanyFranceSpainAustriaResponsible Gaming services onlyPortugalOutside regulated gambling software scopeLuxembourgOn the roadmap: Malta, Romania, Sweden, Denmark, Belgium, and Italy require a B2B supplier licence or software certification we don't yet hold. We take a conservative view — those markets open only once the relevant approvals are in place.
Compliance tools shouldn't be your problem.
Every licensed operator needs the same things: deposit limits, loss limits, self-exclusion, session controls, affordability checks, and a way to monitor at-risk players. None of this is unique to your business. It's table stakes — but it still takes months to build properly, and every market does it differently.
Most teams end up with internal tools that pass the initial compliance review and then quietly rot. Someone on your engineering team knows exactly which spreadsheet tracks the manual exclusion requests. Every audit is a small fire drill.
The alternative isn't to buy a bloated enterprise suite. It's to treat responsible gaming as infrastructure — the same way you treat payments or authentication. You don't build your own payment processor.
"Player protection requirements aren't going away in any EU market. The question is whether you want to maintain that code yourself for the next ten years."
each with its own player-protection rules — Germany's cross-operator deposit caps, Dutch registry checks at login, French affordability thresholds. Virtus maintains them all as configuration, not code you own.
endpoint to call before a deposit or wager processes. Virtus returns allowed: true or allowed: false with the reason.
player data shared between operators. Every tenant runs in an isolated database schema. Your player records are yours.
Everything your regulators
require. Nothing extra.
We built Virtus by reading the player-protection directives of Europe's regulators — GGL, KSA, ANJ, DGOJ and more — and writing down what each one actually requires in code. These are the results.
Hard limit enforcement
Deposit, loss, wager, and session-time limits enforced before a transaction processes — not logged after the fact. Your payment flow calls us first. We decide. Mandatory-limit and cooling-off rules per jurisdiction are built in.
Pre-transactionExclusion network + registry checks
Cross-operator self-exclusion propagates network-wide in under a second, with a reactivation workflow for expired cooling-off periods. A common adapter interface checks national registries where applicable — e.g. Germany's OASIS, the Netherlands' CRUKS — with new markets onboarded behind the same interface.
Cross-operatorRisk & affordability monitoring
Behavioural signals — deposit frequency, withdrawal reversals, payment churn, complaints — feed real-time risk scores. Affordability thresholds and reality checks trigger per-jurisdiction, with age-tiered limits for younger players.
Real-timeCompliance reporting & audit trail
Regulator-ready report aggregation, compliance-gap detection against each market's baseline, and an always-on audit log of every limit, exclusion, and enforcement decision. Exportable per operator.
Audit-readyEnterprise-grade foundations
Schema-isolated tenancy — Operator A cannot query Operator B's records by architecture, not just policy. MFA for portal users, scoped API keys with rotation, rate limiting, and GDPR tooling: export, erasure, retention scheduling.
Data isolation · GDPRUp and running in days, not months.
The API is deliberately simple. If you've integrated a payment gateway before, the pattern will be familiar.
Register your operator
A single POST request creates your account and provisions your isolated tenant database. You get an API key back. That's it.
POST /v1/operators/register
Add two enforcement calls
Before every deposit and every wager, call the matching enforcement endpoint with the player ID and amount. We return allowed or blocked with the reason.
POST /v1/enforcement/deposit
POST /v1/enforcement/wager
Wire up limits & webhooks
Your product calls our API when players set limits or self-exclude — every change is enforced immediately. Your compliance team gets the operator portal, and your backend gets webhooks on high-risk signals and network exclusion events.
POST /v1/players/{id}/limits
Three types of operators
who find this useful.
We're not trying to be everything to everyone. Here's an honest look at who Virtus is actually built for.
Operators preparing a licence application
You need responsible gaming tools that pass a compliance review before launch. Building them yourself delays your go-live. Virtus gets you there faster with tools that are already documented for audit purposes.
Right fit if your engineering team would rather not own compliance tooling long-term.
Operators who've outgrown their in-house tools
You launched with something homegrown, it mostly works, but every regulator guidance update means another sprint. Migrating to Virtus moves maintenance off your team's plate permanently.
Right fit if someone on your team spends meaningful time on responsible gaming tooling you'd rather outsource.
Multi-market operators expanding across the EU
Every new market means a new rulebook — deposit caps, registry checks, reality-check intervals, reporting formats. Virtus carries the per-market rules so market entry is a configuration change, not a rebuild.
Right fit if you operate (or plan to operate) in three or more regulated EU markets.
Get early access.
We're working with a small number of operators ahead of general launch. No commitment — just tell us a bit about where you are, and we'll reach out when we're ready to bring you on.