Which investor portal does each fund administrator use?

Why the administrator matters to investors

An investor in many private funds deals with many portals. Often the fund administrator, not the fund manager, decides which one. Knowing the software behind a portal tells you which access channels may exist, such as a partner API, an SFTP feed or email notifications, and what to ask for when you want documents delivered programmatically. The same product can appear under different names: Apex Group, Ocorian and Aztec Group all run portals on eFront Investment Café, for example.

How the data is compiled

Each deployment links an administrator, or a fund, to a portal product, using public sources such as administrator websites, press releases and vendor case studies. Every row carries a confidence level:

• Confirmed: a public source from the administrator, operator or vendor names the software.
• Likely: inferred from indirect evidence, such as trade press, a case study, an acquisition or a shared technical fingerprint.
• Unknown: the portal exists, but its software is not identified yet.

The data is community research and mostly unverified. Names are normalised, so a deployment recorded under a former name, such as Sanne, appears under the current owner. Each administrator page lists the sources.

Funds with a known portal and no administrator recorded

These funds run an investor portal without a fund administrator named in the registry. Each links to the product entry that describes access. 2 further funds have a named portal whose software is not identified yet.

Correct or add a deployment

Know which portal an administrator or fund uses? Email hello@openinvestorportal.com or open a pull request against registry/deployments.json with a public source. Administrators and vendors can correct their own rows the same way.