Infrastructure
Integration options
Six models, from a referral motion with no engineering work through to a full white-label deployment on your own domain. The right one depends on how much of the experience you want to own and how much engineering capacity you can commit.
White label
The full surface runs under your brand and domain with your identity provider. Users do not see Reuben AI unless you choose to name it. Best where your brand is the reason users trust the platform.
Embedded components
Specific surfaces embed inside your existing interface: screening output, an evidence pack, an investor portal, a reporting view. Best where you have a mature interface and need capability rather than a new front end.
API
You build the interface and call the layer for decisioning, evidence, workflow and reporting. Event subscription reports status changes so you are not polling for them.
MCP for partner agents
Your own assistants and agents read and act on scoped tenant data through a tool interface with explicit permissions. Agent actions are recorded in the same provenance chain as human actions.
- Permissions scoped per tenant
- Actions recorded with their trigger
- No screen scraping and no shared credentials
Referral and co-sell
Introduce Reuben AI directly rather than embedding it, with a joint commercial motion. A reasonable way to test demand before committing engineering time.
Data exchange
Your data feeds the layer and is attributed as the source wherever it supports a finding, which puts your brand in front of users at the point a decision is being made.
Frequently asked
How long does an integration take?
It depends on the deployment model and your own release process, so we set a schedule during discovery rather than quoting one in advance.
Can we run more than one model at once?
Yes. A white-label surface for one user segment and an API integration for another is a common shape.
Do you support single sign-on?
Yes, against your existing identity provider.