Register Health Check
Free · first 20 entities
- Validation report on your existing register
- Every finding located, with how to fix it
- Delivered within 48 hours
The CSSF has warned that its checks now cover more data fields, so a register accepted in 2025 can be rejected in 2026. The 2027 filing will be checked at least as strictly. Find out what will fail before the regulator does.
B_05.01
ICT third-party provider: identification code missing
Fails 3 providers affected · fix: add LEI or other registered codeB_02.01
Contractual arrangement: mandatory field left empty
Fails 7 rows affected · location and fix listed per rowB_06.01
Function supported: data not provided
Not assessed Missing data is never counted as a passB_01.01
Entity maintaining the register
CompleteThe CSSF urged the rest to submit as soon as possible, leaving time to find and fix issues. Large entities put consultants on it. A 15-person ManCo usually can't.
of entities required to file a register had done so as of 16 March
filing deadline set by the CSSF in 2026 (eDesk opened 11 February)
reference date for the 2027 filing
Sources: CSSF, DORA register submission notice (February 2026); EY, DORA register of information quality checks do not stop at submission, citing supervisory data.
Free for the first 20 entities, including everyone we met at Luxembourg Venture Days.
The spreadsheet or the package you filed in 2026. We send you a secure upload link once the NDA is signed.
Starting with missing mandatory fields, so you can fix them before you file.
Every finding, where it sits in the register, and how to fix it.
The register isn't a one-off filing. Providers change, contracts renew, and the rules tighten every year. The compliance engine keeps the register current between filings.
Start from the register spreadsheet you already have. No re-entry and no blank-page migration.
Missing data shows as "not assessed", never as a pass. You see your coverage, not a flattering score.
Evidence, review and approval, with a full audit log and a PDF readiness report for your board and auditors.
The DORA tool that doesn't create a new DORA problem.
| Typical hosted compliance tool | NEXOPS compliance engine | |
|---|---|---|
| Where your register lives | On the vendor's cloud | In your own environment (Helm chart for Kubernetes) |
| Your DORA register | One more ICT third party to register and assess | Ships its own register entry and vendor due-diligence pack |
| Exit | Proprietary, negotiated | Open source core (Apache-2.0) and a documented exit plan |
| Cost | Consulting days or an enterprise GRC licence | Fixed price, agreed up front |
Your register data stays with you. A fully offline demo runs on a laptop with no network connection.
Apache-2.0 licensed. Your IT team can read the code, and you're never locked in.
A vendor due-diligence pack for your DORA file: register entry, exit plan and subprocessors. Available on request.
Every engagement is priced up front. No day rates, no surprises at resubmission.
Free · first 20 entities
Fixed price, agreed up front
Per entity, per year
For ManCos and consultancies
until 31 March 2027, if the CSSF keeps the 2026 timetable (eDesk opened 11 February, deadline 31 March). The 2027 window is not yet published. Five months is one sales cycle for most boards.
Tell us a little about your entity. We'll confirm within one business day and send the NDA and a secure upload link.
Finance-sector IT missions and multi-cloud infrastructure. I understand both the regulatory register and the cloud architecture behind it.
The entity files and remains responsible for its register. The Health Check and the compliance engine are readiness and validation aids, not legal advice or certification. Our job is to catch errors before the regulator does.
We start with the mandatory-field checks from the ESA validation rules. The report lists each finding, where it sits in your register and how to fix it.
For the Health Check you send us a copy under NDA through a secure link, and we delete it once the report is delivered. The compliance engine itself runs in your own environment, so day to day your register stays with you.
No. The compliance engine is self-hosted. It installs in your infrastructure with a Helm chart, and the core is open source under Apache-2.0. That is the point: it doesn't become another ICT third party you have to register and assess.
You don't have to. Many advisors are stretched by smaller clients, and our channel licence lets a ManCo, fund administrator or consultancy run many entities from one install. Validation-first software makes each filing cheaper to prepare and easier to evidence.
The register needs to stay accurate all year, and the validation rules change every year. The annual subscription keeps the rule catalogs maintained. Once your dependencies are mapped, NEXOPS ONE™ adds cost, concentration and exit analysis for your cloud providers.