Fragmented by default
Each party has its own portal, template set and file store. The only thing that spans them is an email thread, and the thread is not a record.
Built for Luxembourg fund operations
The operating system for launching and governing Luxembourg funds.
Fund OS coordinates the entire fund lifecycle across every party — management company or AIFM, fund administrator, depositary and auditor — on one shared, audit-ready system, instead of scattered email, spreadsheets and provider portals.
Private beta · EU-hosted · Software for regulated firms — Regonance is not a regulated entity.
The problem
A fund launch is a multi-organisation project run on single-organisation tools.
Standing up a Luxembourg fund means moving documents, approvals and confirmations between four or more firms that share no system. The coordination is real work — and today it is done by hand, reconstructed after the fact, and often billed as a human service.
Manual and repetitive
The same fund facts are re-keyed into different forms by different firms, and every chase, reminder and re-send is somebody's morning.
Slow where it hurts
Launch timelines slip on waiting, not on work — an unanswered request, an unsigned attestation, a provider who was never formally engaged.
Hard to evidence
When the file is reviewed, the history has to be rebuilt from mailboxes and shared drives — with no single answer to who did what, when, and on whose authority.
The solution
One shared system, and one coordination loop that closes.
Fund OS models the thing the tools miss: the relationship between organisations. Who is engaged, in which role, on which fund, with what authority — and what each of them did about it.
Every party on the same fund
Operators and providers work on the same underlying record from their own organisation's view. No re-keying, no divergent copies, no "which version is current".
Each party sees only its own scope
A provider is engaged on a specific fund in a specific role and sees exactly that. Counterparties are isolated from one another by design.
The record writes itself
Every engagement, request, upload, attestation and approval is captured as it happens, in sequence, attributable to a named person at a named firm.
How it works
Launch, engage, coordinate, evidence.
Four movements — the same four every Luxembourg launch goes through, with the manual coordination taken out of the middle.
- STEP 01
Launch
Set the fund up once — structure, jurisdiction, timeline and the roles it needs filled. The launch workflow lays out every step and who owns it.
- STEP 02
Engage providers
Invite the AIFM, administrator, depositary and auditor into their role. Each engagement is a recorded two-sided handshake — proposed by you, accepted by them.
- STEP 03
Coordinate
Requests, documents, attestations and approvals move between organisations inside the system. Everyone sees what is outstanding and who is holding it.
- STEP 04
Evidence
The audit trail accumulates as the work happens — sequenced, attributed and exportable, so the file is ready when it is asked for rather than assembled then.
Who it's for
Built for the four parties who have to agree.
Fund OS is a multi-sided system. The operator runs the fund; the providers do their part from their own portal, on the same record.
Management companies & AIFMs
Stand up funds faster and keep oversight of every delegated provider in one place, with the evidence attached.
Fund administrators
Receive structured, complete requests instead of email attachments, and close them against a shared checklist.
Depositaries
See appointments, documents and attestations on the funds you are engaged on — with a standing record of what you confirmed.
Auditors
Read a sequenced trail rather than reconstructing one, with scoped access to the funds you are engaged on.
Why Regonance
We built for the space between organisations.
Most fund software is built for one firm's internal work. The hard, expensive, unautomated part of a Luxembourg launch is what happens between firms — and that is the part Fund OS is built around.
Orchestration, not storage
Documents are the output. The product is the sequence: who must act next, on what, and what happens when they do.
Launch and govern, one lifecycle
The record created at launch is the record you govern against afterwards — the same parties, roles and history, carried forward.
Audit trail by design
Nothing is logged as an afterthought. The trail is how the system works, which is why it can be exported without a reconstruction exercise.
Where Fund OS stands today
A working system in private beta — described exactly as it is.
We publish no testimonials, logos or case studies we cannot evidence. What follows is simply the current state of the product.
Built and running
Fund launch orchestration, cross-organisation engagement, requests, documents, attestations and the audit trail are implemented and in use in the beta environment.
In private beta
Access is limited to a small number of Luxembourg operators and the providers they invite, so the workflow model can be shaped against real launches.
Named references
Beta participants are confidential. Named references and firm logos will appear here only once those firms have given written permission.
My Work — decision queue
EngagementAccept depositary role — Alpha Credit FundDue in 2 daysyour move
DocumentReturn signed administration agreementLux Private Equity Iyour move
AttestationConfirm NAV oversight for Q2Apex Yield Fundyour move
ApprovalApprove subscription document packPhoenix Growth Fundwaiting on you
RequestProvide audit confirmation letterDue in 6 dayssent
Illustrative interface — representative data, not a live fund.
Security & trust
Handled the way regulated firms expect.
Fund OS is a software tool used by regulated firms. Regonance is not a regulated entity and provides no fund, legal, tax or advisory services — the language below is deliberately precise.
EU-hosted
Data is hosted within the European Union, with no default transfer outside it.
Built around GDPR
Data minimisation, purpose limitation and subject-rights handling are built into the data model rather than bolted on.
Immutable audit trail
Actions are recorded in sequence and attributed to a named user at a named organisation. Records are appended, never quietly rewritten.
Scoped by relationship
Access follows the engagement: a provider reaches only the funds and requests it has been engaged on.
FAQ
Questions we are asked first.
What is Regonance Fund OS?
Regonance Fund OS is software that coordinates the launch and ongoing governance of investment funds in Luxembourg. It puts the fund's management company or AIFM, fund administrator, depositary and auditor on one shared, audit-ready record, so the work that today runs through email threads and spreadsheets runs through a single system instead.
Who is Fund OS for?
Fund OS is for the organisations that stand up and run Luxembourg funds: management companies and AIFMs, fund administrators, depositaries and auditors. Operators run the fund and invite their providers; each provider works in its own scoped portal on the same underlying record.
What does Fund OS actually do?
It orchestrates a fund launch step by step, engages each service provider through a recorded cross-organisation handshake, coordinates the requests, documents and approvals that move between those organisations, and writes every action to an immutable audit trail that can be exported.
Is Regonance a regulated entity?
No. Regonance is a software provider. It is not a regulated entity and provides no fund, legal, tax or advisory services. Regulatory responsibility stays entirely with the licensed firms using the software.
Is Fund OS CSSF-approved?
No software is. Fund OS is designed for firms operating under the Luxembourg regulatory framework, and its workflow and record-keeping model is built around the documentation and oversight expectations those firms already work to. Approval and authorisation remain matters for the regulated firms themselves.
Where is our data held?
Fund OS is hosted in the European Union and built around GDPR data-protection principles, with role-scoped access so each organisation sees only the funds and requests it is engaged on.
How is Fund OS different from a document portal or a project tool?
A portal moves files and a project tool tracks tasks — both stop at the edge of one organisation. Fund OS models the relationship between organisations: who is engaged in which role, on which fund, with what authority, and what each party did. The audit trail is a by-product of the workflow rather than something reconstructed afterwards.
How do we get access?
Fund OS is in private beta with a small number of Luxembourg operators and their providers. Request access through the contact form and we will arrange a walkthrough of a launch on the system.
See the coordination layer in your own launch
We are onboarding a small number of Luxembourg operators and their providers into the private beta. Tell us about your setup and we will arrange a walkthrough.