BoundsCheck
One integration. A policy engine and audit log for every brand.
Platforms carry the compliance burden for every brand they host. BoundsCheck gives you one API to integrate and a separate tenant per brand, each with its own rules, keys and record.
Multi-brand tenancy is live: each brand gets its own keys, rules, admin and record. Flat monthly pricing by active players across the platform.
tenant northstar-dfs decision ALLOW region US-CO · Denver County activity contest_entry · paid format salary_cap policy northstar v2026.09.28 check_id chk_5ea0…b7c3
Every brand has a different map, and you answer for all of them.
A platform that hosts several brands ends up with several state lists, several sets of exceptions, and one engineering team maintaining all of it. When a brand's processor asks about a transaction, the platform has to produce the record.
Policies diverge
Brands launch in different states, run different formats and exclude different counties. A single platform-wide list serves none of them well.
Changes pile up
When each brand's policy is code, every brand's state change is a ticket for your team. Policy should be data that brand operators can edit within limits you set.
Records get mixed
A brand's audit trail has to be separable from every other brand's. Shared logs make answering a request for one brand slow and risky.
Per-ping pricing scales badly
Multiplying per-check fees across brands makes you ration checks. Flat pricing by active players lets you check every paid action everywhere.
Shared engine, separate tenants.
- A tenant per brandEach brand gets its own API keys, policy rule set, eligible-states list, webhook and audit log, kept in its own database. Boundaries and fraud signals are shared and maintained once.
- Scoped adminBrand operators see and edit only their own policy and log, embedded in your back office or in our hosted panel with required two-factor sign-in. Platform staff see everything. Every admin change is logged with who made it.
- Per-tenant modes RoadmapA new brand runs checks without enforcing while established brands enforce. Flip any tenant to off in an emergency without touching the others.
- Per-brand eligible-states endpointsEach brand's app reads its own live list, with ETags, so opening a state for one brand is that brand's policy edit.
- One integrationYour platform calls BoundsCheck once per paid action with that brand's key and the device fix. Format comes from the contest record, never the request. Same client code across brands.
- Separable audit trailsEvery check is stored under its tenant with inputs, signals, policy version and result. Export one brand's history for a processor or regulator without touching another's.
- Spoofing and VPN signals for everyoneThe fake-GPS flag, VPN and hosting ranges, IP-versus-GPS distance, impossible travel, stale locations and timezone mismatches, applied the same way for every brand.
- Platform-wide pricingOne flat monthly fee by active players across all brands, unlimited checks. Pass it through however your commercial model works.
Questions platform teams ask.
Can each brand on our platform have its own policy?
That is how BoundsCheck is built for platforms: each brand becomes a tenant with its own API key, policy rule set, eligible-states list and audit log, while boundaries and fraud signals are shared. Each brand's data is kept in its own database, so one brand's records can be exported or deleted without touching another's.
Do brand operators get their own admin access?
Yes. A brand operator sees and edits only their own policy and audit log, either embedded in your back office or in our hosted panel, which requires two-factor sign-in. Platform staff see all tenants. Every admin change is logged with who made it.
How is pricing handled across brands?
Pricing is a flat monthly fee by monthly active players, counted across the platform. Unlimited checks. You can pass it through to brands however your commercial model works.
Can one brand run checks without enforcing while another enforces?
Yes. Each brand's integration decides when to act on decisions, so a new brand can run checks without enforcing while established brands enforce. A per-tenant switch for this in the admin panel is on our roadmap.
Hosting more than one brand?
Tell us how many brands you run, which segments they're in, and roughly how many active players in total. We'll walk through the tenant model and what integration looks like on your stack.