White label, components or API: choosing the integration shape

Partners often treat this as a technical decision and then regret it, because the real question is which asset the platform is defending. A network whose brand carries the trust wants the whole surface under that brand. A platform whose interface is genuinely better than the alternatives wants to keep its interface and add capability inside it. A team whose engineering is its advantage wants the API and no opinions about presentation.

The second consideration is speed against control, and it is a real trade rather than a marketing line. White label is the fastest route to a working product and the least control over presentation. The API is the reverse. Components sit between, and are usually where partners land for the surfaces they would rather not build: a screening result view, an evidence pack, an investor portal.

None of the three changes what the layer does. Mandate is held per tenant, findings carry sources and attribution tiers, workflow runs on the same records, and reporting is generated from those records. The shape decides who renders the output, not what the output is.

Each tenant holds its own mandate, records, documents and decision history. Access is scoped per tenant, and the partner chooses the residency option that matches its own obligations. Nothing is pooled across tenants to produce a shared model of a partner's flow.