RTX5 for Platform Owners:
Deployment and Operational Oversight
Define broker-owner and fund-owner responsibilities, the proposed deployment and the staff permissions needed to operate it. Review supported clients, integration evidence and commercial scope before agreeing a launch.
Deployment and Oversightfor Platform Owners
Broker owners oversee account products, staff permissions, providers and operations. Fund owners oversee mandates, capital-manager access and investor reporting; fund ownership does not grant broker-wide administration rights.
The sections below describe proposed operating responsibilities. Confirm supported functionality, licence scope and acceptance evidence for the selected deployment; complete infrastructure outsourcing and verified client availability are not assumed.
Define the Branded Client Scope
Agree supported branding, client builds and component rights in the deployment proposal.
Agree a Reviewed Launch Plan
Plan the sequence and acceptance dependencies before agreeing delivery dates.
Set Commercial Responsibilities
Define permitted commercial terms, broker/provider relationships and approval responsibilities.
Assign Technical Ownership
Assign maintenance, incident response, update approval and customer support responsibilities in the service scope.
Define the owner's operating model
A branded broker platform and a fund's investment operation can use different parts of a deployment. Decide which business owns the client relationship, trading policies and investor mandate before selecting tools.
Swipe horizontally to view all columns.
| Area | Broker owner | Fund owner |
|---|---|---|
| Primary responsibility | Operate the broker's client proposition, account conditions and service arrangements. | Oversee the fund's investment mandate, manager access and investor reporting. |
| Day-to-day users | Onboarding, payments, dealing/risk, support and broker administrators. | Capital managers, risk reviewers and investor-reporting staff, within the agreed operating model. |
| Configuration | Approve applicable account groups, instruments, pricing, routing and provider connections. | Approve strategy permissions, allocation policies and investment limits supported by the broker deployment. |
| Required separation | Ownership does not require every staff account to have unrestricted administrator access. | Fund ownership or trading authority does not automatically grant broker-wide configuration permissions. |
| Acceptance evidence | Demonstrate the agreed client, payment, configuration and operational workflows. | Demonstrate mandates, allocation, fees and reporting for the supported fund workflow. |
Review the Supported Branding Surfaces
Branding is a scoped deployment requirement. Confirm permitted assets, attribution, customization and release responsibilities for each supported client; complete visual control or attribution removal is not assumed.
Custom Application Name & Logo
Specify permitted application names and logo locations for each supported client build.
Brand Colour Scheme & Theme Configuration
Confirm which theme settings are supported and review a rendered brand proof.
Custom Splash Screen & Login Interface
Request supported login/splash customization and its approval and update process.
Proposed Mobile Branding Scope
Mobile branding requires a verified client, licence rights, publisher account and store submission scope.
Custom Domain & Server Address
Agree domain ownership, certificate management, endpoints and required attribution.
In-Platform Marketing Banner Placements
Define permitted placement, content approval, eligibility and display scope for any promotional element.
Branded Welcome Email & Onboarding Flow
Confirm supported onboarding communication, sender responsibility and consent requirements.
Custom Terms of Service & Legal Documentation
The owner must approve the applicable terms and disclosures; verify how the supported client presents and records acceptance.
Asset and Delivery Review: Provide source logos, colour values, usage rights and brand guidelines for review. Delivery dates and future updates require an agreed scope and acceptance record; no fixed build or production-update timeline is published.
Specify the Configuration Your Operation Needs
Configuration scope must be demonstrated on the selected client/server build. The owner defines requirements, while scoped staff roles propose and approve changes; no complete owner portal or unrestricted feature customization is established here.
Asset Class & Instrument Selection
Confirm instrument availability, data rights, broker permissions and the administrator who may change the list.
Enabled Order Types & Execution Modes
Request the supported order types and execution modes for the actual adapter and server build.
Chart Types & Indicator Library Curation
Verify which chart and indicator settings the selected client exposes and any customization limits.
Algorithm and Backtesting Scope
Separate proposed RX5 runtime, marketplace and backtesting availability; no native MQL or universal EA toggle is established.
Signal & Marketplace Access Control
Confirm supported discovery/subscription controls and approved publisher and account terms.
News Feed & Economic Calendar Configuration
Record the licensed content source, available languages and supported configuration.
Leverage & Risk Parameter Defaults
Version and approve risk defaults, test account overrides and denied changes, and retain an audit record.
Account Type & Tier Structure Definition
Define the account group, feature access and commercial policy while verifying supported limits and permissions.
Change Management: A staged change should record requester, target group, previous/new version, approver, effective time and rollback outcome. Confirm the actual broker-administration interface and permissions before using this proposed process.
Commercial Models to Review with the Owner
These are examples to scope, not a verified list of billing or marketplace capabilities. The owner and responsible providers must approve each arrangement; platform licensing and third-party fees remain governed by /buy-platform and the signed quote.
Spread Markup Model
A broker may propose a disclosed markup where its account terms and platform scope permit it; record units and approval.
Illustrative commercial structure: Illustrative arithmetic only: a source spread of 0.1 pip plus a 1.0-pip markup gives 1.1 pips before any separate charges. Actual terms and net revenue require agreement.
Commission per Lot Model
A proposed commission needs instrument units, rate, currency, calculation basis and reversal handling.
Illustrative commercial structure: Illustrative arithmetic only: a $7 round-turn rate applied to 2 eligible lots gives $14 before any agreed adjustments. This is not an RTX5 commission offer.
Subscription Licence Model
A subscription proposal requires approved licence, renewal, cancellation and billing terms plus supported billing functions.
Illustrative commercial structure: A proposed subscription must identify included functions, billing period, renewal and refund terms. Use /buy-platform for RTX5 licence prices.
Signal Marketplace Revenue Share
Marketplace revenue share requires an approved publisher contract and verified transaction workflow.
Illustrative commercial structure: Illustrative arithmetic only: 30% of a $30 subscription is $9. Marketplace availability, publisher entitlement, taxes and settlement require approved terms.
White-Label Data Service Upsell
Data resale or premium access requires licence rights, entitlement controls and approved commercial terms.
Illustrative commercial structure: Any data-service offer requires source licences, redistribution rights, entitlements, coverage and an approved price; no free feed or historical archive is established here.
Introducing Broker Commission
An IB contract must define eligible events, recipients, tiers, settlement and corrections before payout.
Illustrative commercial structure: Illustrative arithmetic only: $5 per eligible lot on 2 lots gives $10 before reversals and settlement. Actual IB terms and supported CRM calculations require agreement.
Agree the Infrastructure Responsibility Split
The signed proposal should identify which infrastructure is supplied, operated or maintained by each party. No live liquidity network, global hosting footprint, sub-microsecond engine, PCI certification or universal maintenance inclusion is established here.
Routing and Matching Component Scope
Identify the routing/matching component owner, permitted branding, supported modes and benchmark evidence.
Provider and Adapter Scope
Confirm each actual provider agreement, account eligibility, adapter version and certification status.
Hosting and Region Scope
Name the hosting provider, regions, network dependencies and measured workload in the quote.
Broker-Hosted Algorithm Scope
Review proposed RX5 broker hosting separately, including supported packages, resources and recovery behavior.
Market Data Rights and Coverage
Confirm data licences, instrument coverage, format, history and measured delivery behavior.
Security Responsibilities
Request the actual payment-provider control scope, access tests and incident responsibilities; no certification transfers by association.
Recovery Acceptance
Agree recovery objectives and demonstrate accepted-order reconciliation in the proposed environment.
Review Mobile Availability and Publishing Scope
A branded mobile application is a proposed deployment option subject to verified clients and agreed licensing and publisher responsibilities. No current store listing, included publishing service or complete mobile feature set is established here.
Proposed Branded Mobile Build
Confirm supported iOS/Android builds, permitted branding and package ownership before proposing a branded app.
App Store & Google Play Submission Support
Agree developer-account ownership, submission responsibility and required review materials; store approval is not guaranteed.
Custom App Icon, Screenshots & Store Listing
Approve the listing assets and required attribution for the supported client and licence.
Push Notification Branding & Configuration
Test notification scope, privacy and delivery separately from final trading or payment state.
Mobile Feature Set Configuration Panel
Request a task-by-task capability record rather than assuming complete desktop or web parity.
App Update Management & Version Control
Define update ownership, compatibility testing, rollout approval and incident recovery responsibilities.
Delivery Dependencies: Dates depend on build readiness, approved assets, account ownership, testing and store review. Agree the actual delivery and update plan; no fixed build duration or store approval timeline is promised.
Verify Each Proposed Broker Connection
No 500-broker directory or out-of-the-box global network is established by this owner page. A provider name or licence purchase does not certify integration; identify supported routes and commercial relationships separately.
Adapter-Specific Broker Compatibility
Request a named broker/provider route with adapter version, message scope, eligibility and acceptance evidence.
Owner-Controlled Broker Whitelist & Blacklist
Confirm supported visibility and connection controls and document the operator permitted to change them.
Default Broker Recommendation Configuration
Any displayed broker suggestion needs an approved commercial relationship and accurate eligibility information.
Introducing Broker Revenue Share Setup
An IB arrangement requires approved recipient, calculation, reversal and reconciliation terms plus supported CRM functionality.
Multi-Broker Account Support for Traders
Confirm each adapter and client task separately and test cross-account isolation before proposing multi-broker access.
New Connection Review: A new route requires technical scope, counterparties, access rights and acceptance testing. Integration timing and introduction support depend on the agreed proposal; no fixed delivery or guaranteed partnership is promised.
Define Owner Metrics and Their Source Records
The proposed owner reporting scope covers account activity, acquisition, operations and commercial review. Confirm the actual dashboard, fields, freshness and exports on a named build; complete real-time analytics is not established here.
Active Trader Count & Growth Trend
Define active-account criteria and reporting periods, then reconcile the counts with source records.
New Registration & Onboarding Funnel
Specify onboarding stages and consent-aware conversion events before comparing funnel outcomes.
Daily & Monthly Trading Volume
Document units, instrument grouping and executed-versus-requested volume definitions.
Revenue by Stream
Keep trading, platform, IB and provider charges separately identifiable with approved recognition rules.
Trader Retention & Churn Rate
Define cohort membership, observation windows and permitted customer-contact actions.
Order Flow & Execution Quality Report
Request actual order outcomes with measurement boundaries rather than unsubstantiated latency benchmarks.
Platform Feature Usage Analytics
Record supported events and access/retention controls for product-usage reporting.
IB Commission Reconciliation
Use stable trade and recipient references to reconcile commissions, cancellations and payouts.
Data Export & API: Request the versioned reporting API or actual export sample, permission scope and retention terms. No CSV/JSON/Excel parity or 36-month storage commitment is published by this guide.
Define and Test the Risk Controls
These are proposed oversight requirements for the broker owner and authorized staff. Confirm implemented controls and accepted boundary tests on the named build; software cannot promise protection from every risk event or all negative balances.
Platform-Wide Maximum Leverage Configuration
Define leverage and margin scope by account group and instrument, then test permitted and denied changes.
Trader-Level Exposure Cap Setting
Specify exposure units, currency conversion and treatment of open and pending requests.
Aggregate Net Position Monitor
Request the supported aggregate view and reconcile its positions with the underlying accounts.
Negative Balance Policy Scope
Any negative-balance protection depends on broker product terms and applicable policy; verify its scope rather than assuming a software guarantee.
Margin and Stop-Out Acceptance
Specify margin warning and stop-out calculations, order of actions, failure handling and disclosure.
Risk Event Alert & Escalation System
Agree alerts, recipients, escalation and response responsibilities with the operating team.
Platform Risk Summary
Require a dated summary with configuration version, measured inputs and traceable exceptions.
Use the Authoritative RTX5 Licence Matrix
The broker plans below follow /buy-platform. Entry includes CRM free; Standard and provisional Enterprise use the standalone CRM add-on. Infrastructure, counting rules, taxes, support and third-party charges require the signed quote; there are no separate Starter/Growth owner offers.
Entry
Up to 1,000 real accounts
- Real-account licence scope
- Bridge and FIX charged separately
- Hosting responsibilities by quote
- Market data rights by provider
- Client scope to verify
- Support scope by quote
Standard
Up to 25,000 real accounts
- Real-account licence scope
- Bridge and FIX included in licence scope
- Infrastructure capacity by quote
- Market data rights by provider
- Client builds to verify
- CRM: standalone add-on
- Support scope by quote
Enterprise (provisional)
Quote required
- Account definition requires quote
- Provider eligibility remains separate
- Deployment scope by agreement
- Market data rights by provider
- Client and branding scope to verify
- Infrastructure capacity by quote
- CRM: standalone add-on
- Support scope by quote
Billing Workflow Scope
Confirm supported usage records, invoice fields and operator access.
Invoice and Counting Rules
Agree real-account definitions, billing periods and any applicable adjustments.
Capacity and Third-Party Costs
Licence counts do not establish infrastructure capacity or provider/data charges.
Term and Renewal Agreement
Discounts, renewals and commitment periods require the signed quote.
Enterprise Scope Review
Provisional Enterprise terms and account limits require confirmation.
Plan the Deployment Around Acceptance
This proposed sequence covers commercial agreement, branding, configuration, connectivity, operator documentation and rollout readiness. Dates depend on supported builds and external approvals; the page does not promise a fixed launch period.
Contract & Licence Agreement
Timing by agreementContract & Licence Agreement
Timing by agreementAgree licence and deployment scope, responsible parties and acceptance criteria before starting configuration.
You Provide
- Signed licence agreement
- Company documentation
- Payment setup
Expected Review Outputs
- Agreed licence scope
- Client access to confirm
- Named delivery owner
Brand Asset Collection & Configuration
Timing by agreementBrand Asset Collection & Configuration
Timing by agreementSubmit approved assets and agree the supported branding surfaces for each verified client.
You Provide
- Logo files (SVG + PNG)
- Brand colour palette
- Brand guidelines document
Expected Review Outputs
- Expected brand proof
- Supported customization scope
- Brand acceptance record
Platform Configuration & Feature Setup
Timing by agreementPlatform Configuration & Feature Setup
Timing by agreementSpecify required instruments, orders, roles, account groups and client tasks; confirm supported settings.
You Provide
- Feature requirements
- Instrument list
- Account tier definitions
Expected Review Outputs
- Expected configuration record
- Agreed test environment
- Acceptance results required
Broker Integration & Liquidity Testing
Timing by agreementBroker Integration & Liquidity Testing
Timing by agreementConfirm the provider agreement and adapter contract, then test supported messages, order outcomes and recovery.
You Provide
- Proposed provider routes
- IB agreements
- Execution quality requirements
Expected Review Outputs
- Adapter scope record
- Expected execution records
- Acceptance review required
Compliance & Legal Documentation
Timing by agreementCompliance & Legal Documentation
Timing by agreementThe operator approves applicable terms, privacy and risk disclosures; confirm supported presentation and consent records.
You Provide
- Terms of service
- Privacy policy
- Risk disclosure documents
Expected Review Outputs
- Supported document workflow
- Operator policy review
- Responsible reviewer
Soft Launch & Trader Onboarding Preparation
Timing by agreementSoft Launch & Trader Onboarding Preparation
Timing by agreementAfter acceptance, the responsible operator may plan a limited rollout with monitoring, incident and rollback responsibilities.
You Provide
- Approved test cohort
- Marketing launch plan
- Support team readiness
Expected Review Outputs
- Launch approval required
- Monitoring scope
- Agreed support coverage
Delivery Ownership: Name the owner of each task and acceptance record, including post-launch support and change approvals. Dedicated success-management or consulting services must be specified in the signed scope.
Agree deployment responsibilities before launch
Use a written deployment scope to assign each operational duty. The table below is a planning framework; the signed order form and service agreement define the actual allocation of responsibilities.
Swipe horizontally to view all columns.
| Workstream | Owner decision | RTX5 / provider scope to agree |
|---|---|---|
| Hosting and capacity | Expected account count, concurrent sessions, instruments, regions and recovery needs. | Who provisions and operates infrastructure; capacity assumptions, limits, scaling charges and monitoring access. |
| Clients and branding | Required desktop, browser and mobile workflows; brand assets and acceptance criteria. | Named supported builds, packaging, release channels, store-listing responsibilities and supported customization. |
| Connectivity and data | Required counterparties, credentials, commercial eligibility and market-data entitlements. | Adapter version, tested message scope, connection count and responsibility for provider certification and fees. |
| Operations and security | Staff roles, approvals, incident contacts and change windows. | Monitoring, backup/restore, patching, audit retention, escalation and incident notification responsibilities. |
| Launch acceptance | Approve results against the agreed client and operating workflows. | Staging evidence, unresolved issues, production readiness and rollback procedure. |
Prepare Accurate Owner Communications
Marketing resources and acquisition workflows require an agreed scope. Avoid claims of active programmes, verified scale, partnerships or released features without supporting records.
Marketing Asset Scope
Agree which editable assets may be provided and verify their usage rights and supported product claims.
Branded Platform Screenshot & Demo Video Kit
Use screenshots from the named build and accurately label demonstrations or proposed functionality.
Co-Promotion Review
Any co-promotion requires separate approval; no active programme or audience reach is promised.
Referral Workflow Scope
Referral workflows require eligibility, consent, approved commission terms and verified tracking/reversal behavior.
Email Onboarding Sequence Templates
Approve sender, consent, recipient scope and claims before using onboarding communication.
Education Event Scope
Event participation, materials and speakers require a separately agreed scope and schedule.
Directory Publication: A listing needs approved eligibility, accurate commercial disclosures and verified publication functionality. This page does not establish a recommended-platform directory or a 90-day qualification programme.
Assign Operational and Regulatory Responsibilities
This page identifies documentation to prepare and review. It does not supply an approved compliance package, jurisdiction-specific templates or a certification of the owner operation.
Client Agreements and Terms
The operator must prepare and approve account terms, charges, order handling and dispute responsibilities appropriate to its service.
Privacy and Data Responsibilities
Identify actual data collection, processors, retention, access and user-request handling rather than assuming a generic framework fits.
Risk Disclosures
Prepare disclosures for the actual trading, counterparty, leverage and technology risks of the offered product.
Onboarding and Review Procedures
Assign onboarding and transaction-review responsibilities to the broker and relevant providers.
Execution Policy
Document the actual routing model, selection rules, intervention permissions and evidence reviewed.
Jurisdiction and Service Scope
The responsible operator must assess its service and jurisdiction with qualified advisers; a platform licence does not grant authorization.
Operator Responsibility: The broker or fund owner remains responsible for its actual service, permissions and disclosures. Confirm professional review and supported platform controls before launch.
Assign Support and Escalation Responsibilities
The table illustrates support requirements to discuss, not services included with a platform licence. Checkmarks indicate a requested item in a fictional scope; channels, named contacts, review cadence and response terms require agreement.
| Feature | Scope A (example) | Scope B (example) | Scope C (example) |
|---|---|---|---|
| Support Channels | Channels by agreement | Channels by agreement | Channels by agreement |
| Named Contact Requested | |||
| Response Terms | By agreement | By agreement | By agreement |
| Technical Support Depth | Scope to confirm | Scope to confirm | Scope to confirm |
| Periodic Review Requested |
Operational Review Scope
Agree review cadence, metrics, responsibilities and any consulting deliverables.
Release Review Process
Use named release records and confirm how changes are assessed for your deployment.
Owner Advisory Scope
Any growth or retention consultation requires an agreed data and service scope.
Connection Enquiry Review
Provider introductions and integration assistance are subject to separate agreement.
Incident Escalation
Define contacts, coverage, severity, targets and remedies in the signed support terms.
Illustrative Owner Deployment Scenarios
These scenarios describe possible broker, fund and platform-owner requirements. They are fictional planning examples, not customer case studies, active deployments or measured business outcomes.
Scenario 1: Broker Client Deployment
Proposed Mobile and Onboarding Scope
Business Model
Illustrative broker configuration
Market
Country and provider eligibility to confirm
Acceptance Focus
Tested client and onboarding evidence
A broker owner wants a branded client and localized onboarding. The review must identify a supported build, publisher and provider responsibilities, account eligibility and accepted onboarding outcomes. No customer, delivery timeline, adoption result or revenue is represented by this fictional scenario.
Scenario 2: Professional Broker Deployment
Proposed Execution and Reporting Scope
Business Model
Illustrative broker cost structure
Market
Jurisdiction and counterparty scope to confirm
Acceptance Focus
Named route and execution evidence
A broker owner evaluates routing, account costs and operational reporting. The proposal needs supported component versions, provider terms, measured order outcomes and a reporting sample. This fictional scenario does not establish Ultency ownership, live liquidity access, customer adoption or revenue.
Scenario 3: Fund-Owner Oversight
Proposed Investor Mandates and Reporting
Business Model
Illustrative fund operating model
Market
Investor and service eligibility to confirm
Acceptance Focus
Permission and allocation acceptance
A fund owner defines the capital-manager mandate, investor reporting and approval responsibilities. Acceptance should reconcile a partial fill and fee example while denying broker-wide configuration access to the fund role. This fictional scenario contains no fund performance or customer result.
Scenario 4: Regional Broker Operations
Proposed Payment and IB Workflow
Business Model
Illustrative broker operational model
Market
Country, currency and method eligibility to confirm
Acceptance Focus
Provider and ledger evidence
A broker owner scopes an eligible regional payment route and IB arrangement. The test should follow approved requests, separate cash and commission entries, reverse a corrected event and reconcile the provider outcome. No live integration, country coverage, deployment count or financial result is claimed.
Questions About Owner Deployment Scope
Review responsibilities, supported capabilities and commercial terms before committing.
Compare Building and Licensing by Scope
Compare the actual functions, ownership, staffing, dependencies, acceptance effort and ongoing service terms of each option. The table is a planning framework, not a cost or delivery benchmark.
| Criteria | Build From Scratch | RTX5 Licence Proposal |
|---|---|---|
| Delivery Plan | Estimate scope and dependencies | Agree supported scope and acceptance |
| Technology Investment | Cost development and ongoing operations | Use /buy-platform plus scoped external costs |
| Execution Components | Build or license; verify component rights | Confirm component origin and supported modes |
| Provider Access | Arrange eligible counterparties and adapters | Provider agreement and certification required |
| Infrastructure Maintenance | Assign staffing and service responsibilities | Agree maintenance and support responsibility |
| Operator Documentation | Prepare for the actual service and jurisdiction | Operator review and supported controls required |
| Broker Connectivity | Verify each adapter and account scope | Verify each adapter and account scope |
| Mobile Client Scope | Plan supported clients and store responsibilities | Confirm builds, rights and publisher scope |
| Changes and Releases | Own testing, approval and rollout | Agree testing, approval and rollout |
| Operational Risk | Assign capacity, security and recovery owners | Agree capacity, security and recovery owners |
Choose against a reviewed requirements list and the verified scope of each proposal. Licensing may reduce some development work, but integration, operations, acceptance and external agreements still need owners; no percentage saving or delivery advantage is established here.
Owner Proposals Requiring Review
These ideas are unverified proposals, not dated delivery commitments or evidence of active development/testing. The central roadmap is the place to review accountable owners, status evidence and later approved changes.
Proposed Owner Retention Analytics
Proposal; evidence pendingPossible reporting scope for approved activity and cohort data. Model availability, effectiveness, permissions and privacy controls require review.
Proposed Configuration Experiment Review
Proposal; evidence pendingPossible comparison of approved onboarding or feature configurations. Supported controls, segmentation and acceptance evidence remain to be confirmed.
Proposed Jurisdiction Policy Workflow
Proposal; evidence pendingPossible operator review of account eligibility and applicable policy. No automated regulatory compliance or legal determination is established.
Proposed Owner Discovery Workflow
Proposal; evidence pendingPossible curated discovery and subscription workflow subject to publisher terms, permissions and supported marketplace functionality.
Proposed Owner Community Tools
Proposal; evidence pendingPossible community and educational workflow with explicit moderation, consent and data-access scope. No released forum service is established.
Build Your Trading Business on RTX5
Define a proposed branded trading deployment, including account capacity, client availability and written commercial scope.
White label
Branding, identity, configuration and user experience.
Business configuration
Products, accounts, trading settings, roles and services where supported.
Broker connectivity
Connect to supported broker and market infrastructure.
- 01
Discover
- 02
Configure
- 03
Integrate
- 04
Test
- 05
Launch
- 06
Operate
Review the RTX5 Deployment Your Operation Needs
Identify broker-owner or fund-owner responsibilities, client tasks, providers, permissions and acceptance criteria. Confirm licensing at /buy-platform and agree the remaining delivery and service scope in a proposal.