Infrastructure
How the embedded layer works
Your users stay in your surface. Requests pass to the decision and operations layer, which reads the mandate, assesses the opportunity, produces evidence with sources attached and runs the workflow that follows. Everything is written back to one record with provenance retained.
1. Your surface stays the front door
Users sign in through your platform with your identity provider. In a white-label deployment the interface carries your brand and your domain throughout, so nothing about the journey suggests they have left.
Where you would rather keep your own interface, individual surfaces embed as components, or you call the API and render the output yourself.
2. The mandate drives the assessment
Each tenant holds a written mandate: what it invests in, at what stage, in which jurisdictions, under what constraints. Opportunities are assessed against that mandate rather than a shared taxonomy.
This is why two users on the same platform, looking at the same asset, can receive different reasoning. The assessment is theirs, not an average.
3. Evidence is produced with its sources
Documents are read into structured findings, and each claim carries its source and how that source was established: self-reported, verified or triangulated.
The output is intended to survive scrutiny from a committee, an auditor or a regulator, which is a different standard from a readable summary.
4. The workflow runs on the same record
Onboarding, eligibility, subscription, allocation, capital events and reporting run on the records that fed the decision. Evidence collected once is reused rather than re-collected.
Reuben AI does not hold client money and does not settle transactions. Where a settlement or registry step belongs to you or a licensed third party, the layer records and coordinates it rather than performing it.
5. Your system stays authoritative
Where you already have a system of record, it stays the source of truth. The layer reads from it and writes back through the API, so you are adding capability rather than migrating a business.
Frequently asked
Do users have to leave our platform at any point?
Not in a white-label or embedded deployment. The journey stays inside your surface.
What happens to our existing system of record?
It can remain authoritative. The layer reads and writes through the API rather than requiring a migration.
Can different tenants have different rules?
Yes. Mandate, criteria, retention rules and residency are configured per tenant.