Reuben AI

    Infrastructure

    What partners embed

    Four capability areas on one record: research and decisioning, diligence and evidence, transaction and onboarding workflow, and portfolio and reporting operations. Partners typically start with one and widen from there.

    Research and decisioning

    Mandate-aware screening on arrival, comparable structuring across opportunities, and reasoning retained alongside every score. Criteria are configurable per tenant rather than fixed for the platform.

    Diligence and evidence

    Structured document intake, findings with tiered source attribution, and evidence packs that can be retrieved long after the decision. Retention rules are set per tenant to match the obligations that apply.

    Transaction and onboarding workflow

    Investor onboarding and eligibility evidence, subscription and allocation, capital calls, distributions and transfers. Reuben AI does not hold client money and does not settle transactions.

    Portfolio and reporting operations

    Position monitoring at network scale, investor statements, periodic packs and committee reporting, generated from live records rather than assembled by hand each period.

    Coverage underneath all four

    The platform supports 68 native asset classes and 314 sub-asset class overlays across 56 of them, across the major fund jurisdictions. For a distribution partner whose users invest across very different structures, that breadth is what makes one layer viable instead of a series of point integrations.

    Frequently asked

    Can we embed one capability rather than all four?

    Yes, and most partnerships start that way. The capabilities share one record, so adding another later does not require re-integration.

    Are the capabilities configurable per tenant?

    Yes. Mandate, criteria, retention and access rules are set per tenant.

    Which asset classes are supported?

    68 native asset classes and 314 sub-asset class overlays across 56 of them. The full list is published on the coverage page.

    Each capability, by market

    How each capability lands for platforms operating in a specific market, including local structures, language and residency expectations.

    Evaluating an embedded layer

    Start a partner conversation