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 /hosting-environment-escrow is a "Continuity Escrow Asset" that promises to "keep hosting services active until normal operations resume" and "keep environments online". In the new model, the job belongs to Continuity, in its agreed wording: we map the live environment at setup, keep the map current and, if the vendor stops, keep it paid and switched on for an agreed period while we recover, with the bills recharged at cost. No duration and no uptime are promised. Hands-on operation isn't mentioned: the brief keeps it to the Continuity and Pricing pages.
  • 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 two halves of the job: mapped in advance, kept online. The sub adds "for an agreed period" straight away, so the headline never reads as an uptime promise.
  • Price: Continuity is the natural fit, so the hero shows its "from" price and setup (6 Oct list).
  • 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. 16 Oct: the mock is labelled Continuity Pro, because only Continuity Pro reviews the map with each rebuild.
  • 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", "If hosting fails, your application goes down with it" (fear line), "Managed funding for critical hosting… keeping environments online", "so the application keeps running without interruption", the nine cloud provider logos and "start at $415 per month".
What we deposit

Hosting environment escrow. Mapped in advance. Kept online.

A SaaS application runs on hosting, cloud accounts and services its vendor pays for. With Continuity, we map that live environment at setup, keep the map current and, if the vendor stops, keep it paid and switched on for an agreed period while we recover.

Book a demo Get the sample evidence pack

Continuity from $1,449. Per application per month. Setup $999 per arrangement.

  • 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 the hosting environment. Production asks "What happens if your hosting environment becomes unreachable?" and answers "If hosting fails, your application goes down with it." The exposure is kept as a plain fact (someone has to pay for where the application runs) and matches the Continuity page ("A bill goes unpaid", "One lapse switches off the rest"). The right-hand column is the confirmed Continuity wording, item by item. Production's "Hosting accounts remain funded and active", "Trust improves because both sides know hosting will remain stable" are gone. 16 Oct: Continuity Pro added; only Continuity Pro reviews the map with each rebuild.

Why it matters for recovery

An application runs only while someone pays for where it runs.

The vendor pays for the hosting, cloud accounts and domains your application runs on. If the vendor stops, so do the payments, and a suspended account can take the live service offline long before a recovery is finished.

Hosting left to the vendor

  • Accounts, billing and admin access held only by the vendor
  • No record of where the application runs, or what it depends on
  • A lapsed bill or an expired domain takes the service offline

The hosting environment with Codekeeper

  • Where it runs, the accounts it depends on and the services it needs, mapped at setup
  • The map kept current, reviewed when the deposit changes and, with Continuity Pro, with each rebuild
  • With Continuity, kept paid and switched on for an agreed period while we recover, with bills recharged at cost
Step 3 in detail: what goes into the map and the deposit. The groups are production's FAQ list ("hosting account credentials, IAM roles, billing information, contact details, environment configurations") arranged under the confirmed map wording (where it runs, the accounts it depends on, the services it needs). Admin and billing access is deposited as credentials, which has its own page. Production capability claim to confirm: which platforms. Production shows AWS, Google Cloud, IBM Cloud, Azure, Oracle Cloud, Alibaba Cloud, DigitalOcean, Rackspace and Heroku logos; the page says "major cloud platforms and hosting providers". Whether customers can see the map in the app isn't confirmed, so the page doesn't say so; "Live environment map" as a customer deliverable is also open (to-confirm). 16 Oct: the review with each rebuild is Continuity Pro only.

What's included

What we map, and what's deposited.

At setup, we go through the live environment with you. The arrangement lists what's in scope. For most SaaS applications, that means:

  • Where it runs. The hosting platform, regions and services the application uses.
  • The accounts it depends on. Cloud and hosting accounts, who owns them and how they're billed.
  • Environment configuration. Infrastructure definitions and settings, so the application can also be rebuilt elsewhere.
  • Contacts and access. Account contacts, and the admin and billing access we agree to hold, deposited as credentials.

That covers the major cloud platforms and hosting providers.

Usually part of
SaaS deposits, with Continuity
How it gets in
Mapped with you at setup, then kept current
How it's kept current
Reviewed when the deposit changes, and with each rebuild on Continuity Pro
Natural fit
Continuity
Steps 3 and 4: from setup to proof. The map is the confirmed Continuity process: mapped at setup, kept current, reviewed when the deposit changes and, with Continuity Pro, with each rebuild; the access we hold is agreed at setup (Continuity FAQ). The configuration arrives like the rest of the deposit; "integrations" and "sync daily" are production claims, flagged. Continuity Pro includes Agentic Verification; base Continuity doesn't. "A run doesn't touch the live environment" follows from the confirmed sealed Verification Lab (cut off from production). The map uses the same six items as the Continuity page and film, in a "mapped at setup" state rather than the "vendor stopped" state shown there. 16 Oct: Continuity Pro added; base Continuity no longer includes Agentic Verification, and the map is reviewed with each rebuild only on Continuity Pro.

How it gets in, and how it's proven

Mapped with you. Kept current. Proven with each rebuild.

The map is made with you at setup and reviewed as things change. The configuration behind it is deposited and checked like the rest of the deposit.

1

Mapped with you at setup

We go through the live environment with you: where the application runs, the accounts it depends on and the services it needs. We agree the access we hold.

2

Configuration deposited and checked

Infrastructure definitions and settings arrive through our cloud integrations, for AWS, Azure or Google Cloud, or by secure upload. An automated check confirms what's there, and you receive a Software Resilience Certificate.

3

Kept current

We review the map when the deposit changes, so it matches what's running. With Continuity Pro, we also review it with each rebuild.

4

Proven with each rebuild

Continuity Pro adds Agentic Verification. AI agents rebuild the application in the Codekeeper AI Verification Lab, cut off from production, so a run doesn't touch the live environment.

Escrow · Resilience · Continuity

Software Resilience Certificate

The environment configuration is 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, 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: Continuity is the natural fit, so its card is outlined. 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. Escrow and Resilience still use the environment details to rebuild elsewhere; only Continuity keeps the live environment switched on, and the Resilience card says so plainly, as the product comparison does ("Not covered"). The Continuity card is the agreed wording. No uptime, duration or hands-on operation is mentioned. 16 Oct: Continuity Pro (from $1,699, setup $999) added to the fine print with the other Pro levels. 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

Only one protection keeps it switched on.

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

The environment details are released to you with the deposit, so your team can redeploy the application on hosting you control. Explore Escrow

From $199

Recovered by us

Resilience

Comes to us→Managed Recovery

They come to Codekeeper, and we bring the application back. The live service isn't kept on meanwhile. Explore Resilience

From $399

The natural fit

Continuity

Live service kept on+Managed Recovery

We map the live environment at setup and keep the map current. If the vendor stops, we keep it paid and switched on for an agreed period while we recover. Bills are recharged at cost. 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.

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.

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.

You're on this page

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 a Continuity buyer asks about hosting, answered as the Continuity page answers them. The period, the bills, uptime and setup answers repeat the Continuity FAQ word for word or nearly, so the two pages can't drift apart. The uptime answer is deliberately direct, because production promised that "the application keeps running without interruption". Legal should review the uptime and setup answers with the Continuity page's. Removed: "$415 per month" and "ISO 27001-aligned systems".

Questions

Hosting environment escrow, answered.

What is hosting environment escrow?

Holding the details of where an application runs, and the access needed to keep it paid and switched on, with a neutral party. At Codekeeper, that's part of Continuity: we map the live environment at setup, keep the map current and, if the vendor stops, keep it paid and switched on for an agreed period while we recover.

For how long do you keep it switched on?

For an agreed period, set per arrangement. We agree it with you when we set up Continuity.

Who pays the hosting bills during that period?

We keep them paid and recharge them to you at cost.

Does it come with an uptime service level?

No. Continuity keeps the live environment paid and switched on for an agreed period while we recover. If you need the cost of a recovery under an agreed service level, add Cost coverage, quoted per arrangement.

What do you need from us at setup?

The details of the live environment: where the application runs, the accounts it depends on and the services it needs. We map it with you and agree the access we hold. Everything you deposit is encrypted at rest, and Codekeeper is ISO/IEC 27001:2022 certified.

The same close on every page. The close turns the page's first step into the call to action: map the live environment now, while the vendor is still there to help. Every page ends on the same two actions in the same order: Book a demo, then the sample evidence pack.

Map where it runs, before you need to.

We'll look at the live environment behind your application and what Continuity would cover.

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.