RTX5 Algorithmic Trading
Signed packages calling the same constrained order API. A running algorithm does not imply a profitable strategy.
Roadmap capability. Not a live product claim until a named version is certified.
Main capabilities
Bot lifecycle
Upload, review, sign, demo, live.
No auto-convert promise
Automatic conversion of any Pine/MQ5 is not an acceptable launch promise.
How it works
- 01
Authenticate
A principal acts inside a tenant and account scope.
- 02
Validate
Pre-trade risk and instrument rules run first.
- 03
Record
A durable journal feeds positions, ledger and audit.
- 04
Operate
Managers and APIs use the same permission-enforced path.
Technical details
Server authority
The client is a user interface. Entitlement, order and risk decisions remain on the server.
No inferred venues
Listing a category does not establish venue, data or regulatory access.
Security and controls
Authorization
Tenant, object and function checks are enforced server-side.
Frequently asked questions
Is this live today?
Roadmap capability. Not a live product claim until a named version is certified.
Can I get a quote?
Yes. Use Request a Quote on the contacts page.
A proposed path from source to broker execution
Build RX5 algorithms with Rust and the proposed RTX5 SDK. RX5 identifies the intended package format; it does not rename or claim ownership of the Rust language.
- 01
Prepare authorized source
Keep the source origin, dependency licences and required permissions with the project. Migrated Pine or MQL source must fall within a documented, tested subset.
- 02
Build and validate
Compile in an isolated worker and bind the artifact to its source hash, dependency inventory and SDK/compiler versions. Compare original fixtures on desktop before deployment review.
- 03
Approve a scoped instance
The proposed broker workflow assigns the account, instruments, order permissions, resource budget and risk limits to a signed package version.
- 04
Control server execution
An eligible mobile or web client would monitor the broker instance. Server acknowledgment establishes a lifecycle change; a phone disconnect does not establish that the bot stopped.