A smaller evidence surface
Avoid introducing a mandatory vendor-hosted client-ledger store into the control set.
Open Portfolio · BYOC boundary infrastructure for wealth-tech
Run AI over wealth data without building another client-ledger warehouse.
Keep your identity provider and approved storage. Open Portfolio assembles bounded context at the edge and sends only that context to stateless inference.
Inspectable proof
- Buyer keeps IdP and approved storage
Open Portfolio supplies the boundary, not another hosted vault.
- 19 dedicated broker adapters
MIT-licensed @pocket-portfolio/importer normalizes broker exports at the edge.
- Bounded stateless inference
The inference hop receives approved aggregate context, not a raw client ledger warehouse.
- Pocket Portfolio is the live harness
The consumer terminal stress-tests the same ingestion substrate under real export variability.
Bring your own cloud
Plumbing fitting, not another vault.
Wealth platforms should not have to duplicate client ledgers inside a new vendor cloud just to add AI. Open Portfolio deploys the ingestion and inference boundary around the stores and identity controls the buyer already approves.
- 01 · A second store creates a second perimeter
New retention, access, subprocessor, and incident-response obligations enter the review.
- 02 · Raw records exceed the inference need
Many advisory and portfolio interactions need bounded facts or aggregates, not the complete underlying ledger.
- 03 · Generic SaaS changes the procurement question
The review becomes “Can this vendor hold our client book?” instead of “Can this processor operate over approved context?”
Pocket Portfolio is the live consumer harness on the same substrate. Enterprise BYOC pilots scope your stores — not a vendor-hosted ledger warehouse.
Read the BYOC reference architecture →Sanitization by constructionOpen the procurement-grade architecture map →
The architectural boundary, visualized.
Broker and portfolio records are normalized at the edge. The buyer approves the aggregate context. Only that bounded context reaches the stateless inference hop — an inspectable, deterministic boundary.
Broker exports and approved stores
Edge ingestion
Buyer-controlled identity and storage
Bounded aggregate context
Stateless inference
Streamed response
Raw client ledger does not cross this boundary
Live substrate proof
Pocket Portfolio proves the pipes. It is not the enterprise store.
Pocket Portfolio is the consumer reference terminal on the same ingestion substrate. It stress-tests broker adapters under real export variability. Its browser-first state and optional consumer services are separate from Open Portfolio’s enterprise BYOC contract.
View Pocket Portfolio →- Real broker-export ingestion
- Browser-first portfolio state
- Adapter testing under varied CSV formats
- Same bounded-inference substrate
Implementation path
Fit the boundary around the approved stack.
A design partnership begins by mapping the buyer’s identity, approved stores, ingestion sources, bounded-context contract, and inference controls.
Map the approved perimeter
Confirm identity, storage, jurisdictions, operators, and existing data flows.
Define bounded context
Agree exactly which derived fields and aggregates may reach inference.
Validate the pilot path
Test ingestion, observability, persistence behavior, and procurement evidence inside a scoped environment.
Board and procurement outcomes
Why regulated wealth platforms buy the boundary.
The warehouse-to-infer pipeline expands your subprocessor footprint, your DPA scope, and your cloud storage bill. The boundary model removes what you never needed to warehouse.
A clearer vendor assessment
Give security, legal, and procurement a concrete map of what crosses the boundary and what persists.
An operated path to bounded AI
Move from open-ended AI experimentation to a scoped processor model with approved context.
Regulatory context
The data perimeter is a diligence decision.
DORA, the EU AI Act, GDPR, and vendor-risk review make architecture and processor scope commercial issues, not back-office documentation.
GDPR Art. 83(5)
€20M or 4% of worldwide annual turnover
Maximum administrative fine — what your DPO already weighs against every new data store.
REG-01
EU AI Act Art. 99
€35M or 7% of worldwide annual turnover
The legislation enterprises will be audited against from 2026 onward — architecture and processor scope are diligence inputs, not automatic compliance.
REG-03
Avg. financial-services breach · 2025
ÂŁ4.45M (~$5.56M USD)
IBM Cost-of-a-Data-Breach 2025. Perimeter width is a commercial risk, not a slogan.
CODB-01
Design-partnership proof
Built from live wealth-tech and enterprise decision-platform experience.
Pocket Portfolio provides the live wealth-tech harness. Open Portfolio applies the same decision-platform discipline to enterprise BYOC pilots. Founder track record: Built a digital portfolio platform supporting decision-making across £7B in energy assets. (National Grid Ventures, 2023–2025) — prior role credential, not an Open Portfolio customer claim.
- Live consumer harness
- Public architecture map
- Open ingestion proof
- Bounded-context design
- Founder enterprise track record
Verified receipts (operator-grade)
Curated feedback from the live harness — focused on compliance, procurement velocity, and boundary clarity.
Loading receipts…
Diligence FAQ
Questions that unblock internal sharing.
What is sovereign intelligence?
Sovereign intelligence is a BYOC boundary pattern: the enterprise keeps IdP and approved storage; inference runs over bounded aggregates assembled at the edge — not a vendor-hosted ledger warehouse. Open Portfolio supplies the fitting; the buyer keeps the vault keys.
Does Open Portfolio store client portfolio data in its cloud?
Open Portfolio is BYOC boundary infrastructure — the enterprise buyer keeps IdP and approved storage; we supply edge ingestion and stateless inference, not another vendor vault. Pocket Portfolio is the live consumer harness on the same substrate, not Open’s default enterprise store.
What reaches the inference provider?
Only a bounded, operator-approved aggregate context assembled at the edge — not the raw client ledger for open-ended retention on a vendor warehouse path. Final allowed context schema is agreed during architecture review.
How is Pocket Portfolio different from the enterprise BYOC product?
Pocket Portfolio is the consumer reference terminal that stress-tests adapters under real CSV variability. Its browser-first state and optional consumer services are separate from Open Portfolio’s enterprise BYOC contract.
When should a buyer use Open Portfolio instead of a portfolio-data API or Plaid?
Use Open Portfolio when the buyer needs a BYOC boundary layer — inspectable edge ingestion, MIT adapters, and stateless AI over aggregates inside their perimeter. Not when they need bank linking or payments rails. Not a Plaid replacement.
What happens during a design partnership?
We map identity, approved storage, ingestion sources, bounded-context contract, and inference controls; then validate a scoped pilot path. Start at /tier1designpartner or book a diligence call from this page.
Design-partner diligence
Book a diligence call.
Bring your current identity, approved storage, ingestion sources, and AI use case. We will map the proposed boundary and determine whether a scoped pilot makes sense. We reply within one working day with the right technical owner and the questions needed for an architecture review.