Skip to content
All news

Multi-tenant isolation: why every operator deserves their own environment

· sixteen87 Team · 4 min read

A row of separate dark glass cubes each holding a small gold core light

Shared platforms are efficient for the supplier. Isolated environments are safer for the operator. Here is how sixteen87 provisions both without making anyone choose.

Most white-label platforms put every brand in the same database and the same application servers, separated by an operator id on each row. It is efficient, and for many brands it is fine. It also means a noisy neighbour can slow your lobby, a migration for one brand is a migration for all, and a data request from your regulator involves extracting your rows from everyone else’s.

sixteen87 takes a different position. Each operator is provisioned into an isolated environment: its own databases, its own application processes, its own configuration and its own credentials. The code is shared, the state is not.

What isolation buys you

  • Performance that depends on your traffic, not the platform’s busiest brand
  • Data residency you can point to: your environment runs in the region your licence expects
  • Maintenance windows and upgrades scheduled around your calendar
  • A clean answer to audit and regulatory requests, because the boundary is physical
  • Credentials and integrations that belong to your brand alone

What it does not cost you

Isolation used to mean bespoke hosting and slow releases. That is a tooling problem, not an architectural one. Environments are provisioned from a template through the platform orchestrator, which creates the databases, deploys the services, issues certificates and registers the brand in the operator console in one run. Upgrades are rolled out environment by environment, which means a problem is contained rather than shared, and a brand that wants to stay on a version for a week can.

Groups and sub-brands

Operators who run several brands can choose the boundary that suits them. A group can have one environment with several brands sharing a player base and a wallet, or separate environments per licence with a group-level view in the orchestrator. Segments, campaigns and content rules are defined per brand either way, so the marketing team never has to guess which brand a change affects.

The principle is simple: the supplier’s convenience should never be the operator’s risk. An isolated environment makes the platform a little more work to run and a great deal easier to trust.

Written by the sixteen87 Team.

More from the team

· 4 min read

Why wagering requirements should be weighted by game category

A single multiplier treats a high-volatility slot and a low-margin table game as if they cost the operator the same. They do not. Here is how category weighting fixes the maths without confusing the player.

Read article

See it on your own brand

We will show you the platform features behind this article running on a demo environment.