The questions a fiduciary should ask.
Working with centerbeam
An administrator keeps the fund's books. They don't manage your entities, monitor your covenants, or hold the operating data your firm runs on, and their systems are theirs, not yours. centerbeam isn't a replacement for your admin. It's the operating layer they were never meant to be.
centerbeam deploys single-tenant, inside your perimeter. Your data is never pooled with another manager's and never sits in a vendor cloud. If we disappeared tomorrow, it would still be exactly where it is: with you.
Historical positions, entities, transactions, and prior-period records load in after configuration and mapping is completed. Once data is in, it's fully versioned: you can reconstruct any prior state, on any date, exactly as it stood.
Every read and every write passes through a single zero-trust gateway: one chokepoint that gates both authentication and authorization. No direct database access, no side doors. Authorization is resolved per record, per user, at the gateway. Deployment is single-tenant, in your perimeter, never pooled. And every write is versioned in full: SCD2 history, nothing overwritten, every prior state reconstructable and every action attributable.
The AI has no privileged access. It is governed like any other user, and subject to the same zero-trust gateway, the same per-record authorization, the same audit trail. It can see only what the person asking is entitled to see, and it can touch nothing directly. It doesn't write. It doesn't reach around the security model. It composes a query, the deterministic engine executes it, and the answer returns with its provenance - the query, the records, the lineage. And it never produces the number itself. Which means it cannot invent one.
Configuration, not a release cycle. Your entities, fields, relationships, workflows, and reports are all configured, not coded. A new structure, a new lender covenant, a new reporting requirement is a change you make in hours. And you don't need to wait on us to get it done.
centerbeam isn't built around a fixed schema for one strategy. The data model is yours to define. Real estate, private credit, buyout, multi-strategy: the entities, positions, and relationships are configured to how you actually operate, not forced into someone else's template.
Every action is attributable - versioned, logged, tied to who did what, when, and to which record. Nothing happens in the dark. That’s the point of a single gated path: there is always an answer to “how did this number come to be,” and it’s a record, not a reconstruction. Accountability isn’t a policy layered on top. It’s a property of how the system is built.
centerbeam doesn't compete with your stack. It unifies it. The cost was never in any single system, but in the seams between them. Your systems each solved one problem and created a new one at every handoff. centerbeam doesn't add another handoff - it's the layer they all resolve into, so there's nothing left to reconcile.