Skip to main content

Protection is a decision order, not a feature

Most platforms bolt player protection onto the side of a commercial engine. We are building the opposite, and the controls that layer will orchestrate already ship with every deployment.

What is built, and what is being built

Harm-First Orchestration is in active development. It is not live today, and we will not describe it as live until it is.

The controls it will orchestrate are live now, in the account core of every deployment. They are the five below.

The controls that ship today

Nothing on this list is planned, in beta or behind a flag. Each one is in the account core of every deployment, which is what makes it hard for anything else in the platform to route around.

Account safety states

Freeze, suspend, ban and self-exclusion live on the account itself rather than in a marketing tool, so every other part of the platform has to respect them.

Deposit and session limits

A limit a player sets on themselves is enforced by the account core, not by the campaign that would benefit from ignoring it.

A player record in the back office, with the account state, the trust tier, identity and screening status shown as chips above the document checks that produced them.

A five-tier trust model per player

T0 to T4, with thresholds configurable per brand. Deposit and withdrawal eligibility is decided automatically rather than through a support ticket.

The decisions tab of a player record, filtered by operation and outcome, showing a deposit decision with its amount, its result, the player tier and the policy applied to it.

Compliance-gated transactions

The wallet reads a player's standing before any money moves, so compliance and payments act as one system rather than two that disagree.

The audit trail, where configuration, compliance and authentication events share one stream and every row carries the actor, their role, their location and the device they used.

A full-platform audit trail

Every action by every player, staff member and system lands in one searchable stream. It is what a regulator evidence pack is built from.

Screenshots on this site are captures of the demo tenants MaxBet and LuckyOni. Every figure on screen is demo data.

Our position

Most platforms treat player protection as a module bolted to the side of a commercial engine. We are building the opposite: a decision hierarchy where harm and safer gambling are evaluated first, then fraud and abuse, then compliance, and only then commercial optimisation. Commercial optimisation proceeds only once the layers above it return clear.

Harm-First Orchestration is in active development. It is not live today, and we will not describe it as live until it is. What is live today is the set of controls it will orchestrate, listed above: player safety states in the account core, a five-tier trust model per player with thresholds configurable per brand, compliance-gated transactions where the wallet checks a player's standing before any money moves, and a full-platform audit trail covering every action by every player, staff member and system.

Operators remain responsible for their own regulatory obligations in every market they serve, including advertising standards, affordability and player protection requirements. Our job is to give them tools that make the right decision the easy one.

The order we are building

Each layer has to return clear before the layer below it is allowed to run. That sequence is the whole design, and it is the part that cannot be added later.

In active development

Read the Harm-First page
  1. 01

    Harm and safer gambling

    Player protection holds the highest priority and can stop a downstream commercial action before it starts.

  2. 02

    Fraud and abuse

    Potential fraud, bonus abuse and suspicious behaviour are assessed before any incentive or payout proceeds.

  3. 03

    Compliance

    Identity, jurisdiction and regulatory controls decide whether the action is permitted at all.

  4. 04

    Commercial optimisation

    Retention, bonuses and engagement are optimised only once every layer above has returned clear.

Where your duties begin, and where ours end.

The platform supplies controls and a record. It does not absorb an operator's regulatory obligations, and no platform can.

What we supply

  • Safety states held on the account itself

    So a campaign cannot reactivate a self-excluded player, and a frozen account cannot quietly take a deposit.

  • Tiered checks before money moves

    Deposit and withdrawal eligibility decided against the thresholds you have set for that brand.

  • A record that survives the question

    One audit stream behind every action, which is what a regulator evidence pack is assembled from.

  • Staffed withdrawal review

    Every withdrawal passes a person, with the player's compliance profile shown beside the amount.

What stays with the operator

  • Which markets you accept

    Decided by your licence and by each jurisdiction's own rules, not by us.

  • Where the thresholds sit

    You set the tier thresholds, the limits, and the evidence each tier requires.

  • Advertising and affordability duties

    Marketing standards and affordability requirements in every market you serve are yours to meet.

  • What happens to an escalated case

    We record it. You decide it.

Where a person can find help

This site sells platform technology to operators, so nobody arrives here in difficulty by accident. The organisations below are independent of us, free to contact, and worth having on any page a player can reach.

18+ only

18+ only. The platform ships player protection controls as standard: deposit and session limits, self-exclusion, account freeze and suspension, and tiered compliance checks before money moves.

Scalara Platform is a business to business supplier. We provide casino platform technology to licensed operators and to operators launching under our licence. We do not accept wagers and we do not offer gambling services to players.

Bring your player safety requirements to the first call.

Tell us the thresholds your regulator expects, the limits you want enforced and the evidence you need to produce. Those are configuration questions, and they are cheaper to settle before a deployment than after one.

Harm-First Orchestration is in active development. The controls above are not.