Everything the unified interface gives you, with nothing to run. We operate a dedicated vault for your portal keys and second factors, keep every link alive, and deliver your documents, capital calls and capital account statements to wherever your team works.
What is included
A managed vault replaces the client software, the key handling, the second-factor juggling and the morning portal rounds.
Your investor key is generated inside a hardware security module in an environment provisioned for you alone. It is non-exportable: it can sign, it cannot leave. Every signature is logged with the request it authorised. When you leave, the key material is destroyed and we hand you the destruction record.
Portals that still require one-time codes are linked with dedicated authenticator seeds held in the same vault. Where a portal only offers SMS, you get a dedicated number used for nothing else. Codes are consumed by the delivery pipeline and never shown to staff. Email-based codes are routed to a mailbox that exists only for your vault.
New documents, capital call notices, distribution notices and statements are collected from every linked portal and delivered to your SFTP server, SharePoint or Google Drive, your document management system, a mailbox, or our API. Normalised to the ILPA templates, filed by entity, fund and document type, with a daily reconciliation report.
A person on our side who knows your portfolio, re-links portals when a GP migrates to a new platform, chases missing statements, and answers within the business day. For portals that offer no programmatic access at all, that same team collects documents manually under a limited power of attorney you grant us.
Two ways to use the standard
Same protocol, same registry, same document formats. The difference is who holds the keys and who does the work.
| Self-managed, open | Managed Portal Vault | |
|---|---|---|
| Price | Free, open source | Per legal entity per month, plus a per-portal fee |
| Where the key lives | Your device keychain or your own KMS | A hardware security module in a vault dedicated to you |
| Who signs requests | You | Your vault, on a schedule you set, every signature logged |
| Second factors | You, on your phone | Dedicated authenticator seeds and numbers inside the vault |
| Data path | Peer to peer, we never see it | Through your vault, encrypted at rest under your vault key, deleted after delivery unless you ask us to retain |
| Portals without an API | Local read-only connector on your machine | Vault-side connector, or manual collection by our team under power of attorney |
| Delivery | Your own tooling or MCP client | SFTP, SharePoint, Drive, DMS, email, API |
| Support | Community | Named contact, business-day response |
| Leaving | Delete your key | Key destroyed, destruction record and full export handed over |
Security and compliance
Each vault is its own environment with its own key hierarchy, its own network identity and its own logs. A fault or a breach in one vault cannot reach another.
Signing keys and authenticator seeds are created in the hardware module and never exist in plaintext outside it. Our staff cannot read them, export them or copy them to another vault.
Vault links are scoped to reading documents and statements. No vault can acknowledge a capital call, sign a document or change a bank instruction on your behalf.
Each login, signature, download and delivery is written to an append-only log you can export at any time or stream to your own SIEM. Staff access to a vault requires a ticket and is itself logged.
EU data residency, contractual audit rights, incident notification and exit assistance are part of the standard agreement, written to fit the ICT third-party requirements that insurers, pension funds and banks have to meet under DORA.
We link portals through OIPP where it exists, through sanctioned APIs where offered, and through consented automation only where the portal's terms allow it. Where they do not, our team collects documents manually. We never circumvent a portal's protections.
Onboarding
Service agreement, data processing terms and verification of the legal entities you want us to act for.
We list every portal across your positions from the registry and your subscription documents, and agree a delivery schedule and destination.
Your vault is provisioned. On a call with you, each portal is linked to the vault key, or a limited power of attorney is set up for portals without programmatic access.
Documents begin to arrive in your destination within the first cycle. You receive the first reconciliation report and your operations contact.
Questions we get
Yes. In a managed vault documents pass through infrastructure we operate. They are encrypted at rest under your vault key, deleted after delivery unless you ask us to retain them, and staff cannot open a vault without a logged ticket. If that is not acceptable, the self-managed standard is the right choice and it is free.
Investor keys are non-exportable by design, so no. On exit we generate a new key under your control, re-link your portals to it, and destroy the vault key with a signed destruction record. Nothing about your portal accounts changes.
Family offices, fund-of-funds teams, insurers and pension funds, and fund administrators who want programmatic access to every portal without running software or managing keys. If you have an engineering team, start with the open standard.
We do not automate them. Our operations team collects documents manually under a limited power of attorney, on the same schedule, into the same delivery. The registry marks these portals so you know which ones they are.
In the European Union. Other regions are available on request for clients with residency requirements elsewhere.