European Union
Global standards
US
UK
Australia
Netherlands
01 · Software users
You rely on the software.
Asked by auditors, risk teams, and your board.
- Know the software you depend on can be rebuilt
- Answer audit and risk reviews with dated evidence
- Spot gaps while the vendor can still fix them
Agentic Verification. Proof your software builds. In hours, not weeks.
AI agents take your escrow deposit into a sealed lab, work out how it's built, and build it. Every passed run issues a Recoverability Certificate, with the date on it.
Included in Escrow Pro, Resilience Pro, Continuity Pro, and Software Backup Pro. Up to four runs a year, on supported technology stacks.
- Codekeeper's own AI, off public models
- Sealed off from the internet
Payments Core · Run #11
Escrow Pro · Codekeeper AI Verification Lab
- Pre-flight checkStack matched
- Seal the environmentSealed
- Restore the depositRestored
- Work out the build1 private package resolved
- Isolated compileCompiled from source
- Start and checkHealth checks passed
- Write the evidence4 documents
Passed · Sep 3, 2026
Recoverability Certificate issued
Trusted by 3 500+ teams in over 150 countries, from regulated enterprises to fast-growing software vendors
What's new
Rebuild tests used to be a project. Now they're a button.
A manual build test means weeks of specialist work, engineers to book, and quotes to approve, so it was priced for the largest contracts. Agentic Verification runs in hours, whenever you press run, up to four times a year, included in every Pro plan.
Side by side with a typical manual build test
Before
A typical manual build test
Specialists, booked per engagement
- TimeWeeks of specialist work
- Starting a testEngineers to book, quotes to approve
- CostPriced for the largest contracts
- The vendorOften relies on the vendor's engineers
- EvidenceA report at the end of the engagement
Now
Agentic Verification
AI agents, in the Codekeeper lab
- TimeHours
- Starting a testPress run, whenever you choose
- CostUp to four runs a year included, on supported technology stacks
- The vendorNo vendor help on a complete deposit
- EvidenceA report for every run, and a certificate for every passed run
Need specialists to recover the software and test the functions you nominate? That's an Exit Exercise.
Inside a run
Press run. The agents do the rest.
From your deposit to a certificate, with nobody to book. Up to four runs a year, on supported technology stacks, started whenever you choose.
- 1
Pre-flight check
The agents read the deposit and match each part to a supported technology stack.
- 2
Seal the environment
A clean environment opens in the lab, for this run only.
- 3
Restore the deposit
Repositories and documents come back as deposited.
- 4
Work out the build
The agents study how it's built and resolve its dependencies, private packages included.
- 5
Isolated compile
The software is compiled from source, inside the sealed environment.
- 6
Start and check
Services start, and health checks confirm the application runs.
Write the evidence
Rebuild Report, SBOM, and exit workbook. A pass adds the Recoverability Certificate.
Illustration of a typical run. The exact steps depend on the technology stack.
Not sure your stack is supported? Take the free technical assessment: tell us how your application is built, and our escrow engineers will recommend what to deposit and which verification level you need.
Starting a run
Start it whenever you choose.
- Start a run whenever you choose: before an audit, after a release, or when the deposit changes.
- No engineers to book and no quotes to approve.
- Between runs, we compare the deposit with the live repositories and flag what's changed, so you know when to run again.
What you get
Four documents. One answer you can hand over.
Every passed run adds a dated set to your record, each document answering a question someone will put to you.
Recoverability Certificate
Did it build, and when?
The application, the result, and the date, on one page you can hand to an auditor or a client.
Rebuild Report
How did it build?
Each step the agents took, what compiled, and anything that was missing.
SBOM
What's inside it?
Every component the build used, direct and transitive, with versions and licenses, in CycloneDX.
More about SBOMs →Exit workbook
How would we recover it ourselves?
The recovery, step by step, written from the run: environment, deposit, build, configuration, and checks.
Plus a tested isolated compile
Is it ready to deploy?
Every passed run also produces a ready-to-deploy build. It's held with the deposit until a release, when the software user gets it.
See the evidence before you talk to us.
The sample evidence pack holds the Recoverability Certificate and Rebuild Report from one example run, with SBOM and exit workbook excerpts, all with example values.
Who it's for
Proof for both sides of the agreement.
The software user and the vendor get the same dated evidence from the same run.
02 · Software vendors
You build the software.
Asked in client security reviews and procurement.
- Answer client security reviews with a certificate
- Show what's in your deposit before a client asks
- Get an exit workbook that shows clients their recovery is already planned
When a run finds a gap
Found a gap? You found it early.
The Rebuild Report names it, the vendor adds it to the deposit, and you run again.
Run #10Payments Core1 item flagged
- Pre-flight check
- Deposit restored
- Dependenciesledger-core 4.2, a private package, isn't in the deposit
Flagged in the Rebuild Report for the vendor
- Sep 1Vendor notified
- Sep 2Package added to the deposit
Run #11Payments Core · Sep 3, 2026Passed
- Dependencies resolvedIncluding 1 private package
- Isolated compile
- Started, health checks passed
Recoverability Certificate issued
Example values, the same example as in the sample evidence pack.
Security
Sealed. Private. Our own AI.
Your code stays in Codekeeper's environment. Runs use Codekeeper's own AI, which keeps your code off public models, and each run is sealed off.
Codekeeper AI Verification Lab
A sealed environment for each run. Inside it:
- Your deposit
- Codekeeper's AI agents
- Codekeeper's own models
No connection to
- Production systems
- Development systems
- The open internet
- Public AI models
Own models, own infrastructure.
The agents run on Codekeeper's models, in Codekeeper's environment.
The vendor stays in control.
The vendor can add or remove materials at any point, and a run uses only what's there.
Independently certified.
Codekeeper is ISO/IEC 27001:2022 certified.
Plans
Included in every Pro plan.
Escrow Pro, Resilience Pro, and Continuity Pro, each with up to four runs a year, on supported technology stacks, and the full set of evidence. Choose by how you want to recover. Software Backup Pro includes it too, for the software your own team builds and runs.
| Plan | Softwarefrom | SaaSfrom | AIfrom |
|---|---|---|---|
 Escrow ProSelf-Run RecoveryThe deposit is released to you, and your team runs the recovery. | $419 | $599 | $1,019 |
 Resilience ProManaged RecoveryThe deposit comes to Codekeeper, and Codekeeper's engineers run the recovery. | $599 | $789 | $1,299 |
 Continuity ProFull ContinuityOn Escrow Pro or Resilience Pro, the live environment is kept paid and switched on for an agreed period, with bills recharged at cost. | $1,569 | $1,799 | $2,219 |
 Software Backup ProYour own softwareFor the applications your own team builds and runs, backed up in an immutable vault outside production. | $319billed annually | Not offered | Not offered |
One-time setup: $499 per agreement for Escrow Pro and Resilience Pro, $999 for Continuity Pro, and $249 for Software Backup Pro.
Escrow, Resilience, and Continuity include the monthly automated check, with a Vault Report and a Vault Certificate, but no rebuilds.
Have the answer ready before anyone asks.
See a run on one of your own applications, or start with the sample evidence pack.
Frequently asked questions
Before your first run.
What is Agentic Verification?
Agentic Verification is the rebuild test included in every Pro plan. Codekeeper's AI agents rebuild your deposit in the Codekeeper AI Verification Lab and document what happened, and a passed run issues a Recoverability Certificate.
Does our code go to a public AI model?
No, your code doesn't go to a public AI model. The agents run on Codekeeper's own AI and infrastructure, and your code stays in our environment throughout.
Does the vendor have to help?
The vendor doesn't have to help when the deposit is complete. The agents work from what's deposited, and if something's missing, the run flags it and the vendor adds it.
Which technology stacks are supported?
We confirm which technology stacks are supported for your application in the demo, so tell us what it's built with. Each run's pre-flight check also matches every part of the deposit to a supported stack before the build starts.
How often can we run it?
You can run Agentic Verification up to four times a year on each Pro plan, on supported technology stacks. You decide when, so a run can land right before an audit or right after a major release.
Is the Recoverability Certificate a compliance certificate?
No, the Recoverability Certificate isn't a compliance certificate. It records that the deposit built, and when. You can add it to the evidence for an audit or a review, but whether it meets a particular requirement is for you and your assessor to decide.
What if a run doesn't pass?
If a run doesn't pass, the Rebuild Report shows how far the build got and what it was missing. Once the vendor adds the missing parts, start a new run.
How is this different from an Exit Exercise?
Agentic Verification and an Exit Exercise answer different questions. Agentic Verification answers whether the deposit builds. An Exit Exercise answers whether you could exit and keep working: Codekeeper specialists rebuild the software independently of the vendor, bring back the data, deploy it, and test the business functions you nominate. You can add one to any plan.