For platforms, networks and distribution partners
The decision and operational infrastructure for private capital
Marketplaces, transaction platforms, registries, administrators, adviser platforms and data vendors embed Reuben AI under their own brand. Their users get mandate-aware decisioning, evidence-backed diligence and end-to-end workflow. The partner keeps the client, the brand and the relationship.
Your surface, your brand
Reuben AI decision and operations layer
One record underneath
Why the middle layer is the opportunity
Private capital distribution is owned by networks. Marketplaces hold the flow. Transaction platforms hold the rails. Registries hold the record. Administrators hold the service relationship. Adviser platforms hold the client. Each of them owns something difficult to replicate.
What almost none of them own is the layer in between: a system that reads a mandate, screens an opportunity against it, produces evidence a committee can defend, runs the workflow that follows, and keeps the reasoning for as long as anyone will ask for it. Building that is a multi-year programme with a different centre of gravity from the core business.
Reuben AI is that layer, and it is designed to be invisible. It runs behind the partner brand, inside the partner surface, on the partner's terms for residency and data isolation. The partner keeps the client relationship and the pricing. The users get intelligence and operational workflow without leaving the platform they already trust.
Who embeds it
Eight archetypes across private capital distribution. Each has its own hub covering the users, the gaps, the integration surface and the questions that come up.
Marketplaces and deal networks
Relationship-driven flow, without an intelligence layer underneath it.
Read the hubSettlement and transaction platforms
The money moves. The reasoning and the records rarely travel with it.
Read the hubRegistries, transfer agents and custodians
Authoritative records of ownership, with no decision context attached.
Read the hubFund administrators and outsourced back office
Service delivered by people, constrained by the tooling underneath.
Read the hubWealth, adviser and private bank platforms
Advisers are being asked for private markets access they cannot evidence.
Read the hubCapital raising and placement networks
Distribution reach, without a shared evidence standard behind it.
Read the hubData providers and research vendors
Excellent data, sold into workflows the vendor does not control.
Read the hubTokenisation and digital asset venues
New rails for ownership, meeting old expectations about evidence.
Read the hubWhat the layer does
Research and decisioning
Read the mandate, apply it to every opportunity, keep the reasoning.
Each tenant holds a written mandate. Opportunities are assessed against that mandate rather than a shared taxonomy, so two users looking at the same asset can receive different reasoning. Every score carries the inputs that produced it.
- Mandate-aware screening on arrival
- Comparable structuring across opportunities
- Reasoning retained with the assessment
- Configurable criteria per tenant
Diligence and evidence
Findings with tiered source attribution, not unattributed summaries.
Document intake produces structured findings, and every claim carries its source and how that source was established: self-reported, verified or triangulated. That is the difference between a summary and something a committee, an auditor or a regulator can work with.
- Structured document intake and extraction
- Tiered source attribution on every claim
- Evidence packs retrievable on request
- Retention rules set per tenant
Transaction and onboarding workflow
Eligibility, onboarding, subscription, allocation and capital events.
The operational steps around a transaction run inside the partner surface: identity and eligibility evidence, subscription and allocation, capital calls and distributions, transfers. Reuben AI does not hold client money and does not settle transactions.
- Investor onboarding and eligibility evidence
- Subscription and allocation workflow
- Capital calls, distributions and transfers
- Evidence captured once and reused
Portfolio and reporting operations
Monitoring, statements and reporting generated from live records.
Positions taken through the partner stay current, and reporting is generated from the same records that fed the decision rather than assembled by hand each period. Packs carry the provenance of the numbers in them.
- Position and portfolio monitoring at network scale
- Investor statements and periodic packs
- Board and committee reporting for distributors
- Reporting output traceable to source records
Coverage underneath all four: 68 native asset classes and 314 sub-asset class overlays across 56 of them. See the full coverage list.
Six ways to deploy it
White label
The full surface runs under the partner brand and domain. Users never see Reuben AI unless the partner chooses to name it.
Best for: Partners whose brand is the reason users trust the platform.
Embedded components
Specific surfaces, such as screening output, an evidence pack or an investor portal, embed inside the partner's existing interface.
Best for: Platforms with a mature interface that need capability, not a new front end.
API
The partner builds its own interface and calls the layer directly for decisioning, evidence, workflow and reporting.
Best for: Product and engineering teams that want full control of the experience.
MCP for partner agents
The partner's own assistants and agents read and act on scoped tenant data through a tool interface with explicit permissions.
Best for: Partners already running agents who need them working on real records.
Referral and co-sell
The partner introduces Reuben AI directly rather than embedding it, with a joint commercial motion.
Best for: Networks testing demand before an integration commitment.
Data exchange
The partner's data feeds the layer and is attributed as the source wherever it supports a finding.
Best for: Data providers and research vendors.
What you keep
- The client relationship. Users sign in through the partner and stay with the partner.
- The brand. The surface carries the partner identity, not ours.
- The pricing relationship. The partner sets what its users pay.
- Data residency. Hosting jurisdiction is chosen per tenant where required.
- Tenant isolation. One partner's data is not pooled into another's workspace.
- The roadmap conversation. Partners shape what gets built for their archetype.
What we are not
- Reuben AI does not hold client money and does not settle transactions.
- Reuben AI is not a licensed administrator, trustee, custodian or registry.
- Reuben AI is not an auditor, law firm, tax agent or investment adviser.
- Reuben AI is not registered with any securities regulator and does not distribute securities.
- Licensing, fiduciary duties and regulatory filings stay with the partner or the fund manager.
Reuben AI is not SOC 2 certified and does not claim to be. See security and data isolation.
Built for the people who have to decide
Chief executive
Distribution businesses defend themselves with relationships. That defence weakens when users have to leave the platform to do the work that matters. Embedding a decision and operations layer keeps the work, the record and the renewal conversation inside your business, without a multi-year build.
Read the caseChief product and technology officer
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.
Read the caseChief operating and risk officer
The governance question about embedded AI is not whether the output is impressive. It is whether you can reconstruct, months later, what informed a decision, who approved it, and where each claim came from. That reconstruction is the design centre of the layer.
Read the casePartnerships 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.
Read the caseHow a partnership starts
- 01
Discovery
A working session on the archetype, the users, the surface the layer would sit behind, and the residency and governance constraints that apply.
- 02
Scoped pilot
One segment, one workflow, one tenant. Enough to prove the capability with real records rather than a demonstration environment.
- 03
Integration
The chosen deployment model is implemented: white label, embedded components, API, MCP or data exchange, with SSO and residency configured.
- 04
Launch and expand
Rollout to the wider user base, then extension into the remaining capability areas as the partner chooses.
Questions partners ask
What does decision and operational infrastructure actually mean?
It means two things running on one data layer. Decision infrastructure reads a mandate, assesses opportunities against it, produces evidence with sources attached and keeps the reasoning. Operational infrastructure runs the workflow that follows: onboarding, eligibility, subscriptions, capital events, monitoring and reporting. Both sit behind the partner's own surface.
Do our users know they are using Reuben AI?
Only if the partner wants them to. In a white-label deployment the surface carries the partner brand and domain. Some partners prefer to name the underlying layer, and that is a partner decision rather than a requirement.
How is one partner's data kept separate from another's?
Each partner, and where required each of that partner's clients, sits in an isolated tenant. Data is not pooled across tenants, and hosting jurisdiction can be selected per tenant.
Does this compete with our existing CRM or system of record?
It does not need to. The layer can read existing records through the API and treat the partner's system as authoritative, adding decisioning, evidence and workflow on top rather than replacing what already works.
How wide is the asset class coverage?
The platform supports 68 native asset classes and 314 sub-asset class overlays across 56 of them, across the major fund jurisdictions. That breadth is what makes one layer viable for partners whose users invest across very different structures.
What does Reuben AI not do?
It does not hold client money, settle transactions, act as a licensed administrator, trustee, custodian or registry, or provide audit, legal, tax or investment advice. Those responsibilities stay with the licensed party.
How does a partnership start?
With a discovery session, then a scoped pilot on one segment and one workflow before any wider integration commitment.
More detail on the infrastructure FAQ, or read the direct platform positioning.