Hierarchical Casino Operator Platform
This platform models a distribution structure that is common in some markets and almost absent from off-the-shelf casino software: a root owner delegates to sub-administrators, who delegate further, each managing their own branch of players and their own balances. There is no payment gateway in the core model — credit flows down the tree and settlements flow back up, all as manual, recorded operations. That single decision reshapes everything: permissions, reporting, and the audit trail all have to be branch-aware.
Server monorepo with API and notifications worker, plus separate player client and admin console repositories
Documented as an architecture record. The hierarchy and balance model are the interesting parts and neither needs a live instance to explain.
Credit flowing down a hierarchy
Watch how balance moves between levels of the tree, and how every step leaves an attributable record because no gateway exists to produce one.
Top of the tree. Issues credit downward and sees every branch.
How balance reaches a player without a payment gateway.
Highlights
Everything is scoped to a branch
The hierarchy is not a feature sitting on top of the platform; it is the coordinate system the platform is written in. An administrator sees their subtree and nothing above or beside it, and that constraint reaches into permissions, wallet operations and every report.
Hierarchy and permissions
The administrator tree, delegation rules and branch-scoped access control.
- A root owner delegates to sub-administrators, recursively.
- Permissions resolve against position in the tree, not a flat role name.
- An administrator can never see or act on a sibling branch.
Wallet operations
Manual credit and debit between hierarchy levels and to players.
- No external payment gateway in the core model.
- Every movement is recorded as an attributable administrator action.
- The audit trail is the only settlement record, so it has to be complete.
Game integration
Provider catalogue, game launch and session handling for third-party titles.
- Catalogue management for enabling titles per branch.
- Launch integration keeps provider sessions separate from platform identity.
Operations and content
Reporting, support tooling, CMS blocks, banners and notifications.
- Reports are branch-scoped by default rather than filtered after the fact.
- A dedicated worker handles notification delivery off the request path.
Applications and API modules
Four deployables and eleven backend modules. Note that audit sits alongside wallet as a first-class module — with no payment gateway, the audit trail is the only settlement record. 15 units across 4 groups.
Applications
4Hierarchy & money
5Gaming
2Platform
4Stack by layer
Delivered work
Hierarchy and money
- Administrator tree with recursive delegation and branch-scoped permissions.
- Manual credit and debit operations between hierarchy levels.
- Complete attribution of every balance movement to an acting administrator.
- Branch-scoped reporting across players, balances, activity and admin actions.
Product surfaces
- Player web application and an administrator console.
- Provider catalogue with game launch integration.
- CMS blocks, banner management and notification tooling.
- Dedicated notifications worker separate from the API.
Modules and demo strategy
Branch scoping
The coordinate system the whole platform uses.
- Permissions and reports resolve against tree position.
- Sibling branches are invisible to each other by construction.
Manual balance model
Replaces the payment gateway with recorded operations.
- Fits the target market's distribution structure.
- Puts the entire settlement burden on the audit trail.
Provider integration
Third-party titles alongside the operator's own surfaces.
- Catalogue entitlement is branch-aware.
- Provider sessions stay separate from platform identity.