Fast answers to questions we hear often.
No. The only outbound call is a license validation HMAC every hour. No provider, contract, assessment, incident or register data ever leaves your infrastructure.
Yes. tprm.mlab.sh generates all 15 EBA ITS templates (Reporting Framework 4.0) with controlled eba_* codes, runs a referential integrity validation, and builds the deposit-ready xBRL-CSV (.zip) package matching the official structure required by DORA Article 28(3). See EBA export.
Up to 5 ICT providers and 3 users, with dashboard, provider management, contracts, risk assessments and third-party incidents. The DORA register, EBA export, exit strategies, due diligence, audits and analytics are unlocked on the Licensed tier. See Licensing.
Yes. Drop the mysql and clickhouse services from compose and point DB_HOST/CH_HOST at your managed instances. The app stays stateless apart from its uploads and logs volumes.
For up to 48 hours at a time, yes — that's the grace window. Beyond that the instance locks read-only until you restore outbound HTTPS to mlab.sh. Data is never deleted during a lock.
No — tprm.mlab.sh produces the register and the deposit package; you remain responsible for submitting it to your competent authority. The built-in Validate step checks referential integrity, formats, mandatory fields and uniqueness, which catches the most common rejection causes before deposit.
Every typed field in the register uses the official DORA 4.0 controlled vocabularies (eba_CT, eba_TA, eba_qCO, eba_GA, eba_CU, eba_ZZ, eba_CO, eba_BT, eba_RP). You pick a human-readable value in the UI and the correct code is emitted on export.
Yes. From /eba/ you can preview and download any single template as CSV, all raw CSVs at once, or the complete deposit package. The register page (/reg/) also offers a full CSV export and direct print.
Email [email protected]. We read everything; release notes live on the changelog.