MT5 Main License vs White Label vs Grey Label: Understanding the Differences
Quick Answer
“Main license”, “MT5 white label” and “grey label” are terms the brokerage technology industry uses to describe how much of a MetaTrader 5 environment a business controls. A main license usually means a directly licensed environment with the widest control; a white label usually means a branded environment running on someone else’s infrastructure; and “grey label” is an informal, non-standard expression for an even more dependent arrangement. None of them is a regulatory licence.
Anyone researching how brokerages are built quickly meets these three expressions. They appear in proposals, vendor decks and forum threads, often without definitions, and sometimes as if they were fixed product tiers. In practice they are shorthand. They describe a spectrum of control over trading-platform infrastructure, and the precise position of any arrangement on that spectrum is set by contracts rather than by the label attached to it.
This guide explains what each term usually means in the context of MetaTrader 5, how the structures tend to differ in branding, administration and dependency, and why technology access must never be confused with authorisation to provide financial services.
What Is MetaTrader 5?
MetaTrader 5 is a multi-asset trading platform developed by MetaQuotes. For a brokerage it is not only the terminal that clients download: it also includes server-side components, a manager and administrator toolset for configuring accounts, groups and symbols, reporting, and interfaces through which other systems such as CRMs and liquidity bridges connect.
Licensing of the platform, the options available, eligibility and permitted use are determined by MetaQuotes and the contractual documentation it issues. That matters for this article: the expressions discussed below are mostly industry vocabulary. Where they overlap with official MetaQuotes terminology, the official definition prevails, and current terms should always be confirmed through MetaQuotes’ own channels. For a wider technical overview, see our guide to MT5 server architecture and broker administration, and the background on how MT4 and MT5 differ.
What Is Commonly Called an MT5 Main License or Main Label?
In industry conversation, an MT5 main license (also called a main label, full licence, primary server licence or simply an MT5 server license) describes an organisation that operates its own primary MetaTrader 5 environment under a direct arrangement with the platform developer. The phrase is descriptive, not a guarantee of any specific feature set.
What the term usually signals is control. Depending on the agreement and configuration, an organisation running its own environment typically decides on:
- server administration, access roles and manager permissions;
- symbols, trading groups, account types and leverage settings;
- which integrations connect and how, including CRM and reporting systems;
- liquidity connectivity and execution configuration; and
- the wider hosting and infrastructure architecture.
Control brings responsibility. A production brokerage environment involves far more than trading-platform software: hosting and monitoring, liquidity and bridge connectivity, risk technology, a CRM and back office, KYC/AML tooling, payment integrations, security controls and trained staff to run it. The direct structure gives the most room to design those layers; it also leaves the operator responsible for all of them.
What Is an MT5 White Label?
An MT5 white label generally describes a business presenting a MetaTrader 5 trading environment under its own brand while the underlying server infrastructure belongs to, or is administered through, another licensed environment upstream.
To end clients, the environment can look independent: their own brand name, logo and server identity, their own account groups and client communications. Behind that, the upstream operator commonly retains responsibility for the server and grants the white-label business a defined set of administrative and manager rights.
“Defined” is the important word. Two offers that both use the phrase MetaTrader 5 white label can differ widely in:
- which manager and administrator permissions are granted;
- whether the business can create groups, symbols or account types itself;
- access to trade data, reports and audit logs;
- permitted integrations, such as a third-party CRM or risk system;
- liquidity configuration and who controls execution routing;
- support and incident responsibilities; and
- what happens to accounts and data if the agreement ends.
A white label is therefore neither complete independence nor complete dependence. It is whatever the contract grants. Our comparison of white-label and custom-built trading platforms looks at the build-versus-brand decision from another angle.
What Does “MT5 Grey Label” Mean?
“Grey label” is an industry expression. It should not automatically be treated as an official MetaQuotes licensing category, and its meaning is not standardised.
In common usage it describes an arrangement that sits somewhere between an introducing-broker relationship and a fully branded white label. A business described this way usually operates closer to the identity, infrastructure and processes of an existing brokerage. Compared with a typical white label, people using the term often mean some combination of:
- limited or shared branding;
- fewer administrative permissions and less configuration freedom;
- shared infrastructure and operational processes; and
- greater reliance on the upstream brokerage.
Because each provider may use the phrase differently, the only reliable way to understand a specific “MT5 grey label” proposal is to examine its contractual and technical structure, and to confirm that the proposed use is permitted under the applicable platform licensing terms. The companion article white label vs grey label in brokerage technology covers the grey-label question beyond MT5 specifically.
MT5 Main License vs White Label vs Grey Label
The table below summarises how the three terms are typically used. It is deliberately simplified: actual rights depend on the agreements involved.
| Area | Main license (direct environment) | White label | “Grey label” (industry term) |
|---|---|---|---|
| Licensing relationship | Direct arrangement with the platform developer | Operates through an upstream licensed environment | Usually operates under an existing brokerage’s arrangement |
| Branding | Full control | Typically own brand | Often limited or shared |
| Infrastructure control | Operator-controlled | Mostly upstream-managed | Upstream-managed |
| Server administration | Widest | As granted by agreement | Usually narrow |
| Operational independence | High | Moderate, depends on agreement | Generally lower |
| Integrations | Operator decides, within licence terms | Subject to upstream approval | Often fixed by the upstream brokerage |
| Third-party dependency | Lowest | Higher | Highest |
| Regulatory responsibility | Remains with the operating entity | Remains with the operating entity | Depends on the legal and contracting structure |
Technology Licensing Is Not the Same as Regulatory Licensing
This is the single most important distinction in the subject. A platform arrangement, whether described as a main license, a white label or anything else, concerns software and infrastructure. It does not, by itself, authorise anyone to:
- deal in or arrange transactions in financial instruments;
- solicit or onboard clients in a particular country;
- hold or handle client money; or
- describe the business as a regulated broker.
Those permissions come from financial regulators, under the law of each jurisdiction where the business is established or serves clients. A firm can have extensive technology and still be unable to offer services in a market; equally, a properly authorised firm may choose to outsource much of its technology. The two questions should be assessed separately, and the regulatory one with qualified legal advice and the relevant regulator.
The same separation applies to execution model choices discussed in A-book, B-book and hybrid architecture: how risk is handled is a technology and policy design matter, while permission to take that risk is regulatory.
What Should Brokers Evaluate Before Choosing a Technology Structure?
Whichever label a proposal uses, the following points determine how the structure will work in practice:
- Platform permissions — exactly which manager and administrator rights are granted, and which remain upstream.
- Infrastructure ownership — who owns and operates servers, data centres, backups and monitoring.
- Administrative access — who holds credentials, who can change groups, symbols and leverage, and how changes are logged.
- Data control — who owns client and trade data, and what export rights exist.
- Contractual rights — branding rights, exclusivity, service levels and permitted use under the applicable platform terms.
- Termination arrangements — notice periods, account and data handover, and what clients experience if the arrangement ends.
- Regulatory requirements — which entity is authorised, which contracts with clients, and which jurisdictions are served.
- Integrations — whether a chosen broker CRM and back office, bridge connectivity or reporting tools can connect, and through which platform interfaces.
- Operational continuity — incident handling, disaster recovery and how a future move to a different structure would work. Our platform migration guide shows how many systems depend on the platform when that day comes.
Why Terminology Alone Can Be Misleading
The three labels compress a great deal of detail into a few words. A “white label” with broad manager rights and full data export can look more like a direct environment than a restrictive one; a proposal called a white label may, on inspection, be closer to what others call a grey label. Some offers use the vocabulary loosely, and some combine elements of several structures.
The practical rule is to evaluate the actual technical permissions, the contractual rights and the regulatory position, and to confirm the platform licensing aspects directly with MetaQuotes. Treat the label as a starting point for questions, not as the answer.
Frequently Asked Questions
What is an MT5 white label?
An MT5 white label is a commonly used term for an arrangement in which a business presents a MetaTrader 5 trading environment under its own brand while the underlying server infrastructure is connected to, or administered through, another licensed platform environment. The exact permissions depend on the contract.
Is an MT5 white label the same as a brokerage licence?
No. A white label concerns access to trading technology. Authorisation to offer financial services comes from a financial regulator in the relevant jurisdiction, and the operating entity remains responsible for obtaining any permissions its activities require.
What is the difference between an MT5 main license and a white label?
In industry usage, a main license describes an organisation operating its own primary MetaTrader 5 environment under a direct arrangement, usually with the widest administrative control. A white label usually relies on an upstream environment, with branding and administrative rights limited to what the agreement grants.
What does MT5 grey label mean?
Grey label is an informal industry expression, not an official MetaQuotes licensing category. It usually describes an arrangement more dependent on an existing brokerage than a typical white label, but its meaning varies between providers, so the underlying contract must be examined.
Does a white-label broker control the MT5 server?
Usually not in full. The upstream operator commonly retains responsibility for the server, while the white-label business receives the administrative and manager permissions set out in its agreement. Those permissions vary from one arrangement to another.
Can different MT5 white-label arrangements provide different permissions?
Yes. Two arrangements both described as white labels can differ substantially in administrative access, data access, reporting, integrations, liquidity configuration and termination terms. The agreement, not the label, defines what is permitted.
Who should businesses verify MT5 licensing requirements with?
Product licensing, eligibility and permitted use should be confirmed with MetaQuotes through its official channels and the applicable contractual documentation. Regulatory requirements should be confirmed with the relevant financial regulator and qualified legal counsel.
Official references
Related Reading
Related Research
Operator-level analysis supporting trading platforms.
Take this from research to build.
Our team builds and operates trading platforms for brokers and prop firms.