For your role
For the product and technology leader
The layer is designed to be integrated rather than adopted. Your system stays authoritative, tenants are isolated, and the surface can be white label, embedded components, API or MCP depending on how much of the experience you want to own.
How it fits your architecture
The layer does not require you to migrate your system of record. It reads existing records through the API and treats your system as authoritative, then adds decisioning, evidence and workflow on top.
Where you want full control of the experience, use the API and build your own interface. Where you want capability without a front-end programme, embed components inside your existing screens. Both models can run in the same deployment for different surfaces.
- Your system of record stays authoritative.
- Read and write through a documented API.
- Event subscription for status changes rather than polling.
- SSO against your existing identity provider.
Tenant isolation and residency
Each partner has an isolated tenant, and where a partner serves many clients, each client can be isolated too. Data is not pooled across tenants.
Hosting jurisdiction can be selected per tenant where compliance requires it. We describe what is configurable rather than claiming certifications we do not hold: Reuben AI is not SOC 2 certified, and we will not say otherwise in a procurement process.
Agents and MCP
If your team already runs assistants or agents, they can read and act on scoped tenant data through a tool interface with explicit permissions, rather than through screen scraping or a general-purpose chat window with no persistent state.
Permissions are set per tenant, and every action an agent takes is recorded in the same provenance chain as a human action.
Build versus partner, honestly
Screening against a written mandate is tractable. Evidence retention with tiered attribution across many document types is harder. Fund operations workflow across many structures and jurisdictions is where internal builds usually stall, because the surface area keeps growing.
If your roadmap has capacity for that surface area, build. If it does not, an integration is the shorter path and stays reversible.
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
Do we have to migrate data to start?
No. A pilot can run on a scoped set of records read through the API, with your system remaining authoritative.
How are permissions handled for agents?
Per tenant, with explicit scopes. Agent actions are recorded in the same provenance chain as human actions, so an action can be traced back to what triggered it.
Is Reuben AI SOC 2 certified?
No. We do not claim certifications we do not hold. We can describe the data isolation, residency options and access controls that are in place, and answer security questionnaires on that basis.