Wealth-tech design partnership
A clean-room design partnership for regulated wealth platforms — reduce audit perimeter by keeping client ledgers inside the buyer’s approved environment, and prove value via a bounded, stateless inference boundary.
Primary outcome
This surface is intentionally dense. It is written for CTO, Security, and Compliance leaders who need to reduce critical third-party scope under EU DORA / GDPR by limiting data custody.
Wealth platforms · IFAs & wealth managers · Aggregators · Enterprise SDK. The program is designed for regulated wealth platforms where institutional trust and audit scope are the gating constraints.
Limited-Scope Processor
A limited-scope processor architecture: broker data parses in-browser, never warehouses server-side, and AI inference runs stateless — minimising the per-user data footprint by design.
PPI-METER/1
Roadmap specification — not asserted as production metering shipped in this repository.
A design partner needs billing, quotas, and governance without expanding audit scope. Target posture: meter capability usage without ingesting partner/customer PII.
PPI-METER/1 Inputs: capability_id, event_type, timestamp, tenant_id, sku_id Constraints: - no raw portfolio payloads - no customer identifiers - no PII fields (name/email/address/account numbers) Output: counters for billing + governance (aggregate only)
Regulatory posture
Target posture: reduce partner oversight + exit-plan complexity by keeping customer data local and limiting third-party processing scope. DORA classification (critical vs non-critical ICT third party) remains a partner risk decision — our architecture is built to keep you on the non-critical side where feasible.
Escalation path
Start at the architecture map, then escalate to a diligence call. Design-partner engagement is verified without collecting portfolio/trade payloads.
