Skip to content
New Pro plans with Agentic Verification.
SolutionsAll solutionsDORAPRA SS2/21NIS2CRAISO 27001SOC 2ISO 22301FFIECCPS 230ESMAEU AI ActCbwOpEx
By role · ICT and third-party risk

Every critical provider on the register. Evidence you could leave each one.

For ICT and third-party risk managers. Your register lists the providers behind your critical services. Codekeeper holds what it takes to bring each application back without its provider, proves it rebuilds, tests the exit in practice, and keeps the vendor record current, with dated evidence per vendor for your file.

Book a demo Request an enterprise proposal
  • Trusted by 3 500+ teams
  • ISO/IEC 27001:2022 certified
  • Evidence for DORA, PRA SS2/21, NIS2, and CPS 230 files
A third-party risk manager and a procurement manager review the register of critical providers

Trusted by 3 500+ teams, from regulated enterprises to fast-growing software vendors

Airbus Bayer European Parliament General Motors Intuit Nestlé PepsiCo Pfizer

The register

A register lists your providers. Evidence shows you could leave one.

Under DORA, PRA SS2/21, NIS2, and CPS 230, the question has moved from "do you have a contract?" to "could you leave, and keep running?" A planned exit can be negotiated with the provider. A stressed exit can't, because the provider has failed and may not be there to help at all. What you hold for each provider decides the answer.

On paper
With evidence
Register
Critical providers listed, with a risk rating
A protection on each critical application, with a certificate per application
Supplier dependencies
A supplier list and a contract clause
Release or recovery terms agreed up front, and an SBOM for each rebuilt application
Orderly exit
An exit approach that assumes the provider helps
A deposit that rebuilds without the vendor, with build steps and an Exit workbook
Testing
A scenario exercise of a provider failure
A real rebuild, and an Exit Exercise Report on the functions you nominate
Fourth parties
The provider's own providers, unseen
With Continuity, a live environment map of the accounts and services the application depends on
EU

DORA

Regulation (EU) 2022/2554 · financial entities

Exit plans for ICT services that support critical or important functions, documented, sufficiently tested, and reviewed periodically.

DORA evidence UK

PRA SS2/21

PRA supervisory statement · outsourcing and third parties

Exit plans for material outsourcing that cover stressed exits and are tested as far as possible.

PRA SS2/21 evidence EU

NIS2

Directive (EU) 2022/2555 · essential and important entities

Cybersecurity risk management, including the risks that come from your software suppliers.

NIS2 evidence AU

CPS 230

Australia · APRA operational risk management

Evidence for service-provider and continuity reviews, where core technology services are material by default.

CPS 230 evidence

Codekeeper's evidence supports your assessment. Whether it meets a specific requirement is for you and your assessor to decide.

What to hold for each provider

Three protections. Pick one by how critical the application is.

Every Codekeeper plan keeps a current, checked copy of the application you depend on with a neutral party. For each application on the register, ask two questions: when it fails, who should run the recovery, and can it go offline while it's recovered? The answers point to the protection. Pro adds Agentic Verification at every level.

Released to you

Escrow

Released to you→Self-Run Recovery

For the software your own team can bring back. The deposit is released to your team if an agreed condition is met. Escrow Pro adds proof it builds, from $449. Explore Escrow

From $199

Recovered by us

Resilience

Comes to us→Managed Recovery

For the software you can't risk rebuilding yourself. If the application fails, Codekeeper's engineers run the recovery. Resilience Pro starts from a deposit we know builds, from $649. Explore Resilience

From $399

Stays online

Continuity

Live service kept on+Self-Run or Managed Recovery

For the services that just can't go offline. The Escrow or Resilience recovery you choose, plus the live environment kept paid and switched on for an agreed period while it's recovered. Continuity Pro adds Agentic Verification, from $1,699. Explore Continuity

From $1,449

Prices per application per month, for software applications; SaaS and AI applications have their own rows. Setup is $499 per agreement for Escrow and Resilience, and $999 for Continuity. Our guidance for an application that supports a critical or important function (DORA), a material outsourcing arrangement (PRA SS2/21), or a material arrangement (CPS 230): Resilience Pro or Continuity Pro, plus an Exit Exercise. Your own assessment of each application decides. Compare the protections or see all prices.

1

Start from your register

Add the applications behind your critical services, from a vendor or built in-house.

2

Attach the protection

Escrow, Resilience, or Continuity for each one, at the level the application's criticality calls for. The deposit syncs daily from the vendor's repositories.

3

Rebuild and file

With Pro, run up to four rebuilds a year, on supported technology stacks. Each successful run issues a Recoverability Certificate.

4

Exercise the exit

Add an Exit Exercise to test the business functions you nominate, with an annex mapped to your framework in the report.

The tested exit

A written exit plan isn't a tested one.

An exit plan describes what would happen if a provider failed. Testing shows whether it would work. In an Exit Exercise, our specialists recover the application from the deposit alone, without the vendor or the original developers, bring the data back, deploy it, and test the business functions you nominate. The Exit Exercise Report records the result, with an annex mapped to your framework.

  • The original developers aren't involved at any step
  • The customer or the vendor can request one
  • Pass or fail per function, the gaps found, and the date
  • An add-on to any plan, from $12,000, quoted at scoping
Explore the Exit Exercise

Example report. Names and contents are fictional and vary by application.

Add-on · Vendor Risk & Compliance

One proves you can recover. The other proves the vendor earned your trust.

Your escrow is in order. The vendor records often aren't, and an auditor looks at both. Vendor Risk & Compliance keeps your third-party oversight current: each vendor assessed against the frameworks you report to, with a written verdict signed by an analyst. It runs alongside your Codekeeper protections, on the same login.

Vendor oversight by hand

  • ×Assessments scattered across inboxes and folders
  • ×A spreadsheet that goes stale between audits
  • ×Questionnaires rebuilt from scratch for every audit
  • ×Changes at a vendor found late, sometimes by the auditor

With Vendor Risk & Compliance

  • Each vendor assessed on an ongoing basis against DORA, NIS2, CRA, ISO 27001, SOC 2, and GDPR
  • A written verdict for each vendor, signed by an analyst: a name, a date, and a decision
  • An evidence packet per vendor and per framework, versioned and dated
  • Sub-processor changes, certification lapses, and breach disclosures flagged as they're published, not at the audit

Bringing a new vendor on board?

Start the assessment without a questionnaire from scratch. 10 000+ vendors are monitored already, and new ones are onboarded within five business days. Available as an add-on to any protection, quoted for your account.

Explore Vendor Risk & Compliance

Onboarding a vendor

How a provider comes under protection.

Every Codekeeper protection runs on an agreement that names the parties, what's deposited, and what happens when the application fails. Codekeeper's legal team prepares it from your choices, and your own lawyers can mark it up. The customer or the vendor can pay: the vendor can sponsor the protection as part of its offer, or you pay for it.

1

Choose the structure

Two-party, between the vendor and Codekeeper, so protection can extend to any customer who asks. Three-party, where the vendor, you, and Codekeeper all sign. Multi-party, for several beneficiaries, each with its own release conditions.

2

Set the terms

The legal context, the jurisdiction, and the release conditions, such as the vendor's insolvency, a failure to maintain or support the software, or a material breach. Our legal team drafts from your choices and reviews every change.

3

The vendor connects its repositories

Deposits sync daily through 50+ integrations, and an automated check confirms what's deposited every month. With Resilience, the vendor sets it up once and each new customer is added to the list.

4

Evidence per vendor

A dated certificate or report every time a check, a rebuild, or an Exit Exercise runs, tied to one application, ready for your file.

What's on file for each providerCodekeeper evidence
Every protectionPlan certificateVault ReportVault CertificateThe deposit is held, and an automated check confirms what's in it every month. Release or recovery terms are in the Escrow Agreement or Software Resilience Agreement.
Escrow Pro · Resilience Pro · Continuity ProRecoverability CertificateRebuild ReportSBOMExit workbookUp to four rebuilds a year in the Codekeeper AI Verification Lab, on supported technology stacks, with anything missing flagged for the depositor to add.
Continuity · Continuity ProLive environment mapContinuity Vault ReportContinuity Vault CertificateThe live environment mapped at setup and kept current, and monthly checks that confirm we can take over the accounts if the vendor stops.
Exit Exercise, an add-on to any planExit Exercise ReportFramework annexExit Exercise CertificateThe result, the gaps, and the date, with an annex mapped to the framework you report against.
Vendor Risk & Compliance, an add-onVendor verdictEvidence packetA written verdict signed by an analyst, and an evidence packet per vendor and per framework, versioned, dated, and traceable.

A verdict records an analyst's assessment of the vendor. It's evidence for your file, not a certification of the vendor. The Recoverability Certificate documents a rebuild; release rights come from the agreement. See the escrow agreement, or how it works for the vendor.

Many applications or several claimants?

One proposal for your whole estate, with a protection and level for each application, matched to how it's deployed and how critical it is. Software, SaaS, and AI applications on one account, with dedicated contacts for legal, technical, compliance, and billing.

Request a proposal

Frequently asked questions

Before you map your register.

Which protection should a critical provider get?

Choose by who runs the recovery and whether the service has to stay on. For an application that supports a critical or important function (DORA) or a material outsourcing arrangement (PRA SS2/21), our guidance is Resilience Pro or Continuity Pro, plus an Exit Exercise when the exit plan needs to be exercised. Your own assessment of each application decides.

Our critical provider is a SaaS vendor. Does this still work?

Yes. SaaS applications have their own price row. We hold the code, infrastructure, data exports, and the access needed to bring the service back, and rebuilds run on supported technology stacks.

Does the vendor have to agree?

Everyone who's party to the agreement signs it. A two-party agreement is between the vendor and Codekeeper, so protection can extend to any customer who asks. In a three-party agreement, the vendor, you, and Codekeeper all sign: both parties log in and approve it before signature requests go out, and deposits open once every signature is in. The customer or the vendor can pay for the protection.

How is an Exit Exercise different from Agentic Verification?

Who runs it and what it tests. Agentic Verification uses AI agents to prove the deposit builds, in hours, up to four times a year, on supported technology stacks. In an Exit Exercise, our specialists recover your software from the deposit alone, without the vendor or the original developers, bring the data back, deploy it, and also test the business functions you rely on. You don't need a Pro plan for an Exit Exercise.

Will this make us compliant with DORA?

No product can do that on its own. Codekeeper gives you evidence for your file: certificates, Rebuild Reports, SBOMs, Exit workbooks, and Exit Exercise Reports with a DORA annex. Whether it meets a specific requirement is for you and your assessor to decide. See DORA.

Every provider on the register. Evidence you could leave each one.

In a demo, we go through the applications behind your critical providers and suggest a protection and a level for each one.

Book a demoRequest a proposal