rMarket takes provider data in, applies your market logic and delivers execution or settlement out — server-side infrastructure built for load, in two editions: Financial and Sports.
Financial and sports markets differ commercially, but share the engineering problem: fast inputs, market logic, transactions and settlement under load. Choose the edition that matches your scope.
A price update arrives from a liquidity provider.
The price is normalised and distributed to rPlatform and, where integrated, an MT5 server. A client order is routed and executed; the fill is written to history.
rMIB and reporting read the same execution history.
A match update arrives from a sports-data feed.
Markets and odds are recalculated; a bet is accepted and processed.
The bet settles when the event resolves; the transaction is written for the player account and reporting.
Provider connections for your own feeds (coverage is confirmed per provider); rPlatform, a supported MT4/5 setup or your sportsbook front end as the consumer.
rMarket takes provider feeds in and serves platforms, servers and risk out. Choose the edition first: Financial connects liquidity and MT4/5; Sports connects sports-data providers.
Integrated, normalised and distributed; provider coverage confirmed per setup.
Server-side integration for execution and accounts, where supported.
Feeds into markets, odds and settlement.
Client front end and risk signals — native.
Choose Financial or Sports when you start the demo — the environment, settings and provider connections differ. Configure instruments or markets, routing and settlement rules.
A rMarket environment in the edition you choose — Financial or Sports.
Instruments or sports markets, provider connections, routing and settlement rules.
Configuration and provider setup when production is activated.
A business email and company details. Provider credentials to connect your own feeds.