Players judge a platform by its front end. Operators live in its back office. CUBE, the operator side of our platform, is where promotions get built, withdrawals get approved, reports get read and players get managed, eight hours a day, every day.
That is why CUBE gets the same product attention as anything player-facing. Over the last six months of releases it has learned new languages, rebuilt its permission system, and grown real-time reporting. Here is the tour.
A back office that speaks Spanish and Portuguese
CUBE is now multilingual. Admins can switch the entire Back Office to Spanish or Portuguese from their profile, alongside English. If your operations team sits in Bogotá or São Paulo, they work in their own language: menus, modules, everyday navigation.
For a platform active across Latin America and Africa, this is not cosmetic. Training gets faster, mistakes get rarer, and hiring stops being constrained by English fluency. It is the back-office counterpart of what we already do player-side, where registration pages adapt to the player’s browser language automatically.
Who can do what, finally obvious
Permissions are where back offices quietly rot: roles accumulate, nobody remembers what “Promo Editor” can actually touch, and audits take days. We rebuilt the Roles & Permissions module around visibility. Permissions are grouped into collapsible sections with human-readable names and contextual tooltips. Roles can be created directly from the page, assigned during user creation instead of afterwards, and a role filter in user management answers “who has this role?” in one click.
Granularity grew with it. A dedicated PROCESS_WITHDRAWALS permission controls who can complete or void withdrawal requests. Access to sensitive report sections and the social feed is individually permissioned. This is operational hygiene, but it is also compliance: clean role separation is exactly what auditors and regulators expect from a certified platform. It is the same thinking behind our GLI-19 certification.
Numbers without asking anyone
Dashboard Reports bring the core KPIs into one view: registrations, FTDs, deposits, withdrawals, GGR, turnover and loyalty spend, with interactive charts, brand and period filters, and predefined ranges from “last 7 days” to full custom spans. GGR and turnover split into Total, Casino and Sport tabs; every figure displays in the selected brand’s currency; the loyalty section itemises free spins and free bets given and spent, with a data-freshness timestamp so nobody argues about how current the numbers are.
Less reliance on manual report requests means decisions happen where the work happens.
A hundred small frictions removed
The rest of the story is detail work, which is where back offices live or die. Time zones prepopulate from the selected brand across promotions, leaderboards, missions and rewards. Account expiration times display in the configured CUBE time zone instead of GMT. Self-exclusion supports custom end dates. Image uploads show recommended dimensions for every placement, and banners can opt into high-resolution handling with no compression. Even logging in got smarter: CUBE now returns you to the page you were actually trying to open.
Each of these shipped through our public release cycle; the full history is in our release notes, and the product overview lives on the Command Centre page.
Why we invest here
An operator’s margin is made or lost in operations. Every minute your team does not spend fighting the back office is a minute spent on players, promotions and growth. That is the standard CUBE is built to, and we would much rather show it than describe it.
For how the same product thinking plays out player-side, read Ivaylo on casino merchandising automation and Eran on payments for South Africa.
