Agentic compliance for financial services

Run DORA without rebuilding your register of information every year

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.

  • Register of information in the EU templates
  • Reporting templates for 4 hours, 72 hours and one month
  • Hosting in the EU, Germany or the US

Example data

Obligations check

How well your DORA programme holds up in operations

Tick what runs in a way you can prove. Your result stays in your browser and is never sent.

Governance
ICT risk management
ICT third parties
Incidents and testing
Your progress0%

A supervisor would find gaps fast

Book a demo
Which DORA framework applies to your firm
Is your firm a financial entity under Art. 2(1) DORA, such as a credit institution, payment or e-money institution, investment firm, crypto-asset service provider, insurer, fund manager or crowdfunding service provider?

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.

What financial firms deal with

DORA does not end with your first register

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.

01The register is due every year

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.

02Four hours from classification

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.

03Your contracts predate DORA

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.

04Your provider is on the list and your duties stay

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.

How it works

A DORA programme that keeps up with daily operations

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.

01 Gap Audit Agent

Find out which DORA rules apply to each entity

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.

Key factsProportionality
Simplified framework only for the five entity types in Art. 16(1)
Microenterprises stay in the full framework with specific reliefs
TLPT only if your authority identifies you
02 Gap Audit Agent

Build the ICT risk management framework on your controls

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.

Key factsArt. 5 to 15
The management body approves the framework and holds final responsibility
Review at least yearly and after major incidents
Continuity plans tested at least yearly
03 Contract Agent

Check every ICT contract against Art. 30

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.

Key factsArt. 28 to 30
Art. 30(2) applies to every ICT contract
Art. 30(3) adds exit strategy and audit rights for critical or important functions
Assess concentration risk before signing
04 Contract Agent

A register that stays current between submissions

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.

Key factsRegister of information
Templates per Implementing Regulation (EU) 2024/2956
At entity and group level
BaFin window 2026 from 9 to 30 March
05 Policy Agent

Spot major incidents and report them on time

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.

Key factsArt. 19
Initial notification 4 hours after classification, at the latest 24 hours after awareness
Intermediate report 72 hours after the initial notification
Final report one month after the latest intermediate report
Deadlines

The dates and cycles DORA sets

16 Jan 2023DORA enters into forceRegulation (EU) 2022/2554 enters into force.
17 Jan 2025DORA appliesAll obligations apply directly.
18 Nov 2025Critical providers designatedThe ESAs publish the first list and update it every year.
9 to 30 Mar 2026Register to BaFinSubmission as of 31 December 2025.
Every yearRegister to the supervisorReport your ICT contractual arrangements.
At least yearlyFramework and testingReview the framework, test systems for critical functions.
Per major incident4 h, 72 h, 1 monthInitial notification, intermediate report, final report.
Every three yearsTLPTFor firms your authority identifies.
Never alone

Business teams ask and GetTeddy answers from the approved record

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.

1

Ask GetTeddyDoes this provider support a critical function? Where does our cloud provider keep our data? Every answer points to the contract clause.

2

Agents do the groundworkThey check contracts against Art. 30 and maintain the register. The classification checklist and the reporting templates are ready.

3

Our team backs you upA compliance engineer helps with supervisory requests, register submissions and inspections.

TeddyYour company · Example data
The supervisor asks which contracts support payment processing.
22 contracts support critical or important functions.
  • Payment processing4 contracts
  • Art. 30(3) met3 of 4
  • Exit strategy1 missing
Shall I export the list for the supervisor?
Export listAsk our team
CEYour compliance engineer helps with supervisory requests.
Why GetTeddy

One programme for DORA and the frameworks around it

  • AI agents that support your DORA work
  • DORA, ISO 27001 and NIS2 on one control set
  • Compliance engineer included
  • A human approves every decision
  • Hosting in the EU, Germany or the US

Read next DORA · ISO 27001 · Legal teams · CISOs · Enterprise

FAQ

Questions from financial services firms

Does NIS2 apply on top of DORA?

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.

Can we use the simplified framework under Art. 16?

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 is an ICT incident major?

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.

What has to be in an ICT contract?

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.

Our cloud provider is designated as critical. Does that change our duties?

No. The European Supervisory Authorities oversee designated providers directly. Your contract, your register and your exit strategy remain your responsibility.

Where is our data hosted?

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.

Before and after

What changes with GetTeddy

TypicalThe register gets filled once a year
With GetTeddyThe register keeps up all year
TypicalWith GetTeddy
Contract reviewClause by clause, by handChecked by the Contract Agent
Register of informationA spreadsheet with broken linksBuilt from your contracts
IncidentsThresholds looked up mid-incidentChecklist and templates with named roles
ISO 27001 and NIS2Separate projectsBuilt on the same controls
OngoingAnnual reviewGap audits every week

Your DORA programme, built from your contracts and controls

In 30 minutes we show you on your own contracts.

  • Backed by Antler
  • Hosting in the EU, Germany or the US
  • Compliance engineer included