Scalara Platform
The product, and the subject of this site. Player accounts, the wallet and ledger, compliance, games, brand control and the back office, sold to operators on two commercial routes.
Why the order of decisions is the product
Scalara Platform is built by Scalara Labs and licensed through Quantum Digital Solutions. Three names, one operation, and a deliberate order in which the platform decides things.
What we are building, and what we are not
Scalara Platform is a casino platform sold to operators in two ways. New operators launch under our licence. Licensed operators take the platform layer and keep their own licence, their own payments and their own commercial relationships. Both routes run the same software.
That much is ordinary. The part we are actually building the company around is less ordinary, and it is a question about sequence rather than about features.
The order things are decided in
When a player deposits, claims a bonus or asks to withdraw, several systems have an opinion. A risk tool. A compliance rule. A retention engine. In most stacks those opinions are formed separately, and whichever system is quickest to act usually acts first. That is normally the one trying to grow revenue, because it has the fewest checks to run.
We are building the layer that fixes the order: player harm and fraud settle first, compliance next, and commercial optimisation only once the layers above it return clear.
In active development
Harm-First Orchestration is in active development. It is described here as design intent, not as behaviour available on the platform today. What exists now, and what does not, is set out in full on the Harm-First page.
What exists today
Parts of that order already run. The wallet reads a player's compliance standing before money moves. A five-tier trust model decides deposit and withdrawal eligibility per brand rather than through a support ticket. Every action by every player, staff member and system lands in one searchable trail. Those are inspectable in the back office, and we would rather you inspected them than took our word for it.
The orchestration layer that coordinates all of it, on every event rather than only on money movements, is the part still being built.
Why a company rather than a product
The reason this needs a company rather than a feature is that the order has to hold everywhere, permanently, including on the days when reordering it would make more money. That is an organisational commitment before it is a technical one, which is why it is on the about page rather than in a release note.
The part of that order you can already inspect
Every deposit and withdrawal request is recorded against the player it was made for: what was asked for, what the platform decided, the trust tier it was judged at and the policy that judged it. The list filters by operation and by outcome, so a denied withdrawal can be found and explained rather than argued about.
Decisions, per player
Captured in a demo tenant, so every figure on the screen is demo data.
How we decide what to build
Four rules that have to survive contact with a deadline, because a rule that does not is a preference.
Protection before optimisation
The decision order puts player harm and fraud ahead of commercial optimisation. That layer is in active development, and it is labelled as such everywhere it appears.
One codebase, every deployment
Our own brands and every private copy sold to an operator run identical software. A fix is built once and reaches everyone, so quality compounds instead of forking.
Publish the number or drop it
Every figure on this site carries its source. Where a figure belongs to a partner it is attributed to them, never presented as a result we measured.
Say what is not built yet
Roadmap capabilities carry a label wherever they appear, including in the meta description of their own page. Nobody should discover the roadmap in month three.
Three names you will find, and what each one is
A buyer meets all three during diligence, on the contract, on the licence and in the code. Here is which is which.
Scalara Labs
The software company that builds the platform. Scalara Labs also builds custom software and iGaming titles, and the platform team sits inside it rather than beside it.
Quantum Digital Solutions
The licensed entity. It holds the gaming licence that operators on the White Label route trade under. The full wording, the scope, the validity window and the public register are on the licensing page.
Operators on the Turnkey route hold their own licence, and ours does not apply to them.
We publish the price, the licence and the roadmap status. Anything we cannot show you, we say we cannot show you.
The people who make these calls
Thirteen people run product, engineering, compliance, delivery and commercial. The executive group is below, and the full team is on the leadership page.
Executive
3 peopleHassan Naveed
Founder and Chief Executive Officer
Sets the direction of the platform and the commercial model behind it.
Built and scaled businesses across real estate and software in the UK, the UAE and Europe, and now leads the development of a regulated, AI native iGaming platform.
Branko Petrovic
Chief Technology Officer
Owns the platform architecture and the engineering organisation that builds it.
A technical leader specialising in high performance, real time systems and platform architecture.
Gayle
Chief Legal Officer
Owns licensing, jurisdictional scope and the commercial contracts behind both routes.
An expert in gaming licensing, multi jurisdiction compliance and commercial contracts for regulated markets.
Ask us the questions diligence asks
Thirty minutes with the team who built it, in the live back office, on your own operation rather than on a sample one.
We reply within one working day.
