Skip to main content

Multi-Tenant and White-Labelling

The platform is designed to be deployed as a white-labelled product: each client organisation (tenant) gets their own branded, configured instance. To people inside that organisation, it looks and behaves like their product — their logo, their colours, their enabled features. The underlying platform is shared infrastructure; the surface presented to staff and customers is specific to each tenant.

What "white-labelled" means in practice​

When a tenant is set up, the platform is configured with that organisation's identity:

  • Branding — company name, logo, favicon, and colour scheme are applied throughout the admin panel and customer portal
  • Login theming — the customer-facing login page can be styled with a theme variant and custom background, making it feel like a proprietary product
  • Domain — each tenant typically operates under their own domain or subdomain

From a customer's perspective, there is no sign that the platform is shared with other organisations. From an agent's perspective, everything they see reflects their employer's brand.

Configuration is per-tenant​

Beyond branding, each tenant has its own configuration set. This includes:

  • Products and features enabled — modules like copy trading, bot trading, investment, sports betting, and casino can be toggled on or off. A tenant that doesn't offer copy trading simply doesn't see it anywhere in their admin panel or customer portal.
  • Trading account types and wallet types — each tenant defines the account structures and wallet categories that match their offering
  • Payment methods — deposit and withdrawal methods, processors, and limits are configured per tenant
  • Email templates and branding — outgoing emails use the tenant's name and template design
  • Reference data — supported currencies, countries, and languages can vary by tenant

This means two tenants running on the same platform can have completely different products visible to their customers.

What is fixed​

Not everything is customisable per tenant. The core platform behaviour — how leads move through the system, how the approval chain works, how permissions are granted, how financial transactions flow — is consistent across all tenants. Configuration changes the surface and the feature set; it doesn't change how the underlying workflows operate.

Similarly, the admin panel's structure (navigation, pages, general layout) is the same for all tenants. What changes is the data inside it, the branding around it, and which features are active.

Who configures it​

Initial setup (provisioning the tenant, configuring branding, enabling products) is typically done by a platform admin during onboarding. Ongoing configuration — adjusting colours, enabling a new product module, updating templates — is managed via Settings in the admin panel and follows the same permission controls as everything else.

See also​