For your role
For the partnerships and distribution lead
There are six ways to work together, from a referral motion through to a full white-label deployment. The usual path is a discovery session, then a scoped pilot on one segment, then the deployment model that fits how much of the experience you want to own.
Six ways to work together
White label, embedded components, API, MCP for your own agents, referral and co-sell, and data exchange. Most partnerships start narrow and widen once a pilot has produced evidence.
- White label: your brand and domain, our layer underneath.
- Embedded components: capability inside your existing screens.
- API: you build the interface, we serve the capability.
- MCP: your agents work on scoped tenant data.
- Referral and co-sell: introduce first, integrate later.
- Data exchange: your data drives the workflow and is attributed.
The pilot path
A pilot is deliberately small: one segment, one workflow, one tenant, real records. The purpose is to see whether the capability changes what users do, not to demonstrate features.
We do not publish integration timelines, because they depend on the deployment model and on your own release process. Discovery is where a realistic schedule gets set.
Commercials
Commercial terms are agreed per partnership and depend on deployment model, scope and support expectations. The partner sets what its own users pay, because the partner owns the client relationship.
Why breadth matters to a distribution partner
A distribution partner rarely has users in one asset class. The platform supports 68 native asset classes and 314 sub-asset class overlays across 56 of them, across the major fund jurisdictions, which is what makes one embedded layer viable rather than a series of point integrations.
This seat, by partner archetype
- Marketplaces and deal networks
- Settlement and transaction platforms
- Registries, transfer agents and custodians
- Fund administrators and outsourced back office
- Wealth, adviser and private bank platforms
- Capital raising and placement networks
- Data providers and research vendors
- Tokenisation and digital asset venues
By market
- Embedded infrastructure in Australia
- Embedded infrastructure in Singapore
- Embedded infrastructure in Japan
- Embedded infrastructure in the United States
- Embedded infrastructure in the United Kingdom
- Embedded infrastructure in Brazil
- Embedded infrastructure in Canada
- Embedded infrastructure in Hong Kong
- Embedded infrastructure in Europe
- Embedded infrastructure in Latin America
Questions in this seat
Can we start without an integration?
Yes. A referral or co-sell motion needs no engineering work and is a reasonable way to test demand before committing to an integration.
What do you need from us for discovery?
The archetype and user base, the surface the layer would sit behind, the workflows in scope, and the residency and governance constraints that apply.
How is the partnership priced?
Per partnership. We do not publish partner economics and do not quote figures before understanding scope.