Platforms with the possibility of multi-brands and affiliate sites
Introduction
Multi-brand platforms and white-label solutions allow one technological core to serve several independent casino brands and partner sites at once. This reduces development and support costs, speeds new sites to market, and gives centralized control over infrastructure. Below is a detailed description of the key components, architectural approaches and business processes.
1. Multi-tenant architecture
1. Data isolation
Shared database, separate schema: one instance of the DBMS, but according to the scheme for each brand.
Separate databases: separate bases for complete logical and physical separation, increased security.
Row-level tenancy: a single table with the 'tenant _ id' field, suitable for small projects with a small number of brands.
2. Tenant-aware microservices configuration
Each service receives a brand ID ('X-Tenant-ID') in the request headers.
Middleware or service dispatcher pulls configuration (topics, limits, payment methods) from a centralized config store.
3. Feature flags and customization
Feature-toggle per tenant: enable or disable individual features (VIP programs, tournaments).
UI theming: templates, CSS and logos are stored in file storage or CDN, associated with tenant ID.
2. White-label and affiliate sites
1. Domain and brand management
Support for arbitrary domains: SSL wildcard, automatic TLS update (Let's Encrypt).
Mapping domain → tenant: DNS records send a request to a specific config instance.
2. Content isolation
CMS solution with division of rights: each partner manages its own catalog of shares, the "About us" page, news blocks.
API gates: a single backend, but content by tenant\_ id is filtered and returned by the corresponding site.
3. Partner connection and affiliate portals
Partner's white-label dashboard: reports on attracted players, commissions, conversions.
API-hook 'and webhook' and: automatic transfer of registration/deposit data to partners.
3. Payment methods and billing
1. Tenant-specific payment flows
Configuration of available gateways: bank cards, e-wallet, cryptocurrency, local methods.
Set up brand-level fees and currency.
2. Billing and partner commission calculation
Three-level model: platform → brand → partner.
Calculation pipeline Gross Gaming Revenue (GGR) and Net Gaming Revenue (NGR) per tenant/partner.
Automated generation of invoices and statement of payments to partners.
4. Game and Provider Management
1. Provider Directory
Tenant-specific whitelisting: which game providers and slots are available to a particular site.
Versioning: the ability to keep outdated versions of the SDK for one brand and new for another.
2. RTP and Volatility Configuration
Global defaults and overrides per tenant: adjusting RTP within regulatory requirements.
API for "hot" changing settings without restarting the engines.
5. Safety and compliance
1. Multi-tenant access control
RBAC with tenant-level rights separation: Administrators of one brand do not see the other's data.
Centralized Identity-Provider (Keycloak/OAuth2) with SSO and SAML support for all sites.
2. Regulatory requirements
Localization of KYC/AML procedures: the same microservices, but with different providers and verification rules per tenant.
Logs and audit-trail: storing records of all operations in separated or marked tenant\_ id indexes.
6. Monitoring, analytics and reporting
1. Multi-table analytics
Data warehouse model "star" with measurement 'tenant _ id' in facts: GGR, DAU, conversions.
BI-dashboards (Looker, Tableau) with filters by brand and partner.
2. Real-time metrics
Prometheus with label 'tenant' for all service metrics.
Alerts per tenant: notifications of a drop in p99-latency, an increase in errors, exceeding limits.
7. CI/CD and Deployment
1. Mono repository and GitOps
Common codebase, but separate helm charts or Overlay configs per tenant (Kustomize).
Argo CD/Flux: automatic deploy of new versions of services and themes via git-commits.
2. Feature-branch per tenant
The ability to roll out experimental features first to one brand, test, then to the rest.
8. Scalability and fault tolerance
1. Horizontal scaling
Each tenant-aware service is launched with HPA in terms of total consumption, allowing you to serve peak loads at once on all brands.
2. Isolation of resources
Namespace or project level in Kubernetes for critical brands with dedicated resources (CPU/GPU, memory).
QoS classes: guaranteed resources for VIP brands.
Conclusion
Platforms with support for multi-brands and affiliate sites are built on a multi-tenant architecture, tenant-aware microservices and flexible configuration. White labels and affiliate portals receive individual branded frontend and reporting, and operators manage all sites from a single CI/CD pipeline and administrator console. This approach provides maximum resource savings while maintaining strict data isolation, payment settings, KYC/AML and analytics for each individual project.
Multi-brand platforms and white-label solutions allow one technological core to serve several independent casino brands and partner sites at once. This reduces development and support costs, speeds new sites to market, and gives centralized control over infrastructure. Below is a detailed description of the key components, architectural approaches and business processes.
1. Multi-tenant architecture
1. Data isolation
Shared database, separate schema: one instance of the DBMS, but according to the scheme for each brand.
Separate databases: separate bases for complete logical and physical separation, increased security.
Row-level tenancy: a single table with the 'tenant _ id' field, suitable for small projects with a small number of brands.
2. Tenant-aware microservices configuration
Each service receives a brand ID ('X-Tenant-ID') in the request headers.
Middleware or service dispatcher pulls configuration (topics, limits, payment methods) from a centralized config store.
3. Feature flags and customization
Feature-toggle per tenant: enable or disable individual features (VIP programs, tournaments).
UI theming: templates, CSS and logos are stored in file storage or CDN, associated with tenant ID.
2. White-label and affiliate sites
1. Domain and brand management
Support for arbitrary domains: SSL wildcard, automatic TLS update (Let's Encrypt).
Mapping domain → tenant: DNS records send a request to a specific config instance.
2. Content isolation
CMS solution with division of rights: each partner manages its own catalog of shares, the "About us" page, news blocks.
API gates: a single backend, but content by tenant\_ id is filtered and returned by the corresponding site.
3. Partner connection and affiliate portals
Partner's white-label dashboard: reports on attracted players, commissions, conversions.
API-hook 'and webhook' and: automatic transfer of registration/deposit data to partners.
3. Payment methods and billing
1. Tenant-specific payment flows
Configuration of available gateways: bank cards, e-wallet, cryptocurrency, local methods.
Set up brand-level fees and currency.
2. Billing and partner commission calculation
Three-level model: platform → brand → partner.
Calculation pipeline Gross Gaming Revenue (GGR) and Net Gaming Revenue (NGR) per tenant/partner.
Automated generation of invoices and statement of payments to partners.
4. Game and Provider Management
1. Provider Directory
Tenant-specific whitelisting: which game providers and slots are available to a particular site.
Versioning: the ability to keep outdated versions of the SDK for one brand and new for another.
2. RTP and Volatility Configuration
Global defaults and overrides per tenant: adjusting RTP within regulatory requirements.
API for "hot" changing settings without restarting the engines.
5. Safety and compliance
1. Multi-tenant access control
RBAC with tenant-level rights separation: Administrators of one brand do not see the other's data.
Centralized Identity-Provider (Keycloak/OAuth2) with SSO and SAML support for all sites.
2. Regulatory requirements
Localization of KYC/AML procedures: the same microservices, but with different providers and verification rules per tenant.
Logs and audit-trail: storing records of all operations in separated or marked tenant\_ id indexes.
6. Monitoring, analytics and reporting
1. Multi-table analytics
Data warehouse model "star" with measurement 'tenant _ id' in facts: GGR, DAU, conversions.
BI-dashboards (Looker, Tableau) with filters by brand and partner.
2. Real-time metrics
Prometheus with label 'tenant' for all service metrics.
Alerts per tenant: notifications of a drop in p99-latency, an increase in errors, exceeding limits.
7. CI/CD and Deployment
1. Mono repository and GitOps
Common codebase, but separate helm charts or Overlay configs per tenant (Kustomize).
Argo CD/Flux: automatic deploy of new versions of services and themes via git-commits.
2. Feature-branch per tenant
The ability to roll out experimental features first to one brand, test, then to the rest.
8. Scalability and fault tolerance
1. Horizontal scaling
Each tenant-aware service is launched with HPA in terms of total consumption, allowing you to serve peak loads at once on all brands.
2. Isolation of resources
Namespace or project level in Kubernetes for critical brands with dedicated resources (CPU/GPU, memory).
QoS classes: guaranteed resources for VIP brands.
Conclusion
Platforms with support for multi-brands and affiliate sites are built on a multi-tenant architecture, tenant-aware microservices and flexible configuration. White labels and affiliate portals receive individual branded frontend and reporting, and operators manage all sites from a single CI/CD pipeline and administrator console. This approach provides maximum resource savings while maintaining strict data isolation, payment settings, KYC/AML and analytics for each individual project.
