RTX5Roadmap

RTX5 planning scope, dependencies and available evidence. Status comes from the shared product record; unverified capabilities remain planned or preview, with no invented launch date.

Planned

Platform

Web Trading Terminal

Browser access requires an approved URL, tested browser/task matrix and recovery results. Availability applies only to the client scope named in the review record. Web Trading: build not published; owner not assigned; reviewed not verified.

Platform

Mobile Trading

Confirm iOS and Android official access records, supported builds and tested tasks separately; hosted controls also depend on an approved RX5 runtime. Mobile Trading: build not published; owner not assigned; reviewed not verified.

Developers

RX5 Rust SDK & Compiler

Rust-based SDK for building trading bots and indicators. Compiler, runtime and desktop backtesting require separate build-specific acceptance scope. RX5 Rust SDK: build not published; owner not assigned; reviewed not verified.

Platform

RX5 Bots & Indicators

Bots can execute trades; indicators calculate and display information. Permissions, runtime limits and monitoring controls. Bots & Indicators: build not published; owner not assigned; reviewed not verified.

Developers

Desktop Backtesting

Desktop-based strategy backtesting with configurable spread, fees, slippage, fill modes and reproducibility controls. Desktop Backtesting: build not published; owner not assigned; reviewed not verified.

Developers

Source Migration

Conversion from Pine Script, MQ5 and MQH to RX5 Rust with documented compatibility limits, diagnostics and manual fixes. Not every script will convert automatically. Source Migration: build not published; owner not assigned; reviewed not verified.

Platform

Broker-Hosted Algorithm Execution

RX5 execution independent of phone connectivity requires runtime tests and broker approval. Proposed US$10–20/month, or an eligible broker reward. Algorithm Hosting: build not published; owner not assigned; reviewed not verified.

Solutions

Prop Firm Technology

Challenge rules, daily/static/trailing drawdown formulas, breach lifecycle, simulated vs live accounts, contests and leaderboards. Prop Firm Technology: build not published; owner not assigned; reviewed not verified.

Solutions

Broker Automations

IB rules, group triggers, commission calculations, rewards, campaigns, eligibility, expiry, approval workflows, dry-run and event deduplication. Broker Automations: build not published; owner not assigned; reviewed not verified.

Solutions

Payments Workflows

Deposit/withdrawal request, approval, processing, refund, reconciliation and cash vs credit ledger. RTX5 is broker payment software, not a custodian. Payments: build not published; owner not assigned; reviewed not verified.

Developers

REST & WebSocket API

Authentication, API scopes, commands, idempotency, retries, rate limits, versioning and sandbox examples. REST API: build not published; owner not assigned; reviewed not verified. WebSocket API: build not published; owner not assigned; reviewed not verified.

Preview

Platform

Desktop Trading Terminal

Windows package records are available from the release source. Client task coverage and build-level qualification remain unverified. Desktop Trading: build not published; owner not assigned; reviewed not verified.

Solutions

CRM

CRM planning scope includes onboarding, IBs, groups and payment workflows. Included with Entry commercially; connector and build evidence must be confirmed. CRM: build not published; owner not assigned; reviewed not verified.

Solutions

Broker Administration

Manager/Admin web and Windows EXE are intended client scopes. Publish tested task, permission and isolation records before claiming parity or availability. Broker Administration: build not published; owner not assigned; reviewed not verified.

Connectivity

Bridge / Gateway

Bridge connectivity requires named adapter evidence. Included with Standard for agreed scope; Entry add-on US$2,000/month. Bridge / Gateway: build not published; owner not assigned; reviewed not verified.

Connectivity

FIX 4.4 / 5.0

FIX scope requires a certified adapter, application/session version, message dictionary and recovery results. Commercial inclusion alone does not establish availability. FIX 4.4: build not published; owner not assigned; reviewed not verified. FIX 5.0: build not published; owner not assigned; reviewed not verified.

Platform

RX5 Marketplace

Distribution platform scope for bots, indicators and tools. Purchase, entitlement, activation and demo require explicit acceptance results; refund and publisher terms require approved policies. RX5 Marketplace: build not published; owner not assigned; reviewed not verified.

Milestone Scope, Owners and Evidence

The cards above outline product direction. This record explains the dependencies and evidence needed for the RX5 milestones; it does not assign launch dates.

Swipe horizontally to view all columns.

RX5 milestone record — proposed responsible roles
MilestoneScope and dependencyResponsible rolePublished evidence / reviewed date
Rust SDK, bots and indicatorsVersioned compiler/SDK, runtime permission model and original examples; desktop compatibility must be established.SDK lead and algorithm product owner; named owner to be confirmed.Build, acceptance results and reviewed date: not yet published.
Desktop backtestingLicensed fixtures, declared execution assumptions, reproducibility and export; depends on the tested toolchain.Backtesting engineering lead; named owner to be confirmed.Tested desktop build and reviewed date: not yet published.
Broker hostingApproved-instance execution, quotas, monitoring, stop/restart and broker plan; depends on runtime and account isolation.Runtime lead; named owner to be confirmed.Runtime build, operational tests and reviewed date: not yet published.
Mobile algorithm controlStart, stop and monitor a hosted bot; verify phone-disconnect and reconnect behavior against a supported runtime.Mobile product owner and runtime lead; named owners to be confirmed.Client/runtime matrix and reviewed date: not yet published.
MarketplaceDemo, purchase, entitlement, activation, updates and publisher/refund terms; depends on runtime compatibility and approved policies.Marketplace product owner; named owner to be confirmed.Implemented transaction flows and reviewed date: not yet published.
Source migrationAuthorized supported inputs, diagnostics, Rust output and parity fixtures; depends on compiler and desktop testing.Compiler/SDK lead; named owner to be confirmed.Versioned support matrix and reviewed date: not yet published.

Join a Scoped Beta or Preview

Ask for the specific workflow you need so a product owner can confirm whether suitable access is available.

Swipe horizontally to view all columns.

What to include in an access request
Your requestWhat the preview agreement should establish
Product and taskFor example, validating an original RX5 strategy or evaluating hosted monitoring. Confirm the exact feature scope.
Deployment and environmentBroker/tenant context, client operating system, account type and intended number of users or instances.
Permissions and dataRequired actions, account/instrument scope and permission to use any submitted source or historical data.
Test and feedbackAvailable build, entry requirements, known issues, support contact, feedback route and an agreed end/review point.

This roadmap reflects current planning intent. Feature scope, timing and availability may change. A feature listed as "Planned" is not evidence that a named production build has shipped or passed acceptance tests. Do not publish planned features as released.