White-label iGaming platform
sixteen87 gives operators a complete, multi-tenant platform: player front-end, wallet and accounts, casino, sportsbook, lotto, bonus engine, gamification and a command centre that keeps everything under control.
Products
Each product is built on the same account, wallet and back-office, so a brand can start with one vertical and add the rest without a migration.
Built to fit
Devices, payments, branding and scale are decisions your team makes in the back-office, not tickets in a supplier’s queue.
One responsive player front-end for desktop, mobile web and wrapped apps, with the same wallet and session everywhere.
Cards, bank rails, mobile money, e-wallets and vouchers behind one interface, enabled per brand and routed by rule.
Themes, lobbies, content, limits and promotions are configuration, not code changes, so your team ships without a release.
Add a vertical, a currency or a second brand to the environment you already run.
Each operator runs in its own environment with its own data, credentials and release schedule.
Every movement of value is an immutable entry in minor units, so balances are provable to the cent.
Bonuses, lobbies, limits and journeys are edited in the back-office and take effect without a deployment.
Queues, alerts and dashboards reflect the platform as it is right now, not as of last night’s export.
The people who answer your questions are the people who build and run the platform.
Why sixteen87
A side-by-side view of the choices that shape an operator’s first year.
| Area | sixteen87 | Legacy platforms |
|---|---|---|
| Time to launch | Weeks: a provisioned environment, your brand applied, content and payments switched on | Months of integration, custom build and vendor coordination |
| Player front-end | Modern, modular and restyled per brand without touching the core | Template-bound, with every change routed through the supplier |
| Bonus tooling | Any promotion expressed as rules, weighted by game category, costed per campaign | A fixed menu of bonus types and a spreadsheet for the economics |
| Operations | One command centre for players, payments, risk, content and promotions | Several consoles, several logins, several sources of truth |
| Integrations | Aggregated content and payments behind single interfaces, enabled per brand | One-off integrations that each brand pays for again |
| Tenancy | Your own isolated environment and data residency | Shared database rows separated by an operator id |
How the platform grew
Every product was added to the same account, wallet and back-office rather than bolted on beside them.
Markets
Localisation, payment coverage and regulatory configuration are built into each environment, so entering a new territory is a setup task rather than a project.
Light front-end, mobile money and voucher rails, and lobbies tuned for smaller screens and slower networks.
Jurisdiction-specific limits, identity gates, reporting exports and data residency, all configured per environment.
Several brands under one licence or several licences under one group, with shared or separate player bases as you choose.
Content portfolio
Content is integrated once through a single aggregation layer and switched on per brand and jurisdiction.
News
· 4 min read
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· 5 min read
When a player moves between a bet, a spin and a lotto ticket, money should not have to move with them. A ledger-first wallet makes that possible and makes every balance provable.
Read article· 4 min read
Lotto has its own rhythm: scheduled draws, cut-offs, liability and prize tiers. None of that requires a separate platform if the wallet and the operator console already speak lotto.
Read articleTell us about your market, your licence and the products you want to launch first. We will come back with a plan and a demo environment.
