Fortex provider profile: trading platforms, liquidity connectivity and managed infrastructure

Fortex supplies the technology connecting broker trading applications, liquidity routes and operational systems. Its range serves brokers, banks, liquidity providers, fund managers and professional trading firms. The intended role depends on which components a customer buys.[1]

XForce is the name used in the older architecture materials and still appears in the API description. The accessible 2023 brochure presents an integrated cloud architecture with account administration, pricing, matching, reporting and layered staff roles. It explicitly describes a platform that is not bundled with one liquidity provider. That is useful architectural context, but the historical brochure does not establish today’s module entitlements.[9]

The API can connect custom systems to XForce risk functions, multi-provider access and configured liquidity. This allows a firm to use Fortex infrastructure behind an independently developed interface. Protocol availability alone does not specify a production session’s message limits, permitted actions, recovery sequence or data entitlements; those were not established by the public overview.[4]

Fortex’s May 2026 MT4 release is particularly relevant to platform transitions. A broker can introduce the Fortex 7 interface while retaining MT4 accounts and infrastructure. That separates a change in customer experience from a change in the system holding the account. The release does not establish that an MT4 Expert Advisor or plugin runs natively inside Fortex 7.[11]

Fortex routes commercial enquiries to its sales team and does not publish a complete numerical tariff in the reviewed product material. The MT4/5 WebTrader page describes a SaaS subscription charged on processed volume, without a cash rate or a definition of billable volume. Its statements about avoiding separate licensing, upgrade, maintenance and support fees apply to that described application model.[5]

A meaningful Fortex quotation has to identify the purchased layer. A hosted server, a client application, a bridge and an external liquidity account incur different obligations even when they appear in one workflow. The reviewed public information does not establish a standard minimum commitment, renewal notice, cancellation fee, migration-out charge or universal free trial for all these components.

XCLOUD describes initial MT4/MT5 deployment, migration from existing servers, plugin and data-feed administration, backup and disaster-recovery setup, Windows maintenance, and running-status or stale-quote monitoring. Its maintenance list also includes data backup, archiving and download, which is more specific than a general statement that records are available.[6]

The Web Trader history panel includes deposits, withdrawals and open or closed ticket history searchable by time and symbol. This supports routine investigation of account activity. It does not document a complete bulk export, record-retention period or handover after the contract ends; those remain gaps in the public exit specification.[21]

Support hours require product-level precision. The API webpage advertises 24/6 assistance in English and Chinese. The 2024 hosting brochure advertises proactive 24/7 support. These descriptions do not resolve which window applies to a particular subscription; neither supplies a verified contractual severity matrix or guaranteed restoration time.[4][7]

The support page provides current download routes alongside older platform manuals and release history. Its January 2026 Fortex 7 notes mention two-factor-authentication improvements, while separate news pages describe later releases. A release list should therefore be read with the installed product and build, rather than assuming every listed enhancement is present in every hosted environment.[10]

Fortex Inc. states that it is a technology supplier, neither a broker-dealer nor an investment company. Its trading, matching, bridging and liquidity-distribution functions must therefore be distinguished from the regulated business using them. A broker or LP may execute or finance transactions through the software without Fortex becoming that customer’s financial counterparty.[2]

The terms also identify dependencies such as data feeds, communications links, hardware and counterparties. An operational incident can originate at any of those layers. This limits how far a generic platform-speed claim explains an individual order: a connection, an application response and a confirmed execution are different events.[2]

The contact directory also lists New York, Boston, Japan and Hong Kong offices. The older corporate narrative still refers to Redwood Shores; this profile uses the explicit Palo Alto headquarters listing for current contact context. The distinction avoids turning an old company description into a current address assertion.[3]

Operator

Fortex Inc.

Service scope

Trading applications, aggregation and bridge technology, broker backoffice, APIs and managed infrastructure for brokerage and institutional workflows. External liquidity counterparties remain separate.

Customer types

Retail and institutional brokers; Liquidity providers; Banks; Hedge funds; Asset managers; Proprietary trading firms

Delivery

SaaS; Hosted; API; Managed service

Pricing publication

Quote only

Headquarters

Palo Alto, California, United States

Platforms

Fortex 7; XForce; Bridge OMX; XCLOUD

Integrations

MT4/MT5; FIX API; RESTful API; WebSocket API; Duplikium

Pricing scope

The public MT4/5 WebTrader description specifies volume-based SaaS but no numerical unit rate. Hosting, integrations and other product terms require a configured offer.

Implementation

Cloud platform and private-label options; XCLOUD also supports dedicated/VPS hosting, MetaTrader installation, migration, backups and monitoring.

Support

Client portal and support tickets; API/hosting webpages advertise 24/6 English/Chinese assistance, while older brochures advertise 24/7. Confirm the purchased service window.

Permissions and regulatory scope

Fortex identifies as a technology solutions provider, not a broker-dealer or investment company. Platform access and an LP connection do not establish brokerage permission or custody by Fortex.

Provider metadata checked 20 Oct 2026Source 2Source 3Source 4Source 5Source 6Source 8Source 1Source 10Source 7Source 18

Cross-symbol hedging leaves a residual exposure decision

Cross-Symbol STP is available across Fortex 7 and Liquidity Hub, including MT4/MT5 and FIX environments. Fortex’s example converts the gold exposure in an RKG/CNH trade into an XAU/USD hedge. The remaining USD/CNH exposure can be retained, automatically hedged or managed manually under the broker’s strategy. This is a related-instrument hedge with a currency-management decision, not evidence that the original instrument has identical external liquidity or settlement.[17]

Price-feed failover and execution are separate controls

Symbol-level failover monitors pricing quality and switches only affected instruments to backup feeds. Other symbols remain on their existing route, and the description includes alerts and pricing visibility. This is a more granular response than replacing an entire feed. Its usefulness still depends on the chosen backup and the order route: restoring a displayed quote does not by itself confirm that an executable hedge exists on matching terms.[16]

MCP can expose trading actions to AI agents

The August 2026 MCP announcement explicitly covers more than market-data retrieval. It describes AI agents connecting to accounts, positions, orders and prices, including execution of trading actions from natural-language instructions. The published announcement does not set out default permissions, approval requirements, exposure limits or an audit-retention policy. Those specifics matter because the integration can affect a live account rather than only answer a question.[14]

Managed allocation and external copying use different workflows

The new PAMM module automates allocation across managed accounts within the Fortex stack. Separately, the Duplikium integration copies trades between platforms through an external cloud service. Copying requires its own account connections and execution/risk settings. These routes should not be treated as the same investment accounting model, and neither announcement establishes an identical return for every participating account.[13][18]

For daily investigation, the Web Trader manual distinguishes the server time displayed in the status bar from the user’s local time. It also separates order, ticket and position views. Consistent time references and record identifiers help an operations team compare a screen event with external execution or funding records without confusing display timing with the underlying transaction.[20]