relioops
Contact Book a demo
Before you book a demo Curious what a broker CRM looks like day to day? Ours is running one click from here. Watch it work, then click around the real screens at your own pace. No sign-up, no sales call. Take a look

Forex CRM, back office and MT4/MT5 for brokers

Brokerage technology,
built and operated for you.

A broker CRM, MetaTrader support, live risk and infrastructure, run by one team. Whatever you take, it runs on one client record — so your CRM, your platform and your payment provider always agree about the same account.

Platforms
  • MT4
  • MT5
  • cTrader
Products
  • Broker CRM
  • Live risk
  • Client area
Connectivity
  • Bridge & liquidity
  • Payments
  • Platform APIs
Environments
  • Production
  • Disaster recovery
  • Monitoring
Request a technical demo See what we deliver
On the board now
  1. 01The client signs up; identity is checked
  2. 02The record is written; the deposit posts to it
  3. 03The client area reads it; the account goes to the platform
  4. 04Prices come in; an order goes out to the venue
  5. 05The fill comes back; exposure books on the desk
  6. 06Desk history to the record; the record is mirrored
The operating board One client record
Client Trade Recovery relioops runs it We connect to it
Products & services / 02

Everything a brokerage runs on, from one team.

Buy the CRM. Hand us MT4 and MT5. Put live risk on your book. Let us run the infrastructure, and build the tools your desk is missing.

See what we deliver
What we operate MT4 / MT5 · cTrader · CRM · Risk · Infrastructure · DR
01 / Launch — what we stand up before your first client 02 / Operate — the back office you get

We set the
brokerage up.

We set up your whole brokerage: white label or your own licence, MT4 or MT5 servers, the client area, payment and KYC providers, and the website in front of it. You launch with one team instead of five vendors.

  • 01.01 / Licensing
  • 01.02 / White label
  • 01.03 / Website
  • 01.04 / Infrastructure
  • 01.05 / Launch

Then you run it
from this back office.

The relioops broker CRM and back office: clients and trading accounts, deposits and withdrawals, IB payouts, KYC status and platform activity — on one screen your team works from all day, so nobody has to switch systems to answer a client.

01.04Infrastructure 02.01MT4 / MT5
01.02White label 02.02CRM / Client area
01.01Licensing 02.03KYC / AML
01.03Website 02.04PSP / Payments
01.05Launch 02.05APIs / Integrations
Product 01 / Client area

A client area your
traders actually use.

Explore the client area

The trader-facing side of the same record: verification, deposits and withdrawals, trading accounts and support — on your brand. Clients serve themselves, and everything they do lands on the record your desk reads.

  1. 02.01Verification

    Verified once, on the record

    Documents go up from the client area and land on the same client record the compliance desk reviews. The trader sees the state the desk sees, not a copy of it.

  2. 02.02Deposit

    Money in, without a ticket

    Card, crypto or bank, chosen by the trader; the deposit is settled against the client record and the wallet the desk reconciles. No email to finance, no second ledger.

  3. 02.03Withdrawal

    Money out, with the rules applied

    Eligibility, limits and the return-to-source rule are checked against live account state before the request reaches the desk. What the trader is told is what will happen.

  4. 02.04Trading accounts

    Accounts opened from the record

    A trader opens an MT5 account in the client area and it is created on the server against their record. Balance, equity and status read back from the platform.

  • Client area
  • CRM
  • KYC / AML
  • Account management
  • Transactions
  • Partner operations
Product 02 / Live risk

Your book, live
from MetaTrader.

See risk management

Forex risk management that works while positions are open: exposure, long and short positions, net book, account risk and dealing activity, read live from MetaTrader through the Manager API — so you act on the book as it is now, not as it was yesterday.

Long Short
Monitoring
  • Symbol exposureTracked
  • Client exposureTracked
  • P&LLive
  • AlertsActive
Risk & dealing view
  • Exposure
  • Long / Short
  • Net position
  • Dealing
  • Alerts
  • Monitoring
Service 01 / MetaTrader

MetaTrader, run for you.

Explore MetaTrader services

MetaTrader support for brokers, end to end. We set up, migrate and run your MT4 and MT5 servers — with monitoring, backup, disaster recovery and technical support — so your team works on the business, not on the server. cTrader connected through Open API.

  1. 01

    Environments we run

    Primary and DR environments, access servers and desks in more than one region, deployed and administered to your own account structure and rules.

  2. 02

    Built for your desk

    Dealer tools, internal dashboards, reporting systems, client portals, back-office automation and trading algorithms — written against the same APIs and deployed with the rest of your stack.

  3. 03

    Through published APIs

    Manager, Gateway, Report and Web APIs on MetaTrader; Open API on cTrader. Nothing is scraped, and nothing depends on a screen staying open.

Client terminal, mobile terminal, web terminal and back-office APIs
Algo trading · market making

Your price on every venue.
Your fill first.

We build and run the engine behind your flow. Prices stream over FIX API to your MT4 and MT5 servers, LPs, ECNs and exchanges at the same time. When two venues disagree, the arbitrage is taken before the gap closes. Market making quotes both sides, manages inventory and builds volume on your book.

Where the money comes from
  • Spread incomeEvery quote you make on your own book earns the spread instead of paying it.
  • Arbitrage P&LEvery gap between two venues is booked as profit, both legs recorded.
  • VolumeSteady volume means better LP terms, tighter costs and a book that is always live.
  • FIX API orders and pricesOrders sent and routed, prices distributed, to every venue you connect.
  • Cross-venue arbitrageSpots the gap between venues and closes it automatically.
  • Market makingTwo-sided quotes, skew by inventory, spreads per client group.
  • Safe on a live bookPosition limits, loss limits and a kill switch on every strategy.
Algo trading
Service 02 / Infrastructure

We run the servers
your book trades on.

Explore infrastructure

Production and disaster-recovery hosting for your brokerage: data centres, low-latency links, bridge, gateway and liquidity connectivity, monitoring, backup and failover — built to stay up and recover fast.

Operated environment

Servers don’t
page themselves.

Production and disaster-recovery environments available in twelve locations worldwide, watched continuously. An alert reaches the on-call engineer, not a queue.

Locations
  • London
  • Frankfurt
  • Amsterdam
  • Limassol
  • Dubai
  • Singapore
  • New York
  • Tokyo
  • Sydney
Why brokers call us

Four things brokers
ask us to fix.

These are the four problems we are usually brought in for. Each one has a product or a service on this page that answers it.

  1. 01

    The same client exists three times.

    Every deposit, leverage change and re-verification has to be entered again somewhere, or reconciled after the fact.

    With relioops

    One client record. CRM, platform and payment events write to the same history.

  2. 02

    Risk is read after the event.

    Exposure, margin level and platform health sit in separate terminals, usually read once the session is over. By then the account has been a problem for hours.

    With relioops

    Exposure, margin and platform health on one live view, with rules that act while the position is open.

  3. 03

    Every new provider is a project.

    A new PSP, a second KYC vendor, another platform or another brand means an integration written from scratch — and one more place where the same number can drift.

    With relioops

    Providers connect once. New brands and platforms inherit the connection instead of rebuilding it.

  4. 04

    Month-end is assembled by hand.

    Client, trading and payment figures are exported, pasted together and checked twice, because no single system holds the whole picture. The reporting is only ever as current as the last export.

    With relioops

    Reporting reads the operational record the business already runs on. No export, no second set of numbers.

One client record. Every product on this page writes to it. One record · Every product

What we connect to

It plugs into what
you already run.

Explore integrations

Connect MetaTrader, your CRM, PSPs, KYC vendors, liquidity and internal systems through supported APIs — manager APIs, provider APIs and webhooks. Nothing has to be replaced, and adding a provider takes configuration, not a project.

01

Route

Each connection goes through its own supported interface — manager APIs, provider APIs, webhooks. Nothing is scraped.

02

Retry

A failed delivery is retried with backoff until it lands. Nothing is dropped on the floor.

03

De-duplicate

A repeated event is discarded as already applied. The book sees it once.

04

Reconcile

Every delivery is reconciled against the provider statement. Nothing fails quietly.

Blog

From the operations desk.

All posts
Compatibility · some of what we connect to
01

Trading platforms

Accounts, groups, symbols and execution through the platform’s own manager interface.

  • MetaTrader 5
  • MetaTrader 4
  • cTrader
02

Payments

Deposits, withdrawals and settlement reconciled against the client record, not a provider dashboard.

  • BridgerPay
  • Match2Pay
  • Visa
  • Mastercard
03

Identity & compliance

Verification results land on the client record, so onboarding state is one value rather than three.

  • Sumsub
  • Onfido
  • iDenfy
04

Client communication

Voice, messaging and campaign activity logged against the same history the desk works from.

  • Twilio
  • Voiso
  • Mailchimp
05

Infrastructure

Deployed to your cloud account or ours, on managed components rather than bespoke ones.

  • Amazon Web Services
  • Microsoft Azure
  • Kubernetes
  • PostgreSQL

A sample, not a list: any platform, provider or internal system with a published interface can be connected. Marks shown are the property of their respective owners and indicate technical compatibility, not partnership or endorsement.

Who we work with

Where brokers start.

Most engagements begin with one product or one service. The rest is there when you want it.

  1. 01

    Launching a brokerage

    The licence is in hand or close. The operational stack has to exist before the first client does — and it has to be defensible on day one, not retrofitted after the first audit.

    Usually starts with White labelCRMFirst platform
  2. 02

    Consolidating a running book

    The business works. It just runs on six tools and a spreadsheet, and every number has two versions. You want one record without stopping to replatform.

    Usually starts with CRMPaymentsReporting
  3. 03

    Multi-brand groups

    Several brands, several servers, one back office. Each brand needs its own front and its own rules; the controls, reporting and reconciliation behind them should be the same system.

    Usually starts with Shared layerPer-brand configuration
  4. 04

    Funded trader programmes

    Evaluation rules, breach handling and payout eligibility have to be enforced against live account state — not reconstructed from yesterday’s report once a trader disputes the result.

    Usually starts with Risk rulesAccountsPayouts
How it starts

Three steps — none of
which is a migration.

  1. 01

    Map what you run

    One working session on your actual setup: platforms, providers, brands, and the points where the record breaks today. You keep the map whether or not anything follows it.

    You change nothing
  2. 02

    Connect, do not replace

    The layer is stood up alongside the systems you already run, reading and writing through their own interfaces. Your platform, your providers and your data stay where they are.

    Nothing is migrated
  3. 03

    Operate with engineering behind it

    Ticket-based support with named technical contacts, incident tracking across platform, CRM, infrastructure and integrations — and, where it is warranted, a dedicated Slack or Microsoft Teams channel to your engineers.

    Tracked, not chatted
Next step

See it running on your stack.

A technical session on your own setup: your MetaTrader environment, CRM, providers and integrations, and what we would deploy, migrate or build first.

Book a technical demo Explore the platform