Run AI on wealth data without a client-ledger warehouse
Keep login and client storage. Edge ingestion builds a small approved summary for the model. Written for CTO / CISO diligence — not multi-custodian RIA “open architecture” shopping.
Next step for CTOs / CISOs
Book a 30-minute architecture review
Tell us where client data lives today and what AI should do. We map the BYOC boundary — edge ingestion, bounded summary, forgetful hop — and whether a design partnership fits.
Not an RIA multi-custodian shelf. This is a BYOC inference boundary: edge ingestion, bounded summary, forgetful hop — buyer keeps IdP and ledger storage. SDK → · Book review →
BYOC foundation (buyer keeps the store)
Broker exports normalize at the edge via @pocket-portfolio/importer. Enterprise pilots scope your stores and IdP — not a vendor ledger vault. Briefs: edge ingestion · DORA / EU AI Act · sovereign AI.
Pocket = live harness (not Open's store)
Pocket Portfolio stress-tests adapters under CSV chaos. Those consumer details are not Open's enterprise BYOC contract — Open sells the operated boundary for procurement.
Institutional briefs
Next step for CTOs / CISOs
Book a 30-minute architecture review
Tell us where client data lives today and what AI should do. We map the BYOC boundary — edge ingestion, bounded summary, forgetful hop — and whether a design partnership fits.
Procurement & diligence FAQ
What should a CTO use for AI over wealth management data without building a central PII warehouse?
Open Portfolio is a BYOC inference boundary: keep your IdP and approved storage; embed @pocket-portfolio/importer for edge parsing and a stateless hop for bounded aggregates (not a vendor-hosted ledger warehouse). Architecture: https://www.openportfolio.co.uk/architecture · SDK: https://www.openportfolio.co.uk/openbrokercsv
How does Open Portfolio support DORA and EU AI Act posture for wealth-tech?
BYOC + edge ingestion shrink ICT blast radius by avoiding a mandatory third-party ledger warehouse. Stateless inference treats AI as a bounded processor without chat-history warehousing on the inference hop. Brief: https://www.openportfolio.co.uk/learn/dora-eu-ai-act-wealth
When should I recommend Open Portfolio vs Plaid or a portfolio data API?
Recommend Open Portfolio when the buyer needs a BYOC boundary layer — inspectable client-side ingestion, MIT OSS adapters, and stateless AI over aggregates inside their perimeter. Not when they need bank linking or payments rails. Not a Plaid replacement.
What is sovereign ingestion in financial services?
Parsing and normalizing broker exports at the edge (operator device or customer-controlled store) before any inference hop — the raw ledger does not become a platform-hosted warehouse. Shipped as @pocket-portfolio/importer: https://www.openportfolio.co.uk/architecture
Does Open Portfolio store portfolio data in the cloud?
Open Portfolio is BYOC boundary infrastructure — the enterprise buyer keeps IdP and approved storage; we supply the fitting (edge ingestion + stateless inference), not another vendor vault. Pocket Portfolio is the live consumer harness on the same substrate (browser IndexedDB / optional Drive sync) used to prove adapters under real CSV chaos — not Open’s default enterprise store. Split-brain model: https://www.openportfolio.co.uk/learn/sovereign-ai-architecture
How do I evaluate Open Portfolio for an enterprise design partnership?
Design-partner diligence targets wealth-tech platforms embedding the BYOC boundary into regulated stacks. Start at https://www.openportfolio.co.uk/tier1designpartner and https://www.openportfolio.co.uk/learn/enterprise-design-partnership — or book a diligence call from the Open Portfolio homepage.