eFront vs Intralinks FundCentre: API, MCP and investor access compared

Key differences

• API. eFront: partner only (for GP and fund administrator users). Intralinks FundCentre: partner only (REST, API key, for GP, fund administrator and partner users).
• Capabilities. Listed for eFront only: Capital account statements; listed for Intralinks FundCentre only: Tax documents and KYC.
• Export formats. EFront lists: PDF and XLSX; none recorded for Intralinks FundCentre.
• Asset classes. Listed for eFront only: Infrastructure; listed for Intralinks FundCentre only: Hedge funds.
• Standards. Intralinks FundCentre lists: ILPA reporting template; none recorded for eFront.
• Automation in the terms. Recorded as unknown for eFront and prohibited for Intralinks FundCentre.
• Known deployments. The registry links 4 known deployments to eFront and 1 to Intralinks FundCentre. This counts what the community has documented, not market share.

What the entries have in common

• Email notifications: both are recorded as available.
• Neither entry documents an MCP server, SFTP or webhooks.
• Investor-side API: unknown for both, according to the assessment.
• Difficulty: both are rated 4 of 5 (web login only, exports possible).
• Regions: both list Global, Europe and North America.

Which fits which need

Neither product is right for every team. The statements below are conditional and come straight from the registry fields above.

For investors and LP operations teams

• If your investors or your operations team need documents and data through an API, the registry records the API as partner only (aimed at GP and fund administrator users) for eFront and partner only (aimed at GP, fund administrator and partner users) for Intralinks FundCentre. Access for the investor itself is recorded as unknown for both.
• If you want to reach the data from an AI assistant, the MCP server is not documented for either.
• If you process capital call and distribution notices from your inbox, email notifications are available for both.
• If you load files into your own systems, the registry lists PDF and XLSX for eFront and no export formats for Intralinks FundCentre.
• If you plan to automate your own login, automation in the terms is unknown for eFront and prohibited for Intralinks FundCentre. Where it is prohibited or unknown, ask the GP or the vendor for a sanctioned channel first.

For GPs, fund administrators and buyers

• If you need to connect the product to your back office, both entries record API partner only, webhooks not documented and SFTP not documented.
• If the product must carry the core LP reporting items (capital calls, distributions, capital account statements and tax documents), the structured capabilities cover capital calls, distributions and capital account statements for eFront and capital calls, distributions and tax documents for Intralinks FundCentre.
• If your investors are concentrated in particular markets, the regions recorded are Global, Europe and North America for eFront and Global, North America and Europe for Intralinks FundCentre.
• If you manage a specific strategy, the asset classes recorded are private equity, private credit, real estate, infrastructure and fund of funds for eFront and private equity, hedge funds, private credit, real estate and fund of funds for Intralinks FundCentre.
• If you want to see who already runs each product, the registry documents 4 known deployments for eFront and 1 for Intralinks FundCentre. The portal pages name the operators.
• If your investors will want programmatic access later, the difficulty rating is 4 of 5 for both, where 1 is a documented self-serve API an investor can use and 5 is web login only with MFA.

For a structured shortlist beyond these two products, see the guide how to choose an investor portal.

What the research says

eFront Investment Café

Assessment. Hosted web portal per GP or administrator. API is back-office integration for GPs. No public docs, no MCP.

Research notes. BlackRock-owned since 2019. Widely used by European GPs and administrators, including Aztec Group for its investor reporting portal. 56m+ documents shared with investors per vendor. No LP-side programmatic access identified. See registry/deployments.json for known deployments.

• Web: Hosted browser portal, deployed per GP or administrator, so investors meet many separate instances. SSO and MFA not stated.
• API: Press material cites API capabilities for sync with the eFront back office. No public docs. Also distributed by Apex Group.

Sources: www.efront.com/alternative-investment-software/efront-investment-cafe/ · www.apexgroup.com/technology-platforms/investor-portal/

SS&C Intralinks FundCentre

Assessment. GP-side API behind engagement. LP side is web login. Terms prohibit bots and API-key sharing.

Research notes. The LP portal product of SS&C Intralinks (the deal data room is a separate product). ILPA templates built in. Carta LP Portfolio Analytics documents vendor-arranged API access to Intralinks for automated retrieval.

• Web: One Intralinks login across GPs (170k+ individuals). SSO via professional services. Link AI assistant answers LP questions over approved documents.
• API: Library of APIs with Swagger docs behind engagement. Keys are customer-specific and may not be shared.
• Email: LPs notified on publication.
• Terms: Terms prohibit bots, spiders, automated retrieval causing excessive usage, and sharing API keys or User IDs.

Sources: www.intralinks.com/products/fundcentre/reporting · www.intralinks.com/why-intralinks/apis-deployment · www.intralinks.com/terms-of-use

Frequently asked questions