NewEscrow Pro, Resilience, Continuity and Agentic Verification: from holding the code to proving it comes back.The new line-up is here.See what's new
Why this page exists. Resilience is new: production has no page for it. Escrow releases the deposit to you and you run the recovery; Resilience brings the deposit to Codekeeper and we run it. This page sells that difference, and the two levels.
  • The headline is the canonical line from the launch site: "When it fails, we bring it back."
  • The 56-second Resilience film sits in the hero, as the Escrow Pro film does on the Escrow page. It's the 6 Oct cut (same file as the launch site). Per the 6 Oct notes, its line R3 was re-recorded to drop "Add Continuity"; confirm this file is the re-recorded version before launch. The play button is centred and the title sits under the film, because the poster already carries its own title at the top and a corner label would print over it.
  • The base level is never weak. Resilience is "everything you need to be protected", with the recovery run by us. Its recovery is best effort, which the page says plainly where the inclusions are listed.
Resilience · Resilience Pro

When it fails, we bring it back.

With Resilience, the deposit comes to Codekeeper, and if a critical application fails, we run the recovery. With Resilience Pro, we've proven it builds long before we need it.

Resilience from $399. Resilience Pro from $649. Per application per month.

  • Trusted by 3,500+ teams
  • ISO/IEC 27001:2022 certified
  • 50+ integrations, synced daily

Resilience and Resilience Pro · the film, 56 s

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
Steps 1 and 2: the exposure and the shift, specific to Resilience. The launch line carries the argument: receiving a deposit gives you the code, and someone still has to bring it back. The three cards name why that someone shouldn't have to be you. None of them criticises Escrow; they describe a different job.

Why Resilience

Having the code is the start. Having it back is the goal.

Boards and auditors want to know what happens if a critical application fails. A deposit gives you the code. Someone still has to rebuild it, configure it and run it. With Resilience, that someone is us.

The vendor stops

Insolvency, a takeover or discontinued support. The people who knew how to run the application may go with it.

Your team runs the business

Rebuilding someone else's software under pressure is specialist work. Most teams aren't staffed for it, and shouldn't need to be.

The recovery needs an owner

"Who brings it back?" is the first question in a review. Resilience answers it with a name: Codekeeper.

Step 3, the model: four steps, one sentence each. The arrangement mock makes the job concrete: who deposits, who claims, who recovers. "Claimant" is the agreed noun for whoever relies on the application; one is included. To confirm before launch: what the Resilience Arrangement names as the events that start a recovery (the mock says "recovery conditions", by analogy with Escrow's release conditions). Names in the mock are fictional.

How it works

The deposit comes to us. So does the recovery.

1

Add the application

Vendor software or a system you built yourself: software, SaaS or AI.

2

Put the Resilience Arrangement in place

It names the depositor, the claimants who rely on the application, what's deposited and when recovery starts.

3

Keep the deposit current

Connect once and deposits sync daily. We check what's deposited and issue a Software Resilience Certificate. With Pro, AI agents also rebuild it.

4

If it fails, we bring it back

The deposit comes to Codekeeper and we run the recovery. Recovery work is billed to the claimants who need it.

Two levels, each named by its job, plus the add-ons that change the economics. Inclusions are the confirmed list. Resilience recovery is best effort, said where it's listed, not hidden in a footnote. Cost coverage uses only the agreed wording: the cost of a recovery, under an agreed service level, quoted per arrangement. It is not insurance and must not be called that. To confirm before launch: whether "$299 a month more" for 12 rebuilds is per application (the commercial notes don't say).

Choose your level

Resilience and Resilience Pro.

With both, we run the recovery. Resilience Pro proves the deposit builds before we need it.

Recovered by us

Resilience

From$399per application per month

We recover it. Everything you need to be protected, with the recovery run by Codekeeper.

  • Custody of the deposit
  • Recovery run by Codekeeper, best effort, under a Resilience Arrangement
  • Automated check of what's deposited, with a vault report
  • Software Resilience Certificate
Recovered by us · tested in advance

Resilience Pro

From$649per application per month

Proven before we need it. Everything you need to recover, with the recovery run by Codekeeper.

  • Everything in Resilience
  • 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

Cost coverage

Quoted

The cost of a recovery, under an agreed service level. Quoted per arrangement, for Resilience and Resilience Pro.

12 rebuilds a year

$299 a month more

Twelve rebuilds a year instead of four, for applications that change often.

Setup $499 per arrangement. One claimant included; more as an add-on. Recovery work is billed to the claimants who need it. See full pricing

Step 4, the proof: why Pro matters for a recovery operator. Resilience Pro's line is "Proven before we need it", so the proof section shows exactly that: a run report from a rebuild done months before any failure, with a missing package flagged and added. The checks are confirmed Agentic Verification facts. The duration and run number are example values, labelled as such.

Resilience Pro

Recovery starts from a deposit we know builds.

With Resilience Pro, AI agents rebuild the deposit in a sealed sandbox long before anything goes wrong. When a recovery starts, we aren't finding out how the application builds. We've already done it.

  • Four rebuilds a year included, on supported technology stacks
  • Anything missing is flagged, so the depositor can add it
  • Build steps, an SBOM, an Exit workbook and a deployable copy
  • Codekeeper's own models: your code stays in our environment
Show where Resilience sits, and the step up. The same three-job comparison as on the Escrow and Continuity pages, with Resilience outlined. The lead is the agreed price logic, word for word. Continuity is the answer for applications that can't stop at all, which is also how the re-recorded film now ends.

Same account

Escrow, Resilience or Continuity.

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.

Released to you

Escrow

Deposit→Released to you→You recover

When the agreed conditions are met, the deposit is released to the beneficiary. Explore Escrow

From $199

You're here

Resilience

Deposit→Comes to us→We recover

If the application fails, Codekeeper runs the recovery for you. Resilience Pro proves it builds first.

From $399

Kept switched on

Continuity

Live service kept on+We recover

Everything in Resilience Pro, plus the live environment kept paid and switched on for an agreed period. Explore Continuity

From $1,449

Three buyers for a recovery operator. Adapted from the launch site's "who it's for". The vendor card is new: the commercial model allows a vendor to sponsor the protection (who pays is a billing field), and a recovery run by a neutral party is a stronger answer in due diligence than a release clause alone.

Who it's for

When someone has to actually bring it back.

Risk and compliance leaders

Show that critical applications can be recovered, and name who does it when the vendor is gone.

Operations and IT leaders

Cover the applications your operations run on without staffing a recovery team for each one.

Vendors selling to regulated buyers

Offer customers a recovery with a named operator, not only a release clause, so due diligence moves faster.

The full Resilience price grid, so nobody has to leave the page. These are the Danny-approved list prices of 6 Oct (new customers). The price logic explains why Resilience costs more than Escrow without making Escrow look thin. Exit Exercise "from $12,000" is confirmed, but its unit isn't published: confirm it before launch. Don't add annual or monthly billing or discounts until sales confirms them.

Pricing

Priced per application.

Resilience costs more than Escrow because we do the recovery. Prices differ by the kind of application.

ApplicationPer application per monthResilienceWe recover itResilience ProProven before we need it
SoftwareOn-premise and licensed applications$399$649
SaaSHosted and subscription applications$449$799
AIAI models and AI systems$949$1,149
Setup. $499 per arrangement.
Claimants. One included. More are available as an add-on.
Recovery work. Billed to the claimants who need it.
Cost coverage. The cost of a recovery, under an agreed service level. Quoted per arrangement.
Exit Exercise. From $12,000, as an add-on to any plan. Exit Exercise
Enterprise. Many applications or many claimants? Talk to us for a quote.
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
Objections in the order sales hears them. First "how is this different from escrow?", then "what does best effort mean?" and "who pays?". The best-effort answer is deliberately plain: Resilience alone has no recovery service level, and Cost coverage is how a customer gets one. Legal should confirm that wording, and the answer on internal applications, before launch.

Questions

Before you put recovery in our hands.

How is Resilience different from Escrow?

It's who runs the recovery. With Escrow, the deposit is released to you and your team brings the application back. With Resilience, the deposit comes to Codekeeper and we run the recovery for you.

What does "best effort" mean?

We run the recovery, but Resilience on its own doesn't come with a recovery service level. If you need the cost of a recovery under an agreed service level, add Cost coverage, quoted per arrangement.

Who pays for the recovery work?

Recovery work is billed to the claimants who need it. The list price covers custody, the checks and certificates and, with Resilience Pro, Agentic Verification.

What is Cost coverage?

An add-on for Resilience and Continuity: the cost of a recovery, under an agreed service level. It's quoted per arrangement, based on the application and the recovery it would need.

What does Resilience Pro add?

Agentic Verification. AI agents rebuild the deposit in a sealed sandbox up to four times a year, with no help from the vendor. Each successful rebuild issues a Recoverability Certificate, with build steps, an SBOM, an Exit workbook and a deployable copy. When a recovery starts, we already know the deposit builds.

Which technology stacks can you rebuild?

Rebuilds run on supported technology stacks. Tell us what you run and we'll confirm coverage during the demo.

Can we use Resilience for applications we built ourselves?

Yes. An application can be vendor software or a system your own team built. What matters is that your business can't lose it.

What if the application can't stop at all?

That's Continuity: everything in Resilience Pro, plus we keep the live environment paid and switched on for an agreed period while we recover.

The same close on every page. The close repeats the page's promise in one line: a recovery with an owner, for the applications you can't lose. Every page ends on the same two actions in the same order: Book a demo, then the sample evidence pack.

Put recovery behind the applications that matter.

We'll walk through Resilience, Resilience Pro and Cost coverage for your stack.