Open PortfolioOpen Portfolio.
SOC 2 / BYOCZero-trust architecture matching institutional data boundary controls (SOC 2 posture).

Vendor Lock-In

Proprietary formats and hosted vaults expand switching cost — open ingestion boundaries prevent capture.

Legacy wealth-tech often locks value in a vendor-hosted ledger copy. Leaving means renegotiating data extraction, schema mapping, and AI context — after the warehouse is already the system of record.

Open Portfolio’s substrate is the opposite: MIT OSS adapters (@pocket-portfolio/importer), BYOC store placement, and stateless inference over bounded aggregates. Switching cost stays in your perimeter controls, not our vault.

Pocket Portfolio stress-tests the adapter floor as a consumer harness. Enterprise buyers evaluate Open for embeddable boundary infrastructure — not another portfolio tracker SaaS.

Diligence FAQ

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

How do I evaluate Open Portfolio for an enterprise design partnership?

Tier-1 design partnership targets 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

Vendor Lock-In and the Sovereign Substrate