§ DEPLOY
Run it inside your organisation.
Everything AYVES does on public filings, it can do on yours. Load your group’s own figures before you publish and see what an outside reader will see. Track every entity in your structure, including the ones that never file publicly. Watch competitors and counterparties on the same indicators, scored the same way.
Your data stays in your deployment. It is not used to train anything, and it is not visible to us.
What you get
AYVES runs on infrastructure you control. The public corpus syncs in. Nothing of yours syncs out.
Your internal figures and the public record, on the same indicators, in one view. A jurisdiction you have not filed on yet is read the same way as one you have.
Priced per organisation. Adding a colleague costs nothing, so the people who need the answer are not rationed.
No private fork of the rules. Your deployment scores exactly as the public one does, which is the point: a result you can hand to someone outside.
What it is for
Pre-publication review. Run your own country-by-country report through AYVES before it is filed. Whatever it flags, an analyst reading the published version will see too. Most of what surfaces is explainable in a footnote you have not written yet.
Group coverage. Public filings cover the entities required to file. Your structure is larger than that, and the entities that never appear in a public report are often the ones worth a second look.
Peers, on your terms. Same indicators, same thresholds, applied to the companies you actually compare yourself against rather than a sector average you did not choose.
How data is handled
Private figures you load are stored in your deployment’s own database. They are never transmitted to AYVES. They never enter the public corpus. They are never used to train or tune any model. The corpus sync runs in one direction: public data flows in.
Air-gapped operation is supported. A deployment with no outbound connectivity keeps working on the corpus it already holds, and says how old that corpus is rather than presenting stale data as current.
Getting it running
Deployment is a container stack and a database. The corpus sync, the private-data loader, and the upgrade path are documented, and the first sync is the longest step.
Internal deployment is part of the Firm tier, at €5,000 a year for the organisation. Pricing is annual and current.