Aevus

Platform

The layer between your agents and your fund’s systems

Aevus turns administrators, banks, ledgers and data rooms into one set of governed actions. Agents get capabilities. Your firm keeps control.

The lifecycle of an action

Six steps, every time, for every agent

  1. 1

    Request

    An agent calls a typed action with an idempotency key.

  2. 2

    Authorize

    The policy engine checks scope, limits and data freshness.

  3. 3

    Compute

    Deterministic services calculate every amount.

  4. 4

    Approve

    Irreversible steps wait for named approvers.

  5. 5

    Execute

    A durable workflow runs it once, or rolls back.

  6. 6

    Record

    An append-only ledger entry captures everything.

Connectors

APIs where systems have them, careful automation where they don’t. Each connector has a health check and stops the moment its source looks wrong.

  • Health-checked
  • Fails closed
  • API or automation

One model of your fund

Funds, LPs, commitments, capital accounts, transactions and documents, resolved across systems so every agent sees the same truth.

  • One source of truth
  • Entity resolution
  • Typed data

Policy engine

Rules are written as code, reviewed like code and checked at the boundary of every action. A prompt can’t talk its way past them.

  • Rules as code
  • Checked on every call
  • Versioned
Policy check: capital call 7Live
  • Agent holds capital-call scope: Done
  • Amount within fund limits: Done$24.8M
  • Source data under 24 hours old: Done3h
  • Two approvers required: Waiting for approvalWaiting for approval

Approval gates

Money movement, filings and LP-facing sends always stop for people. Approvers see the request, the math and the sources on one screen.

  • Named approvers
  • Dual control
  • Full context

Audit ledger

Every action writes an append-only record: who asked, what policy said, how the number was computed, who approved and when.

  • Append-only
  • Every step
  • Exportable

Agent interface

Agents reach Aevus over MCP or a typed REST API with scoped, short-lived tokens. Bring any vendor’s agent or your own; the controls are the same.

  • MCP and REST
  • Scoped tokens
  • Any vendor

Guarantees

What an agent can never do in Aevus

These are enforced by the platform, not by prompts, so they hold even when a model makes a mistake.

See the full security model
  • Calculate, round or “double-check” a financial amount
  • Approve its own request, or skip a gate for convenience
  • Act on data that is stale, unreconciled or unverified
  • Take instructions from documents or emails it reads
  • See another firm’s data, or LP data it isn’t cleared for
  • Touch a source system directly

See Aevus run your workflows

Thirty minutes with our team, on your systems and your process. No slides.