- The exposure: four ways an application you don't control can take a stable process down (the Failure, Attack, Non-compliance and Broken tabs kept from production).
- The shift: from a recovery plan nobody runs to a routine with dated results.
- The model and the proof: the routine in four steps, and an evidence map built from the questions an operating review asks.
- The next step: book a demo, or get the sample evidence pack.
Resilience as an operating discipline. Proven, not assumed.
Operational excellence is about how you run things every day. Codekeeper brings the software you depend on into that routine: a protection on each critical application, rebuilds you run when you choose, and a dated record of every result.
- Trusted by 3,500+ teams
- ISO/IEC 27001:2022 certified
- 10+ years securing software
Trusted by 3,500+ teams, from regulated enterprises to fast-growing software vendors
Where the rules are
Operational excellence isn't a regulation.
No single standard defines operational excellence, and no regulator enforces it. It's a way of running operations, drawing on methods such as Lean and Six Sigma. The rules on continuity and suppliers sit in other frameworks. If one of them applies to you, start there.
DORA
Regulation (EU) 2022/2554 · financial entitiesExit plans for ICT services that support critical or important functions, documented and tested.
DORA EUNIS2
Directive (EU) 2022/2555 · essential and important entitiesBusiness continuity and supply chain security, among the measures entities in scope must take.
NIS2 UKPRA SS2/21
PRA supervisory statement · outsourcing and third partiesExit plans for material outsourcing that cover stressed exits and are tested as far as possible.
PRA SS2/21 ISOISO 22301
ISO 22301:2019 · business continuity managementContinuity strategies, plans and an exercise programme, in a certifiable management system.
ISO 22301 ISOISO 27001
ISO/IEC 27001:2022 · information security managementAnnex A controls for suppliers, disruption and backup.
ISO 27001 USSOC 2
United States · service organisation auditsVendor risk and availability, in your own report from your service auditor.
SOC 2 USFFIEC
United States · banking supervisionThird-party risk across the relationship life cycle, including escrow for purchased software.
FFIEC AUCPS 230
Australia · APRA operational risk managementOperational risk, service providers and continuity for APRA-regulated entities.
CPS 230 EUCRA
Regulation (EU) 2024/2847 · products with digital elementsSecurity for products with digital elements, including documenting their components in an SBOM.
CRACodekeeper's evidence supports your assessment. Whether it meets a specific requirement is for you and your assessor to decide.
Where software fits
Stable processes. Software you don't control.
You can standardise a process and still lose it to an application someone else runs. Four things take software away. Each has a routine that brings it back.
The vendor stops.
Insolvency, an acquisition or a change of strategy can take an application away, along with the people who know how to run it. The process that depends on it stops too.
The routine
- Release or recovery terms agreed before anything goes wrong
- The deposit kept current, synced daily from the vendor's repositories
- A rebuild without the vendor, before you need one
An attack takes it down.
Ransomware and supply-chain attacks hit live systems and backups alike. Getting back depends on a clean copy kept somewhere else, and on someone who can run the recovery.
The routine
- The deposit held by a neutral party, encrypted at rest
- With Resilience, Codekeeper runs the recovery
- With Continuity, the live environment kept paid and switched on for an agreed period while we recover
The auditor asks for proof.
Customers, auditors and regulators ask whether you could carry on without a supplier, and what evidence you have. A policy answers the first half of the question.
The routine
- A dated Software Resilience Certificate with Escrow, Resilience and Continuity
- Evidence mapped to the framework you answer to
- A Tested Exit Report for the applications that matter most
The deposit doesn't build.
Code you can't build is code you can't use. A missing file or a private package is easy to miss until the day you need the application back.
The routine
- Agentic Verification rebuilds the deposit in hours, in the Codekeeper AI Verification Lab
- Missing items flagged, so the depositor can add them
- An Exit workbook with the recovery steps
Know what you run on
List the applications behind each critical process, in-house or from a vendor.
Attach a protection
Escrow, Resilience or Continuity for vendor applications. Resilience or Backup for your own.
Prove it, on a rhythm
Rebuild when the deposit changes or the quarter turns. Four rebuilds a year come with the Pro levels.
Review and improve
Close the gaps each run flags, and take the results to your operating review.
Evidence map
The questions an operating review asks.
For each critical application, a dated document, not a status someone typed in.
| The question | Codekeeper evidence |
|---|---|
| Which applications does this process depend on? | Every critical application in one account, with its protection and a checked record of what's deposited. With Continuity, a map of where the live service runs and what it needs. Software Resilience CertificateVault reportLive environment mapEscrow · Resilience · Continuity · live environment map with Continuity |
| Who runs the recovery if a vendor stops? | Written down before anything goes wrong: released to you, or recovered by us. Escrow AgreementResilience ArrangementEscrow · Resilience · Continuity |
| Could we run it without the vendor? | AI agents rebuild the deposit in the Codekeeper AI Verification Lab, with no help from the vendor, in hours. Recoverability CertificateRun reportDeployable copyEscrow Pro · Resilience Pro · Continuity Pro |
| Is the recovery written down? | The recovery process step by step, and the components the application needs. Exit workbookBuild stepsSBOMEscrow Pro · Resilience Pro · Continuity Pro |
| Has anything changed since we last checked? | Deposits sync daily. Between rebuilds, we compare the deposit with the live repositories and flag what changed. Vault reportEvery protection · change flags with the Pro levels |
| Have people tested the business functions, not just the build? | A clean-room rebuild by our specialists, tested against the business functions you nominate, without the original developers. Tested Exit ReportExit Exercise, an add-on to any plan |
Codekeeper's evidence supports your assessment. Whether it meets a specific requirement is for you and your assessor to decide.
Which protection fits
One routine, three jobs.
Escrow means the deposit is released to you and you run the recovery. Resilience costs more because we do the recovery. Continuity costs more again because we also keep the live environment switched on.
Escrow
Released to you→Self-Run Recovery
When the agreed conditions are met, the deposit is released to you. Escrow Pro adds proof it builds. Explore Escrow
From $199
Resilience
Comes to us→Managed Recovery
If the application fails, Codekeeper runs the recovery for you. Resilience Pro starts from a deposit we know builds. Explore Resilience
From $399
Continuity
Live service kept on+Managed Recovery
Everything in Resilience, plus the live environment kept paid and switched on for an agreed period while we recover. Continuity Pro adds Agentic Verification. Explore Continuity
From $1,449
Prices per application per month, for software applications; SaaS and AI applications have their own rows. Rebuilds come with Escrow Pro (from $449), Resilience Pro (from $649) and Continuity Pro (from $1,699). For systems you run yourself, Software Backup attaches the same way. See all prices
Sample evidence pack
See what your auditor would receive.
An anonymised set of outputs from a real Agentic Verification run, so you can judge the evidence before you talk to us.
- Recoverability Certificate
- Run report
- SBOM and Exit workbook excerpts
Questions
Building it into how you operate.
Is operational excellence a regulation?
No. No single standard defines it, and no regulator enforces it. If a regulation or standard applies to you, such as DORA, NIS2, PRA SS2/21 or ISO 22301, its requirements come first. See Solutions.
Where does software resilience fit in operational excellence?
Operational excellence aims for processes that run the same way every day. A process that depends on an application you don't control carries a risk the process can't fix on its own. A protection, regular rebuilds and a dated record bring that application into the same routine as everything else.
How is this different from business continuity or ISO 22301?
Operational excellence is about everyday performance. Business continuity, and ISO 22301, plan for disruption. They meet at one question: could this process keep going if an application stopped? See our ISO 22301 page.
How often should we rebuild?
That's your call. The Pro levels include four rebuilds a year, run when you choose. Between runs, we compare the deposit with the live repositories and flag what changed, so you can rebuild when it matters. Twelve rebuilds a year are available for $299 a month more.
Do our vendors have to take part?
For vendor applications, yes: the vendor is the depositor and connects its repositories once, and deposits then sync daily. For systems you build yourself, you're the depositor.
Is there a certificate for operational excellence?
No, and we don't issue one. Escrow, Resilience and Continuity come with a Software Resilience Certificate, and with the Pro levels each successful rebuild issues a Recoverability Certificate. They document the deposit and the rebuild; release rights come from the agreement.
Want the background first? Our operational excellence guide is in Resources.
Make recovery part of how you operate.
We'll look at the applications behind your critical processes and show you the routine that keeps each one recoverable.