RTX5 Web Trading Preview
Explore the proposed browser client for account views, charts and permitted trading actions. Public access, supported browsers and tested task coverage require confirmation.
Browser Access. Defined Scope.
The proposed web client provides browser access to an agreed set of account and trading tasks. Confirm browser versions, broker permissions and reconnect behavior before use. Desktop compilation and backtesting are outside this browser proposal.
The web terminal is coming soon. This page describes the planned browser workflow.
Proposed Features at Your Fingertips
Browser-Based Trading
Proposed browser access; public access and supported builds are not yet confirmed.
Real-Time Market Data
Market-data coverage depends on the broker, instrument permissions and connection state.
Advanced Charting Tools
Confirm supported charts, indicators and timeframes in the named web build.
Order Controls
Order actions require supported routes, account permissions and measured execution results.
Multi-Device Access
Confirm browser and device support separately; task coverage can vary.
Secure Environment
Review authentication, session expiry, permissions and transport protection for the deployment.
Designed for Modern Traders
Review the proposed browser workflow with your broker. Available controls, saved settings and accessibility behavior should be demonstrated in a named build.
Clean and intuitive interface
Evaluate navigation against the tasks supported by the preview build.
Smooth navigation
Test switching assets, timeframes and indicators under a defined workload.
Customizable layouts
Confirm available panel controls and layout persistence in the named build.
Dark & light mode support
Check available display themes and readability on the supported device.
Web Version vs Desktop Version
Browser support, client tasks and recovery
The public web terminal is coming soon. The tables below define the proposed task boundaries; they do not certify browser compatibility or feature parity.
Swipe horizontally to view all columns.
| Browser family | Compatibility information | Current evidence |
|---|---|---|
| Chrome / Edge | Exact browser version, operating system, session handling and order workflow. | Supported-version results have not been published here. |
| Firefox | Exact browser version, chart behavior, streaming data and reconnect tests. | Supported-version results have not been published here. |
| Safari | Exact macOS/iOS version, browser version and supported device workflow. | Supported-version results have not been published here. |
Swipe horizontally to view all columns.
| Task | Web | Mobile | Desktop |
|---|---|---|---|
| Charts, market data and orders | Planned browser workflow | Planned mobile workflow | Confirm for the supplied build |
| Balances, positions and history | Planned; server state is authoritative | Planned; server state is authoritative | Confirm for the supplied build |
| Hosted bot monitoring and control | Confirm scope during preview | Proposed start, stop and monitor | Requires eligible broker runtime |
| Local compilation and backtesting | Not in the current proposal | Not in the current proposal | Current proposed location |
| Install/access | Browser endpoint when released | Official store listing when released | Published package and broker credentials |
- 01
Recognize a lost connection
Treat quotes and account data as stale when the client reports a disconnected session. Do not infer that an order failed merely because an acknowledgement did not arrive.
- 02
Restore the session
Reconnect to the approved broker endpoint and reauthenticate if the session expired. Confirm the correct account and wait for market and account state to refresh.
- 03
Reconcile before retrying
Look up the original order in the server’s active orders and history. Match the order identifier and status before submitting another instruction.
- 04
Escalate an unresolved state
Record the client version, time, account reference and order identifier for broker support. Ask for server-side reconciliation when the client cannot establish the result.
Web control of a proposed broker instance
The client would display server state and request permitted actions. Broker bot execution remains on server infrastructure; the client does not run an unrestricted native strategy package.
Swipe horizontally to view all columns.
| Client task | Required information or behavior |
|---|---|
| Identify the instance | Show demo/live status, broker, account, package version, permissions, hosting charge and applicable risk limits. |
| Monitor state | Show server-reported lifecycle state, last heartbeat, P&L and risk status. Mark stale or unavailable data explicitly; a disconnected screen must not falsely show stopped. |
| Activate or change risk | Require confirmation for live activation and material risk increases. Use a request ID and expected version, then wait for the authoritative server result. |
| Choose a stop action | Explain stop-new-orders, cancel-pending-orders and close-position choices separately according to approved broker policy. Display the confirmed outcome. |
| Reconnect | Retrieve the latest instance, order and position state before retrying an uncertain request. A permitted hosted bot is intended to continue under server risk controls while the client is disconnected. |
| Notifications | Use authenticated notifications that prompt the user to open the client; do not put sensitive account secrets into push content. |
Proposed Uses for Supported Tasks
Trading on the go
Evaluate permitted account access from a supported browser and trusted device.
Quick market analysis
Confirm available market data, chart tools and refresh behavior.
Backup trading platform
Test the web fallback procedure and account reconciliation before relying on it.
Multi-device traders
Check device support and which settings persist across permitted sessions.
Performance to Validate
Qualify the web client on a named build, browser and device. Record workload, network conditions and reconnect results before relying on it for a trading task. No benchmark or uptime commitment is published here.
Review Security Requirements
Review the deployed web client against the broker’s access and data-handling requirements. The controls below are qualification requirements; implementation and test evidence must be supplied for the named build.
Encrypted connections
Confirm TLS configuration and handling of expired or untrusted certificates.
Secure login systems
Confirm authentication factors, role permissions and session expiry.
Data protection protocols
Agree data locations, retention, access rights and deletion procedures.
Continuous monitoring
Agree monitoring coverage, incident ownership and escalation terms.
Scoped Integration
The web integration proposal covers account views, alerts and permitted broker-hosted bot controls. Confirm supported APIs and reconcile state after reconnecting. Browser access does not imply local bot execution or full desktop task coverage.
Professional Trading From Your Browser
Explore proposed browser access to account and trading tasks. Confirm the supported build, browsers and broker permissions.
Browser-based trading
Coming SoonProposed charts, market data, orders, positions, watchlists and alerts.
Account monitoring
Coming SoonSee balance, positions and activity when the web terminal is available.
Secure sessions
Confirm session expiry, permissions and server-side order reconciliation.
Public web access is planned. Published desktop packages, preview enquiries and store availability are listed separately.
Explore Web Access
Request a scoped preview and confirm supported browsers, permitted tasks and access instructions before deployment.