Infrastructure
Partner questions
The questions platforms, networks and administrators ask most often before embedding a decision and operations layer, answered without marketing hedging.
What this section covers
These answers apply to partners embedding the layer. Questions about direct use by a fund manager are answered on the main site.
The boundary, stated once
Reuben AI is a decision and operations layer. It does not hold client money, does not settle transactions, and is not a licensed administrator, trustee, custodian, registry or securities intermediary. Where a step belongs to the partner or to a licensed third party, the layer records and coordinates it rather than performing it. It also holds no certifications it has not earned: it is not SOC 2 certified and will not be presented as such in a procurement process.
Partners ask for that boundary in writing early, because it determines which of their own licences and obligations the arrangement touches. Stating it plainly on a public page is cheaper for both sides than discovering the assumption in legal review.
How to evaluate the layer without a long build
The evaluation that produces a decision is narrow: one user segment, one workflow, real records rather than a demo dataset, and a named person on the partner side who can judge whether behaviour changed. Everything else, including the wider integration and the commercial structure, follows from what that shows.
Questions that are genuinely deployment-specific, such as integration duration and support boundaries, are settled in discovery rather than quoted in advance, because the honest answer depends on the partner's own release process.
- Pick the segment where the current process visibly hurts
- Use real records so the evidence output can be checked
- Fix a review date before starting
- Decide in advance what a changed behaviour would look like
Where the rest of the detail lives
Deployment models and the integration surface are covered on the integration page. Isolation, residency, access control and questionnaire handling are covered on the security and residency page. Commercial structure and end-user pricing are covered on the commercials page. Jurisdictional configuration is covered on the markets page.
Frequently asked
Will our users know they are using Reuben AI?
Only if you want them to. In a white-label deployment the surface carries your brand and domain. Naming the underlying layer is a partner decision.
Do we have to replace our system of record?
No. Your system can stay authoritative while the layer reads and writes through the API.
How is our data separated from other partners' data?
Each partner sits in an isolated tenant, with client-level isolation inside it where required. Data is not pooled across tenants.
Is Reuben AI SOC 2 certified?
No, and we will not say otherwise in a procurement process. We can describe the isolation, residency and access controls that are in place.
Does Reuben AI hold money or settle transactions?
No. It does not hold client money, settle transactions, or act as a licensed administrator, trustee, custodian or registry.
How wide is the asset class coverage?
68 native asset classes and 314 sub-asset class overlays across 56 of them.
Can our own AI agents use it?
Yes, through MCP, with permissions scoped per tenant and every agent action recorded in the same provenance chain as a human action.
How do we start?
A discovery session, then a scoped pilot on one segment and one workflow before any wider integration commitment.