TECHNOLOGY

Intelligence needs infrastructure

What runs underneath the r* products: models applied to specific product decisions, in-house GPU compute, real-time data engineering, and APIs with clear boundaries. Each one is verifiable in the products that use it.

AI
01 / AI MODELS

Models applied to product decisions

The shared foundation makes models available to every product; a product uses them where it needs a decision made — an answer, a score, a segment, an action. The three applications below are where that is verifiable today.

01
Assistance and workflow automation

Answering from your knowledge, choosing the next step and completing it across systems — the engine behind rAgent.

02
Behavioural clustering, anomaly detection, risk scoring

Linking trading, account and payment signals into explained scores — the engine behind rMIB.

03
Lifecycle and segmentation decisions

Which segment, which communication, which limit — inside rPAM’s account operations.

SEE IT INrAgentrMIBrPAM
02 / COMPUTE & GPU

In-house compute for the intelligence layer

RoboAI operates its own GPU compute for model development and inference, shared across product teams. One foundation serves seven products; no product has to build its own.

01
Model development

Training and evaluation for the product models above.

02
Inference

Serving models inside the products, close to the data they act on.

SEE IT INrAgentrMIB
FIG. 14 — SHARED COMPUTEDEVELOPMENT · INFERENCE
Shared AI computeMODEL DEVELOPMENT · INFERENCE
GPU RESOURCESDATA LAYERENGINEERING
03 / DATA & REAL-TIME ENGINEERING

Where provider data becomes a market, a bet or a payment

Integrating external providers, normalising streams, running high-load services and keeping operational history — the discipline rMarket and rGateway are built on.

E—01External-provider integrations
E—02Data normalisation and event processing
E—03Real-time systems and high-load services
E—04Operational history and analytical workflows
E—05API connectivity between technology layers
SEE IT INrMarketrGateway
04 / APIs, BOUNDARIES & INTEGRATION

Every product has its own API and its own boundary

A product is deployed, configured and billed on its own. Where two r* products are connected, the integration is native and implemented — not every pairing exists. Towards your systems, integration goes through documented APIs, and the connectors that are live for your case are disclosed in the demo flow.

01
Native where implemented

Accounts, payments, risk, execution and experience meet without custom work on the connections that exist — each product page lists its own.

02
Documented towards your stack

APIs for the systems you already run; third-party connectors stated per product.

How integration worksSee the products