--- title: "Software continuity: Continuity and Continuity Pro · Codekeeper" description: Should the vendor stop, Continuity pays for the live environment and keeps it running for an agreed period during the recovery, while Pro shows it builds beforehand. canonical_url: https://codekeeper.co/en-gb/continuity --- # Software Continuity. Keep your critical applications _online._ Should the vendor stop, Continuity pays for the hosting and services behind your application and keeps them running for an agreed period while the software is brought back. Continuity Pro shows the deposit builds beforehand. From **$1,339** /mo [Book a demo](https://codekeeper.co/book-a-demo) [View pricing plans](https://codekeeper.co/pricing/continuity) * ISO/IEC 27001:2022 certified * Daily syncs across 50+ integrations ![Check-in agents serve travellers in a sunlit airport hall, their systems still running](https://codekeeper.co/hubfs/codekeeper-site/images/continuity/hero-day-1600.webp) 0:00 / 1:02 **Continuity and Continuity Pro**Services that keep running1:02 * Code in a neutral vault * Live environment mapped * Kept paid and switched on * Rebuild passed_Pro_ Relied on by 3 500+ teams across more than 150 countries, from regulated enterprises to software vendors growing at pace ![Airbus](https://codekeeper.co/hubfs/codekeeper-site/logos/customers/airbus.svg) ![Bayer](https://codekeeper.co/hubfs/codekeeper-site/logos/customers/bayer.svg) ![European Parliament](https://codekeeper.co/hubfs/codekeeper-site/logos/customers/eu-parliament-dark.svg) ![General Motors](https://codekeeper.co/hubfs/codekeeper-site/logos/customers/general-motors.svg) ![Intuit](https://codekeeper.co/hubfs/codekeeper-site/logos/customers/intuit.svg) ![Nestlé](https://codekeeper.co/hubfs/codekeeper-site/logos/customers/nestle.svg) ![PepsiCo](https://codekeeper.co/hubfs/codekeeper-site/logos/customers/pepsico.svg) ![Pfizer](https://codekeeper.co/hubfs/codekeeper-site/logos/customers/pfizer.svg) Why Continuity ## Open for business _while your software is recovered._ Where software underpins patient care, banking, logistics, or other critical services, going offline simply isn't acceptable. Continuity keeps the services your organisation depends on running while your team, or ours, restores the critical software that failed. The vendor stops Agreed period · recovery under way Software restored Live environment Claims Portal Kept running * Hosting Cloud account and serversPaid * Domain claimsportal.examplePaid * Payment provider Merchant accountPaid * Email delivery Transactional email servicePaid Charted from day one Every account behind it A record of hosting, domains, and supporting services, made long before a failure. Who restores it Your team or ours Escrow leaves the recovery with your own team, while Resilience puts Codekeeper's engineers on it. Illustrative names and values for a sample application. The cost of downtime ## For some applications, waiting out a recovery isn't possible. A vendor that stops can take the live service down with it. Keeping that service running and restoring the application are separate tasks, and Continuity takes care of both. ### An invoice goes unpaid. Your application runs on hosting, cloud accounts, and domains the vendor pays for, and those payments end when the vendor does. ### A single lapse brings down the rest. One suspended account or expired domain can knock the application offline, and every service relying on it too. ### Recovery isn't instant. Restoring an application from its deposit takes real effort, and your users and customers still rely on the live service throughout. Kept running ## Software continuity, in plain terms. Software continuity is a business continuity solution, set up through a legal agreement between the vendor, their customers, and Codekeeper, that keeps a critical application's live service running during its recovery. * **The vendor** places the software on deposit, along with details of the hosting and services behind it. * **Codekeeper** pays for those accounts and keeps them running for an agreed period should the vendor stop, recharging the bills at cost. * **Their customers** carry on using the live service during the recovery, which their own team runs under Escrow or our engineers run under Resilience. Continuity is built for applications that depend on paid hosting and outside services, SaaS and AI among them. Software running solely on your own servers carries no such bills, which makes Escrow or Resilience the better choice. ![A courier checks the next drop on his handheld on a sunny city street, the app still working](https://codekeeper.co/hubfs/codekeeper-site/images/continuity/frontline-day-1200.webp) **Software continuity agreement**Courier App · Continuity ProMap current **Depositor**Northwind Software Ltd. Vendor **Claimant**Example Logistics Group1 included **Where it runs**Hosting · Cloud accountMapped **What it needs**Domain · Payments API Mapped **If the vendor stops**Kept paid and switched onAgreed period A sample, with made-up names. How it works ## Mapped in advance. Kept on. _Brought back._ 1. 1Define the scope and map for every application. Our specialists settle the vault's contents with you and chart where each application runs and which services it relies on. Show details Who Your team and a Codekeeper specialist, from the first onboarding call. In the vault Usually the source code, build scripts, documentation, and data, plus credentials and configuration where relevant. On the map The hosting, accounts, and outside services each application can't run without. You get A deposit scope for each application, and a map of its live environment. 2. 2Lock in when a release happens. A single agreement, signed by the vendor and their customers, fixes the release conditions and the agreed period. Show details Who The vendor, their customers, and Codekeeper. For vendor software, the vendor signs, since the code can only come from them. Your options Two-party (bipartite), where the vendor signs once and adds claimants as they come on board, or three-party (tripartite), where one claimant signs alongside the vendor from day one. You get A software continuity agreement with the release conditions, such as insolvency, discontinued support, or a material breach, and how long we keep the environment on. 3. 3Plug in the tools your developers use. Changes sync daily through 50+ integrations, while a monthly Vault Report shows which agreed materials sit in the deposit. Show details Who Our specialists, working with your developers to connect the first deposits. Then Each change syncs daily, the deposit is checked automatically every month, and the live-environment map is kept current. You get A Vault Report and a Continuity Vault Report each month, a Vault Certificate, a Continuity Vault Certificate, and a Continuity Certificate that shows the arrangement is in place. 4. 4Put the rebuild to the test with Continuity Pro. Run a build test from your account at any time, and add the certificate it produces to your evidence. Show details How AI agents in the Codekeeper AI Verification Lab rebuild the deposit in isolation and flag anything missing, without calling on the vendor. The map We review the live-environment map with each rebuild. You get Proof it builds: a Recoverability Certificate, backed by a Rebuild Report, an SBOM, an exit workbook, and a tested isolated compile. 5. 5Keep your live service up until the application is restored. Should the vendor stop, we pay for the live environment and keep it running for the agreed period while the recovery goes on. Show details First We confirm the release condition, as we would for any release. The bills Paid by us while the environment is on, and recharged to you at cost. The recovery Run by your team on Escrow, or by our engineers on Resilience. Play with voice Want to see what we'd keep switched on for your applications? [Talk it through with a specialist](https://codekeeper.co/book-a-demo) Continuity or Continuity Pro ## Kept on while it's recovered. _Proven before you need it._ Continuity keeps the live environment running throughout the application's recovery. Continuity Pro also puts the deposit to the test, as Codekeeper's AI agents rebuild it at a time you pick, so the recovery begins from a deposit already known to build. ### Continuity From **$1,339** per month Your choice of Escrow or Resilience recovery, with complete continuity. Included * Software held by a neutral party * Syncs every day through 50+ integrations * Missing files caught each month * The live environment paid for and kept running for an agreed period should the vendor stop [Choose Continuity](https://codekeeper.co/pricing/build-a-plan?prot=continuity&level=base) ### Continuity Pro Recommended From **$1,569** per month Complete continuity, tested beforehand, with Escrow Pro or Resilience Pro. Everything in Continuity, plus * Agentic Verification, with as many as four rebuilds a year on supported technology stacks * Sovereign AI agents in the Codekeeper AI Verification Lab * A review of the live-environment map at every rebuild * A tested isolated compile you can deploy * An exit workbook to guide the recovery * Recoverability Certificates and SBOMs on file [Choose Continuity Pro](https://codekeeper.co/pricing/build-a-plan?prot=continuity&level=pro) ![An example Continuity Certificate, issued by Codekeeper for a fictional application](https://codekeeper.co/hubfs/codekeeper-site/images/certificates/continuity-1200.webp) Continuity**Continuity Certificate**Confirms the agreement is active and the deposit has been checked. Values are examples. ![An example Recoverability Certificate for a passed rebuild of a fictional application](https://codekeeper.co/hubfs/codekeeper-site/images/certificates/recoverability-1200.webp) Continuity Pro**Recoverability Certificate**Records the rebuild and its outcome. Release rights stay with the agreement. Values are examples. Get the sample evidence pack [See Agentic Verification in action](https://codekeeper.co/agentic-verification) Included with Continuity ## We take care of the agreements, the mapping, and security. ### Agreements written and negotiated on your behalf. Our in-house counsel drafts and negotiates your two-party, three-party, or multi-party agreement, under whichever jurisdiction you pick. ### A map of your live environment. During setup, we chart the hosting, accounts, and services each application needs, then keep the map up to date. ### One dashboard for all parties. Track the arrangement through a log of every change, and keep certified software resilience evidence within reach. ### Credentials kept secure. Store the logins and keys the live environment relies on with AES-256 encryption and MFA, in storage that can't be tampered with. ### Requests reviewed 24/7/365. Report a problem whenever it happens, and our team tests the request against the terms of your software continuity agreement. ### Recovery files that stay up to date. With your repositories and cloud platforms connected through 50+ integrations, each change lands in the vault every day, ready to support a recovery. * ![GitHub](https://codekeeper.co/hubfs/codekeeper-site/logos/integrations/github.svg) * ![Bitbucket](https://codekeeper.co/hubfs/codekeeper-site/logos/integrations/bitbucket.svg) * ![AWS](https://codekeeper.co/hubfs/codekeeper-site/logos/integrations/aws.svg) * ![Microsoft Azure](https://codekeeper.co/hubfs/codekeeper-site/logos/integrations/azure.svg) * ![Google Cloud](https://codekeeper.co/hubfs/codekeeper-site/logos/integrations/gcp.svg) * ![Shopify](https://codekeeper.co/hubfs/codekeeper-site/logos/integrations/shopify.svg) * ![Stripe](https://codekeeper.co/hubfs/codekeeper-site/logos/integrations/stripe.svg) * ![Chargebee](https://codekeeper.co/hubfs/codekeeper-site/logos/integrations/chargebee.svg) Vendor out of the picture ## The vendor stops. _The service doesn't have to._ The vendor's payments for the hosting and services behind your application end when the vendor stops. Continuity steps in and pays them, keeping the service live while the software is restored. 1 ### We check the request. Our team makes sure it meets a release condition set in your software continuity agreement. 2 ### We cover the bills. All the services on the map keep running for the agreed period. 3 ### The application is restored. Your team handles it under Escrow, or our engineers under Resilience, and on Pro they work from build steps already proven to work. ![A Codekeeper engineer and a colleague check that a customer's live environment is still switched on](https://codekeeper.co/hubfs/codekeeper-site/images/continuity/engineer-day-1200.webp) Application types ## How your application runs shapes what we keep running and what we hold. Each of Software, SaaS, and AI depends on its own blend of hosting and outside services. Pick your application type to see which services Continuity keeps running and what it holds ready for the recovery. [Software Installed and on-premises applications Kept paid Hosted components Third-party services Held for recovery Source code Data Documentation From **$1,339** Software continuity pricing](https://codekeeper.co/pricing/continuity?type=software) [SaaS Subscription and hosted applications Kept paid Cloud hosting and storage Domains and DNS Email and payment services Held for recovery Source code Data Documentation Deployment infrastructure Third-party services Credentials and access From **$1,479** SaaS continuity pricing](https://codekeeper.co/pricing/continuity?type=saas) [AI AI systems and models Kept paid GPU hosting Inference endpoints Vector stores and data services Held for recovery Models Model deployments Agents and prompts Workflows From **$1,799** AI continuity pricing](https://codekeeper.co/pricing/continuity?type=ai) Other ways to protect ## Can your service pause while it's being restored? Where the service can afford to be offline during the recovery, pick self-run or managed recovery. Self-Run Recovery ### Escrow **For the software your own team can bring back.** Secure critical software in a neutral vault, ready for your engineers to restore when a release condition applies. From **$189** [Explore**Escrow**](https://codekeeper.co/escrow) Managed Recovery ### Resilience **For the software you can't risk rebuilding yourself.** Recover critical third-party software after a failure, with our engineers leading the effort. From **$369** [Explore**Resilience**](https://codekeeper.co/resilience) [Compare plans](https://codekeeper.co/pricing/compare) ## Full continuity for the applications _you can't lose._ Lose one payment, and an entire service can switch off. Our continuity specialists can show you how to keep the accounts behind your applications paid for and live. [Book a demo](https://codekeeper.co/book-a-demo) [Build a plan](https://codekeeper.co/pricing/build-a-plan) Frequently asked questions ## Get the whole story on Continuity. What sets Continuity apart from Resilience? What sets Continuity apart from Resilience is the live environment: Resilience restores the application, while Continuity also keeps its live environment running during that work. We map the environment ahead of time, and should the vendor stop, we pay for it and keep it running for an agreed period during the recovery. What recovery is included with Continuity? The recovery included with Continuity is the one you choose. With Escrow, the deposit is released to your team and you carry out the recovery. With Resilience, the deposit is released to Codekeeper and our engineers handle the recovery on a best-effort basis. Continuity Pro sits on Escrow Pro or Resilience Pro, so Agentic Verification tests the deposit too. Must the vendor be involved? Yes, for vendor software the vendor must be involved, since only the vendor can deposit their source code, and it's the vendor who signs the software continuity agreement. With a two-party agreement, the vendor sets up once and adds claimants later, while a three-party agreement includes one claimant from day one. Which parts do you keep running? The parts we keep running are those of the live environment the application depends on, as recorded on the setup map, which usually means hosting, cloud accounts, domains, and critical third-party services. For how long does the live environment keep running? The live environment keeps running for an agreed period, fixed in each agreement. We settle the length with you while setting up Continuity, and if a recovery might run longer, the Coverage Length SLA add-on extends it. Who covers the bills in the meantime? We cover the bills in the meantime and recharge them to you at cost. Does the hosting move to Codekeeper? No, the hosting doesn't move to Codekeeper. We pay the bills while your current providers carry on hosting and running everything they supply, so the way the service runs stays exactly the same. Could your engineers handle running the service? Yes, our engineers can handle running the service for you, as an add-on. Hands-on work on the live service, including monitoring, incidents, and fixes, is charged by the hour and carried out on a best-effort basis, without a guarantee or service level. Is there an uptime service level with Continuity? No, there's no uptime service level with Continuity. It pays for the live environment and keeps it running for an agreed period during the recovery, with no uptime promise. To bring a recovery's cost under an agreed service level, add Cost coverage, which is quoted per agreement. Are there costs on top of the monthly price? Yes, on top of the monthly price there's a one-off setup fee of $999 per agreement, the same on Continuity and Continuity Pro, plus release processing at $199 per hour should a release ever be requested. One claimant comes included, with more available as an add-on, and hands-on operations and Cost coverage can be added if you need them. What extra does Continuity Pro include? Continuity Pro includes Agentic Verification as its extra: AI agents independently rebuild a complete deposit in the sealed Codekeeper AI Verification Lab, as many as four times a year, on supported technology stacks. Every successful rebuild issues a Recoverability Certificate, along with a Rebuild Report, an SBOM, an exit workbook, and a tested isolated compile, and we review the live-environment map each time. Let us know what you run, and we'll confirm your stack in the demo. What's required from us to get started? To get started, we require the details of the live environment: where the application runs, which accounts it relies on, and what services it needs. We map it alongside you, agree the access we'll hold, and set up the first deposits and integrations with your team, beginning with an [onboarding call](https://codekeeper.co/book-onboarding-call) . Everything you deposit is encrypted at rest, and Codekeeper holds ISO/IEC 27001:2022 certification.