Your MT5 infrastructure.
Our bridge to liquidity.
Drovix develops the bridge technology connecting approved institutional MT5 environments to its principal liquidity. Explore the interface between the broker’s platform, Drovix pricing and counterparty controls.
Integration architecture / Responsibilities exposed
A bridge joins systems.
It preserves boundaries.
Select a component to inspect its role. The model separates your broker infrastructure, the Drovix bridge and the principal liquidity relationship.
Select a component
Exploded view / conceptual architecture
- Broker infrastructureSelected
- Drovix bridge
- Drovix counterparty
Your side
Broker infrastructure
The broker operates its MT5 environment and its client relationships. Drovix connects to an approved institutional counterparty; this bridge is not a Drovix retail trading account.
- Consider at the boundary
- Server topology, instrument universe and authorised order sources.
- What it contributes
- The institutional instructions and price subscriptions to integrate.
- Verify together
- Which server, authorised order sources and instrument subscriptions belong in the integration scope?
The translation boundary
The same instruction.
On both sides.
A symbol name alone is not a complete mapping. The integration brief needs to align instrument identity, size conventions, order states and the record returned to the broker.
Instrument
MT5 symbol and contract definition
Map the symbol, precision and volume convention to the agreed Drovix instrument.
Instruction
Order request or lifecycle event
Agree which instructions are supported and how acceptances, rejections and fills are represented.
Record
Broker-side order and deal records
Define identifiers and reporting so operations can reconcile the same transaction across the connection.
Integration considerations are illustrative. Supported events, conventions and behaviour must be confirmed in the agreed interface specification.
Integration review / Test the boundaries
The exception
belongs in the brief.
Use UAT to establish what both sides should observe when the normal path changes. Open a scenario to inspect the questions it raises.
AThe session disconnects
Establish who detects the break, how reconnect works and how open instructions are reconciled. Document ownership before enabling production activity; the expected behaviour comes from the session specification.
BAn instruction is rejected
Verify that the rejection reason and identifiers can be traced on each side. Confirm how the broker receives the outcome and whether any further instruction is appropriate under the agreed order workflow.
COnly part of an order fills
Check filled and remaining quantities, identifiers and subsequent lifecycle events. The broker and Drovix records need to reconcile the same result without assuming every instruction produces one complete fill.
DA symbol configuration changes
Review contract size, precision, sessions and permitted activity before changing a mapping. Agree the validation, operational notice and cut-over responsibilities for the new configuration.
The next conversation
Bring the platform details.
Share your MT5 environment, instruments and order requirements. The institutional desk can frame the bridge and counterparty review around the actual integration.
Discuss your MT5 integrationLeveraged OTC products, including Forex and CFDs, carry a high level of risk and a counterparty may lose more than its initial margin. The Drovix offering is directed exclusively at Eligible Counterparties and Professional Clients; Drovix does not provide services to retail clients.
MT5 connectivity is for approved institutional counterparties. Drovix does not offer retail MT5 accounts. Availability, supported functionality and production access depend on counterparty approval and the agreed configuration.