Skip to content
iGaming Platform Provider
Confirmed named events

iGaming provider deployment evidence

Named platform migrations and launches with exact product, market, event, and relationship boundaries. A confirmed historical launch is never presented as a current deployment.

4 confirmed deployment records3 named relationships2 providersEvidence checked August 13, 2026 · Page updated August 13, 2026
Each row is a confirmed deployment event
Product scope, event date, deployment stage, and current relationship status remain separate. A confirmed event does not expand beyond its named product, market, or period.

Three separate axes

Event, deployment stage, and relationship state

Axis 1
Event type
The recorded event: selection, agreement, extension, migration, launch, current listing, or testimonial.
Axis 2
Deployment stage
Announced, in implementation, currently live, historical, or unknown.
Axis 3
Relationship state
Current, planned, ended, not confirmed after a historical event, or unknown.

Bounded event record

Confirmed deployment events

“Live” means a current production state. Historical events remain historical when current continuity is unknown. Product and market stay unidentified when the record does not establish them.

Confirmed historical event

4 confirmed deployment units.

Swipe horizontally to view all columns.
Confirmed historical event deployment records
Provider / counterpartyProduct / marketEvent / relationshipScope and boundaryCurrent statusRecord status
Altenar
EstrelaBet
Altenar sportsbook carrying Inspired V-Play Football Brazil
Brazil
Launch
Current status not confirmed
V-Play Football Brazil launched at EstrelaBet through the Altenar sportsbook on August 12, 2025. This product-and-event record does not establish current continuity, the rest of the operator stack, availability, performance, or provider-wide adoption.V-Play Football Brazil launched at EstrelaBet through the Altenar sportsbook on August 12, 2025. Current continuity, wider modules, availability, performance, and commercial outcomes are not confirmed.
Confirmed
EveryMatrix
bet-at-home
EveryMatrix turnkey platform
Malta-licensed .COM offering
Migration
Current status not confirmed
Confirmed event: outsourcing of the Malta-licensed .COM offering to EveryMatrix in February 2023. Current contract scope, product acceptance, service levels, and outcomes are not confirmed.The Malta-licensed .COM offering moved to EveryMatrix in February 2023. Current module scope, service continuity, availability, and performance are not confirmed.
Confirmed
EveryMatrix
bet-at-home
EveryMatrix turnkey platform
Germany-licensed .DE offering
Migration
Current status not confirmed
Confirmed event: completion of the Germany-licensed .DE migration in October 2023. Current contract scope, product acceptance, service levels, and outcomes are not confirmed.The Germany-licensed .DE offering completed its EveryMatrix migration in October 2023. Current module scope, service continuity, availability, and performance are not confirmed.
Confirmed
EveryMatrix
Szerencsejáték Zrt. (TippmixPRO)
OddsMatrix end-to-end digital sportsbook
Hungary
Launch
Current status not confirmed
Confirmed event: the Hungary OddsMatrix launch on October 25, 2023. The deployment record does not include the separate infrastructure, report-volume, event-volume, conversion, or outcome claims.The refreshed TippmixPRO platform launched on OddsMatrix in Hungary on October 25, 2023. Current service continuity, infrastructure, event volume, and outcomes are not confirmed.
Confirmed

Turn a logo into a reference check

Match the architecture
Confirm entity, product versions, modules, market, brand count, wallet/PAM, integrations, hosting, managed services, and migration scope.
Match the operating scale
Use active players, transaction and bet volumes, content, payments, currencies, environments, support model, and peak events—not a global client count.
Ask for evidence
Request current customer confirmation, acceptance output, incident and SLA samples, change history, reconciliation, staffing, and unresolved limitations.
Separate outcome from attribution
Revenue, retention, margin, or launch-time results need a baseline, period, method, denominator, confounders, and permission to attribute them to the supplier.
Check the present state
Verify that the relationship and named products remain live now; a 2022 launch does not establish the current architecture.
Cross-check approval
Map the same legal entities and product scope to current credentials. A deployment does not substitute for supplier, operator, or product approval.

Deployment evidence questions

Is every row a current live platform deployment?

No. Confirmed historical migrations and launches stay historical unless current production continuity is also established. Event and relationship status are separate fields.

Which deployments are published here?

Each row is a confirmed named event with matched provider, product, market, event, and relationship scope. Records without event-level confirmation are excluded.

Why can a past launch have an unknown current relationship?

A confirmed launch event does not establish that the same contract, modules, markets, or production state remain current years later.

Does a deployment prove the supplier is licensed for that market?

No. Deployment and credential evidence are separate. Verify the exact supplier and operator entities, credential types, product approvals, terms, and market status independently.

Does a named deployment prove performance or ROI?

No. It does not prove uptime, launch speed, retention, revenue, margin, support quality, catalogue breadth, or applicability to another buyer. Those need scoped evidence and reference diligence.