Hosted Trading Platform Access: Permissions and Deployment Scope
FxTrusts hosted trading platform access is built for broker and trading businesses that need defined access to a hosted trading environment without assuming ownership of every underlying infrastructure component. Final permissions, licence rights, hosting responsibilities and deployment scope are contract-dependent and confirmed before go-live.
What Is Hosted Trading Platform Access?
Hosted trading platform access gives a broker or trading business controlled access to a trading environment operated under a defined hosting and licensing arrangement. Rather than owning every underlying server or platform component, the client receives the terminals, permissions and APIs set out in the agreed deployment scope. Licence rights, server ownership and manager-level access remain scope-dependent and are documented in the implementation agreement before production use begins.
What the $3,500 Monthly Hosted Platform Access Offer Covers
This is a proposed hosted platform access package, not FxTrusts’ universal platform pricing — other FxTrusts services, including broader turnkey subscription tiers, are structured and priced differently. Treat the figure below as the specified offer for this deployment model and confirm final scope in writing before signing.
Included - Verified
- Hosted access to a trading environment under the agreed scope
- A defined deployment and approval process as outlined on this page
Additional verified inclusions are confirmed in the commercial scope.
Scope-Dependent
- Platform version and server specification
- Manager permissions and API access
- Number of environments and integrations
- Branding options and additional server locations
- Dedicated support tier
Separate / Third-Party
- Commercial scope to be confirmed
Any third-party licensing, liquidity or payment costs are documented separately where applicable.
Always verify exact manager permissions, API throughput limits, sandbox validation periods, maintenance response SLAs, and exit/migration terms in the formal implementation agreement prior to execution.
Manager Permissions, API Access and Operational Limits
The interactive matrix below details the 25 operational functions involved in a hosted deployment. Values marked "Not publicly verified" have not been confirmed for this specific package and should be requested directly. No function is presented as unrestricted access unless explicitly confirmed in writing.
| Function | Client Access | Manager Access | API Access | Approval Required | Technical Notes |
|---|---|---|---|---|---|
| View trading accounts | Scope-dependent | Allowed | Scope-dependent | No | Standard operational function |
| Create trading accounts | Restricted | Scope-dependent | Scope-dependent | Yes | Typically manager or admin function |
| Modify account settings | Restricted | Scope-dependent | Scope-dependent | Yes | Confirm exact fields in scope |
| View balances | Scope-dependent | Allowed | Scope-dependent | No | Standard operational balance oversight |
| View positions | Scope-dependent | Allowed | Scope-dependent | No | Real-time open position tracking |
| View orders | Scope-dependent | Allowed | Scope-dependent | No | Historical and working order access |
| Manage symbols | Restricted | Scope-dependent | Scope-dependent | Yes | Platform-level instrument configuration |
| Configure leverage | Restricted | Scope-dependent | Scope-dependent | Yes | Risk-relevant, closely scoped parameter |
| Configure commissions | Restricted | Scope-dependent | Scope-dependent | Yes | Commercial spread & commission markup |
| View trade history | Scope-dependent | Allowed | Scope-dependent | No | Historical executed trades log |
| Export reports | Scope-dependent | Scope-dependent | Scope-dependent | No | Format and frequency confirmed with FxTrusts |
| CRM synchronization | Not publicly verified | Not publicly verified | Not publicly verified | Yes | Depends on CRM integration in scope |
| Account synchronization | Not publicly verified | Not publicly verified | Not publicly verified | Yes | Automatic user ledger synchronization |
| Payment synchronization | Not publicly verified | Not publicly verified | Not publicly verified | Yes | Third-party payment gateway dependency |
| KYC synchronization | Not publicly verified | Not publicly verified | Not publicly verified | Yes | Compliance provider dependency |
| Liquidity connectivity | Not applicable | Scope-dependent | Scope-dependent | Yes | Depends on institutional liquidity setup |
| Trade execution controls | Restricted | Scope-dependent | Scope-dependent | Yes | Risk-sensitive routing control |
| Risk controls | Restricted | Scope-dependent | Scope-dependent | Yes | A-Book / B-Book and drawdown parameters |
| User administration | Restricted | Scope-dependent | Not applicable | Yes | Confirm administrative permission tier |
| Server administration | Not applicable | Not applicable | Not applicable | Yes | Dedicated root access not client-held |
| Database access | Not applicable | Not publicly verified | Not publicly verified | Yes | Raw SQL database replication scoping |
| Log access | Restricted | Scope-dependent | Not publicly verified | Yes | Audit and trading journal inspection |
| API credentials | Scope-dependent | Scope-dependent | Scope-dependent | Yes | Issued under approved deployment agreement |
| Webhooks | Not publicly verified | Not publicly verified | Not publicly verified | Yes | Real-time event notification stream |
| Reporting API | Scope-dependent | Scope-dependent | Scope-dependent | No | Confirm endpoints, schema and rate limits |
Deployment Scope: Server, Platform, CRM and Connectivity
A hosted trading server involves multiple operational layers: provisioning, network connectivity, platform installation, environment separation, security controls, monitoring, backups, credential management, maintenance, upgrades, incident handling and migration. Hosting regions are deployment-dependent — current FxTrusts infrastructure leverages ultra-low latency locations such as Equinix LD4, NY4, TY3 and SG1 for its institutional ecosystem.
| Deployment Area | Operational Coverage | Status |
|---|---|---|
| Server provisioning | Allocating hosting resources and computing capacity | Scope-dependent |
| Hosting region | Physical or logical location of the financial server | Scope-dependent |
| Network connectivity | Ultra-low-latency links between platform, CRM & liquidity | Scope-dependent |
| Environment separation | Strict isolation between sandbox testing and live production | Standard practice |
| Security controls | Access restriction, role-based controls & IP whitelisting | Confirm with FxTrusts |
| Monitoring & backups | 24/7 server health oversight, replication & snapshot routines | Not publicly verified |
| Maintenance & upgrades | Scheduled patches, security updates & build upgrades | Confirm with FxTrusts |
| Incident handling | Formal response protocols for server anomalies or failover | Confirm with FxTrusts |
Platform Version, API and Build Verification
Before committing to a hosted deployment, technical teams should confirm the platform name, version, build number, API connectors, environment isolation, authentication protocols, and testing dates.
| Field | Value | Verification Status |
|---|---|---|
| Platform | Confirmed per deployment | Confirm with FxTrusts |
| Version | — | Not publicly verified |
| Build | — | Not publicly verified |
| API | — | Not publicly verified |
| Connector | — | Not publicly verified |
| Environment | Sandbox / Production | Standard practice |
| Authentication | — | Not publicly verified |
| Permissions | Per permissions matrix | Scope-dependent |
| Last Tested | — | Not publicly verified |
| Evidence | — | Not publicly verified |
See the API documentation for connector references where published.
Sandbox, Testing and Production Readiness
Production access follows a staged, 10-step deployment methodology. Each stage specifies an accountable owner, client input, and technical dependency to ensure operational safety and compliance.
Initial Scoping
- Owner
- Client + FxTrusts
- Client Input
- Defines requirements & jurisdictions
- Dependency
- Commercial fit assessment
- Approval
- Yes
Commercial Agreement
- Owner
- Both parties
- Client Input
- Executes service schedule & scope
- Dependency
- Legal & compliance sign-off
- Approval
- Yes
KYC & Entity Review
- Owner
- FxTrusts Compliance
- Client Input
- Submits corporate docs & UBO details
- Dependency
- Sanctions & regulatory checks
- Approval
- Yes
Platform Provisioning
- Owner
- FxTrusts Engineering
- Client Input
- Specifies desired environment & symbols
- Dependency
- Server infrastructure allocation
- Approval
- Internal
Sandbox Access & Credentials
- Owner
- FxTrusts
- Client Input
- Tests login credentials & manager limits
- Dependency
- Environment isolation active
- Approval
- No
Connector & Integration Testing
- Owner
- Client + Technical Team
- Client Input
- Provides CRM, liquidity & payment endpoints
- Dependency
- API readiness & IP whitelisting
- Approval
- No
User Acceptance Testing (UAT)
- Owner
- Client
- Client Input
- Executes simulated order routing & reporting
- Dependency
- Working sandbox environment
- Approval
- No
Production Go-Live Sign-Off
- Owner
- Client + FxTrusts
- Client Input
- Signs formal go-live release document
- Dependency
- Satisfactory UAT & risk controls
- Approval
- Yes
Production Deployment
- Owner
- FxTrusts Operations
- Client Input
- Validates production endpoints
- Dependency
- Production server green status
- Approval
- Yes
Handover & Ongoing Monitoring
- Owner
- FxTrusts Support
- Client Input
- Designates emergency support contacts
- Dependency
- 24/7 technical monitoring active
- Approval
- No
Approval Dependencies Before Production Access
Production provisioning requires sign-off across commercial, legal, and technical items. Not every deployment requires every checkpoint — the exact scope is finalized during onboarding.
Hosted Access vs Grey Label vs White Label vs Independent Platform
Terminology varies across the forex technology sector. The comparison below helps evaluate control, dependency, and administrative scope across common deployment models.
| Deployment Model | Brand Control | Infrastructure Control | Manager Access | API Scope | Dependency | Typical Use Case |
|---|---|---|---|---|---|---|
| Hosted Platform Access | Scope-dependent | Low — provider managed | Scope-dependent | Scope-dependent | High — provider infrastructure | Businesses needing defined operational access without managing infrastructure |
| Grey Label | Limited | Low | Restricted, scope-dependent | Restricted, scope-dependent | High | Lighter-weight entry with minimal branding and infrastructure rights |
| White Label | Higher, contract-dependent | Scope-dependent | Scope-dependent | Scope-dependent | Medium, contract-dependent | Brokers desiring strong brand presence with dedicated partner support |
| Independent Platform | Full, client-held | Full, client-held | Full, client-held | Full, client-held | Low | Established institutions holding direct platform vendor licences |
Compare related solutions: Forex White Label, Technical Infrastructure, or MetaTrader 5 Platform.
Deployment Scope: Server, Platform, CRM and Connectivity
The diagram below illustrates the conceptual deployment dataflow between your brokerage operations, the hosted environment, the trading core, and institutional integrations.
Conceptual deployment architecture. Actual production connectors depend on the approved commercial scope.
Who This Deployment Model Is Best For
Hosted platform access provides a focused solution for specific operational models. Review the scenarios below to evaluate your alignment.
Requiring Hosted Platform Infrastructure
Best fit for an emerging broker that needs a turnkey, operational trading environment without building complex server infrastructure from scratch.
Potential limitation: Requires planning for scope-dependent permissions rather than root-level server access.
- Which manager permissions are included?
- What is the onboarding timeline?
Needing a Defined Hosted Deployment
Suited to an established broker restructuring or consolidating its hosting stack under a predictable, SLA-governed technical agreement.
Potential limitation: Account and history migration depends on source database format.
- What data migration assistance is available?
- How are existing liquidity feeds connected?
Requiring Controlled Trading Infrastructure
Ideal for proprietary trading challenges and evaluation accounts requiring strict risk parameters and automated account creation.
Potential limitation: Real-time risk rules and drawdown controls must be explicitly scoped.
- Which risk controls exist at manager level?
- Is API access suitable for challenge engines?
Evaluating Grey-Label vs White-Label
Designed for engineering leaders comparing operational trade-offs, API access, and infrastructure overhead before making long-term commitments.
Potential limitation: Industry terminology varies; written contract specifications take precedence.
- What exact rights distinguish hosted vs WL?
- What exit rights exist if needs expand?
How Hosted Platform Access Ends or Changes
Notice periods, termination terms, data retention windows and migration support are contract-specific. The 10-step sequence below outlines the structured offboarding procedure.
| Step | Operational Action |
|---|---|
| 01 | Client formally requests operational change or termination in writing |
| 02 | Commercial scope and notice period are reviewed against agreement |
| 03 | Access dependencies (CRM, payments, liquidity feeds) are identified |
| 04 | Data export and trading history retention requirements are scheduled |
| 05 | API credentials and external webhooks are safely revoked |
| 06 | Third-party licences and bridges are decommissioned per vendor terms |
| 07 | Trading access and client terminals are smoothly transitioned |
| 08 | CRM and wallet connections are disconnected |
| 09 | Final environment access is disabled |
| 10 | Final confirmation and completion handover delivered |
Notice periods, termination fees, data retention and migration assistance: contract-specific.
Hosted Platform Access Readiness Checklist
Track what should be confirmed before signing and before production deployment. Your progress is saved automatically in your browser session.
Frequently Asked Questions
What is hosted trading platform access?+
Hosted trading platform access is a service model in which a broker or trading business receives defined permissions to operate on a trading environment that FxTrusts deploys and manages, rather than owning the underlying server, licence or source code outright. The exact scope of terminals, APIs and administrative rights is set out in the implementation agreement.
How much does hosted trading platform access cost?+
The proposed hosted platform access offer is $3,500 per month. This figure reflects a specific hosted-access package and should not be treated as FxTrusts’ universal platform pricing, since other FxTrusts services are structured differently. Final pricing and inclusions are confirmed during a commercial assessment.
What does the $3,500 monthly access fee include?+
The monthly fee covers hosted access to a trading environment under the scope agreed with FxTrusts. Specific components such as platform version, server specification, manager permissions, API access, number of environments and support tier are scope-dependent and confirmed in writing before contracting.
Who owns the trading platform licence?+
Licence ownership depends on the contracted deployment model and is not transferred to the client by default under a hosted access arrangement. The implementation agreement documents which party holds the platform licence for a given deployment.
Who hosts the trading server?+
Under a hosted access model, the server is typically provisioned and maintained by FxTrusts or a named technology partner rather than the client. The specific hosting entity, region (e.g. Equinix LD4/NY4) and maintenance responsibilities are confirmed in the implementation scope.
What manager permissions are available?+
Manager permissions are scope-dependent and vary by deployment. Functions such as viewing accounts, configuring symbols, adjusting leverage or accessing reporting may be allowed, restricted or unavailable depending on the agreed permission set, documented in the permissions matrix before go-live.
Do I get API access?+
API access, where available, is scoped to specific functions such as reporting or account synchronization rather than granted as unrestricted access. The exact endpoints, authentication method and rate limits depend on the platform, connector and approved deployment.
Can hosted access be used for a forex brokerage?+
Hosted access is one of several deployment models a forex-facing business can use, alongside grey label, white label and independent licensed deployment. Suitability depends on jurisdiction, business model, licensing status and the permissions required, which are reviewed case by case.
What is the difference between hosted access and a grey label?+
Hosted access generally refers to scoped operational access to a hosted trading environment, while grey label typically describes a lighter branding and operational arrangement where the client depends on the underlying provider for infrastructure functions. Exact rights differ by provider and by contract.
What is the difference between grey label and white label?+
White label arrangements generally give a client more branding control and, in some cases, a dedicated technical environment, while grey label arrangements are typically lighter-weight with fewer branding and infrastructure rights. Neither term has a single universal legal definition, so specifics must be confirmed per contract.
Can the hosted environment be tested before production?+
Yes, a sandbox or test environment is typically used to validate credentials, connectors and workflows before production deployment. The scope and duration of testing access is defined during the approval process and confirmed as part of the implementation plan.
What happens if we want to leave or migrate?+
Exit and migration terms, including notice periods, data export and any applicable fees, are contract-specific and documented in the implementation agreement. FxTrusts does not publish a universal notice period or termination fee, as these depend on the agreed terms.
Request a Scoped FxTrusts Implementation Assessment
Get the platform, hosting, permissions, integration and deployment scope reviewed before you commit to a hosted access model.