ON THIS PAGE
Treat Grey Label as a defined service arrangement
Grey Label is used in the industry for narrower or more dependent service arrangements, but it does not have one universal technical specification. Before comparing offers, ask which environment is provided, what branding can be changed and which configuration controls you receive. The actual contract and architecture matter more than the label attached to the package.
Questions about access and control
Confirm whether your team can manage account groups, instruments and client provisioning, or whether these changes must be requested from the service operator. Determine who holds administrative access and who owns data exports. Establish whether APIs, reporting access and independent integrations are available. These answers affect daily operations and the ability to migrate later.
Branding and client experience
Describe which client-facing components need your identity: website, client area, platform presentation, statements and communications. Do not assume that every distribution channel or application can be rebranded. Record the permitted branding scope and any platform-provider requirements before promising a particular trader experience.
Support, costs and transition planning
A dependent arrangement can reduce the amount of infrastructure you operate directly, but it also creates a reliance on the operator for changes and incident resolution. Compare setup, recurring charges, change requests and support boundaries. Ask how account and configuration data can be exported and what assistance would be required to move to a different arrangement.
Compare with a broader White Label scope
Use a requirements checklist covering access, configuration ownership, integrations, data portability and support. If independent CRM or liquidity interfaces are essential, verify their availability first. A project discussion can then determine whether the narrower scope matches your operating model or whether a broader platform deployment is required.