Updated October 6, 2026 · 15 min read

Forex Broker Technology Stack 2026: 8 Layers and How to Choose

The forex broker technology stack in 2026, layer by layer: platform, terminals, liquidity, CRM, payments, KYC, risk and security, and how to pick providers.

Key takeaways
  • A forex broker’s technology stack has eight layers: trading platform, client terminals, liquidity and bridge, CRM, payments, KYC, risk and back office, and security.
  • Most new brokers combine components from several providers rather than building everything or buying one closed bundle.
  • Platform access comes first: MetaQuotes has tightened MT5 eligibility since 2022, so every other choice depends on how you secure it.
  • The web terminal is the layer new clients see first, yet it is often left generic; since 2022 each broker runs its own MT5 web terminal and can present it on its own domain.
  • When choosing a forex broker technology provider, judge ownership of data, domains and configuration, integration points and exit terms, not just feature lists.
  • Build the stack in order (licence, platform, liquidity, CRM, payments, terminals, security), and plan reporting and data exports before launch, not after.

What is a forex broker technology stack?

A forex broker technology stack is the set of systems a brokerage needs to onboard clients, take their money, let them trade and manage the resulting risk. In 2026 it usually has eight layers: a trading platform (most often MetaTrader 5), client terminals, a liquidity bridge, a CRM and client area, payments, KYC and compliance tools, risk and back-office software, and security infrastructure. Few brokers build these themselves; most combine products from several technology providers and keep control of the parts that touch their brand and data.

#LayerWhat it doesTypical options
1Trading platformAccounts, prices, orders, executionOwn MT5 licence, MT5 white label, other platforms
2Client terminalsWhere clients trade: desktop, mobile, webStandard apps, branded web terminal, custom terminal
3Liquidity and bridgeConnects the platform to liquidity providers and routes ordersBridge providers, prime-of-prime, aggregation
4CRM and client areaRegistration, account opening, documents, IB managementBroker CRM products, custom portals
5PaymentsDeposits and withdrawalsBanks, card processors, PSPs, crypto gateways
6KYC and complianceIdentity checks, AML screening, regulatory reportingKYC vendors, screening tools
7Risk and back officeExposure, A-book/B-book decisions, reporting, accountingRisk tools, reporting plug-ins, BI
8Security and infrastructureDDoS protection, access control, hosting, backupsCloudflare, data centres, monitoring

The layers are connected. The CRM creates platform accounts, the bridge reads platform orders, the risk tool reads both, and the terminal is where the client finally sees the result. A weak link anywhere shows up as a support ticket somewhere else, which is why the stack should be planned as a whole rather than bought piece by piece in a hurry.

Which trading platform should a forex broker use?

For most retail FX and CFD brokers the trading platform is still MetaTrader 5. It holds client accounts, streams prices, accepts orders and keeps the trade history every other layer depends on. There are three common ways to get it:

  • Own server licence: you hold the licence directly with MetaQuotes and run your own trade, access and history servers (usually hosted by a specialist). Maximum control, highest responsibility.
  • White label: you operate under a licence holder’s server with your own brand and groups. Faster to start, less control over configuration.
  • Other platforms: some brokers choose alternative or proprietary platforms, often alongside MT5 rather than instead of it.

The platform layer has become harder to secure. MetaQuotes stopped selling MT4 licences to new customers on 12 January 2018, according to trade press. In late 2022, industry reports say, MT4 white labels were discontinued, new MT5 white labels were suspended and MT5 access began to require a regulated FX/CFD company with a corporate bank account; MetaQuotes has not published an official page on this. In February 2024 several prop firms lost platform access, and some regained it during 2025. Trade press also reported a licence fee increase from 1 January 2025 and a cut-off for old platform builds on 1 July 2025. Our MetaQuotes policy timeline collects these events, and white label vs grey label vs own MT5 licence compares the routes in detail.

The practical lesson: confirm how you will obtain platform access before you sign anything else, because CRM, bridge and terminal choices all assume a working platform. For licensing questions specifically, a dedicated resource such as mt5license.net covers the options.

Client terminals: desktop, mobile and web

Clients reach the platform through three kinds of terminal. The desktop terminal suits active traders who use Expert Advisors and custom indicators. The mobile apps cover trading on the move. The web terminal runs in the browser with nothing to install, which is why it is often the first terminal a new client opens straight after registration.

According to MetaQuotes, the MT5 web terminal is built on HTML5, works in Chrome, Safari, Edge, Opera and Firefox on Windows, macOS and Linux, is optimised for mobile browsers, supports all MT5 order types and one-click trading, and handles both netting and hedging accounts. It offers 30 indicators, 24 analytical objects, 9 timeframes and 3 chart types. It does not run Expert Advisors or custom indicators, so it complements the desktop terminal rather than replacing it; see MT5 WebTrader vs desktop vs mobile.

The important change came on 12 October 2022. MetaQuotes announced a new web terminal that “operates as an individual web terminal, which only works with a specific broker’s platform”, running on the broker’s own access server and linked to a domain. Brokers with a web terminal licence can deploy it at no extra fee. Since then, the question is no longer whether you have a web terminal but how you present it.

PresentationHow it worksClient experienceMain trade-off
Plain linkYour site links to the terminal addressClient leaves your brand at the moment of tradingFast, but looks generic and is easier to imitate
Iframe embedTerminal shown inside a page of your websiteStays on your site, but inside a frameLayout, mobile and cookie behaviour need testing
Full-screen on your own domainTerminal served at an address such as trade.yourbrand.comConsistent brand, clear address to bookmarkNeeds DNS, certificates and a delivery layer
Custom terminalYour own front end built on an APIFully bespokeDevelopment and maintenance effort

FXPTrader sits in this layer. It delivers your MT5 web terminal on your own domain through a Cloudflare Worker deployed in your own Cloudflare account, with automatic SSL, no servers to run, login control by account range and settings such as company name, address, licence and privacy links kept as environment variables. It is not an MT5 licence or a white label: you need your own MT5 access. See how it works and MT5 WebTrader on a custom domain.

Liquidity and bridge: how orders reach the market

The bridge connects the trading platform to liquidity providers. It receives orders from MT5, applies routing rules and sends them either to external liquidity (A-book), keeps them in-house (B-book) or splits flow between the two (hybrid). Aggregation tools combine prices from several providers into one feed.

Questions to settle before you choose:

  • Connectivity: which liquidity providers and prime-of-prime firms are already integrated, and how new ones are added.
  • Routing rules: can you route by group, symbol, account or trade size, and who is allowed to change those rules?
  • Monitoring: how execution quality, rejections and slippage are recorded and reported to you.
  • Hosting: where the bridge runs relative to your trade server and your providers, since physical distance affects execution.
  • Configuration ownership: whether you or the vendor manages the setup day to day.

Keep the bridge separate in your mind from the web layer. Execution speed depends on the trade server, the bridge and the liquidity venues; how the web terminal is delivered to the browser affects page loading and connection reliability, not order execution. Our guide on WebTrader latency and uptime explains the difference.

CRM, payments and KYC: the client lifecycle layers

These three layers turn a visitor into a funded, verified client and keep them that way.

CRM and client area. The CRM handles registration, account opening, document collection, deposit and withdrawal requests, and introducing broker (IB) commissions. It should create MT5 accounts automatically through the platform’s manager interface, assign the right group and leverage, and send the client straight to your web terminal once approved. A good test: how many clicks and emails separate “registration complete” from “first trade”?

Payments. Payments are often the hardest layer for a new broker because banks and payment service providers review your licence, jurisdiction and business model closely. Most brokers use more than one provider so a single account closure does not stop deposits. The CRM should record every transaction and reconcile it with platform balance operations.

KYC and compliance. Identity verification and AML screening tools plug into the CRM, ideally so that approval flows back automatically. Regulatory reporting draws on both CRM and platform data. Your client-facing pages, including the web terminal, should show your company name, address and legal links; see compliance details your web terminal should show.

IntegrationData that flowsWhat goes wrong if it is missing
CRM to platformAccount creation, groups, balance operationsManual account opening, errors in leverage or groups
Payments to CRMDeposit and withdrawal statusFunds credited late or twice, reconciliation work
KYC to CRMVerification result, risk scoreUnverified clients trading, or approved clients waiting
CRM to web terminalLogin details, server name, linkClients cannot find where to trade
Platform to reportingTrades, positions, balancesLate or inconsistent finance and regulatory reports

Risk, back office and security infrastructure

Risk and back office. Risk tools monitor net exposure by symbol, flag unusual client behaviour and support A-book/B-book decisions. Back-office and reporting tools turn platform data into finance, commission and regulatory reports. Plan reporting early: the data model you pick at launch is disruptive to change once months of history exist.

Security and infrastructure. Brokers are frequent targets of DDoS attacks and phishing clones that copy their branding to steal logins. MetaQuotes partnered with Cloudflare in 2020 to protect MT5 endpoints against DDoS. On the client side, a few habits reduce risk considerably:

  • Serve every client-facing property, including the web terminal, over HTTPS on a domain you control.
  • Publish one clear terminal address so clients can recognise a fake one.
  • Restrict which account ranges can log in through each terminal address; see restrict MT5 WebTrader login ranges.
  • Use two-factor authentication and role-based access for staff in CRM, manager and admin tools.
  • Keep backups and documented recovery steps for every layer you operate yourself.

Cloudflare states that its network spans 348 cities in over 100 countries, with about 95% of internet users within 50 ms. Its Workers runtime supports WebSockets and its Custom Domains feature creates DNS records and certificates automatically. A Worker cannot host an MT5 trade server, however, so it belongs in the delivery and protection layer, not the execution layer. The WebTrader security checklist covers the details.

Build, buy or white label: what to choose for each layer

Every layer can in principle be built, bought as a standalone product or taken as part of a white-label bundle. In practice the pattern below is common for small and mid-sized brokers.

LayerUsually boughtUsually white-labelledSometimes built
Trading platformOwn MT5 licenceMT5 white labelRarely
Web terminalBranded WebTrader layerProvider package terminalCustom terminal on an API
Liquidity and bridgeYesIn bundlesRarely
CRM and client areaYesIn bundlesLarger brokers
Payments and KYCYesNoNo
Risk and reportingYesIn bundlesLarger brokers
SecurityYes (for example Cloudflare)NoNo

A turnkey bundle gets you live with one contract, but it concentrates risk: if the relationship ends, several layers may need replacing at once. Buying best-of-breed components takes more integration work but lets you swap one layer without touching the rest. Building makes sense only where a component is a genuine competitive advantage and you have the team to maintain it for years. For the web layer specifically, white label WebTrader options for MT5 brokers compares the routes.

How to choose a forex broker technology provider

Feature lists from forex brokerage technology vendors look alike. The differences show up in ownership, integration and what happens when you leave. Use these criteria for any provider, whatever the layer:

  1. Ownership: who owns the client data, the domains, the certificates and the configuration? You should be able to export all of it in a usable format.
  2. Account and access: does the product run in your own accounts (cloud, platform, DNS) or only in the vendor’s? Running in your own account makes audits and exits simpler.
  3. Integration points: which APIs, webhooks and platform connections are documented, and which are custom work?
  4. Regulatory fit: can the product show the legal details, disclosures and links your regulator expects, and keep the records it requires?
  5. Change control: who can change settings, how changes are logged and how quickly you can make one yourself.
  6. Support model: named contacts, response expectations in writing and an escalation path.
  7. Exit terms: notice periods, data hand-over, and whether anything stops working on the day the contract ends.
  8. Multi-brand support: if you plan several brands or entities, whether each can have its own configuration and address.
Question to askGood answerWarning sign
Where does my data live?In named locations, exportable on request“In our system” with no export format
Who controls my domain?You, in your own DNSThe vendor registers it for you
How do I change a setting?Self-service, with a change logTicket only, no visibility
What happens if we part ways?Documented hand-over, nothing hiddenUnclear, or “we will discuss”
Which platform access do I need?Stated clearly up frontVague about licences

Technology providers that resell or bundle web terminals have their own considerations; see WebTrader for technology providers.

Typical technology stacks by business type

The eight layers stay the same, but their weight changes with the business model.

  • New retail broker: MT5 white label or own licence, a broker CRM, one or two PSPs, a bridge to a prime-of-prime provider, KYC integrated into the CRM, and a branded web terminal on your domain so clients trade where they registered.
  • Established broker: own MT5 licence, multiple liquidity providers, in-house risk desk and reporting, often a custom client area, and one terminal address per regulated entity.
  • Prop firm: platform access through a partner broker or own licence (access has changed several times since 2024), a challenge dashboard, automated account creation and a branded terminal restricted to challenge accounts; see WebTrader for prop firms.
  • Introducing broker: the partner broker’s platform, liquidity and payments, plus your own marketing site and a branded terminal address for your clients; see WebTrader for introducing brokers.
  • Multi-brand group: one platform, several brands or entities, each with its own legal details, login range and terminal address; see multi-brand WebTrader.
  • Crypto CFD broker: the same layers, with crypto gateways in payments and extra attention to symbol settings and trading hours; see WebTrader for crypto CFD brokers.

In what order should you build the stack?

Sequence matters because each layer depends on the one before it. A practical order for a new brokerage:

  1. Licence and entity. Platform access, banking and payment providers all depend on your regulatory status.
  2. Platform access. Secure MT5 through your own licence or a white label, and agree server hosting.
  3. Liquidity and bridge. Connect providers, define groups and routing, and test execution on demo.
  4. CRM and KYC. Configure registration, verification and automatic account creation.
  5. Payments. Integrate at least one provider, ideally two, and test reconciliation.
  6. Client terminals. Publish the desktop and mobile download links and your branded web terminal; MetaQuotes says its broker video guides take you from domain selection to website integration within 30 minutes.
  7. Security. Put DDoS protection in front of web properties, restrict terminal logins by account range and set up staff access controls.
  8. Reporting. Confirm finance and regulatory reports work with real data before you open to clients.

The web terminal step is short when the platform is ready. With FXPTrader the terminal is typically live the same day, because setup consists of deploying a Worker to your Cloudflare account and filling in environment variables. The branded WebTrader launch checklist lists each item.

Common mistakes when assembling a broker tech stack

  • Signing for tools before platform access is confirmed. A CRM or bridge contract is of little use if the platform route falls through.
  • Leaving the web terminal generic. Clients who register on your brand and then trade on an unfamiliar address are more likely to hesitate or fall for clones.
  • Letting a vendor own the domain. Domains, DNS and certificates should sit in accounts you control.
  • Only one payment provider. A single account review can stop deposits overnight.
  • Manual hand-offs between layers. Copying data from KYC to CRM or from CRM to platform by hand creates errors and delays.
  • Treating reporting as an afterthought. Retrofitting reporting after launch is slow and disruptive.
  • Confusing delivery speed with execution speed. A fast-loading terminal page does not change how quickly the trade server and liquidity providers execute orders.
  • No exit plan. Know how you would replace each layer before you need to.

Sources

Licensing policy events from 2018 to 2025 are based on trade press reports; MetaQuotes has not published official pages for all of them.

Frequently asked questions

What technology does a forex broker need?

A forex broker needs eight layers: a trading platform, client terminals, a liquidity bridge, a CRM and client area, payments, KYC and compliance tools, risk and back-office software, and security infrastructure. Most brokers buy these from several providers and integrate them, rather than building them in-house.

What is a forex broker technology provider?

It is a company that supplies one or more layers of a brokerage’s stack, such as the platform, CRM, bridge, payments integration or web terminal. Some sell turnkey bundles covering most layers; others specialise in one layer and integrate with the rest.

Should a new broker buy a turnkey bundle?

A bundle is fast to launch with a single contract, but it concentrates risk if the relationship ends. Before signing, check who owns the data and domains, how much configuration you control yourself and what the exit terms say.

Which trading platform do most forex brokers use?

For retail FX and CFD brokers it is still mostly MetaTrader 5, obtained through an own licence or a white label. Access has become stricter since 2022, with industry reports saying MetaQuotes now expects a regulated company with a corporate bank account.

Where does the web terminal fit in the stack?

It is part of the client terminals layer, alongside desktop and mobile apps. It is often the first terminal a new client uses because nothing needs installing, so presenting it on your own domain keeps the experience consistent with your website.

Does every MT5 broker have its own web terminal?

Since MetaQuotes’ announcement of 12 October 2022, each broker’s web terminal runs on its own access server and works only with that broker’s platform. Brokers with a web terminal licence can deploy it at no extra fee; others request it through MetaQuotes support.

Which layer is hardest to set up?

Usually payments and banking, because banks and payment providers review your licence, jurisdiction and business model closely. Platform access has also become harder since 2022. Starting both early avoids delays elsewhere in the stack.

How do I protect the stack against DDoS and phishing?

Use network-level protection for platform endpoints and web properties; MetaQuotes partnered with Cloudflare for MT5 DDoS protection in 2020. Against phishing, publish one clear HTTPS terminal address on your own domain and restrict which account ranges can log in through it.

Can a Cloudflare Worker host the MT5 trading server?

No. The trade server must run on MetaQuotes-compatible infrastructure under your licence or white label. A Worker can deliver and protect the web terminal on your domain, which affects page loading and access control, not order execution.

Is FXPTrader an MT5 white label?

No. FXPTrader delivers your existing MT5 web terminal on your own domain through a Cloudflare Worker in your own Cloudflare account. You still need your own MT5 access through a licence or white label.

How long does it take to assemble a broker technology stack?

It depends mostly on licensing, platform access and payment providers, which can take far longer than the technical work. Individual layers such as a branded web terminal can be live the same day once the platform is ready.

How should a multi-brand broker set up its stack?

Most groups share one platform and back office but give each brand or entity its own legal details, login range and terminal address. With FXPTrader that means one Worker and configuration per brand, so each brand’s settings stay separate.

See your brand on a live WebTrader

Send us your company name and domain. We will set up a personalised demo so you can see exactly how your terminal will look.