MT4, MT5 and cTrader trading infrastructure
Trading operations,
run from one place.
Running several MT4, MT5 or cTrader servers usually means the same change made five times, and mistakes nobody can trace. relioops puts every server in one console: accounts, groups, symbols, routing and platform health. Make a change once, apply it everywhere, and see who made it.
One console for every server
Live and demo, one brand or twenty, managed from one screen. We read each platform through its official manager API, so what you see is exact.
Every change is recorded
Group moves, leverage changes and symbol edits are logged with who made them and why. No more guessing what changed overnight.
See which clients are affected
When a session drops or a bridge slows down, you see the accounts it hits, not only the server name. Your desk acts before clients call.
Change a group once. It applies everywhere.
Group settings on the left, session health and routing on the right. One change reaches every server, with no copy-paste between terminals.
Account and group management
Open, classify and move trading accounts without opening the platform terminal. Group templates carry the right leverage, margin and symbol rules, so an account that changes segment gets the correct setup automatically — no manual edits to remember.
- Account opening, live and demo, from the client record
- Group templates for leverage, margin and symbol rules
- Bulk moves with a preview of what will change
- Per-brand defaults on a shared configuration
- Balance operations with reason codes and an author
Symbols, spreads and sessions
Maintain symbol sets, spreads, swaps and session times per group and per brand. You make a change once and it is applied the same way on every server, so your servers never drift apart.
- Symbol sets per group, per brand
- Spread and markup rules
- Swaps, sessions and trading hours
- Apply once across multiple servers
- Change history per symbol
Execution and routing
See bridge and gateway state, routing rules and liquidity coverage next to the accounts they serve. Answering a routing question takes one screen, not a second system and a phone call.
- Bridge and gateway status
- Routing rules by group and symbol
- Liquidity coverage per instrument
- Execution and fill telemetry
- A/B and demo routing for testing
Platform health monitoring
We track server sessions, connectivity and service state continuously, and every alert names the affected accounts, not just the host — so you can act before clients start calling, and you know exactly who it touched.
- Session and connectivity monitor
- Service state per environment
- Alerting routed to the responsible desk
- Incident timeline against the client record
Your whole stack in one view.
Terminals, access servers, trade servers, bridge and liquidity, with what each layer is doing right now.
platform changes made once, across every server, in the last year
What it reaches
- MT5 Manager API
- Accounts, groups, symbols, deals, balance operations and session state.
- Read / write
- MT4 Manager API
- Accounts, groups, symbols and trade records on legacy environments.
- Read / write
- cTrader Open API
- Accounts and trading data for cTrader environments.
- Read / write
- Bridge / gateway
- Routing configuration and connection state for the bridge in use.
- Read / write
- Liquidity providers
- Coverage and session availability per instrument, through the bridge.
- Read
What it connects.
Reached through each system’s own interface, so nothing has to be replaced to be included.
Trading platforms
Accounts, groups, symbols and execution through the platform's own manager interface.
Infrastructure
Deployed to your cloud account or ours, on managed components rather than bespoke ones.
Marks shown are the property of their respective owners and indicate technical compatibility. They are not a claim of partnership or endorsement.
