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 /data-escrow sells data as "one of the asset types included within Codekeeper's broader Software Escrow offering". In the new model it's one of eight materials a deposit can hold, under any protection. Data touches privacy, so the page states only confirmed security facts and adds a pointer to the data processing agreement for personal data.
  • 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 names the outcome: the application comes back with its data, not empty.
  • 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).
What we deposit

Data escrow. So it comes back with its data.

An application without its data comes back empty. Codekeeper holds the database exports, schema, reference data and files your application needs, kept current and checked, under the terms your agreement sets.

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 data. Production asks four questions ("What happens if essential application data becomes unavailable?"…) and closes with "even minor gaps can stall operations, delay recovery, and create costly setbacks". Here the exposure is one calm sentence: a rebuilt application without its data comes back empty. Production's "With data escrow" list ("Recovery becomes clearer, faster, and more predictable", "Both sides gain confidence") is replaced by what the deposit does.

Why it matters for recovery

An application without its data comes back empty.

Code and build files bring the system back. Its data makes it useful: the records, settings and reference tables it runs on. If the vendor holds the only copy, a recovery can rebuild the application and still leave your team without the information it needs.

A deposit without data

  • The application rebuilds, but starts empty
  • Reference and configuration data recreated by hand
  • No record of which export is held, or how old it is

Data with Codekeeper

  • The datasets the agreement lists, held with the code
  • Kept current through integrations or regular uploads
  • Checked with the rest of the deposit, with a vault report and a Software Resilience Certificate
Step 3 in detail: what a data deposit holds. The groups are production's ("configuration files, structured exports, or reference data", "application-generated files") plus the schema, which the Software escrow page lists. Production capability claim to confirm: which databases. Production shows MySQL, Redis, PostgreSQL, Oracle, MongoDB, AWS RDS, Google Cloud and SQL logos; the page says it in plain words ("relational or NoSQL, self-hosted or managed in the cloud") and shows no logos. Production's "Codekeeper validates structure and completeness to ensure the deposit is usable" says more than the confirmed automated check, so the page uses the confirmed wording. For legal: the personal data note is new. It makes no handling claim beyond pointing to the existing data processing agreement; no retention period is stated.

What's included

What a data deposit holds.

The agreement lists exactly which datasets are deposited, and how often they're updated. For most applications, that means:

  • Database exports. From the databases the application runs on, relational or NoSQL, self-hosted or managed in the cloud.
  • Schema. The structure the data lives in, so it can be restored into a rebuilt application.
  • Reference and configuration data. Reference tables, settings and configuration files.
  • Application files. Files the application creates or stores, where the agreement includes them.
Usually part of
Software, SaaS and AI deposits
How it gets in
Cloud and storage integrations, or secure upload
How it's checked
Automated check, with a vault report
How it's proven in use
Functional tests in an Exit Exercise
Personal data? Deposit only what a recovery needs, and agree the scope with your data protection team first. Codekeeper's data processing agreement sets out how we process personal data.
Steps 3 and 4: from the data store to the proof. Amazon S3, Azure and Google Cloud have integration pages in the kit; the FAQ already says that for AWS and similar platforms "you give us the details, such as bucket names or URLs, and we pull in what's needed". "Sync daily" is a production claim, flagged. 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 rebuild proves the application builds; whether a run also restores the data is not confirmed, so the page doesn't say it does. Testing the application with its data in use is what the Exit Exercise does (functional tests on nominated business functions), so step 4 says that. 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

Exported on a schedule. Checked every time.

Exports arrive through cloud and storage integrations or secure upload, on the schedule the agreement sets. Then they're checked with the rest of the deposit.

1

Connect or upload

Connect the storage where your exports land, such as Amazon S3, Azure or Google Cloud, and deposits sync daily. Or upload exports 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 rebuild the application the data belongs to in the Codekeeper AI Verification Lab, cut off from production, development and the open internet. Anything missing is flagged.

4

Tested in use, with an Exit Exercise

To test the rebuilt application with its data, our specialists rebuild it by hand in a clean room and test the business functions you nominate.

Escrow · Resilience · Continuity

Software Resilience Certificate

The datasets 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. 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, with your data, 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 can hold data, so no card is outlined. The Continuity line says the live environment, including its database, stays on; that matches the Continuity map, which includes the database. 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 restores the data.

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 data is released to you with the code, so your team can restore it into the rebuilt application. Explore Escrow

From $199

Recovered by us

Resilience

Comes to us→Managed Recovery

The data comes to Codekeeper, and we use it in the recovery we run for you. Explore Resilience

From $399

Stays online

Continuity

Live service kept on+Managed Recovery

The live environment, database included, stays paid and switched on for an agreed period while we recover. 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.

Deployment assets escrow

Data

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

You're on this page

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
The questions buyers ask about data, and the privacy one they should. Kept from production: what it is and what to deposit. New: personal data (for legal to review), security (confirmed facts only: no handling detail or retention period beyond MESSAGING §6) and how it differs from a backup, because "data escrow" and "backup" are often confused and Backup is a peer protection with its own page. Removed: "$125 per month", "stored in ISO 27001-aligned environments" and "Getting started is simple".

Questions

Data escrow, answered.

What is data escrow?

An agreement in which a software provider deposits the data its application needs with a neutral party such as Codekeeper. If an agreed release condition is met, the data is released to the beneficiary, so they can restore, support or move the application without losing it.

Which data should we deposit?

What a recovery would need: usually database exports and schema, reference and configuration data, and the files the application relies on. The agreement lists the datasets and how often they're updated.

Can the deposit include personal data?

It can, if the agreement includes it. Agree the scope with your data protection team first, and deposit only what a recovery needs. Codekeeper's data processing agreement sets out how we process personal data.

Is our data secure 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.

Is data escrow the same as a backup?

No. A backup restores systems you run yourself. Data escrow holds a vendor's data under an agreement, for a recovery when a condition is met. For copies of your own systems, see Software Backup.

The same close on every page. The close repeats the headline's outcome: an application that comes back with its data, not empty. Every page ends on the same two actions in the same order: Book a demo, then the sample evidence pack.

Bring it back with its data.

We'll look at what your application runs on and which datasets a recovery would need.

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.