MT5 gray label: access boundaries and open dependencies.
An MT5 gray label gives a branded platform environment under a provider arrangement. For architecture purposes, the key question is where your access ends and the provider’s begins.
Boundaries to document
Trading groups, manager logins, symbol list, spread control and client account actions available to you. Record each as a permitted or not-permitted capability in your design file.
Dependencies left open
CRM, payments, liquidity, hosting of ancillary services and any compliance tooling remain yours to arrange. Whether you need a company or a forex license depends on your jurisdiction and activity; see the licence inputs.
When the boundary is too tight
If you need sub-licensing, full server ownership or deeper integration, evaluate an MT5 white label. Decide based on required capabilities, not label names.
Verification after provisioning
After the environment is provisioned, verify each documented capability: log in with every role, create a test group, check symbol visibility and confirm client account actions. Keep screenshots and notes. These become your baseline if anything changes later.
Capability register
Create a register with capability, status, evidence and owner. Examples: create trading group, change spread markup, view client positions, run reports, reset passwords. Update it as the provider confirms or changes access. It becomes the contract of what you can actually do.
Questions we hear
Is gray label the same as grey label?
Yes. Two spellings, one term. The scope defines the product.
Can CRM be added after launch?
Typically yes, as an additional integration with its own scope and tests.