Hosting, security, compliance
Your project data stays in France
Application and database hosted on Azure, France Central region. Separation by client, backups restored every week for verification, automatic monitoring of code and infrastructure.
Common foundation across every planOrnexia in 3 sentences
- Ornexia is the steering hub for your committees and your action plans.
- The AI drafts your minutes, extracts the actions, and advises you at the right moment.
- Every decision becomes a tracked action, with an owner and a due date, through to closure.
Three questions before handing over your minutes
Before putting your committee minutes in a vendor's hands, you want to know where the data lives, what happens if it disappears, and who can read it. Those questions come before the functional demo, and they deserve answers you can check.
Here they are, without the marketing.
Where your data lives
Application and database: Microsoft Azure, France Central region, within the European Union.
AI analysis: a model hosted in the European Union, and switched off until your organisation switches it on.
This marketing site is served from the United States. It holds none of your project data.
Every client in their own space
Ornexia is multi-client, with no data sharing. Your organisation has its own space inside the database: its tables, its libraries, its users.
This is not a client identifier added to shared tables, with the risk that a forgotten filter lets a neighbour's data through. The separation is structural: a query on your space cannot reach anyone else's.
If your data disappeared
Point-in-time restore across the last thirty-five days, plus a daily backup per client kept on a rolling cycle: the last seven days, the last four weeks, the last six months.
Those backups are genuinely restored, every week. Two automatic checks replay a full restore onto disposable infrastructure, verify the data is there, then destroy everything. A backup never restored is not a backup.
What's watched, continuously
Dependencies and system images — every time the code changes, libraries and system images are checked against known vulnerabilities. A published flaw blocks the release.
The infrastructure — every night, an automatic check verifies your domains' certificates, their reachability, access rights and version consistency across environments.
Regressions — a functional test suite replays real journeys before every release.
A platform that keeps moving
Ornexia evolves through short, frequent releases rather than large annual versions. Fixes and improvements arrive as they are ready.
There is no upgrade for you to schedule: you always work on the current version.
What each release adds and fixes is published in the version log, available from the application's "About" window.
Access control is set in your governance, every change leaves a trace in the history, and your libraries stay exportable at any time through reversibility.