Skip to content

iGaming Platform Frontend & CMS Comparison

Frontend control determines how quickly an operator can change the player experience without surrendering product scope, release control or accessibility. This comparison keeps builder, templates, custom design, headless delivery, responsive web, PWA and native apps as separate conclusions.

Last updated August 20, 2026 · 18 providers · 12 frontend fields · overall-score order

Five boundaries that change the implementation

Availability in one route does not establish another, and none of these fields creates a frontend feature score.

Builder versus service

A supplier can build a bespoke site without giving the operator a self-service visual builder.

Custom versus owned

Custom design does not establish repository access, source ownership or independent deployment rights.

Headless versus complete

An API-led frontend can still depend on supplier widgets for regulated or transactional journeys.

Web, PWA and native

Responsive web, installable PWA and store-distributed native apps are three distinct delivery routes.

WCAG is evidence-specific

No audit or target on record remains Unresolved; it is never converted into an accessibility failure.

Provider frontend and CMS records

Product names appear only beside fields mapped to that surface. Every field value below remains a provider-level conclusion unless its product scope is explicitly identified. Unresolved remains visible and distinct from No.

  1. 8.8

    overall score

    Mapped product surfaces

    • EveryMatrix Casino (CasinoEngine)Headless frontend: Yes — Casino, wallet, lobby, game, live-table, sports, and data APIs support operator-built experiences.
    • OmnichannelNative apps: iOS, Android — The platform supports responsive and native-mobile front ends; app design, packaging, and store operation are bespoke/operator-specific.

    Build and control

    Frontend builder
    NoVerified conclusionFront ends are delivered through APIs, responsive web apps, templates or bespoke EveryMatrix/Goma builds; no drag-and-drop self-serve builder is included.
    Template library
    YesVerified conclusionThe sportsbook offer includes off-the-shelf templates alongside bespoke front ends.
    Custom design
    YesVerified conclusionBespoke front-end capacity was expanded with the 2025 Goma Gaming acquisition.
    Headless frontend
    YesVerified conclusionCasino, wallet, lobby, game, live-table, sports, and data APIs support operator-built experiences.

    Web and app delivery

    Responsive design
    YesVerified conclusion
    PWA
    NoEditorial inferenceEveryMatrix supports a responsive mobile-first web app, bespoke Web API front ends and native apps; a standard PWA package, installability scope and service-worker commitment remain unresolved.
    Native apps
    iOS, AndroidSupported conclusionThe platform supports responsive and native-mobile front ends; app design, packaging, and store operation are bespoke/operator-specific.

    Acquisition and onboarding

    SEO readiness
    UnresolvedFrontend products are configurable; SEO feature specifications and technical commitments remain unresolved.
    A/B testing
    UnresolvedA general native frontend experimentation module is not established.
    Social login
    NoEditorial inferenceGamMatrix has no standard social identity-service inventory or universal social-login module; bespoke operator identity integration is not a native entitlement.
    Registration flow
    Quick sign-up or multi-step, with license-specific requirementsVerified conclusion

    Accessibility

    Accessibility / WCAG
    UnresolvedPortfolio-wide WCAG target, audit and conformance status remain unresolved.

  2. Rank 02

    Playtech

    8.7

    overall score

    Mapped product surfaces

    • PAM+ Engagement CentreA/B testing: Yes — Done through Campaign Manager with test and control groups, aimed at promotions and player journeys rather than UI experiments.

    Build and control

    Frontend builder
    YesVerified conclusionOperators configure the player-facing front-end through Playtech Portal and IMS rather than rebuilding the back end.
    Template library
    YesEditorial inferencePlaytech supplies configurable portals, lobbies and native/web frameworks, with bespoke design on top; the exact template count is unresolved.
    Custom design
    YesVerified conclusion
    Headless frontend
    YesEditorial inferenceOperators can integrate Playtech products into existing technology and use external JSON APIs or embedded launches with operator-controlled front ends. A self-service headless framework and complete unauthenticated API surface are not established.

    Web and app delivery

    Responsive design
    YesVerified conclusion
    PWA
    OptionalEditorial inferenceResponsive and operator-controlled web delivery can be packaged as a PWA; native apps and responsive web are available without one mandatory PWA shell.
    Native apps
    iOS, AndroidVerified conclusion

    Acquisition and onboarding

    SEO readiness
    YesEditorial inferenceOperators control CMS content, routes and brand presentation; game and logged-in account surfaces remain application-like and are not inherently indexable.
    A/B testing
    YesVerified conclusionDone through Campaign Manager with test and control groups, aimed at promotions and player journeys rather than UI experiments.
    Social login
    UnresolvedPAM+ exposes identity integrations and Nevis passwordless login; named social-OAuth login support remains unresolved.
    Registration flow
    Multi-step with IMS KYC onboardingVerified conclusionIMS handles the account flow and ties in third-party KYC providers for identity checks during onboarding.

    Accessibility

    Accessibility / WCAG
    UnresolvedProduct-level WCAG conformance remains unresolved; this does not establish non-conformance.

  3. Rank 03

    SOFTSWISS

    8.3

    overall score

    Mapped product surfaces

    • Turnkey SportsbookNative apps: iOS, Android — The Sportsbook offers native iOS and Android applications. The Casino Platform's standard mobile route is a PWA, so app availability is product-specific.
    • Sportsbook IntegrationHeadless frontend: Yes

    Build and control

    Frontend builder
    YesVerified conclusion
    Template library
    YesVerified conclusion
    Custom design
    YesVerified conclusion
    Headless frontend
    YesVerified conclusion

    Web and app delivery

    Responsive design
    YesVerified conclusion
    PWA
    YesVerified conclusion
    Native apps
    iOS, AndroidVerified conclusionThe Sportsbook offers native iOS and Android applications. The Casino Platform's standard mobile route is a PWA, so app availability is product-specific.

    Acquisition and onboarding

    SEO readiness
    YesVerified conclusion
    A/B testing
    NoVerified conclusionNo native A/B tool. Operators set up Google Tag Manager to run their own tests.
    Social login
    YesEditorial inferenceSocial login is optional through frontend or identity integration rather than a universal core module; availability depends on the operator frontend, identity stack and market rules.
    Registration flow
    Configurable multi-step KYC; Pay N Play where supportedVerified conclusionStandard registration is configured around local KYC requirements, while Trustly Pay N Play can remove a separate registration step in eligible markets.

    Accessibility

    Accessibility / WCAG
    UnresolvedResponsive and custom frontends are supported; current WCAG audit, conformance level and VPAT remain unresolved.

  4. 8.2

    overall score

    Mapped product surfaces

    • CMS & Front EndFrontend builder: Yes — This is a CMS plus responsive templates and bespoke frontend delivery, not evidence of a drag-and-drop site builder. · Headless frontend: Yes — API-first and headless by design, but operators can also take Pragmatic's responsive templates or bespoke front-end development rather than building alone. · Native apps: iOS, Android — The frontend supports both native mobile platforms.

    Build and control

    Frontend builder
    YesSupported conclusionThis is a CMS plus responsive templates and bespoke frontend delivery, not evidence of a drag-and-drop site builder.
    Template library
    YesVerified conclusionThe current front-end product offers quick-start responsive templates alongside bespoke development.
    Custom design
    YesVerified conclusionFull-custom front ends are supported given the headless, API-first model.
    Headless frontend
    YesVerified conclusionAPI-first and headless by design, but operators can also take Pragmatic's responsive templates or bespoke front-end development rather than building alone.

    Web and app delivery

    Responsive design
    YesVerified conclusion
    PWA
    NoEditorial inferenceThe current frontend offer explicitly covers responsive templates, bespoke web delivery and native iOS/Android support but does not include a standard PWA product. A bespoke operator build remains possible.
    Native apps
    iOS, AndroidVerified conclusionThe frontend supports both native mobile platforms.

    Acquisition and onboarding

    SEO readiness
    UnresolvedOperator control does not establish specific technical SEO capabilities.
    A/B testing
    YesSupported conclusionAvailable through pre-integrated CRM/engagement partners including Optimove and Xtremepush, which support campaign and gamification test/control workflows. This is partner-enabled rather than a native CMS experiment engine.
    Social login
    UnresolvedOpen identity integration does not prove a native social-login feature.
    Registration flow
    Configurable PAM onboarding with jurisdiction-specific KYC and payment steps; Pay N Play is available through external partnersSupported conclusion

    Accessibility

    Accessibility / WCAG
    UnresolvedA current WCAG level and universal conformance status remain unresolved.

  5. 8.1

    overall score

    Mapped product surfaces

    No product-specific frontend mapping is established. The conclusions below remain provider-level.

    Build and control

    Frontend builder
    NoEditorial inferenceThe customizable widget-based sportsbook frontend is not a self-service visual builder.
    Template library
    NoEditorial inferenceThe retained offer has no current operator-site template library.
    Custom design
    YesSupported conclusion
    Headless frontend
    UnresolvedAPI integrations and customizable front ends do not establish a standard headless-frontend product.

    Web and app delivery

    Responsive design
    YesVerified conclusion
    PWA
    NoEditorial inferenceNo standard Aristocrat Interactive PWA deliverable is established; operators can build their own frontend.
    Native apps
    Yes, including operator-branded mobile deploymentsVerified conclusion

    Acquisition and onboarding

    SEO readiness
    UnresolvedFrontend rendering and SEO specifications remain unresolved.
    A/B testing
    NoEditorial inferenceNo native frontend experimentation suite is established in the current product set.
    Social login
    NoEditorial inferenceThe portfolio has no standard social-login service inventory or universal player-authentication module; a customer-specific identity integration is not a native entitlement.
    Registration flow
    Customizable with KYC, age and market controlsEditorial inference

    Accessibility

    Accessibility / WCAG
    UnresolvedNo portfolio-wide WCAG target, audit or conformance statement is established.

  6. Rank 06

    Altenar

    8.0

    overall score

    Mapped product surfaces

    • Turnkey SportsbookNative apps: iOS, Android — The Flutter-based native application supports biometric login and push notifications and can be white-labelled per brand.

    Build and control

    Frontend builder
    YesVerified conclusionA React-based widget front end and CMS control layout, content, skins, odds formats, limits, bonuses and market presentation without extensive custom coding.
    Template library
    YesSupported conclusionAltenar's Market Templates library provides reusable sportsbook market and selection layouts across desktop, mobile and apps, with sorting, translation and preview controls. This is a sportsbook presentation library, not a complete turnkey-site theme catalogue.
    Custom design
    YesVerified conclusion
    Headless frontend
    YesSupported conclusionOperators can integrate Altenar's modular sportsbook and widgets into an existing portal or custom front end.

    Web and app delivery

    Responsive design
    YesVerified conclusion
    PWA
    NoEditorial inferenceA PWA is not a standard Altenar deliverable; the established mobile routes are responsive web and white-labelled native iOS and Android apps.
    Native apps
    iOS, AndroidVerified conclusionThe Flutter-based native application supports biometric login and push notifications and can be white-labelled per brand.

    Acquisition and onboarding

    SEO readiness
    YesVerified conclusion
    A/B testing
    UnresolvedA general front-end A/B testing system is not established.
    Social login
    NoEditorial inferenceA standard social-login or third-party identity-provider option is not established for PAM, mobile app or DGBuilder.
    Registration flow
    Configurable multi-step flow with document, liveness, email and phone verificationVerified conclusion

    Accessibility

    Accessibility / WCAG
    UnresolvedAltenar's accessibility statement applies only to its informational property, not to operator front ends.

  7. Rank 07

    Kambi

    8.0

    overall score

    Mapped product surfaces

    • Front EndFrontend builder: Yes — Configurable betting front end, strengthened by the 2022 Shape Games acquisition; or run headless on the API and build your own. · Native apps: iOS, Android — Native iOS and Android betting apps delivered via the Shape Games front-end technology.

    Build and control

    Frontend builder
    YesVerified conclusionConfigurable betting front end, strengthened by the 2022 Shape Games acquisition; or run headless on the API and build your own.
    Template library
    YesEditorial inferenceConfigurable front-end templates are available through Shape Games; the depth of pre-built templating is unresolved.
    Custom design
    YesVerified conclusionFully custom via headless API integration, or configurable via the Shape Games front end.
    Headless frontend
    YesVerified conclusionOperators can run headless on the Kambi API and build their own front end, or take the Shape Games front end.

    Web and app delivery

    Responsive design
    YesVerified conclusion
    PWA
    OptionalEditorial inferenceOperators can ship Kambi as managed web, embedded web or a headless custom build; a PWA is therefore an implementation choice rather than a fixed Kambi shell.
    Native apps
    iOS, AndroidVerified conclusionNative iOS and Android betting apps delivered via the Shape Games front-end technology.

    Acquisition and onboarding

    SEO readiness
    YesEditorial inferenceThe open/headless and custom-development models let operators control routing, metadata and indexable editorial pages around the betting product.
    A/B testing
    YesEditorial inferenceFront-end experimentation/personalisation via the Shape Games toolset.
    Social login
    YesEditorial inferenceSocial or federated identity can be provided through Kambi's optional PAM or the operator's chosen external identity stack; it is not a sportsbook-specific login.
    Registration flow
    Configurable through Kambi PAM or an external PAM; supports onboarding, identity verification and market-specific compliance stepsVerified conclusionKambi now presents registration as part of its optional full-service PAM while retaining platform-agnostic third-party PAM integration.

    Accessibility

    Accessibility / WCAG
    UnresolvedManaged and custom front-end delivery can meet operator and public-lottery accessibility requirements; a universal WCAG conformance level is not established.

  8. 7.7

    overall score

    Mapped product surfaces

    • Integrated Player Portal & PaymentsFrontend builder: Yes — Partial — configurable API-driven casino lobby/player portal, not a general website CMS.

    Build and control

    Frontend builder
    YesVerified conclusionPartial — configurable API-driven casino lobby/player portal, not a general website CMS.
    Template library
    YesEditorial inferenceConfigurable portal/lobby components.
    Custom design
    YesVerified conclusionYes for the integrated player portal.
    Headless frontend
    YesVerified conclusionYes — API-driven lobby and integrations.

    Web and app delivery

    Responsive design
    YesVerified conclusion
    PWA
    YesEditorial inferenceSupported by API-driven responsive delivery.
    Native apps
    Mobile framework and app integrations for iOS/Android; operator owns the final appEditorial inference

    Acquisition and onboarding

    SEO readiness
    YesEditorial inferenceOperator frontend dependent.
    A/B testing
    YesEditorial inferenceSupported through operator analytics/portal configuration.
    Social login
    UnresolvedSupported social-identity providers and a native OPS social-login flow are unresolved. General SSO and configurable registration do not establish social login.
    Registration flow
    OPS-managed and configurableVerified conclusion

    Accessibility

    Accessibility / WCAG
    UnresolvedImplementation-dependent; require contractual WCAG target.

  9. Rank 09

    Pariplay

    7.5

    overall score

    Mapped product surfaces

    No product-specific frontend mapping is established. The conclusions below remain provider-level.

    Build and control

    Frontend builder
    NoVerified conclusionNo — Fusion is a content layer.
    Template library
    NoVerified conclusionNo operator-site template library.
    Custom design
    NoVerified conclusionNo full-site design service; campaign surfaces can be branded/configured.
    Headless frontend
    YesVerified conclusionYes — API-delivered content into the operator experience.

    Web and app delivery

    Responsive design
    YesVerified conclusionYes for HTML5 games and engagement interfaces.
    PWA
    NoVerified conclusionNo Pariplay PWA product.
    Native apps
    None — operator owns iOS/Android applicationsVerified conclusion

    Acquisition and onboarding

    SEO readiness
    NoVerified conclusionOperator frontend responsibility.
    A/B testing
    NoVerified conclusionA native frontend A/B-testing suite is not established.
    Social login
    NoVerified conclusionOperator/PAM responsibility.
    Registration flow
    Operator/PAM responsibility; Pariplay receives an authenticated game sessionVerified conclusion

    Accessibility

    Accessibility / WCAG
    No established conformanceVerified conclusionWCAG conformance is operator-frontend and game-supplier specific; platform-wide Pariplay conformance remains unresolved.

  10. Rank 10

    Digitain

    7.1

    overall score

    Mapped product surfaces

    • DGBuilderFrontend builder: Yes — DGBuilder is a no-code drag-and-drop website builder for operators to build and manage their own pages without touching the backend. · Template library: Yes · Custom design: Yes · SEO readiness: Yes — DGBuilder includes SEO controls, Open Graph and social-card settings. · Headless frontend: Yes — Operators can design their own UI across channels while consuming Digitain's betting and data services. · Registration flow: Operator-configurable — DGBuilder lets operators design registration and player-account forms.
    • Native ApplicationsNative apps: iOS and Android · PWA: Yes — Digitain's current sportsbook collateral explicitly includes a progressive web app alongside native mobile applications. · Responsive design: Yes · Registration flow: Operator-configurable — DGBuilder lets operators design registration and player-account forms.
    • Centrivo CRMA/B testing: Yes — Centrivo CRM supports campaign A/B testing and automatic player exclusion. This does not establish native randomized frontend-layout testing.

    Build and control

    Frontend builder
    YesSupported conclusionDGBuilder is a no-code drag-and-drop website builder for operators to build and manage their own pages without touching the backend.
    Template library
    YesSupported conclusion
    Custom design
    YesSupported conclusion
    Headless frontend
    YesSupported conclusionOperators can design their own UI across channels while consuming Digitain's betting and data services.

    Web and app delivery

    Responsive design
    YesSupported conclusion
    PWA
    YesSupported conclusionDigitain's current sportsbook collateral explicitly includes a progressive web app alongside native mobile applications.
    Native apps
    iOS and AndroidSupported conclusion

    Acquisition and onboarding

    SEO readiness
    YesSupported conclusionDGBuilder includes SEO controls, Open Graph and social-card settings.
    A/B testing
    YesSupported conclusionCentrivo CRM supports campaign A/B testing and automatic player exclusion. This does not establish native randomized frontend-layout testing.
    Social login
    NoEditorial inferenceSocial login and third-party identity-provider integration are not established across registration, mobile and DGBuilder.
    Registration flow
    Operator-configurableSupported conclusionDGBuilder lets operators design registration and player-account forms.

    Accessibility

    Accessibility / WCAG
    No established conformanceEditorial inferenceA WCAG target, VPAT, accessibility audit and conformance statement for the operator frontends remain unavailable.

  11. 7.1

    overall score

    Mapped product surfaces

    • Front End & Native AppsFrontend builder: No — A self-serve page builder is not included. The drop-in cashier can be styled with CSS, which is narrower than a frontend builder. · Custom design: Yes — Operator-licensed PAM can include a White Hat-built frontend based on the customer's UI, paid custom development and a frontend source-code license. · Responsive design: Yes — Delivery covers desktop and mobile-formatted sites plus native iOS and Android applications. · Headless frontend: Yes — The customer or an external third party can manage the frontend while White Hat supplies APIs, documentation and mobile-app integration. · Native apps: iOS, Android — Native iOS and Android scope can include design, development, support, acceptance and PAM integration. Availability and ownership remain project-specific.

    Build and control

    Frontend builder
    NoVerified conclusionA self-serve page builder is not included. The drop-in cashier can be styled with CSS, which is narrower than a frontend builder.
    Template library
    NoVerified conclusionAn operator-selectable frontend template library is not established.
    Custom design
    YesVerified conclusionOperator-licensed PAM can include a White Hat-built frontend based on the customer's UI, paid custom development and a frontend source-code license.
    Headless frontend
    YesVerified conclusionThe customer or an external third party can manage the frontend while White Hat supplies APIs, documentation and mobile-app integration.

    Web and app delivery

    Responsive design
    YesVerified conclusionDelivery covers desktop and mobile-formatted sites plus native iOS and Android applications.
    PWA
    OptionalEditorial inferenceWeb-app packaging is implementation-specific; a standard PWA product is not established.
    Native apps
    iOS, AndroidVerified conclusionNative iOS and Android scope can include design, development, support, acceptance and PAM integration. Availability and ownership remain project-specific.

    Acquisition and onboarding

    SEO readiness
    YesEditorial inferenceWhite Hat-operated domains are indexable; technical SEO guarantees remain unresolved.
    A/B testing
    YesEditorial inferenceSplit tests are available through integrated CRM/journey tools such as Xtremepush; this does not establish page-builder A/B testing.
    Social login
    NoVerified conclusionA standard social-login capability is not established for regulated player onboarding.
    Registration flow
    Market-configured multi-step registration with KYCEditorial inferenceFlow depth changes by B2C licence, state and identity provider; there is no universal one-click registration.

    Accessibility

    Accessibility / WCAG
    UnresolvedWCAG level, accessibility audit and platform conformance are unresolved.

  12. Rank 12

    GR8 Tech

    7.0

    overall score

    Mapped product surfaces

    No product-specific frontend mapping is established. The conclusions below remain provider-level.

    Build and control

    Frontend builder
    YesVerified conclusion
    Template library
    YesVerified conclusion
    Custom design
    YesVerified conclusion
    Headless frontend
    YesVerified conclusionThe sportsbook API and modular widgets support an operator-owned front end; iFrame and full-platform routes remain available.

    Web and app delivery

    Responsive design
    YesVerified conclusion
    PWA
    OptionalEditorial inferenceResponsive web and installable/mobile shells are supported; native apps remain the more established mobile route.
    Native apps
    iOS; AndroidVerified conclusion

    Acquisition and onboarding

    SEO readiness
    YesEditorial inferenceCustom/headless front ends can implement SEO. Server-side rendering for the refreshed sportsbook was still being rolled out in 2026, so confirm the selected front-end mode.
    A/B testing
    YesVerified conclusion
    Social login
    YesVerified conclusionPAM supports email, phone and social logins, including social-registration flows such as Google and Facebook. Provider coverage remains configurable.
    Registration flow
    Configurable mobile-first flow with geo rules, progressive KYC, tiered limits and optional bonus routingVerified conclusionSince July 2026, the no-code Form Builder and reusable Registration Page and Widget cover registration, login, personal-data editing and password recovery. Operators can create multiple unique URLs, attach welcome bonuses, control geo visibility and run alternative acquisition flows.

    Accessibility

    Accessibility / WCAG
    No established conformanceEditorial inferenceA WCAG conformance level and accessibility audit remain unresolved. This is a compliance gap, not proof that every interface is inaccessible.

  13. Rank 13

    GiG

    6.8

    overall score

    Mapped product surfaces

    • XSiteFrontend builder: Yes — XSite is GiG's active website and brand deployment framework. · Custom design: Yes · Responsive design: Yes · SEO readiness: Yes — XSite supports localized front ends and SportX includes operator-controlled SEO text management. · Headless frontend: Yes

    Build and control

    Frontend builder
    YesVerified conclusionXSite is GiG's active website and brand deployment framework.
    Template library
    UnresolvedXSite is a custom frontend builder and deployment framework; a maintained ready-made operator-template inventory remains unresolved.
    Custom design
    YesVerified conclusion
    Headless frontend
    YesEditorial inference

    Web and app delivery

    Responsive design
    YesVerified conclusion
    PWA
    OptionalEditorial inference
    Native apps
    iOS and Android operator-branded apps available by projectEditorial inference

    Acquisition and onboarding

    SEO readiness
    YesVerified conclusionXSite supports localized front ends and SportX includes operator-controlled SEO text management.
    A/B testing
    UnresolvedAI-led UX optimization is available; a self-service experimentation or statistical A/B-testing product is not established.
    Social login
    YesEditorial inferenceAvailable through configurable identity integrations.
    Registration flow
    Configurable by market, from streamlined onboarding to full KYC-first flowsVerified conclusion

    Accessibility

    Accessibility / WCAG
    No established conformanceEditorial inferenceA platform-wide WCAG conformance commitment is not established.

  14. 6.7

    overall score

    Mapped product surfaces

    No product-specific frontend mapping is established. The conclusions below remain provider-level.

    Build and control

    Frontend builder
    YesEditorial inferenceLimited configurable turnkey front end; Bragg is primarily PAM/content infrastructure.
    Template library
    YesEditorial inferenceTurnkey implementations can reuse configurable components; a drag-and-drop template library is not established.
    Custom design
    YesEditorial inferenceYes through turnkey implementation and bespoke operator content.
    Headless frontend
    YesVerified conclusionYes — API-led PAM/HUB can sit behind operator or third-party front ends.

    Web and app delivery

    Responsive design
    YesVerified conclusionYes — HTML5/mobile web delivery.
    PWA
    OptionalEditorial inferenceOperator/front-end dependent; not a named Bragg product.
    Native apps
    Operator or specialist front-end responsibility; no Bragg consumer app productEditorial inference

    Acquisition and onboarding

    SEO readiness
    YesEditorial inferenceConfigurable at the operator front-end; not a differentiating PAM feature.
    A/B testing
    YesEditorial inferenceAvailable through data, campaign and front-end integrations; exact tooling depends on scope.
    Social login
    YesEditorial inferenceCan be integrated in the PAM registration flow subject to KYC and market rules.
    Registration flow
    Configurable PAM onboarding with KYC, age, geolocation and responsible-gaming controlsVerified conclusion

    Accessibility

    Accessibility / WCAG
    UnresolvedWCAG conformance level, VPAT status and accessibility-audit status remain unresolved for Bragg frontends. Responsive or configurable delivery does not establish accessibility conformance.

  15. 6.3

    overall score

    Mapped product surfaces

    • Casino BuilderFrontend builder: Yes · Template library: Yes · Custom design: Yes · Responsive design: Yes · Headless frontend: No — The builder is template/CMS-led; a headless component API and bring-your-own-frontend contract are not established. · Native apps: None — No standard operator iOS or Android application framework appears in the current product portfolio.

    Build and control

    Frontend builder
    YesSupported conclusion
    Template library
    YesSupported conclusion
    Custom design
    YesSupported conclusion
    Headless frontend
    NoEditorial inferenceThe builder is template/CMS-led; a headless component API and bring-your-own-frontend contract are not established.

    Web and app delivery

    Responsive design
    YesSupported conclusion
    PWA
    NoEditorial inferenceCasino Builder is responsive; a standard PWA package is not established.
    Native apps
    NoneEditorial inferenceNo standard operator iOS or Android application framework appears in the current product portfolio.

    Acquisition and onboarding

    SEO readiness
    YesSupported conclusion
    A/B testing
    NoEditorial inferenceA general native frontend experimentation module is not established.
    Social login
    NoEditorial inferenceSupported social identities and a social-login module are not established.
    Registration flow
    Configurable fields, KYC requirements and antifraud triggersSupported conclusion

    Accessibility

    Accessibility / WCAG
    UnresolvedWCAG target, accessibility audit and conformance are unresolved.

  16. 6.0

    overall score

    Mapped product surfaces

    No product-specific frontend mapping is established. The conclusions below remain provider-level.

    Build and control

    Frontend builder
    YesVerified conclusion
    Template library
    YesVerified conclusion
    Custom design
    YesVerified conclusion
    Headless frontend
    YesVerified conclusionOperators can build a custom frontend against Swarm, Partner and Odds Feed APIs, with an open-source frontend library available.

    Web and app delivery

    Responsive design
    YesVerified conclusion
    PWA
    YesEditorial inference
    Native apps
    iOS, AndroidVerified conclusion

    Acquisition and onboarding

    SEO readiness
    YesVerified conclusion
    A/B testing
    YesVerified conclusionRuns through the CRM as AI-powered A/B testing of campaigns and messaging, not a built-in site or app split-test tool in the frontend builder.
    Social login
    YesVerified conclusionThe Swarm API supports authentication and registration through Google, Facebook and Auth0.
    Registration flow
    Configurable API-driven multi-step flowEditorial inferenceSwarm exposes registration, social authentication, CAPTCHA, terms acceptance and partner-configured KYC steps. A universal one-click flow is not established.

    Accessibility

    Accessibility / WCAG
    UnresolvedWCAG conformance, audit status and target level remain unresolved for the operator frontend.

  17. 5.8

    overall score

    Mapped product surfaces

    • Self-Service CasinoHeadless frontend: Yes — Partial. Custom front ends can use platform files and APIs, but a formal headless CMS or composable frontend framework is not established.
    • Slots BundleResponsive design: Yes

    Build and control

    Frontend builder
    NoVerified conclusionFront-end gets customized by giving developers access to the casino files or by having the SoftGamings team build it, not through a no-code page builder.
    Template library
    YesVerified conclusion
    Custom design
    YesVerified conclusion
    Headless frontend
    YesEditorial inferencePartial. Custom front ends can use platform files and APIs, but a formal headless CMS or composable frontend framework is not established.

    Web and app delivery

    Responsive design
    YesVerified conclusion
    PWA
    NoEditorial inferenceResponsive web; a distinct PWA product is not established.
    Native apps
    UnresolvedA specific first-party iOS or Android app deliverable is not established; responsive and mobile delivery do not by themselves prove native-app support.

    Acquisition and onboarding

    SEO readiness
    YesEditorial inference
    A/B testing
    NoEditorial inferenceA native experimentation suite is not established.
    Social login
    UnresolvedNot established.
    Registration flow
    Configurable by operator and jurisdictionEditorial inferenceThe platform supports conventional registration and KYC levels; crypto marketing language does not override jurisdictional verification duties.

    Accessibility

    Accessibility / WCAG
    UnresolvedWCAG conformance remains unresolved.

  18. Rank 18

    Soft2Bet

    4.8

    overall score

    Mapped product surfaces

    • CMSFrontend builder: Yes — The in-house CMS includes a drag-and-drop builder for landing pages, lobbies and promotional hubs, with reusable components, dynamic banners, personalized modules and SEO controls. · Headless frontend: Yes · Native apps: iOS, Android — Soft2Bet supports native mobile delivery and app-store submission; availability varies by market and brand.

    Build and control

    Frontend builder
    YesSupported conclusionThe in-house CMS includes a drag-and-drop builder for landing pages, lobbies and promotional hubs, with reusable components, dynamic banners, personalized modules and SEO controls.
    Template library
    YesSupported conclusion
    Custom design
    YesSupported conclusion
    Headless frontend
    YesSupported conclusion

    Web and app delivery

    Responsive design
    YesSupported conclusion
    PWA
    NoEditorial inferenceResponsive mobile web and native iOS/Android delivery are standard; an installable PWA is not. A bespoke operator frontend can still implement one.
    Native apps
    iOS, AndroidSupported conclusionSoft2Bet supports native mobile delivery and app-store submission; availability varies by market and brand.

    Acquisition and onboarding

    SEO readiness
    YesSupported conclusion
    A/B testing
    YesSupported conclusion
    Social login
    NoEditorial inferenceA standard social-login product is not established in the PAM, frontend or onboarding scope. Market-specific identity integrations remain possible.
    Registration flow
    Configurable by market, KYC tier and riskSupported conclusion

    Accessibility

    Accessibility / WCAG
    UnresolvedWCAG conformance and an accessibility audit are unresolved; this does not establish non-conformance across deployed brands.

Frontend acceptance test

  1. 01Inventory every editable route, widget, content type, metadata field, translation and regulated message.
  2. 02Demonstrate roles, draft and approval workflow, preview, scheduling, rollback, audit history and cross-brand isolation.
  3. 03Run the selected responsive, PWA and native routes separately through release, offline, deep-link and account-state tests.
  4. 04Prove the headless API covers registration, account, wallet, cashier, KYC, bonuses and game launch without hidden widget dependencies.
  5. 05Set a named WCAG target and test keyboard, focus, semantics, contrast, zoom, screen readers and error recovery on the actual implementation.

Frequently asked questions

Is a frontend builder the same as a complete CMS?

No. A builder can control selected pages, widgets, lobbies or sportsbook layouts without controlling every route, content type, metadata field, account screen or regulated message. The exact editable surface, roles, publishing workflow and rollback behavior must be defined for the selected product.

Does custom design mean the operator owns the frontend?

No. Bespoke design can still be delivered as a supplier-controlled theme or paid implementation. Repository access, source-code ownership, deployment control, component rights, change responsibility and post-termination use are separate contract terms.

Does headless delivery guarantee complete frontend freedom?

No. Headless establishes an API-driven route, not complete API coverage or independence. Registration, wallet, cashier, KYC, bonuses, game launch, account controls and regulated messages can still require supplier widgets or restricted workflows.

Are responsive web, PWA and native apps interchangeable?

No. Responsive web adapts in the browser. A PWA adds an installable web-app layer and can add service-worker behavior. Native iOS and Android apps use separate binaries, release processes and store obligations. A provider can support one route without establishing the others.

Does an unresolved WCAG field mean the frontend is inaccessible?

No. Unresolved means that a product-specific conformance target, audit, VPAT or equivalent accessibility record is not established. It is not converted into No. Procurement should name the target level, components in scope, test method, remediation owner and release gate.

Does A/B testing mean the page builder can test layouts?

Not necessarily. The established scope may be CRM campaigns, messages, promotions or player journeys rather than randomized frontend components. Experiment allocation, success metrics, statistical rules and the exact editable surface must be established separately.