iGaming Platform Back Office Comparison

PAM / operator control plane

The tracked surface includes player-account or back-office control. Managed services remain a separate scope, and exact permissions are product- and deployment-specific.

Yes

GamMatrix is now EveryMatrix Platform.

Yes

Marketing, affiliate, CRM, VIP, product, payments/fraud, UX, safer gambling, and 24/7 customer support are available modularly.

Role-based per-application access

Unified Access Control manages access to individual back-office applications and configurations.

Yes

Yes

System and user actions on player records are tracked.

Yes

PAM supports player tagging, batch processing, segmented campaigns, and bulk operational actions.

Yes

Wallet adjustments are available for reconciliation and established abuse.

Yes

Payment/risk tooling supports transaction review, holds, KYC/AML checks, and operator workflows.

Yes

Yes

Rules, alerts, role-based actions, manual review, and Bonus Guardian restrictions are supported.

Yes

Yes

Support teams get player profiles, transaction monitoring, game replays, limits, account history, and managed-service workflows.

Yes

Yes

Payments and risk modules provide real-time monitoring and rule-based fraud alerts.

PAM / operator control plane

The tracked surface includes player-account or back-office control. Managed services remain a separate scope, and exact permissions are product- and deployment-specific.

Yes

Yes

Role-Based Access Control

IMS is run by around 11,000 admin users across partner companies through 600-plus back-office interfaces, so access is split by role. The exact permission granularity remains partner-gated.

Yes

Yes

Yes

Yes

Yes

Withdrawals can be configured with periods and limits, and deposits/withdrawals trigger fraud checks before processing.

Yes

Yes

Real-time fraud detection runs through the Featurespace ARIC engine built into IMS, which flags deposits, withdrawals and account changes for review.

Yes

Yes

Yes

Yes

PAM / operator control plane

The tracked surface includes player-account or back-office control. Managed services remain a separate scope, and exact permissions are product- and deployment-specific.

Yes

Yes

Optional add-on covering first-line support, anti-fraud, VIP, retention, reactivation and content management.

Role-based, multiple permission levels

Yes

Unresolved

The back office contains game and player activity history. A dedicated admin action log remains unresolved.

Yes

The bonusing module supports issuing bonuses and auto-generating banners and rules across the player base. Bulk player edits beyond bonusing remain unresolved.

Yes

Yes

Operators accept or cancel payment requests from the back office.

Yes

Yes

Integrated anti-fraud system with automated triggers. Deeper case investigation is largely handled through the optional Managed Services anti-fraud team.

Yes

Back office gives a full view of player accounts plus real-time filtered reporting on bets, bonuses and balances.

Yes

Back office handles player accounts, balance corrections and document checks. Staffed first-line support agents come through the optional Managed Services tier, not the core tooling.

Yes

Payment requests can be accepted or cancelled and admin access is tiered by permission level. A general configurable multi-step approval engine is not established.

Yes

Automated triggers fire on suspicious or fraudulent activity with customizable settings. Broader configurable operator notifications remain unresolved.

PAM / operator control plane

The tracked surface includes player-account or back-office control. Managed services remain a separate scope, and exact permissions are product- and deployment-specific.

Yes

PAM is the company's core product. The platform is built around the player account, wallet, CRM, bonus, payments and KYC/AML tools.

No

24/7 support, onboarding and dedicated development are offered, but no current end-to-end managed B2C operations or standard managed-hosting product was established.

Role-based permissions for platform administration

Role-based access control is included; exact role matrices are deployment-specific.

Yes

Multi-user role-based administration is included.

Yes

The platform specification includes administration audit logs; Data Lake lineage is a separate control.

Unresolved

A general bulk-operations toolkit is not established.

Unresolved

Wallet and account control are established; a specific manual-adjustment workflow remains unresolved.

Unresolved

Payment rules and limits are established; a native human approval workflow was not.

Partial

Core KYC controls and integrations are present; native case-management depth remains unresolved.

Partial

Core fraud rules and integrations are present; native case-management depth remains unresolved.

Yes

The 'Player Account' module gives a complete, global real-time view of the player journey for support/ops teams.

Yes

The PAM provides a complete global player view, transaction history, wallet and account controls for service teams.

Unresolved

No general configurable approval-workflow engine was established.

Unresolved

Real-time data is established, but a general operator-alert catalogue was not.

PAM / operator control plane

The tracked surface includes player-account or back-office control. Managed services remain a separate scope, and exact permissions are product- and deployment-specific.

Yes

Yes

Yes — customer support, payments, risk/fraud, AML, CRM/marketing, compliance, responsible gambling and managed trading.

Role-based; exact permission matrix unresolved

The regulated enterprise PAM separates operator roles; cross-product role granularity remains unresolved.

Yes

Enterprise PAM, lottery operations and managed-service deployments support multiple operational users; seat and workspace rules are contract-specific.

Yes

Privileged actions are auditable across regulated PAM and lottery operations; exact event coverage remains unresolved.

Unresolved

A back-office bulk-action catalogue is not established.

Yes

A regulated PAM and managed player operation require controlled account adjustments; permissions and approval thresholds are contract-specific.

Partial

Managed payment, reconciliation, AML and risk operations support reviewed withdrawals; native workflow and threshold details are product-specific.

Partial

KYC integrations and managed compliance support case handling, but the tooling may be third-party and varies by deployment.

Partial

Managed fraud operations support case handling, but the tooling may be third-party and varies by deployment.

Yes

NeoCube provides an iLottery central player view and Gaming Analytics provides land-based real-time insights; equivalent iGaming PAM console detail remains unresolved.

Yes

The 24/7 Michigan service operation and managed player support use agent tooling; the console and feature set remain customer-specific.

Yes

Regulated payment, player-account and lottery operations support controlled approvals; a unified workflow catalogue is not established.

Unresolved

Monitoring exists in individual products; a unified operator-alert catalog is not established.

PAM / operator control plane

The tracked surface includes player-account or back-office control. Managed services remain a separate scope, and exact permissions are product- and deployment-specific.

Yes

Integrated player-account management in the turnkey sportsbook.

Yes

Retail hierarchy: Owner, Partner, Super Agent, Agent, Cashier, User; core PAM administrator-role matrix unresolved

Yes

Yes

Retail cashier tools include audit tracking for settlements, reprints, adjustments and voids. The retention period, tamper controls and coverage of every core PAM administrator action remain unavailable.

Yes

Player Tags can be created, edited and assigned in bulk, and campaigns can be automated across segments.

Yes

Cashier and agent roles can post deposits, withdrawals and transfers to player accounts. Arbitrary online-PAM corrections and maker-checker controls remain unresolved.

Unresolved

The operator withdrawal-approval workflow and approval matrix remain unresolved.

Yes

Yes

Yes

Yes

Unresolved

A general maker-checker or multi-step back-office approval specification is not established.

Yes

PAM / operator control plane

The tracked surface includes player-account or back-office control. Managed services remain a separate scope, and exact permissions are product- and deployment-specific.

Yes

Kambi now offers an optional full-service in-house PAM alongside continued third-party PAM support. It covers registration, banking, KYC, bonus and loyalty engines and an integrated casino platform. The inherited OMEGA stack had 300+ KYC, payment, CRM, affiliate, sports and game-provider integrations. Station Casinos is the first named customer for Kambi's in-house PAM, but no go-live date or completed production deployment is established.

Yes

Managed Trading takes the book and risk off the operator's hands, powered by the Tzeract AI division.

Granular operational roles

Trading, risk, partner, support and compliance duties require separated permissions and auditability across operator teams.

Yes

Unresolved

A product-level administrative audit-trail specification remains unresolved. Regulated operation and certification do not substitute for a feature specification.

Yes

Network-scale market, event and liability management necessarily includes bulk operational actions in the trading back office.

Yes

Available when the operator takes Kambi's full-service PAM; sportsbook-only customers use the equivalent controls in their external PAM.

Yes

The PAM banking layer supports controlled withdrawal handling; rules and approval thresholds are operator-configured.

Yes

KYC and identity verification are explicit PAM functions, with vendor integrations selected by the operator.

Yes

Core sportsbook controls include liability management, stake acceptance, player profiling and 24/7 integrity monitoring; the optional PAM adds account, KYC and payment-case context.

Yes

Kambi already maintains real-time betting-risk views and player profiles; the optional PAM adds the full account lifecycle view.

Yes

The optional full-service PAM manages the player lifecycle and supplies operator-side account tooling; sportsbook-only customers continue using their PAM's support console.

Yes

Regulated trading, risk and offer changes use controlled operational workflows with role separation and audit trails.

Yes

Trading and risk alerting reaches operator and trading teams; exact controls are partner-gated.

PAM / operator control plane

The tracked surface includes player-account or back-office control. Managed services remain a separate scope, and exact permissions are product- and deployment-specific.

Yes

Yes — Open Platform System is a full casino PAM.

Yes

Limited to platform/content support, account management, promotions, custom game development and regulatory guidance; no managed B2C operation.

Granular role-based administration

Yes

Yes

Yes

Yes

Yes with permissions and audit trail.

Yes

Yes through OPS/payment workflows.

Partial

Via integrated KYC providers and OPS workflows.

Partial

Via third-party risk integrations and OPS tooling.

Yes

Yes

Yes

Yes

Component/content portal, not a PAM control plane

The supplied console administers its own component. Player account, wallet, cashier and operator casework remain in the connected PAM.

No

Fusion connects to an operator's existing PAM. Aristocrat Interactive's PAM belongs to the separate iGaming & Sports business.

No

No end-to-end B2C managed operation; 24/7/365 content/platform support is included.

Role-gated partner portal/back office; exact permission matrix is partner-specific

Yes

Yes for enterprise operator/studio accounts.

Unresolved

Regulated administration and ISO change controls do not establish the exact administrator-event history, retention or export scope.

Yes

Partial — cross-vendor campaign/configuration and bulk asset access; player operations are outside scope.

Unresolved

No PAM or player balance.

Unresolved

No cashier.

Unresolved

Operator/PAM responsibility.

Unresolved

Operator/risk-stack responsibility.

No

No full player view; only game-session and campaign/leaderboard context.

Unresolved

Not applicable to B2C player support.

Yes

Content, certification and campaign configuration controls; exact multi-step approvals are partner-specific.

Yes

Operational alerts and 24/7 support escalation are available; delivery channels and thresholds are contractual.

PAM / operator control plane

The tracked surface includes player-account or back-office control. Managed services remain a separate scope, and exact permissions are product- and deployment-specific.

Yes

Centrivo provides player profiles, brand management, cashier, bonus, dashboards, automations and risk controls. Universal is the all-in-one model; Dynamics is the more modular configuration.

Yes

Trading/risk, hosting, support, payments integration, licensing guidance and marketing/business support are available; exact scope is contractual.

Configurable role and permission controls

DGBuilder and Centrivo Retail include permission-based access and adaptable roles; field-level granularity remains unresolved.

Yes

Yes

Centrivo CRM records important-action history; Paydrom also records access, actions and events. Retention and immutability remain unresolved.

Yes

Paydrom provides Batch Update and Batch Notify for transaction management; Centrivo also supports centralized brand configuration and trigger-condition-action automations. Bulk-edit coverage across every PAM module remains unresolved.

Yes

Centrivo's cashier and player-management tooling plus Paydrom's manual transaction controls support controlled adjustments. Adjustment types, limits and dual-control rules remain unresolved.

Partial

Paydrom provides pre-authorization checks, automated and manual transaction management, transaction flags, Batch Update and account restrictions. This supports payment-review handling; a configurable maker-checker withdrawal approval chain remains unresolved.

Yes

Yes

Yes

Yes

Centrivo player profiles, transaction histories, risk controls and real-time views provide the core support-agent workspace.

Yes

Configurable roles, permissions, trigger-condition-action rules, transaction flags and manual exception handling support operational approval workflows. Full maker-checker coverage by module remains unresolved.

Yes

Paydrom includes PCI DSS logging, monitoring and alerts; APIs and hosted services include proactive monitoring and incident response.

PAM / operator control plane

The tracked surface includes player-account or back-office control. Managed services remain a separate scope, and exact permissions are product- and deployment-specific.

Yes

Yes

Managed services are available, but scope and fees are agreed in a separate addendum.

Role-based; permission depth unresolved

RBAC covers support, administration, compliance and reporting responsibilities; the entitlement matrix remains unresolved.

Yes

The platform supports distributed support, compliance, operations and engineering users.

Unresolved

Regulated case handling and end-to-end traceability provide an audit trail; admin-event detail remains unresolved.

Yes

The bonus engine and CRM integrations execute segmented and automated campaigns at scale.

Yes

Controlled manual account and balance actions are supported; permissions and dual approval remain unresolved.

Yes

Configurable withdrawal rules automate decisions and route exceptions into risk review.

Yes

Electronic ID verification, AML workflows, Shufti document/biometric checks and managed compliance are integrated.

Yes

Real-time risk alerts and managed risk/fraud services support investigation workflows; detailed queues and rules remain unresolved.

Yes

The back office provides full player history in real time across states and live contact monitoring.

Yes

The managed-service back office supports player service, contact monitoring, reporting and quality assurance.

Yes

Withdrawal, marketing approval, compliance and escalation workflows are present; a generic no-code workflow builder is not established.

Yes

Real-time risk alerts and customer-interaction triggers surface payment, player-protection and operational events.

PAM / operator control plane

The tracked surface includes player-account or back-office control. Managed services remain a separate scope, and exact permissions are product- and deployment-specific.

Yes

Yes

Includes managed trading/risk, implementation hypercare, payment optimization and operational support; full B2C operations depend on scope.

Granular role, permission and data-masking controls

Yes

Yes

Yes

CSV upload/export and bulk campaign, promo-code and monitoring workflows are available.

Yes

Wallet, reward and account operations support controlled manual actions with audit logging.

Yes

Payment Hub supports withdrawal routing, restrictions, risk checks and approval/control workflows.

Yes

KYCAid and SumSub multiforms allow an individually rejected document to be resubmitted without restarting the complete verification flow.

Yes

Yes

Yes

UBO adds global player and transaction search via Cmd or Ctrl+K without exposing sensitive data in the result list; X-Segments are visible inside Player Info.

Yes

Payment, affiliate payout, KYC and role-sensitive workflows have approvals; there is no universal no-code workflow builder for every module.

Yes

Risk, payment and operational monitors surface real-time flags and event-driven restrictions.

PAM / operator control plane

The tracked surface includes player-account or back-office control. Managed services remain a separate scope, and exact permissions are product- and deployment-specific.

Yes

CoreX is the current proprietary PAM. Legacy Sportnco Alira clients are being migrated through 2026, and major clients on the Spanish legacy platforms had agreed by July to move to the certified CoreX stack.

Yes

Granular by user, brand, market, licence and operational function

Yes

Yes

Yes

Yes

Yes

Yes

CoreX and ServiceX support KYC/EDD case handling and integrate automated risk scoring.

Yes

Yes

Player activity surfaces in the back office in about 0.5 seconds.

Yes

Yes

LogicX can configure compliance, bonus, risk and player workflows without code changes.

Yes

PAM / operator control plane

The tracked surface includes player-account or back-office control. Managed services remain a separate scope, and exact permissions are product- and deployment-specific.

Yes

Yes — proprietary Bragg PAM. Sold standalone or inside operator-licensed turnkey packages.

Yes

Yes — marketing, operations, 24/7 customer support, payments, fraud prevention and responsible-gaming support can be included.

Unresolved

A concrete role and permission model is not established. Regulated multi-team operation does not by itself establish RBAC granularity.

Yes

Yes

Yes — required for regulated operations and exportable campaign logs.

Yes

Supported for content and player operations; exact tooling remains unresolved.

Yes

Yes with controlled permissions and audit trail.

Yes

Yes through PAM/cashier and managed operations; rules depend on operator.

Yes

Yes — KYC tools and player-protection workflows are part of the PAM.

Yes

Yes — fraud and risk rules operate in the PAM.

Yes

Yes — real-time behaviour and player journey data feed Fuze, support and risk workflows.

Yes

Yes — Bragg can provide 24/7 player support as a managed service.

Yes

Configurable for payments, player adjustments, campaigns and compliance.

Yes

Yes — automated risk/RG triggers and operational notifications.

PAM / operator control plane

The tracked surface includes player-account or back-office control. Managed services remain a separate scope, and exact permissions are product- and deployment-specific.

Yes

The core casino platform supplies player accounts, back office, wallet, KYC, antifraud, bonuses and reporting.

Yes

Account management, 24/7 technical support and selectable services are offered; full operations outsourcing is not universal.

Unresolved

Multi-user operations are established; the role/permission matrix and field-level access-control specification are unresolved.

Yes

Account management and bulk-operation workflows imply multiple operator users; seat and role limits are private.

Unresolved

Transaction, KYC and status histories provide an operational record, but a searchable administrator-action log, its immutability, retention and export scope remain unresolved.

Yes

The antifraud/player module supports bulk activation, blocking and bonus enable/disable actions.

Yes

Operators can change player status and controls; manual balance adjustment and maker-checker rules are unresolved.

Partial

Transactions and fraud risks are monitored; the approve/reject queue and maker-checker controls are unresolved.

Yes

KYC case management includes configurable documents, risk requirements, ongoing monitoring and stored results.

Yes

Risk categories, rules, alerts and player-level actions are supported; AI mainly summarizes existing signals.

Yes

Current modules expose project- and player-level metrics and actions.

Yes

Live chat and player-management tools exist; a full case/ticketing suite is not established.

Unresolved

Risk and player actions exist; a configurable multi-level approval or maker-checker workflow is not established.

Yes

Antifraud rules can generate alerts and actions; channel and severity configuration are private.

PAM / operator control plane

The tracked surface includes player-account or back-office control. Managed services remain a separate scope, and exact permissions are product- and deployment-specific.

Yes

The proprietary Spring platform provides player accounts, wallet, back office and operations. Spring BME is the separate business-management console used to create projects and order or enable products and services; it is not itself the transaction or PAM engine.

Yes

Role and permission controls across users, projects and functions

Spring back office supports roles and permissions; Affigates adds global and individual permission controls plus hierarchy-based access. Exact field-level permissions remain unresolved.

Yes

Unresolved

Player activity, reporting and access controls are established; the scope of a searchable immutable administrator-action log remains unresolved.

Yes

Yes

Yes

Back office processes and manages withdrawal requests; a formal multi-step approval chain remains unresolved.

Yes

Yes

Yes

Yes

Player account management and CRM messaging sit in the back office. A dedicated support-agent desk is not established.

Yes

Roles and permissions gate who can act, and a promo timeline reviews campaign activity, but configurable multi-stage approval chains are not spelled out.

Yes

Umbrella supports configurable internal and external alerts, missed-alert notifications and automated actions; component incident subscriptions are also available.

PAM / operator control plane

The tracked surface includes player-account or back-office control. Managed services remain a separate scope, and exact permissions are product- and deployment-specific.

Yes

Yes

Role-based access; exact permission granularity private

Yes

The back office is run by operator staff; exact staff roles and permission levels remain unresolved.

Yes

Yes

Batch bonus, player-category, game and reporting operations fit the established back-office workflows.

Yes

Partial

Withdrawal processing sits in the back office; a formal multi-step approval flow remains unresolved.

Partial

Staff can review player documents and set a KYC level, but SoftGamings leaves the actual KYC verification vendor to the operator.

Partial

The payment layer includes fraud resistance; dedicated fraud case-management and investigation tooling is not established.

Yes

Partial. The Single Customer View centralizes player, payment, bonus and activity information; refresh latency is not specified.

Yes

The back office supports player lookup, account actions, KYC review and payment handling for first-line support.

Yes

Partial. Operational actions and payment review are supported; configurable multi-person approvals remain unresolved.

Yes

Partial. Operational monitoring and notifications exist; alert-rule coverage and on-call integrations are unresolved.

PAM / operator control plane

The tracked surface includes player-account or back-office control. Managed services remain a separate scope, and exact permissions are product- and deployment-specific.

Yes

Yes

The Channels Media Group / Waddibet scope includes managed acquisition and retention services.

Granular by role, brand and market

Yes

Yes

Unresolved

Feature-level bulk-operations capability remains unresolved.

Yes

PAM provides in-depth account administration; specific permissions and dual-control rules depend on configuration.

Yes

Automated payouts support configurable limits, rules, approvals, and manual review of flagged cases.

Yes

Yes

Yes

Yes

A proprietary support dashboard unifies chat, calls, email, routing, and quality monitoring.

Yes

CMS and payment operations include governed approval workflows.

Yes