Explore RTX5 client applications, broker operations and the planned RX5 developer ecosystem. Compare licence scope, review published packages and confirm the tested capabilities for your deployment.
Explore terminals, trading engine, risk, administration and integrations. Availability and supported tasks must be confirmed for each build.
Product scope and publication status. Released or beta availability requires a named build and supporting review record.
Swipe horizontally to compare scope and release information.
| Feature | Status | Client and scope | Build / last verified | Release information |
|---|---|---|---|---|
| Desktop Trading | Preview | Windows baseline; confirm OS, package origin and publisher-signing evidence. | Build evidence not published Verification date not supplied | View roadmap and evidence |
| Web Trading | Planned | Browser and task scope require confirmation; public access may differ from beta access. | Build evidence not published Verification date not supplied | View roadmap and evidence |
| Mobile Trading | Planned | Confirm iOS and Android store or beta access separately. | Build evidence not published Verification date not supplied | View roadmap and evidence |
| CRM | Preview | Confirm onboarding, IB and each platform adapter in the agreed deployment. | Build evidence not published Verification date not supplied | View roadmap and evidence |
| Broker Administration | Preview | Confirm web/EXE builds and permitted tenant, account and group actions. | Build evidence not published Verification date not supplied | View roadmap and evidence |
| Bridge / Gateway | Preview | Availability is specific to an adapter and counterparty. | Build evidence not published Verification date not supplied | View roadmap and evidence |
| FIX 4.4 / 5.0 | FIX 4.4: Preview / FIX 5.0: Preview | Confirm dialect, session version, messages and certification per adapter. | FIX 4.4: Build evidence not published; FIX 5.0: Build evidence not published Verification date not supplied; Verification date not supplied | View roadmap and evidence |
| RX5 Bots & Indicators | Planned | Proposed Rust runtime; order permissions are separate from chart calculations. | Build evidence not published Verification date not supplied | View roadmap and evidence |
| RX5 Marketplace | Preview | Preview only; purchase, entitlement and publisher policies require confirmation. | Build evidence not published Verification date not supplied | View roadmap and evidence |
| Algorithm Hosting | Planned | Proposed broker runtime; resources and mobile controls depend on the broker plan. | Build evidence not published Verification date not supplied | View roadmap and evidence |
| Backtesting | Planned | Desktop-only in the current proposal; data and cost assumptions must be declared. | Build evidence not published Verification date not supplied | View roadmap and evidence |
| Source Migration | Planned | Authorized source and supported subsets only; desktop validation is required. | Build evidence not published Verification date not supplied | View roadmap and evidence |
| REST / WebSocket API | REST API: Planned / WebSocket API: Planned | Versioned contracts, sandbox access and executable examples are pending. | REST API: Build evidence not published; WebSocket API: Build evidence not published Verification date not supplied; Verification date not supplied | View roadmap and evidence |
| Prop Firm Technology | Planned | Proposed challenge rules, account types and breach handling. | Build evidence not published Verification date not supplied | View roadmap and evidence |
| Broker Automations | Planned | Proposed IB, groups and campaigns with approvals and eligibility controls. | Build evidence not published Verification date not supplied | View roadmap and evidence |
| Payments Workflows | Planned | Broker/provider transaction workflows; funding responsibility is separately defined. | Build evidence not published Verification date not supplied | View roadmap and evidence |
Account capacity, CRM and the agreed connection scope determine the right RTX5 licence. Use the pricing page for the complete inclusion list and optional services.
Up to 1,000 real accounts and unlimited demo account count. CRM is included; bridge and FIX are separately scoped options.
Up to 25,000 real accounts and unlimited demo account count. Agreed bridge and FIX connection fees are included; standalone CRM is optional.
Agree the real-account cap, deployment and entitlements in a written quote. Agreed bridge and FIX scope is included; final annual terms remain provisional.
Tell us the products you need, expected real-account count, client applications and integrations. We will distinguish available functionality from proposed scope.
Explore the proposed services, client scope and broker requirements across the RTX5 ecosystem.
Explore proposed signal and copy workflows with defined permissions, allocation and stop controls. The cards below illustrate tasks, rather than live signals or performance.
Reconcile activity
Compare instructions and fills
Illustrative workflow
Scope custom RX5 development, ownership and acceptance tests before engaging a developer.
API scope is planned; named versions and sandbox-tested examples are not yet published. Read the current API documentation.
Scope account data, order actions and event streams before integrating. Confirm protocol versions, permissions, limits, idempotency and recovery behavior in a tested sandbox contract.
Explore each area and its current scope. A product description does not establish tested build availability.
Explore RTX5 scope for traders, developers and broker operations within the Orrnn ecosystem.
Scope account operations, connectivity and risk requirements for your brokerage.
Review proposed allocation, reporting, permissions and fund-management workflows.
Explore client availability, task guides and published product information.
Review planned signal controls, strategy disclosures and account permissions.
Explore the proposed RX5 Rust SDK, desktop testing and marketplace workflow.
Proposed broker-hosted RX5 runtime: US$10–20/month, with resources and terms to agree.
Agree support hours, response targets, escalation and ownership in the broker quote.
Review proposed REST, WebSocket and FIX scope before requesting a tested contract.
Review RTX5 publication requirements, proposed workflows and the records needed to confirm deployment readiness.
Review product scope and supporting records before planning a deployment.
Release Notes lists published package records. Feature coverage, tested clients and signing evidence must be confirmed separately.
Check Windows package availability and request access instructions for the planned browser and mobile clients.
The proposed Rust workflow separates source development, desktop testing and controlled broker-runtime deployment.
Define each connection and operating responsibility before integration.
A provider or platform name does not establish an RTX5 partnership. Request the adapter version, supported operations and certification record.
Provide account capacity, client requirements and integrations so a demonstration can distinguish proposed scope from tested functionality.
Evidence needed for release readiness
Use named, dated records when evaluating release readiness and commercial scope.
Awaiting published review records
Confirm in the written quote
Explore the RTX5 trading and broker-technology scope, from account workflows to planned RX5 automation. Confirm each client, operating mode and integration against a named build before deployment.
Use these areas to scope your deployment. Supported tasks and client availability need build-specific confirmation.
Analyze markets, manage positions and execute trades through professional trading tools.
Explore planned Rust/RX5 development, desktop testing and hosted execution.
Monitor portfolios, allocations, performance and risk.
Manage capital, allocations, strategies and investor relationships.
Build and operate trading infrastructure with tools for execution, risk, clients and administration.
Use RTX5 infrastructure to build and operate modern trading services.
The availability registry distinguishes preview and planned scope from verified releases. Build-specific test records are required before a capability can be presented as released or beta. Licence inclusion and website examples are not release evidence.
Explore the platform or talk with the RTX5 team about your requirements.
