KYC providers for private funds: a buyer’s comparison

The first question when comparing KYC providers for private funds is who will work the investor files. Software can collect documents and prepare checks while your team investigates exceptions. A managed service adds people to that workflow. A fund administrator may supply KYC within a much broader engagement. Those proposals need different cost and responsibility checks.

This guide compares AgentKYZ, Fenergo, Flow and Passthrough using their published product, commercial and data-processing information. It is written for fund COOs, compliance officers and administrators buying investor onboarding, periodic reviews or remediation. Jump to the provider comparison, or start with the buying criteria below.

Disclosure and evidence limits: AgentKYZ publishes this guide and is one of the providers compared. Sources were reviewed on 31 October 2026. This is a public-source comparison, not a hands-on benchmark, independent endorsement or exhaustive market survey. Product descriptions are vendor-reported unless identified as contract terms. No comparable quotes or private service-level agreements were obtained. “Not established in the reviewed sources” means ask for evidence, not that a capability is absent.

Choose the service model before the provider

An institutional investor can bring a feeder, nominee, trust or multi-layer company structure. Identity verification alone does not resolve who owns or controls it, which people need screening, why the risk rating is appropriate or who approves an incomplete file. Define the evidence your policy requires before choosing the tool or team.

We focus on KYC providers, rather than ranking fund administrators, because the purchase here is investor due diligence. AgentKYZ’s managed KYC service addresses that work directly. Fenergo, Flow and Passthrough also publish investor or asset-management workflows. Full administration additionally covers work such as accounting, net asset value (NAV) controls and reporting, as illustrated by SS&C’s published administration scope. Use our fund administrator selection guide for that wider decision.

For a reviewer-capacity gap, compare managed delivery. For a team that can investigate and approve cases but needs better tooling, compare software. Our in-house KYC, managed services and AI software guide helps resolve that operating-model choice. If your administrator already does the work and you need evidence of its quality, scope file testing and oversight separately. Replacing an administrator may be unnecessary.

The legal responsibility needs its own answer. For Cayman financial services providers in scope, CIMA FAQs 24–26 retain ultimate responsibility with the provider and its governing body and call for defined roles, escalation, records access and ongoing oversight of outsourced work. Confirm the position for each fund and manager entity; a product description is not legal advice.

Our published comparison criteria

We selected these four providers to examine different delivery models with published relevance to funds or investor KYC. They appear alphabetically, with no scores or overall winner. Apply the same five checks to each proposal:

1. Scope and decision ownership. Who collects documents, traces beneficial ownership, investigates alerts, reviews the file and approves the investor? Which ongoing reviews and monitoring tasks are included?
2. Total cost. Add implementation, licences, data charges, managed review, retained staff time, exceptions, support, renewal and exit costs. Compare the same case population and period.
3. Demonstrated AI capability. A named task and published workflow are a starting point. Require a demonstration on representative cases, source-linked findings and human override records before treating the capability as proven for your fund.
4. Support and escalation evidence. Examine named owners, coverage hours, response and resolution commitments, compliance escalation and references. A support channel or testimonial alone does not establish service quality.
5. Delivery locations and data arrangements. Identify reviewer and support locations, contracting entities, hosting, backups, subprocessors and international transfer mechanisms. Headquarters and the fund’s domicile do not answer these questions.

Record each requirement as documented, demonstrated in your evaluation, or still to confirm, with a dated source. Do not turn missing public information into a negative score. Required jurisdictional coverage, lawful data arrangements and access to records should be appointment conditions, not weaknesses that a lower fee can offset.

Compare four KYC providers

This table summarises the published operating models. The linked profiles explain what the evidence supports and what a buyer still needs to establish.

On narrower screens, scroll the table sideways to compare all columns. Keyboard users can focus the table and use the arrow keys.

AgentKYZ

AgentKYZ is relevant when the purchase is case preparation and human-reviewed KYC file work, including a backlog, periodic reviews or onboarding alongside an existing administrator. Its published software workflow describes document reading, ownership mapping, sanctions, politically exposed person (PEP) and adverse-media screening, and reasoned assessments. Reviewers check the findings, record overrides and escalate high-risk or complex cases to senior compliance. Software-only and hybrid arrangements are also offered.

The managed service quotes a fixed price per case for agreed scope. This is a pricing basis, not a public numerical tariff or evidence of a lower total cost. Ask what makes a case billable, how missing documents affect delivery, and which enhanced due diligence and rework are included. AgentKYZ’s published delivery targets are conditional on scope and evidence availability.

Still to establish: a representative output file, results from your evaluation, named escalation contacts, coverage hours and contractual response times. Hosting, access, retention and transfers are confirmed in the engagement letter; the public service page does not establish the delivery countries for your account. AgentKYZ says client documents are not used to train models. Verify the full processing chain, including inference providers, before file transfer. The engagement leaves investor acceptance and compliance responsibility with your firm and does not replace fund accounting or appoint an MLRO.

Fenergo

Fenergo is relevant to a team evaluating a configurable KYC and client lifecycle platform across connected systems. Its KYC and Transaction Compliance page describes investor risk assessment, ownership and control structures, screening and monitoring of fund activity. It identifies integration with transfer agency, custody and fund systems. That is a wider technology scope than a standalone file-remediation project; establish who operates it and whether any implementation or managed support is separately contracted.

Its Fen-AI / KYRA materials name specific tasks: document classification and extraction, screening-hit assessment, data sourcing and material-change escalation, with human governance and recorded actions. These are concrete vendor descriptions, not independently verified accuracy results. Confirm which capabilities are available in the proposed package rather than assuming every item on an AI page is included.

Still to establish: licence and module fees, configuration and integration effort, data subscriptions, operational staffing and the applicable support agreement. The trust centre provides a useful starting point for hosting-region and support-tool diligence, but it does not itself promise compliance-case turnaround. Ask the proposed implementation and support teams to show a difficult investor case and its full export.

Flow

Flow is relevant when the main requirement is LP document collection and KYC within a broader investor experience. Its KYC/AML page describes data collection, AI-powered identity verification, screening and workflows embedded in fund subscriptions. The FAQ describes Flow as a software provider that does not bundle services, although the same page also promotes SPV administration services. Confirm the model for the specific offering: your proposal should identify who investigates alerts and reviews files, whether that is your team, an administrator or another provider.

Flow publishes a useful pricing basis: an annual platform fee linked to the vehicles’ assets under management (AUM) and the number of unique limited partners (LPs). It does not publish a numerical quote for the workload used in this guide. Ask how repeat investors, additional funds, screening usage and growth affect the fee. Include the cost of reviewers retained outside the platform.

Still to establish: the scope and measured performance of AI identity checks, treatment of layered entity structures, screening-data charges and contractual escalation times. The product page carries a named customer testimonial about responsiveness, which is a reference lead rather than a service-level commitment. Its subprocessor list identifies infrastructure and support providers with US locations; confirm the actual processing and access map for your account.

Passthrough

Passthrough is relevant when subscription documents and investor KYC need to share a workflow, with a choice of self-serve or managed delivery. Its KYC/AML page describes ownership-document collection, identity review, automated screening and nightly screening in the managed service. It says KYC can also be bought standalone. Verify which jurisdictions the managed review covers: configurable document collection alone does not establish that a provider performs every local compliance obligation.

Its Master Subscription Agreement, last updated 26 February 2026, describes KYC components that may be priced individually or together in an order form. Section 8.4 provides a default 7% renewal increase unless the order form provides otherwise or Passthrough gives at least 60 days’ notice of different pricing. Section 8.1.1 offers payment by ACH and specifies a US$1,500 administrative fee if the customer does not submit the ACH authorisation form. Confirm how those provisions apply to your proposal; they do not establish that Passthrough costs more than another provider.

Still to establish: the final service scope and escalation commitments. Section 9 leaves support access methods and times to the order form; obtain the response and resolution commitments separately. The reviewed KYC page documents automation, but does not establish model-level AI capabilities or performance. Do not relabel automated screening as demonstrated AI. The public agreement includes data-processing terms and transfer provisions; reconcile these with the current subprocessor jurisdictions and your signed documents. Section 4 retains investor decisions with the customer, except to the extent Passthrough is expressly engaged as AML compliance officer under an order form.

Compare total cost on the same workload

A per-check price is not comparable to a reviewed entity file or an annual investor platform fee. One corporate investor may require several ownership checks, multiple screenings, document requests and a senior reviewer. A managed quote can include work that a software quote leaves with your team.

Use a shared request for proposal (RFP) population. For example, ask every provider to price 200 new investor files, 300 periodic reviews and 100 remediation files over twelve months, with the same breakdown of individuals, companies, trusts, jurisdictions and evidence gaps. Those numbers are an illustrative buying exercise, not a market benchmark.

For retained reviewer time, use observed hours from the evaluation multiplied by your loaded hourly cost. An illustrative 600-file workload needing 45 minutes per file at US$80 per hour costs US$36,000 in internal review time, before software or data charges. At 15 minutes per file, it costs US$12,000. Neither time estimate is a claim about any provider; the point is to measure the work left with your staff.

Request a steady-state renewal year as well as year one. Test a stress scenario with more complex investors, an overdue backlog or a new feeder. Ask about minimum commitments, unused volume, foreign-exchange exposure, taxes and price increases. Confirm who pays for unsuccessful verifications, repeated screening and files closed with unresolved gaps.

If you need a managed proposal, scope the case population with AgentKYZ. Bring counts, jurisdictions, review type and a target date. No identity documents are needed for the initial quote discussion.

Test AI against the file you need to approve

The reviewed providers describe different things: AgentKYZ describes case preparation and review; Fenergo names document, screening and change-detection agents; Flow identifies AI identity verification; Passthrough describes screening and workflow automation. These descriptions are not interchangeable evidence of end-to-end investor due diligence.

Give each shortlisted provider the same permitted test pack, using synthetic or properly authorised, minimised data. Include a straightforward individual, a layered company with a missing ownership link, a trust, a possible sanctions-name match and a later ownership change. Agree the expected treatment with your compliance team before the demonstration.

Ask the team to show:

• the source behind each extracted fact and ownership link, including where the evidence is insufficient;
• how it distinguishes a possible screening match from a confirmed match, and PEP status from sanctions designation;
• the reviewer’s reasoning, overrides, approvals and escalation of unresolved concerns;
• what changes when new ownership evidence arrives, while preserving the earlier decision;
• an export containing documents, findings, screening rationale and review history.

Measure material errors, missed risk indicators, false alerts, reviewer time and unresolved cases. Keep difficult files in the denominator. A polished demonstration or a small pilot cannot establish a general accuracy rate. Record the product version, configuration and human work involved. Apply the same test to AgentKYZ; an “AI-native” label would not answer any of these questions.

Use the AI KYC vendor due diligence checklist to record evidence requests, evaluation findings and contract conditions for each shortlisted provider.

Check support and compliance escalation separately

Technical support restores access or fixes a workflow. Compliance escalation investigates an ownership gap, risk concern or possible sanctions match. A provider may offer one without taking responsibility for the other.

The public evidence differs. AgentKYZ describes qualified review and senior compliance escalation, with delivery terms agreed per engagement. Passthrough’s agreement specifies that support channels and times sit in the order form. Fenergo’s trust centre lists support-ticketing tools, including a phased move to Intercom. Flow lists Zendesk and publishes a customer account of responsiveness. None of those facts establishes a comparable resolution-time commitment across all four providers.

Before appointment, obtain a named primary contact and deputy, coverage hours and holiday calendar, severity definitions, acknowledgement targets and an escalation route. Separate an initial response from a workaround or final resolution. Establish what happens to the delivery clock when an investor has not supplied evidence, and how overdue cases appear in reporting.

Ask a permitted reference from a similar fund about a missed deadline or difficult case, not just routine onboarding. During the evaluation, test a support request and a compliance exception through the proposed channels. Keep a record of the response and follow-through; do not infer customer care from office count or a sales demo.

Map delivery locations and cross-border data flows

“Offshore” can describe a fund domicile, an analyst location or a hosting arrangement. It is too imprecise to compare providers. Request the countries and legal entities involved in review, quality assurance, technical support and subcontracted work, alongside the location of production data, backups and AI processing.

The reviewed sources establish the following starting points, not complete account-specific data maps:

• AgentKYZ: the managed-service page commits to agreeing hosting, access, retention and transfer arrangements before file transfer. Confirm the actual reviewer and support locations and all model-processing routes. Its published Hong Kong and US office addresses are not evidence of where a particular file will be processed.
• Fenergo: its subprocessor list says customers select an AWS region in the US, Canada, EU, Singapore, UAE or Australia. It separately lists support and security processing. For example, Trustwave’s service logs are stored in the EU while its employees operate from Canada, the US, EU and UK. Choosing a hosting region does not settle every access location.
• Flow: its list identifies AWS, Heroku and Zendesk with US locations, among other providers. Ask whether those entries identify the processing location for your service, where backups sit and which separate entities can access investor records. A list of supplier locations does not prove exclusive US residency.
• Passthrough: its list identifies Google Cloud infrastructure processing in the US and EU, ComplyAdvantage screening in the US, and Kustomer support in the US. Its agreement’s data-processing appendix includes EU standard contractual clauses and a UK addendum. Confirm which provisions and processing routes apply to your engagement; the list does not establish an EU-only service.

For a UK GDPR analysis, the ICO’s international transfers guide uses a three-step test covering applicable processing, who initiates the transfer and a separate receiving organisation outside the UK. Making information remotely accessible can matter even when the server stays in the UK. Restricted transfers need an applicable mechanism; appropriate safeguards also require a transfer risk assessment. Other jurisdictions need their own analysis.

Request a data-flow map, processing agreement, subprocessor-change process, access controls, retention and deletion terms, incident-notification commitments and exit export. For AI, ask separately about model training, inference location, logging, retention and onward access. A no-training commitment does not by itself settle those other questions.

Build a shortlist around the work left to do

If your team needs reviewed files under its policy, include AgentKYZ’s managed service in the evaluation and test the output, escalation and scope. If the purchase centres on subscription documents with optional managed KYC, evaluate Passthrough. If you need an investor platform operated with your own reviewers or service partners, evaluate Flow. If the project needs configurable KYC and transaction monitoring integrated across systems, evaluate Fenergo. These are reasons to investigate fit, not recommendations to appoint without diligence.

If your administrator already performs KYC, first establish whether the gap is delivery capacity or oversight evidence. Shadow KYC separately tests administrator-held files against your fund’s policy. Agree independence and reporting; file testing does not replace the wider independent AML audit. For Cayman funds in scope, CIMA FAQs 42–45 explain the need for fund-specific evidence across the compliance programme. Our AIMA administrator due diligence guide gives further evidence requests for that relationship.

For an AgentKYZ proposal, bring your jurisdictions, investor types and counts, existing systems, review backlog and decision owners. Ask us to show a representative reviewed file and put scope, delivery, data arrangements and price in writing. Explore managed KYC or see the software delivery model before the scoping call.