Skip to content
Protocolzone Protocolzone

Distribution module

White-labelled front end

Per-tenant presentation on a shared platform.

Part of the Ashva module inventory — a multi-tenant tote and fixed-odds betting platform we built and operate. The engineering practice behind it is our platform build and integration service line.

The white-labelled front end provides an operator-branded customer surface on the shared wagering platform. It is part of the platform’s per-tenant configuration and white-labelling model.

Define the customer journey

A brand rollout starts with its customer journeys and required presentation: registration, market discovery, bet placement and account activity. We review these against the platform before agreeing the configuration and any changes.

Establish the acceptance criteria

Accessibility, responsible-gambling controls, device coverage and the operator’s jurisdictional requirements need explicit acceptance criteria and verification for the deployed configuration. A branded interface alone does not establish that those requirements have been met.

Discuss a platform rollout.

Module facts

Module group
Distribution
Tenancy
Tenant-aware
Bet types
Fixed odds, Tote, Pari-mutuel, Exotics, Multi, Starting price, Same-race multi
Codes and verticals
Thoroughbred, Harness, Greyhound, Sports, Esports

Integration surfaces

  • Shared platform APIs
  • Tenant configuration

Capabilities

What white-labelled front end actually does.

White-labelled presentation

Branding and front-end configuration for operators on the shared platform.

Shared platform connection

The front end provides the customer-facing surface for the wagering platform.

Other distribution modules

Working on this problem yourself?

We will go through how this module handles it, what it deliberately does not do, and where we would make a different call today.