Home
Who We Serve
About Contact Setup a Demo
Platform

One platform. Every workflow in private markets.

Capital flows in from LPs, through funds, into portfolios — and back out through exits, secondaries and distributions. CapHive runs that whole lifecycle on one record, so the commitment you accept at onboarding is the same number the LP statement prints.

US$ 10bn+AUM administered
US$ 500m+capital raised & secondaries executed
4,000+investors managed
1,000+sellers & investors in transactions
The lifecycle

Follow the capital, not the feature list.

Most platforms are organised around what they do. A fund is organised around where its money is. These are the five places capital sits, and CapHive holds the record at each of them.

Every one of those five states is the same object seen at a different moment. That is the advantage of one platform — a number never has to be retyped between them.

Modules

Five modules, one ledger.

They are not separate products. They read and write the same record, so a commitment, a valuation and a transfer are one dataset seen from different angles.

One record

The same fund, three different rooms.

A GP, an investor and an administrator want different things from the same underlying data. On the same platform, there are tailored views and permissions, not three exports.

GP view

Run the fund

Everything that needs a decision – Capital events waiting to be issued, positions off plan, approvals sitting with you etc.

  • NAV, DPI and TVPI as of today, not as of the last close
  • Capital events in flight, with reconciliation status per LP
  • Portfolio companies flagged against plan
  • Approvals and signatures awaiting you
Investor view

See your own position

Investors get their capital account, their documents and their history — scoped to them, with no spreadsheet emailed anywhere.

  • Capital account: committed, called, distributed, remaining
  • Every notice and statement, versioned and dated
  • Tax and KYC documents in one place
  • Access scoped so an investor sees only their own record
Administrator view

Close the books

Whether the close is run in-house or by an administrator, both sides work on the same ledger instead of exchanging files and reconciling afterwards.

  • Shadow books alongside the administrator, reconciled continuously
  • Fee, expense and carry schedules computed rather than maintained
  • Multi-currency and multi-entity ledgers in a single close
  • An audit trail that answers "why did this change?" without archaeology
What changes

Stitched point solutions leak.

A fund admin tool, a portfolio tracker, a data room and a spreadsheet for the waterfall can each be good software. The gaps between them are where the errors live.

WorkflowWhere it usually livesOn CapHive
Investor onboardingEmail threads and a KYC folderOne link, a live checklist, e-signed pack
Capital callsMail-merged notices, manual bank matchingComputed per LP, issued, reconciled as money lands
WaterfallA spreadsheet one person ownsA computation the system performs
Capital accountsRebuilt each quarterCurrent every day, statements on demand
Company reportingProse in email, inconsistent formatsTemplated request cycles, comparable fields
Valuations and NAVSet weeks after quarter endMarked as data arrives
SecondariesForty email threads and a signature chaseOne coordinated flow, register updated on close
Audit trailReconstructed from inboxesRecorded on the object itself

One record, no rekeying

A commitment entered at onboarding is the same commitment the drawdown calls, the capital account carries and the LP statement prints.

Every action audited

Who changed a valuation, who approved a transfer, who sent which notice and when — recorded on the object, not reconstructed from an inbox.

Numbers current daily

Computations run as events land, so the quarterly close becomes a review rather than a rebuild.

In and out

What feeds it, and what comes out.

A system of record earns its name at the edges: what it can ingest without a person retyping, and what it can produce without a person assembling.

Data in

Arrives on its own

Direct connections where a system has APIs, structured file ingestion where it does not, and an API plus webhooks for everything else.

  • KYC, identity and e-signature providers
  • Accounting and ERP systems
  • Portfolio company templates and document capture
Data out

Generated, not assembled

Because reports read the ledger rather than a copy of it, producing one is a render step — and it agrees with the last one you sent.

  • Investor statements and capital accounts
  • Quarterly LP packs, per investor, branded and versioned
  • NAV bridges, waterfall workings and fee schedules
  • Exports and API access for your own warehouse
AI Agents

Agents that work inside the ledger.

Because the whole lifecycle sits on one record, an agent can answer across it — a fund's DPI after the March distribution, a portfolio company's variance to plan, the open items on a compliance checklist. Same permissions as your team, every action logged.

Implementation

Live on your funds in weeks.

Migration is our work, not yours. We take the spreadsheets and documents you already have and reconcile the platform back to your last audited close.

Discovery

We map your fund structures, fee terms, waterfall mechanics and reporting calendar.

Migration

Historic commitments, capital events and investor records are loaded and reconciled.

Parallel run

One close computed both ways, side by side, until the numbers agree to the last decimal.

Go live

Your team runs capital events and reporting on CapHive, with support on the same channel.

Before you ask

The five questions everyone asks.

Do we have to take the whole platform?

No. Most funds start with Funds or Portfolios and add the rest as they need it. The modules share one record, so adding a second one later is a configuration step rather than a second migration — but nothing forces you to buy the set. See how pricing works.

Does CapHive replace our fund administrator?

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.

What happens to our history?

It comes with you. Historic commitments, capital events, positions and documents are migrated and then reconciled against your last audited close — that reconciliation is our work, and nothing goes live on a difference nobody can explain.

Who owns the data?

You do. It is exportable on demand, and there is an API if you want it flowing into your own warehouse. Security & Trust sets out the controls around it.

How long until we are live?

Weeks rather than quarters for a single fund, longer for a multi-entity, multi-currency family of vehicles. The honest answer depends on how clean your history is and how complex the waterfall terms are, which is what the discovery step establishes.

SOC 2 Type II
AES-256 at rest · TLS 1.3 in transit
ISO 27001:2022
SSO / OAuth & full audit logs
Where next

Pick the thread you care about.

See CapHive on your own fund data.

Book a walkthrough with our team — funds, portfolios, deals & secondaries, end to end.

or write to hello@CapHive.com