MetaTrader 5 trading platform accounted for 65% of combined MT4/MT5 trading volume in Q1 2026, up from 54.2% when it first overtook MT4 in Q1 2025, according to Finance Magnates Intelligence. This shows that the shift toward MT5 has continued steadily, with the platform strengthening its lead over MT4 within just one year.
That growth pushes more forex and CFD brokers and liquidity providers toward the question: how to connect their MT5 server to external liquidity? This article focuses on that technical decision: a native MT5 gateway or a third-party MT5 gateway by a fintech solution provider.
This is different from MT5 bridge vs MT5 gateway, where both solutions are third-party and differ mainly in how the liquidity connectivity architecture is structured.
What Is a Native MetaQuotes MT5 Gateway?
A native MetaQuotes MT5 gateway is a connectivity module developed and maintained by MetaQuotes that connects MT5 to a liquidity provider.
A native gateway is a built-in connectivity module within the MT5 server infrastructure. It connects the platform to a specific liquidity provider or another MT5 server using the protocol supported by the connected liquidity provider, such as FIX or a proprietary API.
Because the gateway is developed and maintained by MetaQuotes, brokers can establish this connection without introducing an additional third-party vendor into the execution stack.
Configuration such as leverage rules, trade request routing, symbol mapping, and price conversion is handled within the MetaQuotes gateway framework. This native integration reduces the number of external components in the execution chain and keeps configuration, monitoring, and support within the MetaTrader ecosystem.
What Is the Ultency MT5 Gateway?
MetaQuotes also offers Ultency, a newer paid liquidity aggregation and matching solution for MT5. It is a separate product from the standard native gateways and should therefore be considered independently when comparing native and third-party connectivity options.
Unlike a standard native gateway, Ultency is designed to work with multiple liquidity providers and adds aggregation, routing, matching, and risk-management functionality within the MetaQuotes ecosystem.
What Is a Third-Party MT5 Gateway?
A third-party MT5 gateway is a connectivity module developed by an external technology provider that connects MT5 to one or more liquidity providers while adding its own aggregation, routing, execution, or risk-management functionality.
A third-party gateway is an external solution built into MT5, either replacing or extending the native gateway.
This is done officially — MetaQuotes publishes the gateway API specifically for fintech solution providers to use. Public access to the gateway API lets providers create a gateway to any liquidity provider or exchange, working within the capabilities and limitations of the API.
Unlike a native gateway, a third-party solution can add an extra layer of execution and liquidity management between MT5 and external liquidity sources. Depending on the vendor, this can include multi-LP aggregation, advanced routing, A/B-book logic, markups, slippage controls, failover rules, and other broker-specific execution settings.
Which Broker Chooses Which Gateway?
| Free native gateway | Ultency gateway | Third-party gateway |
|---|---|---|
| Brokers satisfied with MetaQuotes' out-of-the-box functionality who don't need deep customisation of liquidity aggregation or risk logic | Brokers that want to stay within the MetaQuotes ecosystem but need multi-provider liquidity aggregation and matching | Brokers that require granular execution, routing and risk controls features |
| Brokers who want to minimise the number of vendors in the infrastructure chain | Brokers with relatively basic aggregation, routing, and risk-management requirements | White Label brokers who need faster iteration cycles than MetaQuotes' own release schedule allows |
| Brokers connecting to a single liquidity source rather than aggregating multiple providers | Brokers comfortable adopting a relatively new MetaQuotes liquidity solution | Brokers that need multi-provider liquidity aggregation rather than a single feed |
| Brokers who need a backup LP and symbol failover to avoid execution gaps if a primary liquidity provider drops | ||
| Brokers managing several trading platforms who need one gateway layer across all of them | ||
| Brokers who need sub-second execution speed tuned to their specific liquidity mix rather than MetaQuotes' default routing |
Native Gateway vs Third-Party Gateway Key Criteria Comparison
| Criterion | Free native MetaQuotes Gateway | Ultency | Third-Party Gateway |
|---|---|---|---|
| Licensing | Included in MetaQuotes licensing terms | Separate paid MetaQuotes solution | Requires a separate vendor agreement |
| Liquidity aggregation | Single source per gateway instance | Multi-provider aggregation across supported LPs | Multi-provider aggregation with smart order routing |
| Risk management options | Very limited | Limited | Varies by vendor, from basic to advanced |
| Customization opportunities | Very limited | Limited — customization is restricted to the configuration options provided by MetaQuotes | From lower customization in long-established leaders like oneZero Hub to high customization in newer market leaders like Takeprofit Bridge |
| Integration complexity | Lower — configured within the existing MetaQuotes environment | Low — native MT5 integration with aggregation and execution managed within the MetaQuotes ecosystem | From lower to high — depending on a vendor |
| Monitoring and reporting | Built-in MetaTrader administration and server logs | Centralized order, execution, client, and configuration logs, plus built-in reporting | Dashboards, logs, execution analytics, and monitoring alerts |
| Support | MetaQuotes support channels | MetaQuotes support channels | Dedicated support provided by the gateway vendor |
Pros and Cons
Native MetaQuotes Gateway
Pros:
- Fewer points of failure — one less vendor in the chain
- Full compatibility with the MetaQuotes ecosystem by default
- No additional integration work beyond standard MT5 setup
Cons:
- Limited risk and execution management capabilities
- No multi-provider liquidity aggregation within a single gateway setup
- Smaller choice of supported liquidity providers and venues
- Feature development depends on MetaQuotes’ own product roadmap
- Limited customization compared with third-party liquidity solutions
- Less flexibility for complex or non-standard brokerage setups
Ultency
Pros:
- Native integration with the MetaTrader 5 ecosystem
- Lower infrastructure complexity compared with setups that require a separate external gateway
- MetaQuotes support and development within the same ecosystem
Cons:
- Relatively new product with a much shorter production track record than established third-party solutions
- Fewer years of real-world deployment across different brokerage models and market conditions
- More limited options for bespoke routing, execution, and risk-management logic
- Custom development is dependent on MetaQuotes rather than a vendor adapting the product to an individual broker’s requirements
- Brokers are limited to the LPs, workflows, integrations, and functionality supported within the Ultency ecosystem
- Less suitable for highly customized or non-standard execution setups
- Higher MT5 gateway pricing than most third-party solutions
Third-Party Gateway
Pros:
- Flexible multi-provider liquidity aggregation
- Broader execution and order-routing capabilities
- Advanced risk management and exposure controls
- Faster turnaround on custom requirements — a vendor can ship a change in weeks rather than wait for a MetaQuotes release cycle
- Access to plugin ecosystems MetaQuotes doesn’t provide natively
- Wider choice of liquidity providers
- More flexibility to adapt the setup as the brokerage grows or changes its execution model
- Dedicated vendor support and, in many cases, more hands-on configuration assistance
Cons:
- Adds implementation costs comparing to free native gateways
- Takes time to evaluate vendors, test different solutions, and select the best fit for the broker’s setup
MT5 Gateway from Takeprofit Tech
MT5 Gateway from Takeprofit Tech is called Takeprofit Bridge. It connects MT5 to liquidity providers through the gateway API and aggregates liquidity from multiple providers into a single feed, enabling hybrid order execution.
The solution provides greater flexibility to adjust execution logic and liquidity settings without being limited to the native MetaQuotes gateway functionality.
Try MT5 gateway by Takeprofit Tech to
- configure routing and execution rules across multiple LPs
- automate A/B-book switching
- set swap control rules
- apply markups and slippage settings
- manage risks like exposure, and failover scenarios
Final Words
A native MetaQuotes gateway keeps execution logic inside the MT5 ecosystem, while a third-party gateway adds an external layer for aggregation, routing, monitoring, and risk controls, often using the FIX protocol to exchange prices, orders, and execution reports with liquidity providers.
That architectural difference becomes especially relevant as a broker adds more liquidity providers, instruments, and execution rules.
Overall, third-party MT5 gateways are often the more popular and flexible choice for brokers that need multi-LP aggregation, advanced execution controls, and greater customization. They can provide a more efficient setup for complex liquidity and risk-management requirements.
However, the best option still depends on the broker’s goals. A native MetaQuotes gateway may be sufficient for a simpler setup, while a third-party solution makes more sense when the broker needs broader connectivity, more control, and room to scale.
This comparison is different from the question of MT5 bridge vs MT5 gateway, where both solutions are third-party technologies. In that case, the distinction is mainly architectural: a gateway connects directly to the MT5 server, while a bridge usually acts as a broader external liquidity and execution layer and may itself use a gateway component to connect to MT5.