The Sovereign Stack

The Sovereign Stack separates ingestion (edge adapters), control plane (auth/quotas you scope), and inference (stateless bounded aggregates). Open Portfolio sells the boundary layer that embeds inside your perimeter.

Do not confuse this with Pocket Portfolio’s optional Sovereign Sync (operator-owned Drive file on the consumer harness). Enterprise BYOC pilots scope your approved stores — Drive is one possible customer choice, not Open’s product default.

Deterministic @pocket-portfolio/importer adapters standardize messy broker CSVs at the edge before any model hop. Architecture and Tier-1 design partnership are the diligence path.

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

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