A second brand is a settings page.
GameBridge runs unlimited brands on one codebase and one database with complete player isolation. Network System Defaults set the baseline; each brand overrides what it needs across 100+ settings, from payment rails and pixels to VIP ladders and game exclusions.
- 1
- codebase and database for every brand
- Network defaults
- with per-brand overrides for everything that differs
- 100+
- settings per brand
- Working Brand
- switcher scopes every screen to one brand
- Per brand
- feature flags, payment rails, pixels, senders and content exclusions
Shared where it saves work, isolated where it matters.
Players, wallets, ledger rows and sessions belong to exactly one brand. Configuration inherits from the network until a brand says otherwise.
Isolation and inheritance
- Unlimited brands on one codebase and one PostgreSQL database
- Complete player isolation: accounts, wallets and history never cross brands
- Network System Defaults with per-brand overrides across 100+ settings
- 26 brand configuration pages, from Country and States to Chat Management
- 20 feature flags to switch systems on or off per brand
- Global or brand-scoped suppressions for email and SMS
What each brand controls
- Payment rails through Payment Management
- Pixels and server-side tracking across 7 platforms
- Email and SMS senders and templates
- VIP ladders, XP settings and tier-up bonuses
- Game catalog exclusions and rule-based categories
- Bonus defaults: game contribution rates, playthrough up to 50x, max-win cap, expiry and sports min odds
- Responsible Gaming defaults, brand characters, app icons and splash screens
Business model as a setting
- Sweepstakes, Real Money or Crypto per brand
- The setting gates AMOE and the cashier: Store + Redeem or Deposit + Withdraw
- Wallet types per model: USD, EUR and GBP, BTC, ETH and USDT with full crypto precision, or GC and SC
- Country and state allow and deny lists with a restricted-region page and GPS re-check
- Live casino tables from Iconic21 imported per brand
Running the network
- Working Brand switcher sets the brand every console screen acts on
- Network Configuration: Brands, System Defaults, Wallet Types, Payment Management
- JSON import and export carries bonuses, banners, packages, segments and campaigns between brands and environments
- Segments are reference-protected against deletes and renames across bonuses, banners, campaigns, packages and gamification
- One Activity Log for every admin action on every brand
- Role-based access with action keys for every money-moving operation applies across the network
Sweepstakes here, real-money there, one ledger.
A group can run a sweepstakes brand with Gold Coins, Sweeps Coins and mail-in AMOE entries next to a real-money brand with fiat wallets, deposits and withdrawals. Both write to the same double-entry ledger and answer to the same console.
- The business model gates AMOE and the cashier mapping without code changes
- State-level geo with GPS re-check for sweepstakes; country and state allow and deny lists per brand
- Responsible Gaming defaults and KYC configured per brand
- Per-brand pixels, senders and payment rails keep marketing and money separate
Create, override, import, switch on.
- Step 1Create the brand
Add it under Network Configuration and pick Sweepstakes, Real Money or Crypto. Wallet types and the cashier follow from that choice.
- Step 2Override what differs
Walk the brand configuration pages: payment rails, sender identities, pixels, VIP ladder, RG defaults, categories and exclusions. Everything else inherits from System Defaults.
- Step 3Import proven content
Bring bonuses, banners, packages, segments and campaigns across as JSON. Packages support a dry run before anything is written.
- Step 4Switch on the flags
Enable the systems this brand needs from 20 feature flags, set the Working Brand and soft launch. Hours of configuration, not a new deployment.
What a group gets from one core.
Add brands without adding stacks.
- One codebase, one database, one console
- Network defaults so a shared change lands on every brand that has not overridden it
- Working Brand switcher for the shared team
- Feature flags to stage what each brand offers
Every brand its own funnel, same toolkit.
- Per-brand pixels across 7 platforms
- Senders and templates per brand
- Import a banner set or journey into a new brand as JSON
- Segments and packages scoped to the brand
Isolation by design, rules by brand.
- Complete player isolation
- Business model and AMOE per brand
- Geo lists and RG defaults per brand
- Suppressions global or brand-scoped, with audited lift
What multi-brand groups ask.
Do brands share players or wallets?
How long does a second brand take?
Can brands run different business models?
Can one team work across brands?
Can we copy configuration between brands?
Is there a limit on the number of brands?
Go deeper.
Multi-brand groups
The commercial side: how groups license, launch and run several brands with GameBridge.
और जानेंOperator console
Ninety-one screens, role-based access, an Activity Log and the Working Brand switcher.
और जानेंStore, packages, banners and CMS
Per-brand packages, banners, CMS pages and message templates with JSON import and export.
और जानें