Architecture
Your players live in your database.
This is the part most platform deals get wrong. On Surge, every brand is its own deployment with its own database, so your player data is not sitting in a shared table behind someone else's WHERE clause.
CONTROL PLANE · brand registry, operator accounts, sessions, audit, payment credentials
Demo brandown deploymentsurge-brand-demo
Operator brandown deploymentsurge-brand-<brand>
Your brandown deploymentsurge-brand-<you>
Your deployment binds only your own database. Its back office is physically incapable of reading another operator's players: there is no cross-brand filter to forget, because no other brand's data is present. Players, ledger, bets, casino rounds, bonuses, KYC, chat and affiliates all stay inside your brand.
EDGEDeployed on Cloudflare
Every brand runs as its own Cloudflare Pages project on the edge runtime, close to your players wherever they are.
ISOLATIONOne brand, one database
Adding a brand means a new database, its migrations, its binding and its deployment, scripted rather than hand-rolled SQL.
OPERATIONSOne login, your brands
Operator identity sits in the control plane, so disabling a team member removes their access everywhere at once.
