Our AI agents check every ICT contract against Art. 30 and keep the register of information current from your contracts. They map the ICT risk management framework to the controls you already run.
Example data
Tick what runs in a way you can prove. Your result stays in your browser and is never sent.
A supervisor would find gaps fast
Book a demoProgramme exists, operations not yet
See the contract reviewReady for supervisory questions
Book a demoFirms outside DORA can still fall under the German NIS2 law, so check that next. Explore NIS2 →
Financial entities must put the Art. 30 provisions into your contracts. If the supervisory authorities designate you as a critical provider, they oversee you directly. GetTeddy answers your customers' questionnaires from your evidence.
Art. 16 replaces Art. 5 to 15 for you. The detail is in Title III of Delegated Regulation (EU) 2024/1774. Incident reporting, the register and the contract rules still apply.
Art. 5 to 15 apply in full, with specific reliefs for microenterprises. Add incident reporting, yearly testing, the register and Art. 30.
Your authority has identified you. You run a threat-led penetration test on live production systems at least every three years.
We check the exclusions in Art. 2(3) with you case by case, for example small insurers or pension funds with no more than 15 members. This helper is not legal advice.
DORA has applied directly since 17 January 2025. The project has turned into day-to-day work. Every new contract, incident and test now needs a paper trail.
You report your ICT contractual arrangements to the supervisor each year. In 2026 BaFin accepted registers from 9 to 30 March, as of 31 December of the previous year. Tools that business teams buy themselves belong in it too.
For a major ICT incident the initial notification is due within 4 hours of classification, and no later than 24 hours after you become aware. If you only look up the thresholds once the incident is running, those hours are gone.
Every ICT contract needs the Art. 30(2) provisions. For critical or important functions, exit strategies and full audit rights come on top. Large providers rarely volunteer those clauses.
The European Supervisory Authorities named the first critical ICT third-party providers on 18 November 2025. The ESAs now oversee these providers directly. Managing your own third-party risk is still your job.
Our AI agents map the requirements and read the contracts. They keep the register and the reporting process ready. Legal, risk and the management body make the decisions.
GetTeddy maps each entity in your group to an Art. 2 entity type and checks whether the simplified framework under Art. 16 can apply. The reasoning is ready for Legal.
GetTeddy maps Art. 5 to 15 to the controls you run for ISO 27001 or NIS2. You see what is covered and what DORA adds.
The Contract Agent reads every contract, flags whether the service supports a critical or important function and lists missing provisions. For each gap it suggests wording from your template. Legal decides.
GetTeddy fills the register of information from your contracts and supplier list. When a contract is added or ends, the change shows up as a draft. The entry becomes final only after you approve it.
The Policy Agent drafts the classification checklist against the EU thresholds and the three reporting templates. Every role has a named person, so the 4-hour deadline also holds at weekends.
Procurement, IT and business teams ask about contracts and duties in their own words. GetTeddy answers from the register and your controls. New contracts reach Legal with a draft.
Ask GetTeddyDoes this provider support a critical function? Where does our cloud provider keep our data? Every answer points to the contract clause.
Agents do the groundworkThey check contracts against Art. 30 and maintain the register. The classification checklist and the reporting templates are ready.
Our team backs you upA compliance engineer helps with supervisory requests, register submissions and inspections.
Read next DORA · ISO 27001 · Legal teams · CISOs · Enterprise
Not for the core duties. German NIS2 law exempts financial entities under DORA from its risk management, reporting and management duties. Your programme is built on DORA.
Only if your firm is one of the five types in Art. 16(1), such as small and non-interconnected investment firms or payment institutions exempted under PSD2. A microenterprise is not one of them. It applies Art. 5 to 15 with specific reliefs.
When it affects critical services and either involves malicious unauthorised access that may lead to data loss, or meets at least two other thresholds. From the moment you classify it, the 4-hour clock runs.
Every ICT contract needs the Art. 30(2) provisions, such as a service description, data locations, service levels and termination rights. If the service supports a critical or important function, Art. 30(3) adds exit strategies and full audit rights, among others.
No. The European Supervisory Authorities oversee designated providers directly. Your contract, your register and your exit strategy remain your responsibility.
In the region you choose: EU, Germany or the US. Your data is kept separate from other customers and encrypted. GetTeddy uses read-only access by default and never trains AI models on your data.
| Typical | With GetTeddy | |
|---|---|---|
| Contract review | Clause by clause, by hand | Checked by the Contract Agent |
| Register of information | A spreadsheet with broken links | Built from your contracts |
| Incidents | Thresholds looked up mid-incident | Checklist and templates with named roles |
| ISO 27001 and NIS2 | Separate projects | Built on the same controls |
| Ongoing | Annual review | Gap audits every week |
In 30 minutes we show you on your own contracts.