Questions funds actually ask us.

CapHive runs closed-end and evergreen vehicles, SPVs and co-investment structures, with multi-entity master–feeder arrangements handled in one ledger. The platform is used today across Indian AIF structures and US fund structures, including the fee, hurdle and waterfall mechanics each requires.

Whether your specific structure is supported out of the box or needs configuration is a question we answer in discovery, not in a marketing page. See Funds for the accounting layer, or ask us directly.

One module is a normal way to start. Firms commonly begin with Funds for onboarding and capital events, or with Portfolios when reporting is the immediate pain, and add the rest later.

Because the modules share one underlying record, adding a second one is configuration rather than a second migration.

CapHive fits three ways, and funds pick the one that matches where they are. Some insource fund administration onto the platform outright. Others keep their existing administrator and run shadow books on CapHive — or just use the modules they need, like Portfolios or Investor Relations — while the administrator continues; shadow books are reconciled continuously, which usually makes the relationship easier rather than redundant. And some go for an integrated approach: CapHive plus one of our partner fund administrators, or CapHive plus their existing administrator, who we help train on the platform.

The mechanics are on the Funds page.

Yes. Multi-currency and multi-entity ledgers are computed in a single close, with translation and dual-ledger reporting — EUR and USD in one cycle is a pattern we run today.

Entity hierarchies, feeders and blockers roll up to fund-level and investor-level numbers without a consolidation spreadsheet sitting in between.

Yes. Each investor gets a portal with their capital account, statements, notices and tax documents, scoped so they see only their own positions.

You control what is published and when, so nothing reaches an LP before you have reviewed it. Onboarding through the same portal has taken firms from three weeks to two days.

Yes. Administrators, auditors and outsourced finance teams get their own role-scoped access, with every action written to the audit log.

Administrators can also work through file exchange or the API instead of the interface — see Data & Integrations.

Weeks, not quarters. A single fund with clean records and one module moves fastest; several vintages, multiple entities and a full historic migration take longer.

We give you a sequence and an effort estimate in writing after discovery, so the timeline is yours to hold us to rather than ours to promise.

Migration is our work, not yours. You hand over the spreadsheets, statements and documents you already have; we load commitments, capital events, valuations and investor records, and reconcile the result back to your last audited close.

Anything that does not tie out is raised as a question rather than quietly adjusted.

One close, computed both ways. Your existing process and CapHive produce the same period's NAV, capital accounts and waterfall side by side, and we resolve every difference until they agree to the last decimal.

Only after that do you stop running the old process. It is the step that makes going live uneventful.

Three things: answer structure and fee-term questions in discovery, hand over the historic records you hold, and review the parallel-run comparison. That is where your time goes.

Data entry, template building and reconciliation sit with us. If your records are held by an administrator, we work with them directly.

Common, and workable. We migrate from the last point the records are reliable, carry forward opening balances, and flag the gaps rather than inventing numbers to fill them.

Where a prior period cannot be reconstructed, it stays documented as an opening position, which auditors generally prefer to a reconstructed guess.

Only the data the user asking already has permission to see. Agents run inside the same permission model and audit log as the interface, so an agent cannot surface a fund, entity or investor that the user could not open themselves.

Every agent action is logged with the user, the prompt and the records touched. See AI Agents for what each one does.

Our intent is that client fund data is not used to train third-party models, and that this is written into the contract rather than left to a policy page. Confirm the current wording with us before you rely on it.

The controls, sub-processors and data-flow detail belong on Security & Trust and in the diligence pack we will send you.

Hosting region and data-residency options depend on your jurisdiction and are confirmed in writing during diligence — India and US options are the ones we are asked about most.

Encryption is applied in transit and at rest. The current posture is documented on Security & Trust.

Yes. SSO / OAuth is supported, along with role-based permissions and full audit logging of every user action.

If your firm enforces MFA or conditional access at the identity provider, those controls carry through to CapHive. Details on Security & Trust.

You do. Your fund, investor and portfolio data remains yours throughout, and you can export it — structured records and stored documents — at any point during the engagement, not only at the end.

Exports are available through the interface and the API. See Data & Integrations.

Yes. The API covers funds, investors, capital events, portfolio positions and documents, so CapHive can feed your data warehouse or receive data from systems you already run.

Bank, custodian, ERP and e-sign connections are covered on Data & Integrations.

Pricing is quoted per engagement. The drivers are which modules you take, how many funds and entities you run, how many investors sit on the platform, and how much historic migration is involved.

We do not publish a rate card because a single-fund manager and a multi-vintage platform are not the same engagement. Pricing sets out what goes into a quote.

Investor count is one of the inputs to a quote, so a fund with 4,000 investors is priced differently from one with 40. Whether that appears as a per-investor line or is absorbed into the platform fee depends on how the engagement is structured.

Ask for the breakdown and we will show which component moves when your investor base grows. See Pricing.

Annual terms are the norm, with multi-year options where a larger migration is involved. Migration and implementation are scoped separately from the recurring platform fee, so you can see what is one-off and what is ongoing.

Notice periods and renewal mechanics are in the agreement — read them alongside our Terms of Service.

Every engagement includes a named point of contact who knows your structures, onboarding and training for your team, and support on a shared channel rather than a ticket queue you shout into.

Stated support hours and response-time targets are set out in the agreement. Ask us for the current commitment.

You leave with your data. On exit we provide a full structured export of fund, investor, portfolio and transaction records, plus the stored documents, in formats your next system or administrator can load.

We will also work directly with the incoming provider during the handover. Retention and deletion after exit follow the agreement and our Privacy Policy.