rPlatform is the client-facing layer of a multi-asset trading and investment business: web and mobile trading, accounts and connected trading services. It is the experience; execution comes from a supported backend, with rMarket as the native option.
Customer-facing trading across devices, with accounts, positions and history in one place.
CFD and exchange trading and investing journeys in one client experience.
TradingView integration is in the product scope; confirm availability for your setup in the demo.
Programmatic access for your own tools and partners.
A client opens the mobile app to trade a CFD and fund the account.
Quotes stream from the execution backend — rMarket in this example; the client places the order; the position, margin and history update as execution confirms. A deposit started from the same screen is processed through rGateway when that integration is included.
The client sees one coherent experience on web and mobile; execution and payments run on the backends you have integrated.
A supported execution backend — rMarket natively, or a compatible integration confirmed for your setup.
rPlatform needs an execution and data backend to show anything; rMarket is the native option, compatible integrations are confirmed per setup. Payments and portal are optional additions.
Quotes, execution and account state — native.
Connected server-side through rMarket, where supported for your setup.
Deposits and withdrawals inside the client journey — native.
Portal and app shell around the platform — native.
The demo is the client experience on sample instruments: configure asset groups, account types and branding, then open it on web and mobile.
A configured rPlatform environment with web and mobile client views.
Instruments and asset groups, account types, branding and client-facing settings.
Configuration and branding when production is activated.
A business email and company details. Production needs a live execution source.