RTX5 Algorithm Hosting: Broker Plans and Limits
Explore planned broker-hosted RX5 execution, client controls and resource limits. Availability, service terms and any separate VPS offer require confirmation.
Broker Hosting, Independent of the Phone
The proposed RX5 runtime would run an approved bot on broker infrastructure while a phone provides monitoring and controls. Persistence, recovery and supported actions await build-level testing. A general-purpose VPS is a separate service whose availability must be confirmed.
Broker-Hosted RX5 Execution — Planned
The proposed broker runtime runs an approved RX5 bot on server infrastructure. An eligible client would provide a view and controls for that instance.
Swipe horizontally to view all columns.
| Activity | Execution location | Boundary to confirm |
|---|---|---|
| Strategy development and historical tests | Desktop development environment. | SDK/desktop build, licensed historical data and backtesting resources. |
| Approved RX5 bot | Broker-hosted runtime. | Approved artifact, account/trading permissions, runtime resources and broker availability. |
| Mobile monitoring and control | Phone communicates with the hosted instance. | Supported client, secure access and confirmed start/stop/monitor actions. |
| Phone disconnected | The proposed bot continues on the broker server independently of the phone. | Actual persistence, failure recovery and runtime behavior require build-level testing. |
- 01
Approve the instance
Agree the tested artifact, account, instruments, settings and permission scope with the broker before enabling order execution.
- 02
Observe the server state
Monitor running/stopped/error state, active version, resource use and recent actions. Treat a disconnected phone as an unavailable view, not evidence that the bot stopped.
- 03
Confirm control requests
A start or stop action needs an acknowledgment from the runtime. On reconnect, retrieve current state before repeating a control request.
- 04
Handle orders explicitly
Agree whether stopping affects new strategy actions, pending orders or open positions. Cancellation and liquidation are separate decisions unless an approved policy says otherwise.
Why Evaluate Broker Hosting
These are planning considerations for an approved RX5 instance; they do not establish an available VPS product or an uptime guarantee.
Defined Availability
Agree service hours, maintenance, recovery and measured availability in the broker plan; uninterrupted operation is not guaranteed.
Measured Connectivity
Latency depends on runtime location, routing, broker checks and load. Request the named test environment and measurements.
Phone-Independent Runtime
The proposed server instance does not rely on an open phone session. Confirm disconnect and reconnect outcomes with the supported client.
Explicit Runtime Boundaries
Verify account isolation, access controls and permission-denial behavior for the approved runtime build.
Controlled Order Actions
Broker and market conditions affect acceptance, fills and slippage. Hosting cannot guarantee execution timing or price.
Proposed Hosting Capabilities
Available behavior and service limits must be published for each broker offer before activation.
High-Speed Performance
CPU, memory and concurrency allowances must be specified by the broker and verified against the runtime build.
Low Latency Connectivity
Document the execution route, server region and measured latency; proximity alone does not establish faster fills.
Secure Infrastructure
Require verified permissions, tenant isolation, encrypted transport and audit records for the deployment.
Easy Setup
Approval needs the tested artifact, account scope, configuration and supported deployment procedure.
Remote Access
Monitoring and control depend on eligible clients, authentication and a published client/runtime compatibility matrix.
Runtime Monitoring
Confirm heartbeat, errors, resource use and stop acknowledgments; monitoring does not guarantee uptime.
Scope the Intended Workload
Confirm whether the proposed RX5 runtime supports the intended workflow. The example panel illustrates information to record; it shows no live instance, measured latency or trading result.
- Approved RX5 bot instances
- Separately approved copy workflows
- Permission-scoped signal workflows
- Workload and latency assessment
- Explicit account scope
Review Hosting Terms
Proposed US$10–20/month, or an eligible broker reward. Exact resources, taxes and terms require a broker quote; no separate VPS offer is confirmed here.
Broker Runtime
Proposed RX5 instance
Broker Reward
Eligibility-dependent waiver
Separate VPS
Availability to confirm
Broker Runtime Fees, Quotas and Rewards
These proposed broker-runtime charges apply to an eligible hosted RX5 instance. The broker's offer must identify its resource allowance and how it relates to any separately offered VPS service.
Swipe horizontally to view all columns.
| Item | Planning content | Quote must specify |
|---|---|---|
| Monthly user charge | Proposed US$10–20/month, set by the broker. | Currency, taxes, billing unit, included instances/resources and actual broker price. |
| Eligible fee waiver | A broker may offer an eligible reward or waive the charge. | Eligibility, duration, renewal, expiry and what happens when eligibility ends. |
| Compute and memory | Resources belong to the broker-hosted instance. | CPU allowance, memory cap, concurrency and behavior at a limit. Numeric quotas: to be confirmed. |
| Storage and retention | Logs and instance data need defined limits. | Included storage, retention, export access and handling at renewal or cancellation. |
| Renewal and suspension | Ongoing use depends on the broker plan. | Billing period, renewal consent, notice, suspension/restart policy and treatment of orders/positions. |
| Separate services | Desktop historical testing, data rights and a general-purpose VPS have their own scope. | Which services are included, separately priced or unavailable in the selected offer. |
Review the hosting offer before activation
An eligible broker-hosted RX5 instance would need explicit trader acceptance of its charge, permissions and operating rules. This is a proposed service workflow.
Swipe horizontally to view all columns.
| Item | What must be shown and agreed |
|---|---|
| Price and billing | Proposed US$10–20/month is a planning range set by the broker. Record its actual price, currency, taxes, billing period, included resources and any cap before acceptance. |
| Renewal and cancellation | Show renewal consent, cancellation path, refund policy, notice and treatment of stored data. Approved service terms and effective dates remain to be supplied. |
| Reward eligibility | Review the broker, territory, product and client class before offering a fee waiver. Record eligibility, duration and expiry; do not assume every trader qualifies. |
| Failure and suspension | Define outage, data-gap, quota, licence-expiry and billing-failure behavior. Explain recovery authority and support escalation without promising unmeasured uptime. |
| Orders and positions | State separately whether an action stops new strategy orders, cancels working orders or closes positions. Retain the server confirmation and reconcile before restarting. |
| Service evidence | Publish tested resource quotas, capacity, isolation and restore results before making numerical performance or availability commitments. |
Operational Evidence Required
Approved service agreement needed
Resources must be specified
Named runtime and client build
Restart and reconciliation evidence
Local PC vs Proposed Hosting
Compare execution location and operational responsibility. Hosting does not guarantee better returns, lower latency or continuous availability.
Approval Before Activation
This proposed workflow depends on a released runtime and broker approval; it does not offer instant provisioning or unlimited resources.
Agree the broker plan
Confirm runtime availability, fees, permissions and numeric resource limits before approval.
Complete setup
Submit the reviewed RX5 artifact and configuration. Provisioning time and automation are not yet published.
Connect an eligible client
Use the approved client and access method; a general-purpose remote desktop session is not assumed.
Verify the active artifact
Confirm the runtime build, approved version, account scope and current instance state.
Approve and monitor
Enable only approved actions and verify acknowledgments, failure handling and stop controls.
Dedicated Support
Support channels, service hours, response targets and escalation ownership must be stated in the broker agreement. No round-the-clock support or proactive resolution guarantee is established here.
Plan Broker-Hosted Algorithm Operations
The proposed broker-hosted RX5 runtime would run approved strategies away from a personal computer. Agree resources, permissions, operating hours and recovery procedures.
Operating hours
Agree operating hours and maintenance windows.
Remote access
Confirm permitted remote start, stop and monitoring actions.
Automated strategies
Confirm accepted package versions and runtime limits.
Monitoring
Watch system activity and availability.
Resource management
An environment designed for trading workloads.
This page does not advertise guaranteed uptime, guaranteed execution latency or guaranteed availability.
Review Your
Hosting Requirements
Request a scoped broker-runtime discussion, including build availability, resource limits, operational tests and service terms.