A relationship model, not a file share
The system knows that this organisation holds this role on this fund with this authority. Access, routing and evidence all follow from that.
Why Regonance
The unautomated part of a fund launch is the part between firms.
Accounting, reporting and portfolio systems are mature, and each one serves a single organisation well. What no one owns is the coordination across organisations — and that is precisely the work that is done by hand today, or billed as a human service.
The wedge
Orchestration is the product.
Fund OS does not compete for the seat of record inside any one firm. It occupies the gap between them: the proposals, acceptances, requests, attestations and approvals that make a fund actually launch.
Bilateral by design
Every engagement is proposed by one side and accepted by the other. Counterparties are isolated from each other; nothing is granted unilaterally.
Coordination as software
Chasing, reconciling and re-sending are treated as an automation target, not as an unavoidable cost of doing fund business.
One lifecycle
Launch and govern are the same record.
Most tooling treats a launch as a project that ends and governance as something that starts fresh. In Fund OS they are continuous: the parties, roles, documents and history established at launch are what you govern against for the life of the fund.
At launch
Structure the fund, engage the AIFM, administrator, depositary and auditor, and move through the launch steps with the evidence attaching as you go.
Afterwards
Run periodic and event-driven workflows — provider changes, director changes, capital events, reporting cycles — against the same parties and the same trail.
Audit trail by design
Evidence created at the moment of the act.
An audit trail assembled after the fact is an argument. A trail written as the work happens is a record. Fund OS is built so the second is the only one you ever need.
Sequenced
Events are ordered as they occurred, so the history reads as a narrative, not a pile.
Attributed
Each action names the person and the organisation, in the role they held at the time.
Durable
Records are appended rather than silently rewritten, and can be exported for review.
Focus
Luxembourg first, deliberately.
Luxembourg concentrates the exact conditions this product is for: a dense provider ecosystem, delegation-heavy structures and documentation expectations that make coordination quality a real constraint. We would rather fit one market precisely than fit several vaguely.
Securitisation vehicles are on the roadmap as a further structure type.
We have not committed to a public date for that, and we would rather say nothing than promise a timeline we cannot hold.
Judge it against your own launch
Bring a structure you are standing up now. We will walk the coordination through Fund OS and you can compare it to how it runs today.