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 /deployment-assets-escrow files build and deployment materials under "SaaS Escrow", while the Software escrow page lists them for on-premise software too. In the new model they're one of eight materials a deposit can hold, for any application type.
  • 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 says what the material does in recovery: it's how the code gets built and becomes a running system.
  • 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", "start at $195 per month" (old price; production's SaaS pages say $199 and $179) and the month-to-month billing claim (not stated for the new list).
What we deposit

Deployment assets escrow. How the code gets built.

Source code doesn't deploy itself. Codekeeper holds the build scripts, pipelines, infrastructure definitions and packages that turn it into a working application, kept current, checked and, with Pro, used in a rebuild.

Book a demo Get the sample evidence pack

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 deployment assets. Production frames the risk around the vendor's own delivery ("How do teams release new versions if deployment files are missing?") and closes with "teams face delays, handover friction, and gaps in operational understanding". Here it's framed around recovery, which is the story of the site. Production's "Without / With" list repeats the source code page ("Approval processes slow down", "Software decisions are easier and faster to approve"), template text, so it's rewritten for this material.

Why it matters for recovery

Code that can't be built is only half a deposit.

Build steps often live in pipelines, scripts and the memory of a few engineers. If the vendor stops, the code may be in the deposit while the way to build and deploy it is not. Then a recovery starts with reverse-engineering.

Source code without its build

  • Pipelines and build scripts left behind in the vendor's tools
  • No record of the environment the application expects
  • Every missing step found by trial and error

Deployment assets with Codekeeper

  • Build scripts, pipeline configuration and infrastructure definitions held with the code
  • Checked with the rest of the deposit, with a vault report and a Software Resilience Certificate
  • With Pro, a rebuild that writes up the build steps, so the next team doesn't start from scratch
Step 3 in detail: what a deployment assets deposit holds. The four groups are production's FAQ list ("build scripts, deployment packages, container images, IaC files, CI/CD configurations, orchestration manifests, environment requirements"), grouped. "Usually part of" agrees with the application pages: Software lists build and deployment assets, SaaS lists infrastructure and deployment, AI lists model deployment settings. Production capability claim to confirm: container images, and "connect your build, storage, or container registry tools". The page says packages and images can be included where the agreement lists them and shows them as uploads, until product confirms a registry integration.

What's included

What a deployment assets deposit holds.

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

  • Build scripts and pipeline configuration. CI/CD definitions and the scripts that compile, test and package the code.
  • Infrastructure-as-code. Environment definitions and orchestration manifests that recreate where the application runs.
  • Deployment packages. Release artefacts and container images, where the agreement includes them.
  • Environment requirements. Runtime versions, configuration and the settings needed to get it running.
Usually part of
Software, SaaS and AI deposits
How it gets in
With the code through integrations, or secure upload
How it's checked
Automated check, with a vault report
How it's proven
With Pro, a rebuild that writes up the build steps
Steps 3 and 4: from the pipeline to the proof. Pipeline files and infrastructure definitions usually live in the same repositories as the code, so they arrive through the same integrations. "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. "Every update is logged automatically" is production's; it's covered by the flagged version-record claim on the source code page. 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. Build steps are a confirmed Agentic Verification deliverable, which makes this the material where the rebuild says the most. 16 Oct: Continuity Pro added; base Continuity no longer includes Agentic Verification, so the Recoverability Certificate rung names Continuity Pro.

How it gets in, and how it's proven

Deposited with the code. Proven by a rebuild.

Most deployment assets live next to the code, so they arrive the same way. Then they're checked, and with Pro, used in a rebuild.

1

Connect or upload

Pipeline files and infrastructure definitions in your repositories arrive with the code through our 50+ integrations and sync daily. Packages and anything 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

AI agents work out how the application is built and rebuild it in the Codekeeper AI Verification Lab, in hours. The run writes up the build steps, and 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 build and deployment files are held with the code, and an automated check confirms what's there, 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, and write up the build steps. 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 needs these files to rebuild, so no card is outlined. 16 Oct: Continuity Pro added (from $1,699, 11 Oct list) to the note under the cards, and the lead gains the agreed closing sentence of the price logic. 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 who follows the build steps.

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. At every protection, Pro adds Agentic Verification.

Released to you

Escrow

Released to you→Self-Run Recovery

The deployment assets are released to you with the code, so your team can follow the same build and deploy steps. Explore Escrow

From $199

Recovered by us

Resilience

Comes to us→Managed Recovery

They come to Codekeeper, and we use them to bring the application back for you. Explore Resilience

From $399

Stays online

Continuity

Live service kept on+Managed Recovery

We rebuild from them 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. 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.

Everything else we deposit

One application. Eight kinds of material.

An application usually needs more than one of these to come back. The agreement lists which ones your deposit holds, and they're checked together.

Source code

The codebase, scripts and libraries the application is built from.

Source code escrow

Deployment assets

Build scripts, pipelines and infrastructure definitions that turn code into a running system.

You're on this page

Data

Database exports, reference data and the files the application needs to work.

Data escrow

Documents

Installation guides, architecture and runbooks: how to build, run and support it.

Document escrow

Third-party dependencies

What it takes to maintain or replace the services and packages it relies on.

Third-party dependencies escrow

IP and designs

The designs, diagrams, algorithms and research behind the application.

IP escrow

Hosting environment

Where it runs and the accounts it depends on, mapped and kept current.

Hosting environment escrow

Credentials

The logins, billing roles and keys needed to manage where it runs.

Credentials escrow
What a software deposit holds What a SaaS deposit holds What an AI deposit holds Guides and case studies
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
Production's questions that still apply, reworded. Kept: what it is, how it differs from source code (production asked how it differs from SaaS Escrow, an old product), what can be stored, and cost. New: what a rebuild returns, using the confirmed deliverables only, including the agreed line on the deployable copy (held by the depositor; the customer gains access on a release event). Removed: "$195 per month" and "Codekeeper performs structural checks", which says more than the confirmed automated check. 16 Oct: Continuity Pro added; the rebuild answer names the Pro levels only, and the price answer adds Continuity Pro (from $1,699, setup $999).

Questions

Deployment assets escrow, answered.

What is deployment assets escrow?

An agreement in which the vendor deposits the materials that define how its software is built and deployed: build scripts, pipeline configuration, infrastructure definitions and packages. Codekeeper holds them with the source code, and if a release condition is met, they're released with the rest of the deposit.

How is it different from source code escrow?

Source code is what the application is made of. Deployment assets are how it's assembled and where it runs. A recovery needs both, so they're usually deposited together. Source code escrow

Can you hold container images and infrastructure-as-code?

Yes, where the agreement includes them. Infrastructure definitions usually sync with your repositories; packages and container images can be uploaded securely.

What does a rebuild give us?

With Escrow Pro, Resilience Pro and Continuity Pro, each run returns a report, the build steps, an SBOM and an Exit workbook, and a successful run issues a Recoverability Certificate. The deployable copy it creates is held by the depositor, and the customer gains access to it on a release event.

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 names the gap this page exists for: the build and deploy steps belong in the deposit next to the code. Every page ends on the same two actions in the same order: Book a demo, then the sample evidence pack.

Keep the way it's built with the code.

We'll look at how your application is built and deployed, and what a deposit would hold.

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.