About Orym

Built to close the proof gap.

Orym builds governance and cashflow infrastructure for multi-entity structures. One system, built from the document up.

The company
The Company

Who we are.

We build the layer that shows whether your structure matches what your documents describe — and what your flows confirm.

Orym is a technology company based in Geneva, building infrastructure for the governance layer of complex ownership structures — family offices, investment groups, and real estate holding structures operating across multiple jurisdictions.

We build the layer that confirms whether the structure as documented matches the structure as it actually operates — and gives the CFO the levers to act on what it finds.

The System

The operating system.

Orym maps, derives, evaluates — and pilots. Entity by entity, flow by flow. From documents in, to forecasts, alerts, and recommended actions out.

Orym maps ownership structures from source documents, derives expected cashflows from contracts, evaluates every flow against what actually happened, and surfaces what matters — what to reconcile, what to flag, what to escalate — entity by entity, document by document, flow by flow.

A Verified state means the document trail is complete. Partial surfaces the gap. Mismatch quantifies the delta. Missing escalates. And on top of that: forecast views, threshold alerts, and recommended next actions — so the CFO moves from reading the output to acting on it.

01
📄
Every document gets an identity check.
Before Orym evaluates anything, each source document is classified, its facts extracted, and the entity behind it confirmed. Nothing enters the system unresolved.
02
🔗
Structure is reconstructed, not assumed.
Orym maps ownership relationships and derives expected cashflows directly from contracts on file — not from user input, not from accounting exports.
03
Every flow earns its verdict.
Verified. Partial. Mismatch. Missing. Each state is the result of a complete chain of evidence — not a default, not a flag raised by a rule. A conclusion drawn from documents.
The team
Chief Executive Officer
Fabien Haddad
Fifteen years across finance — controlling, auditing, and running the books of complex structures. Thirteenth year operating in Geneva. Trained in a Big Four environment, then inside real estate funds, private equity vehicles, and multi-jurisdictional holding groups. Sat on every side of the document: the one who produced it, the one who audited it, the one who had to reconcile it with what actually happened. The gap between declared structure and operating reality was the constant — no tool closed it. Orym does.
Chief Technology Officer
Marc Poulain
Fifteen years building financial software where it has to hold — regulated platforms, governance stacks, and live execution systems. Worked on the document side (GRC infrastructure for asset managers) and the flow side (trading systems running in real time). The extraction engine behind Orym draws on both: the logic of how a financial document is structured, and the discipline of software that fails visibly when it fails at all.
Early access · June 2026

See it on your own structure.

Explore a sample group through the product, or start a private conversation about your own.