Platform & Reference Architecture

On top of your CRM.
Not instead of it.

One reference architecture, five modules, 6–8 week deployments — without moving your player data or replacing your stack. The technical detail your engineering team will want.

See production patterns

Why this matters before the diagrams.

A platform built on one reusable core means you don't pay for a custom build, you don't wait 6–12 months, and every future improvement reaches you without a re-implementation. That's why deployment is weeks, not quarters — and why pricing isn't consultancy day-rates.

The architectural argument.

Most "AI platforms" for iGaming are services consultancies in disguise — every client is a custom build from scratch. Arctura runs on a single reference architecture under every module. Each new deployment shares 70–80% of the codebase with the last. What changes are the adapters to your specific stack.

The reference architecture

Five layers, two IP zones. Your data and your CRM live in the bottom three layers — Arctura owns the top two.

"What you keep, what we bring, and why a deployment is weeks not quarters."

Layer 5 — Dashboards & APIsOne screen per team. White-label optional.
RG officer dashboard CRM team dashboard Compliance dashboard Platform admin console REST / GraphQL / Webhooks
Yours / white-label
Layer 4 — Data PlaneYour player data never leaves your infrastructure.
Player database (yours) Event stream (yours) Analytics warehouse (yours) PII boundary Audit storage (hybrid)
Your infrastructure
Layer 3 — Adapter LayerPlugs into the CRM, PAM and payments you already run.
CRM: Optimove, Smartico, Customer.io, Bloomreach, SFMC, custom PAM: SoftSwiss, EveryMatrix, Pragmatic, Playtech, custom Chat: Intercom, Zendesk, LiveChat Payments: Stripe, Adyen, crypto KYC / voice: Sumsub, Veriff, Onfido, Twilio
Deployed in your env
Layer 2 — Domain LogiciGaming economics modelled in, not bolted on.
Bonus abuse patterns Player risk scoring VIP qualification rules Churn signal definitions RG escalation policies Configurable thresholds 20+ languages Workflow orchestration
Arctura core
Layer 1 — Core EngineThe AI you'd otherwise spend 6–12 months building.
ML model repository (uplift, churn, biometrics, RG, voice) LLM orchestration (SGR, multi-agent, tool use) Evaluation framework Audit & explainability Regulatory templates (UK / SE / NL / MGA)
Arctura core
Stays yours: your data, your CRM, your stack — end-to-end. Ours to maintain: the AI core, so you don't build it.

How a routine moment moves through the platform

Three real flows, end-to-end. Each one starts with a commercial outcome and ends in your dashboards.

"A player at risk costs you twice — a regulatory fine if missed, and a real welfare failure. This is how Arctura catches the signal in real time and puts an actionable alert in front of your RG officer."

Flow A — Real-time RG alert

Trigger: Player sends to support chat — "I really need to win back what I lost yesterday."

  1. L3Chat connector forwards the message to Arctura via secure API.
  2. L2Pre-filter: language detection, basic spam check, RG keyword check.
  3. L1RG signal detector evaluates the message via SGR-structured LLM call → distress score 0.87, category "loss chasing", confidence 0.92.
  4. L1Behavioural signal aggregator pulls the player's recent activity → deposit velocity 3× normal, night session pattern, chasing-losses pattern.
  5. L1Audit engine logs the full reasoning trace.
  6. L2Risk scoring methodology combines signals → final risk score 0.79 → "intervene".
  7. L5Alert appears in the RG officer's queue with full context and recommended action.
  8. L4Audit log written to your compliance storage.

"Most of your reactivation budget goes to players who'd have come back anyway. This is how a weekly campaign run ends up spending only on the players whose behaviour actually changes — while your raw data never leaves your side."

Flow B — Batch retention campaign (uplift modeling)

Trigger: Weekly retention campaign — "who should we send a reactivation bonus to?"

  1. L5CRM team triggers the weekly campaign run.
  2. L3Adapter pulls the inactive player segment from your PAM and warehouse.
  3. L4Aggregated player history read — no raw PII, behavioural aggregates only.
  4. L1Uplift model scores each player → P(deposit | bonus) − P(deposit | no bonus).
  5. L2Filter down to "persuadables" (uplift > threshold).
  6. L1Personalised message generation per player via LLM orchestration.
  7. L3Campaign pushed back into your CRM (Customer.io / Optimove / Smartico).
  8. L4Control group hold-out maintained for next week's uplift validation.
  9. L5Campaign queued. Expected lift visible to the CRM team.

"Every routine chat handled by a human is cost you don't need. Every VIP handled by a bot is revenue you just risked. This is how one message gets resolved automatically — and how a VIP gets pulled out to a human before that happens."

Flow C — PlayerDesk conversation (multi-agent support)

Trigger: Player writes to chat — "I can't withdraw my money, what's wrong?" (any language, any platform).

  1. L3Chat connector routes the message to PlayerDesk.
  2. L1Triage Agent detects intent (payout issue), language, urgency, VIP status check.
  3. L2VIP rules check → not VIP → continue with AI handling.
  4. L1Knowledge Agent retrieves relevant policies, common payout issues, KYC status.
  5. L3Action Agent calls PAM API → checks KYC status and pending withdrawals.
  6. L1Response Agent generates a contextual answer with specific account-state info.
  7. L1QA Agent runs real-time evaluation (hallucination, tone, accuracy).
  8. L3Response sent back through the chat connector.
  9. L1Audit engine logs the full conversation with reasoning trace.
  10. L1If complexity / VIP threshold exceeded → Escalation Agent prepares a summary and hands off to a human L2 / VIP manager.

6–8 week deployment vs 6–12 month in-house build.

Production-tested algorithms vs starting from research papers. Your data stays yours. Your CRM stays in place.