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
Why this page looks like this. Production's /source-code-escrow sells source code as "one of the asset types included within Codekeeper's Software Escrow solution". In the new model there is no Software Escrow product: source code is the first of eight materials a deposit can hold, under any protection. The page explains what it is, why recovery fails without it, how it gets in, how it's proven and which protection to attach.
  • One template for all eight "What we deposit" pages, as production has: hero, why it matters for recovery, what's included, how it gets in and how it's proven, which protection fits, the other seven materials, the evidence pack, FAQ and close. Every page follows the same fictional SaaS application, Booking Hub (also on the SaaS escrow page), so the set reads as one story: one application needs several kinds of material to come back.
  • Headline: keeps the search phrase and states the shift in five words. The code is "the start of getting it back", not the whole of it, which sets up the other seven pages.
  • Visual: a mock of what this part of the deposit holds. Production's hero image couldn't be opened from the kit to check it for old product names, so it isn't reused; swap it back only after someone has checked it.
  • Dropped: "Book a free demo" (now Book a demo), the closing line "Let's build bulletproof software resilience together", the press quotes with publication logos (Product Hunt and two others; not customer reviews, and the logos need permission), the third-party tool logos, the per-page e-book block (the sample evidence pack band replaces it) and "Unlimited automated deposits", "Assured recovery support" (retired name) and "start from $125 per month" (old price; production's Software Escrow page says $139).
What we deposit

Source code escrow. The start of getting it back.

Every recovery starts with the code. Codekeeper holds the repositories your application is built from, keeps them current and checks what's there, and with Pro, AI agents rebuild it so you know it builds.

From $199. Per application per month, with the protection you choose.

  • Trusted by 3,500+ teams
  • ISO/IEC 27001:2022 certified
  • AES-256 encryption at rest
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, for source code. Production asks four questions ("What happens if access to your source code becomes unavailable?", "Where would your team start…") and closes with "Unprotected source code puts delivery, trust, and reliability at risk for everyone involved." Here the exposure is named once in the lead, and the comparison carries the canonical shift: having the code is the start, having it back is the goal. Production's "Without / With source code escrow" list is reworded; "A clear, contract-based recovery path is always available" and "Your software remains protected for its entire life cycle" are absolutes and are gone.

Why it matters for recovery

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

If the vendor stops, the people who know the code can go with it. Without the source, nobody can fix a fault, patch a vulnerability or move the application elsewhere. And a copy of the code only helps if it's complete, current and checked.

A copy of the code

  • Sent once, then out of date
  • Some repositories missing, and nobody has checked
  • Whether it builds is found out on the day you need it

Source code with Codekeeper

  • Every repository the application needs, kept current through integrations
  • An automated check of what's there, with a vault report and a Software Resilience Certificate
  • With Pro, rebuilt by AI agents in the Codekeeper AI Verification Lab, with a Recoverability Certificate
Step 3 in detail: what a source code deposit holds. The contents are production's ("the source code and any additional files specified in the agreement") plus scripts and in-house libraries, as the SaaS escrow page lists them. Choosing branches comes from the FAQ's GitHub answer. Production's FAQ says build instructions "fall under software escrow"; in the new model they have their own page (deployment assets), linked here. The key-facts box is the same on all eight pages, and "Usually part of" agrees with the Software, SaaS and AI escrow pages. To confirm: "every deposit is logged with its version" (production's version history claim, listed in to-confirm).

What's included

What a source code deposit holds.

The agreement lists exactly what's deposited. For most applications, that means:

  • Every repository the application needs. Services, front ends, mobile apps and shared code, with the branches you choose.
  • Scripts and libraries. The scripts, in-house packages and libraries the code depends on.
  • A record of each deposit. Every deposit is logged with its version, so you know which release is held.
  • Anything else the agreement lists. Build files and documentation usually sit alongside: see deployment assets and documents.
Usually part of
Software, SaaS and AI deposits
How it gets in
Repository integrations, or secure upload
How it's checked
Automated check, with a vault report
How it's proven
With Pro, a rebuild in the Codekeeper AI Verification Lab
Steps 3 and 4: from the repository to the proof. The four named integrations are production's (their logos sit on the production page) and each has its own integration page in the kit. "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.md. "Sync daily" is a production claim, flagged. Production's "ensuring every version is captured" is dropped as an absolute. The proof steps are confirmed facts: an automated check with a vault report and a Software Resilience Certificate with every protection; on Escrow Pro, Resilience Pro and Continuity Pro, Agentic Verification (the Codekeeper AI Verification Lab, no vendor help, hours, missing items flagged, monitoring between runs). The ladder is the agreed proof ladder, kept short; its last line keeps the agreed wording on release rights. The mock shows the "flagged, then added" case the run reports elsewhere on the site show. 16 Oct: Continuity Pro added; base Continuity no longer includes Agentic Verification, so step 3 and the ladder name Continuity Pro.

How it gets in, and how it's proven

Connect the repositories once. Get proof every time.

Deposits arrive through integrations or secure upload. Each one is checked, and with Pro, rebuilt.

1

Connect or upload

Connect GitHub, GitLab, Bitbucket, Azure DevOps or another of our 50+ integrations, and deposits sync daily. Code that lives anywhere else can be uploaded securely.

2

Checked and certified

An automated check confirms what's in the deposit, with a vault report, and you receive a Software Resilience Certificate.

3

Rebuilt, with Pro

With Escrow Pro, Resilience Pro and Continuity Pro, AI agents rebuild the code in the Codekeeper AI Verification Lab, with no help from the vendor, in hours. Anything missing is flagged so it can be added.

4

Watched between runs

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

Escrow · Resilience · Continuity

Software Resilience Certificate

The source code is held, and an automated check confirms what's in it, with a vault report.

Proves: it's there.

Escrow Pro · Resilience Pro · Continuity Pro

Recoverability Certificate

AI agents rebuild the application from the deposit in the Codekeeper AI Verification Lab, with no help from the vendor, in hours. You also get the run report, an SBOM and an Exit workbook.

Proves: it builds. Agentic Verification

Add-on to any plan

Tested Exit Report

Our specialists rebuild by hand in a clean room and test the business functions you nominate, without the original developers.

Proves: you could exit and keep working. Exit Exercise

The higher you go, the more it proves. The Recoverability Certificate documents the rebuild; release rights come from the agreement. How verification works

Step 3 continued: which protection to attach. The three-job cards appear on every deposit page, each with one line on what that job means for this material on the day it's needed. The "from" prices are the 6 Oct list (Software row); the lead is the price logic sentence, word for word. Every protection holds source code, so no card is outlined. 16 Oct: Continuity Pro added; base Continuity no longer includes Agentic Verification; Continuity Pro (from $1,699, setup $999) joins the other Pro levels in the fine print. 17 Oct: the recovery models are named, as in the launch film (Danny): Self-Run Recovery for Escrow, Managed Recovery for Resilience and Continuity.

Which protection fits

Choose what happens to the code when it's needed.

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

Released to you→Self-Run Recovery

If a release condition is met, the code is released to you, and your team, or a partner you choose, rebuilds the application. Explore Escrow

From $199

Recovered by us

Resilience

Comes to us→Managed Recovery

The code comes to Codekeeper, and we rebuild and recover the application for you. Explore Resilience

From $399

Stays online

Continuity

Live service kept on+Managed Recovery

We recover from the code while the live environment stays paid and switched on for an agreed period. Explore Continuity

From $1,449

Software list prices, per application per month; SaaS and AI have their own rows. Escrow Pro (from $449), Resilience Pro (from $649) and Continuity Pro (from $1,699) add Agentic Verification. Setup is $499 per arrangement, or $999 for Continuity and Continuity Pro. See all prices

Close the loop on the story: one application, eight kinds of material. Production's "Cover your full software infrastructure" block links to only two to five of the other asset pages, and files them under three old products (Software, SaaS and Continuity Escrow). Here all eight appear in the same order on every page, with this one marked, because one application usually needs several of them to come back. The order follows a recovery: what it's built from, how it's built, what it runs on, how to run it, what it calls, the thinking behind it, where it runs and the keys to it. The names match the footer. The links underneath go to the application pages, which say which materials each application type usually deposits, and to the guides hub instead of production's per-page e-book block.
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 people search for, reworded from production's nine. Kept: what it is, who pays (production's answer), security and cost. Removed: "$125 per month" (old price), "Various Verification levels are available as add-ons" (Agentic Verification replaces them), "stored in ISO 27001-aligned environments" (we're certified, so we say so) and "Getting started is simple". New: whether code alone is enough, which is the point of this page. The explainer page goes deeper for searchers who want the basics. 16 Oct: Continuity Pro added; base Continuity no longer includes Agentic Verification; the price answer adds Continuity Pro (from $1,699, setup $999).

Questions

Source code escrow, answered.

What is source code escrow?

An agreement in which a software vendor deposits its source code, and the materials needed to use it, with a neutral party such as Codekeeper. If an agreed release condition is met, for example the vendor's insolvency or discontinued support, the deposit is released to the beneficiary so recovery work can begin. Until then, the vendor's IP stays private. What is source code escrow?

Is source code enough to recover an application?

Rarely on its own. A rebuild also needs build scripts and configuration, usually data and documentation, and for SaaS the hosting environment and access. That's why a deposit can hold all of them. With Pro, Agentic Verification shows whether what's deposited builds.

Who pays for source code escrow?

It depends on the commercial arrangement. Sometimes the vendor pays, as part of delivering the software. Sometimes the customer pays, as part of procurement or risk management. Some contracts share the cost.

Is our code safe with you?

Codekeeper is ISO/IEC 27001:2022 certified. Deposits are encrypted at rest with AES-256 and in transit with TLS. Agentic Verification runs on our own models in the Codekeeper AI Verification Lab, cut off from production, development and the open internet. See the Trust Center.

How much does it cost?

Prices are per application per month, by the protection you choose. For a software application: Escrow from $199, Escrow Pro from $449, Resilience from $399, Resilience Pro from $649, Continuity from $1,449 and Continuity Pro from $1,699. SaaS and AI have their own rows. Setup is $499 per arrangement, or $999 for Continuity and Continuity Pro. See pricing

The same close on every page. The close repeats the page's promise in two steps: the code is the start, and proof that it comes back is the goal. Every page ends on the same two actions in the same order: Book a demo, then the sample evidence pack.

Start with the code. Prove it comes back.

We'll look at your repositories and show you what a deposit, and a rebuild, would cover.

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.