- The result appears on screen, straight away. No email is needed to see it. The demo and the evidence pack are offered with the result, where intent is highest. If marketing wants to keep lead capture here, add an optional "Email me this result" HubSpot form under the result rather than gating it.
- The questions lead to a protection. Step 5 is the product picker from products.html (who runs the recovery, and whether the live service can wait), folded into one question, so the tool and the product overview always give the same answer.
- Arc steps 1 and 5. The tool names the exposure for the visitor's own application, then hands over to the next step.
What's threatening your software?
Five questions about the application your business relies on most. You'll see your exposure, the risks to plan for and the protection that fits, on this page.
Free, and no email needed for your result. Start the assessment
- Trusted by 3,500+ teams
- ISO/IEC 27001:2022 certified
- Your answers stay in your browser
- The score adds points for the threats chosen (step 2), the time the business can cope without the application (step 3) and what's in place today (step 4). Steps 1 and 5 carry no points. The result says it's a guide and not a probability, because it's a weighted sum of answers, nothing more. The weights are a first pass for the team to tune.
- The protection comes from step 5, using the products.html picker: own team → Escrow; Codekeeper and it can wait → Resilience; Codekeeper and it must stay on → Continuity.
- Facts used: the software list prices (6 Oct list), the inclusions in MESSAGING §6, the DORA Art. 28(8) quote and the NIS2 fine floor (Art. 34(4)), both already verified. "Deposits sync daily" is a production claim, flagged.
Five questions
Assess one application at a time.
Pick the application your business would miss first. Answer for that one. You can run the assessment again for the next.
Your progress
- Your role
- Threats
- Impact
- Today
- Recovery
- Your result
How does your business relate to software?
Choose all that apply.
What could stop your most critical application?
Choose all that apply.
How long could the business work without it?
Think of a normal working week, with no workaround in place.
If it stopped tomorrow, what would you have?
Choose the closest.
When it fails, who should bring it back?
This is the question that decides the protection.
Your result
Worked out from your answers, in your browser. Nothing has been sent.
Lower exposure. You have options if this application stops. Keep the evidence current, and run the assessment for the next application you rely on.
Moderate exposure. A failure would hurt, and parts of the recovery aren't settled yet. The steps below close the gaps.
High exposure. The business needs this application back soon after it stops, and there's no tested way back yet. Start with the protection below.
The score adds up your answers. It's a guide to where to start, not a probability.
The protection that fits
What to plan for
- Failure. Agree release or recovery terms now, while the vendor is there to sign them.
- Attack. Hold a copy outside your own environment. Deposits are held by Codekeeper and encrypted at rest.
- Non-compliance. Keep dated evidence that the application can come back. Whether it meets a specific requirement is for you and your assessor to decide.
- Broken. Keep a current, known-good version. Deposits sync daily through integrations, so the deposit keeps pace with the version you run.
- Not sure yet. Start by listing what the application depends on. The Disaster Recovery Planner walks you through it.
- Vendor backups. They sit with the vendor. A deposit held by a neutral party doesn't depend on the vendor still being there.
- Nothing agreed yet. Every protection starts with custody of the deposit, an automated check of what's in it and a Software Resilience Certificate.
- Already tested. Keep the evidence current. Deposits change, so rebuild when they do: Pro includes four rebuilds a year.
Trusted by 3,500+ teams, from regulated enterprises to fast-growing software vendors
The exposure
Four ways an application stops.
Most failures fall into one of four groups. Each needs a slightly different answer, and the assessment above asks which ones apply to you.
The company behind it stops.
Whether you build software or buy it, you rely on vendors. When one stops, the impact lands on you.
- Vendor shutdown. Insolvency, closure or an acquisition can take away the software and the people who know how to run it.
- Geopolitical disruption. Tariffs, sanctions or export rules can cut off access or change the terms.
- Knock-on outages. A failure further down the dependency chain can take your own systems down too.
What helps: release or recovery terms agreed in advance. Escrow releases the deposit to you; Resilience puts the recovery with us.
An attack takes it down.
Attacks hit live systems, development environments and backups alike. Getting back depends on a clean copy kept somewhere else.
- Ransomware. Attackers can lock production, development environments and backups at the same time.
- Supply-chain compromise. One poisoned library or update can spread to everything that uses it.
- Recovery copies as a target. Backups are attacked too, so it helps to hold a copy outside your own environment.
What helps: a deposit held by Codekeeper, encrypted at rest, and a rebuild that shows it builds from that copy alone.
The regulator asks for your exit plan.
Auditors, clients and regulators now ask whether you could leave a supplier and keep working, and what proof you have.
- Tested exit plans. DORA, Article 28(8): “Exit plans shall be comprehensive, documented and, in accordance with the criteria set out in Article 4(2), shall be sufficiently tested and reviewed periodically.” Regulation (EU) 2022/2554
- Fines. Under NIS2, Member States must allow fines of up to at least €10 million or 2% of total worldwide annual turnover, whichever is higher, for essential entities. Directive (EU) 2022/2555, Article 34(4)
- Procurement. Enterprise buyers ask vendors for continuity evidence before they sign.
What helps: dated evidence for your file. See which frameworks may apply to you with the compliance scan.
Codekeeper's evidence supports your assessment. Whether it meets a specific requirement is for you and your assessor to decide.
It breaks from the inside.
Not every failure comes from outside. Changes to the software itself can stop it working.
- Untested code. Code, including AI-generated code, can reach production with errors nobody checked.
- Faulty updates. An update can corrupt data and break core functions.
- Technical debt. Older code gets harder to maintain, and harder to rebuild.
What helps: a known-good version you can go back to, and Agentic Verification to show it still builds after each change.
How your result is worked out
Nothing hidden in the result.
The exposure score
Points for each threat you choose, for how soon the business needs the application back, and for what's in place today. Higher means fewer options on the day. It's a guide, not a probability.
The protection
The two questions from our product picker: who should run the recovery, and can the live service go offline while it's done? The answer points to Escrow, Resilience or Continuity.
The level
If you need proof the deposit builds, for an auditor, a client or your board, the result points to Pro. The base level is everything you need to be protected.
Where the result points
Released to you. Recovered by us. Kept online.
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. Explore Resilience
From $399
Continuity
Live service kept on+Managed Recovery
Everything in Resilience, plus we keep the live environment paid and switched on for an agreed period. Continuity Pro adds proof it builds. Explore Continuity
From $1,449
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. Prices per application per month, software list. 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
About the risk assessment.
Do you store my answers?
No. The assessment runs in your browser and sends nothing to us. Your result is gone when you leave the page. If you'd like to talk it through, book a demo.
Is the score a probability?
No. It adds up your answers: the threats you chose, how soon the business needs the application back, and what's in place today. Use it to decide where to start, not to predict a failure.
We sell software. Is this for us?
Yes. Answer for your own product as your customers would. Their answer is often the reason they ask for escrow, and Escrow Pro lets you show them the deposit builds.
Can I assess more than one application?
Run it once per application. Most organisations have a handful that matter most. In a demo we go through them together and suggest a protection and level for each one.
Does this count as a risk assessment for DORA or NIS2?
No. It's a starting point. Codekeeper's evidence supports your assessment; whether it meets a specific requirement is for you and your assessor to decide. The compliance scan shows which frameworks may apply.
Know what's at risk. Then protect it.
Book a demo and we'll go through your result, one application at a time.