Continuous fund operations
Your fund,
continuously current.
FundOS connects your books, LP records, portfolio data, documents, and workflows so AI agents reconcile, monitor, and prepare fund operations against current data. Your team approves every consequential action.
SOC 2 Type I
Human approval required
Live in production
FundOS operating queue
Monday, 7:43 AM
Recon breakLate corporate action explains the CUSIP mismatchPrime broker file / Portfolio 07
Review
LP reportingQ2 reporting pack ties to the approved NAV runFund III / 46 investor records
Ready
Compliance evidencePerformance claim traced to released booksNAV run 248 / Marketing review
Approved
3 proposals ready for your teamOpen queue
01→
Fundraise and source
LP CRM / DDQ / Deal screening
02→
Execute and close
VDR / Transactions / Pricer
03→
Operate and report
CFO / Risk / HF Ops / K-1s
04
Audit and communicate
Compliance / Evidence / LP reporting
The operating problem
Stop rebuilding the fund every reporting cycle.
The data already exists. It is scattered across the administrator, general ledger, prime broker, CRM, document rooms, inboxes, and spreadsheets. Your team spends its time turning fragments back into a fund.
LP reporting rebuilt from closed books and remembered exceptions.
02Evidence assembled across systems before review can begin.
03One governed context
From fragmented records to current operations.
FundOS connects the systems you already trust, resolves which record wins, and keeps each decision tied to its source. The fund becomes continuously usable, not periodically reconstructed.
Existing sources
Fund administratorQuickBooks / XeroPrime broker / custodianSalesforce / document rooms
●
FundOS operating context
FundOS operating context
Entities, source rules, calculations, obligations, and approvals stay connected.
Canonical entitiesSource priorityFund economicsEvidence lineage
Current outputs
Approved NAVLP reportingRisk exceptionsAudit evidence
Keep your stack
FundOS connects the systems already running your firm.
Goldman SachsMorgan StanleyInteractive BrokersBloombergSalesforceQuickBooksSharePointGoogle Drive
Where teams feel the difference
One operating context across the fund lifecycle.
Start with the work causing the most friction. Every workflow strengthens the same fund record.
Fund accounting and close
NAV, capital accounts, fees, expenses, waterfalls, and vehicle books connected to the underlying records.
Investor operations
Capital calls, distributions, statements, K-1 workflows, side letters, and LP responses from current data.
Portfolio and risk
Positions, covenants, exposure, borrowing bases, reconciliations, and exceptions as information arrives.
Fundraising and LP CRM
Meeting context, DDQs, follow-ups, consultant coverage, and investor materials connected to each relationship.
Deals and transactions
Screening, diligence, term sheets, closing conditions, syndication, and ownership without re-entering the deal.
Compliance and audit
Controls tested against actual books, positions, investor records, and governing documents.
Governed agentic work
Agents prepare. Your team decides.
FundOS agents do more than answer questions. They prepare real work against current fund data and show their reasoning before anything moves.
Sources attached to every proposalHuman approval for consequential actionsPermanent reasoning and decision historyRole and fund-level permissions
Proposal 1842 / Capital call notice
✓
Prepared
Agent assembled the notice from approved commitment and cash requirement records.
✓
Sources checked
LPA, subscription records, approved budget, and investor wiring instructions.
✓
Review complete
Operations lead confirmed amount, due date, and LP population.
●
Ready to issue
Awaiting authorized signatory approval. Nothing has been sent.
Security and trust
Fund-grade controls are part of the operating surface.
FundOS handles LP money, confidential deal flow, and regulated workflows. Access, approvals, evidence, and isolation are designed into the system from the start.
SOC 2 Type I
Independent audit. Report available under NDA.
Role-based access
Roles, scopes, room permissions, and fund-level boundaries.
LP-scoped data
Investors see only their own records, notices, and positions.
Full audit trail
Every agent action, edit, approval, and source is preserved.
Encryption everywhere
Encrypted at rest and in transit, with BYOK on request.
Single-tenant option
Dedicated database and isolated deployment available.
Configured to your fund shape
One operating model does not fit every manager.
FundOS preserves a shared data and control layer while tuning the workflows, calculations, and cadence to your strategy.
Private equity and VC
Pipeline, diligence, portfolio reporting, LP communications, capital activity, and fund close.
Private and structured credit
Borrowing bases, covenant surveillance, waterfalls, lender packs, transactions, and exposure.
Hedge and multi-strategy
Daily recon, NAV packs, breaks, margin, settlements, regulatory reporting, and consolidated vehicles.
Agents and custom workflows
Bring FundOS context to the tools your team already uses.
Connect Claude, Codex, or your own agents through MCP. External agents inherit user scope, propose write-backs for approval, and leave the same audit trail as work prepared inside FundOS.
API
Read and propose
Agents can query current fund context and prepare actions back into the operating queue.
CTRL
Same controls
Permissions, approval gates, and evidence requirements apply across every interface.
Connect through MCPApproval-gated
# Claude claude mcp add --transport sse fundos https://fundos.vantedgeai.com/mcp/sse # Codex codex mcp add fundos --url https://fundos.vantedgeai.com/mcp
Scoped accessHuman approvalAudit logged
✓
Book a 30-minute walkthrough →
Bring one real workflow. Leave with a fit or no-fit answer.
We will map FundOS to your fund structure, source systems, and approval model. No generic tour. A live walkthrough of the operating work your team wants off its plate.