NewResilience, Continuity, the Pro levels and Agentic Verification: from safekeeping to proof you can recover.The new line-up is here.See what's new
Free toolsRisk assessmentCompliance scanTechnical assessmentDisaster Recovery Planner
Why this tool looks like this. Production's /technical-assessment is a three-step HubSpot form: contact details, four "how many" counts (applications, components, hosting environments, third-party services), then complexity, update frequency, codebase size, database size and the code platform. Its side panel says "Our escrow engineers use these answers to size the deposit and recommend the right verification level", so the visitor gets nothing back until sales replies. The rebuild keeps three steps and answers on screen:
  • Step 1 maps the application's parts to the eight "what we deposit" pages.
  • Step 2 maps where the code and files live to the integration pages. The platforms are production's own list from this form, and each has an integration page in the kit.
  • Step 3 maps what the visitor needs to prove to the level: base, Pro (proof it builds) or the Exit Exercise.
No technology stack is named anywhere: rebuilds run "on supported technology stacks" (MESSAGING §5), and the FAQ sends stack questions to the demo. Production's sizing questions (counts, codebase and database size) are left out: they size a quote, which the demo does better. Arc steps 3 and 4.
Free tool · Technical assessment

What should your deposit contain?

Three questions about how your application is built and where it lives. You'll get advice on what to deposit, how to keep it current and which level proves what you need.

Book a demo Get the sample evidence pack

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
Three questions, three parts of the advice. The result has one section per question, in the same order: what goes in, how it stays current, how you prove it. Hosting accounts and credentials share a tag (live-env) that adds one Continuity note, because Continuity maps the live environment at setup: where it runs, the accounts it depends on and the services it needs (MESSAGING §6). Production claim kept and flagged: "deposits sync daily". "50+ integrations" is production's figure, kept and flagged (agreed: production stats stay, flagged). The hub has setup pages for 24 platforms and production's grid shows 40, so Product must confirm the real count; it stays open in to-confirm.md and isn't used. Monitoring between runs comes with Agentic Verification, so the result and the FAQ say "with Pro" (fact-check, 7 Oct). The deposit-type descriptions follow production's own page intros. The monitoring line ("we compare the deposit with the live repositories and flag what changed") and the rebuild facts are confirmed in MESSAGING §6. 16 Oct: Continuity Pro added; base Continuity no longer includes Agentic Verification, so the Pro result names Continuity Pro.

Three questions

Plan the deposit for one application.

Answer for the application you want to protect first. If you're a vendor, answer for the product your customers rely on.

Your progress

  1. What it's made of
  2. Where it lives
  3. What to prove
  4. Your advice

What would someone need to rebuild and run it?

Choose all that apply.

Where do the code and files live today?

Choose all that apply.

What do you need to be able to show?

To an auditor, a customer, your board, or yourselves.

Your advice

Worked out from your answers, in your browser. Nothing has been sent.

1. What goes in the deposit

  • Source code. The repositories the application is built from, kept in step with the version you run. Source code
  • Data. The application data a recovery needs, held in an independent environment. Data
  • Deployment assets. Build scripts, packages and configuration files, so the code can become a running system. Deployment assets
  • Hosting environment. The details of where it runs and the accounts behind it. Hosting environment
  • Credentials. The access needed to manage and pay the providers the application depends on. Credentials
  • Third-party dependencies. The configuration and documentation for the external services it relies on. With Pro, each rebuild produces an SBOM of the components it found. Third-party dependencies
  • Documentation. The instructions a team without the original developers would need. Documentation
  • Designs and other IP. Architecture, technical designs and other proprietary materials behind the software. Technology designs

2. How it stays current

Connect the platforms once and deposits sync daily. With Pro, between rebuilds, we compare the deposit with your live repositories and flag what changed.

  • Somewhere else. See all integrations, or upload materials by hand with Secure Upload. All integrations

3. How you prove it

The base level: Escrow or Resilience. Everything you need to be protected: custody of the deposit, an automated check of what's in it with a vault report, and a Software Resilience Certificate. From $199 per application per month. Which protection?
Pro: proof it builds. Escrow Pro, Resilience Pro and Continuity Pro add Agentic Verification: AI agents rebuild the deposit in the Codekeeper AI Verification Lab, on supported technology stacks, in hours. Four rebuilds a year, with build steps, an SBOM, an Exit workbook, a deployable copy and a Recoverability Certificate. From $449 per application per month. How it works
Add an Exit Exercise. Our specialists rebuild by hand in a clean room, from the deposit alone, and test the business functions you nominate. You get a Tested Exit Report with an annex mapped to your framework. From $12,000, added to any plan. About the Exit Exercise
Start with the base level, then decide. The base level holds and checks the deposit. Pro adds proof it builds. We'll look at what your auditor or customers ask for in a demo. See all prices
Hosting and credentials point to Continuity. If the live service has to stay on, Continuity maps the live environment at setup (where it runs, the accounts it depends on, the services it needs), keeps the map current, and if the vendor stops, keeps it paid and switched on for an agreed period while we recover. Explore Continuity
Book a demoGet the sample evidence pack
Social proof straight after the promise. These are the logos production already uses, loaded from codekeeper.co. Where an image can't load (for example in the preview), the name shows instead. Use the approved set only.

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

Airbus Bayer European Parliament General Motors Intuit Nestlé PepsiCo Pfizer
Step 3, the model: the deposit, part by part. The eight cards are the eight "what we deposit" pages, in the order a rebuild needs them: code, then what turns it into a running system, then what keeps it running, then the knowledge around it. The one-line descriptions follow production's own page intros, without "guarantee" (production's credentials page says "Guarantee your software continuity"). Production files hosting and credentials under "Continuity Escrow Asset"; here they simply link to their pages.

What we deposit

Code is the start. A recovery needs more.

An application is more than its repositories. The deposit holds what a team would need to rebuild it and run it without the original developers.

Source code

The foundation

The repositories the application is built from, connected through the platforms you already use.

Source code

Data

What it runs on

The application data a recovery needs, held in an independent environment.

Data

Deployment assets

From code to a running system

Build scripts, packages and configuration files your teams use to deploy and maintain it.

Deployment assets

Hosting environment

Where it runs

The hosting details and accounts behind the live service.

Hosting environment

Credentials

Access to the providers

The access needed to manage and pay the providers the application depends on.

Credentials

Third-party dependencies

The services it relies on

Configuration, access details and documentation for external APIs, services and libraries.

Third-party dependencies

Documentation

The know-how

Manuals and runbooks, kept current alongside the code.

Documentation

Designs and IP

The thinking behind it

Architecture, technical designs and other proprietary materials.

Technology designs
How the deposit keeps pace, in four steps. Connect, sync, check, rebuild: the platform facts in order. "50+ integrations" is production's figure, kept and flagged (agreed: production stats stay, flagged). The hub has setup pages for 24 platforms and production's grid shows 40, so Product must confirm the real count; "sync daily" is a production claim, flagged until Product confirms it. The monitoring line and the rebuild facts are confirmed (MESSAGING §6). The mock is an example account: repository names are fictional, and the platform names are integrations from production's list, not technology stacks.

Built to stay current

Connect once. The deposit keeps up.

A deposit is only useful if it matches the version you run. Integrations keep it in step without extra work for your team.

1

Connect

Link the platforms where the code and files live, through our 50+ integrations, or upload by hand with Secure Upload.

2

Sync

Deposits sync daily. Add or remove materials at any point.

3

Check

An automated check confirms what's deposited, with a vault report. Missing items are flagged.

4

Rebuild

With Pro, AI agents rebuild the deposit in the Codekeeper AI Verification Lab. We flag changes between runs, so you know when to rebuild again.

Step 4, the proof: the level is the answer to step 3 of the tool. Two cards with the confirmed inclusions (MESSAGING §6) and the lowest software list prices. The base card says "everything you need to be protected" and is never framed as weaker. The Exit Exercise sits under the cards, with its confirmed "from $12,000" price; its unit (per exercise or per application) is still to confirm. 16 Oct: Continuity Pro added; base Continuity no longer includes Agentic Verification: base Continuity joins the base card and Continuity Pro the Pro card.

Then choose the level

Held and checked, or proven to build.

Escrow · Resilience · Continuity

Base level

From$199per application per month

Everything you need to be protected.

  • Custody of the deposit
  • Automated check of what's deposited, with a vault report
  • Software Resilience Certificate
Escrow Pro · Resilience Pro · Continuity Pro

Pro level

From$449per application per month

Everything you need to recover.

  • Agentic Verification: isolated rebuilds by AI agents, on supported technology stacks
  • 4 rebuilds a year, run when you choose
  • Build steps, SBOM, Exit workbook and a deployable copy
  • Recoverability Certificate

Software list prices. Need people to test the business functions too? An Exit Exercise adds a Tested Exit Report, from $12,000, to any plan. See all prices

The secondary conversion, on every page. Visitors who aren't ready to talk can still leave their email. The sample evidence pack is the same offer on every page, so the site has one lead magnet instead of a different e-book per page. It also carries the launch story: proof, not promises. The button goes to the sample evidence pack page.

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
Get the sample evidence pack
The questions tech teams ask. Stacks first, because it's the first technical question, and the answer can't name one: rebuilds run on supported technology stacks, confirmed in a demo. The security answer uses the confirmed Agentic Verification facts (own models, no third-party AI, the Codekeeper AI Verification Lab). "Upload materials by hand" comes from production's credentials page ("clear instructions for manual uploads if needed"); product should confirm it still holds.

Questions

About the technical assessment.

Which technology stacks can you rebuild?

Agentic Verification runs on supported technology stacks. Tell us what your application runs on in a demo, and we'll confirm whether it's covered before you choose Pro.

Does our code leave your environment during a rebuild?

No. Agentic Verification runs on Codekeeper's own models, with no third-party AI, and your code never leaves our environment. Each run happens in the Codekeeper AI Verification Lab, sealed and cut off from production, development and the open internet.

Our platform isn't in the list. Can we still deposit?

Yes. See all integrations, or upload materials by hand. Either way, the automated check confirms what's in the deposit.

How do we know when the deposit is out of date?

With Pro, between rebuilds, we compare the deposit with your live repositories and flag what changed, so you know when to rebuild.

Do we have to deposit credentials?

Deposit what a recovery would need. Credentials and hosting details matter most when the live service has to stay on, which is what Continuity is for.

Do you store my answers?

No. The assessment runs in your browser and sends nothing to us.

The same close on every page. The technical tool closes on the two things it advised on: what goes in, and the proof it builds. Every page ends on the same two actions in the same order: Book a demo, then the sample evidence pack.

Know what to deposit. Know it builds.

Book a demo and we'll plan the deposit for your application with you, and show you a rebuild.

Book a demoGet the sample evidence pack
Chat widget goes here. Production runs HubSpot chat in this corner. Keep it on launch: it catches visitors with a quick question who won't book a demo yet. Route it to sales during office hours.