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 changed: the process stays, the offer becomes a question. Production's /switch-to-codekeeper is built on a buyout offer: "start paying when your current contract ends", with a calculator that shows "6 months at $0" for 3, 6, 9, 12 or 18 months left. That offer is not confirmed for the new list, so the page leads with how switching works and what you get, and presents the offer as "Ask us about the switching offer". The production terms are listed in the offer section's note for sales to confirm.
  • The headline answers the visitor's real worry (being under contract) without the old promise of "without paying double".
  • Production's hero ticks are gone: "No extra costs" is part of the unconfirmed offer, "Live in 24 hours" has no source, and "Agreements drafted for you" is now step 3, flagged.
  • "Trusted by 3,500+ teams" is production's figure (MESSAGING §6), used unflagged as on the home page. Confirm it with the other production claims in to-confirm.md.
  • The visual is an illustration of the four steps built from the mock component, not a product screen. Names and dates are fictional.
Switch to Codekeeper

Under contract elsewhere? You can still switch.

Send us your current agreement. We'll plan the move with you and your counterparties: the new agreement, fresh deposits synced from the source, and the right protection for each application.

Book a demo Get the sample evidence pack

Still paying your current provider? Ask us about the switching offer.

  • Trusted by 3,500+ teams
  • ISO/IEC 27001:2022 certified
  • Nothing changes until you sign
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: why teams move, framed as the shift. Production's heading, "Traditional escrow secured a moment in time. Codekeeper protection grows with you", is the right idea, so it's kept in spirit. The comparison uses the same generic "traditional" wording as the Why Codekeeper page, so the two pages agree, and every Codekeeper line rests on MESSAGING §6. "Synced daily" and "50+ integrations" are production claims, flagged until Product confirms them. Legal should check the "often" side, as with any comparative claim.
  • Left out: production's "90% of untested escrow deposits fail when they are used in recovery" (no source; find one or keep it off), "Software Verification" (old name), "Six to eight weeks of drafting" vs "24 hours" (no source), "unlimited deposits" and "no hidden costs".
  • Left out: production's six framework cards ("answers SOC 2 criteria CC9.2 and A1.3 directly", "time recovery against your BIA targets", "compile the results against the NIST CSF 2.0 Recover function", "test the exit strategy for each critical ICT provider"). They describe services and mappings that aren't in the confirmed line-up. The framework pages carry the evidence story now.
  • Comparisons with named providers live on the Why Codekeeper page, which links to each one.

Why teams move

A deposit that was right once isn't enough.

Software changes every day, and auditors now ask whether you could actually recover. Having the code is the start. Having the application back is the goal.

Escrow as it's often done

  • Deposits uploaded by hand, on a fixed schedule
  • A record that a file arrived, with no proof it builds
  • The code is released to you, and the recovery is yours to run
  • Prices on application, agreement by agreement

With Codekeeper

  • Deposits synced daily through 50+ integrations
  • A Software Resilience Certificate on every protection, and with Pro, proof the deposit builds
  • Released to you, or with Resilience, recovered by us
  • Published prices per application, from $199 a month

"As it's often done" describes common practice in software escrow, not any single provider. Comparing specific providers? See Why Codekeeper, with a side-by-side page for each.

Step 3: how switching works, in four steps. Production has three steps (apply with proof of your contract; legal drafts the buyout agreement "within 24 hours"; deposit and sync). They're kept, with a mapping step added, because a switch is the moment to pick the right protection under the new line-up.
  • Step 1 keeps production's useful detail: a copy of the contract or a screenshot is enough.
  • Step 3 to confirm: production says "our in-house legal team drafts your buyout agreement within 24 hours". The page says we prepare the agreement with you, with no time stated. "Nothing changes until you sign" is production's line.
  • Step 4 rests on "deposits sync daily" and "50+ integrations", both production claims flagged in to-confirm.md. Deposits open once the new agreement is signed (FAQ).

How switching works

Four steps from your old agreement to a new one.

You stay in control at every step, and nothing changes until you sign.

1

Send us what you have

Your current agreement (a copy or a screenshot is enough), the applications it covers, who's party to it and when it ends.

2

Pick the right protection

For each application we suggest a protection and level, based on what should happen on the day it fails.

3

Review and sign

We prepare the new agreement with you and your counterparties. You review it, everyone signs, and it takes effect.

4

Connect and deposit

Connect your repositories once. Deposits sync daily, and we check and certify what's there.

The question every switcher asks: what happens to our deposits? Production only says "deposit and sync straight away". This section explains the actual approach: the new deposit is taken fresh from the source rather than copied from the old provider, then checked and certified. That's a stronger answer than a migration, because the new deposit reflects the version you run today. Everything here rests on confirmed facts (automated check, vault report, Software Resilience Certificate, Agentic Verification with the Pro levels) or flagged production claims (daily sync, 50+ integrations).
  • 16 Oct: Continuity Pro added; base Continuity no longer includes Agentic Verification, so step 3 names Escrow Pro, Resilience Pro or Continuity Pro.
  • The old provider's copy: the page says the current agreement's exit terms decide what happens to it, and that we'll go through them with you. Sales should confirm they do this.
  • The mock uses integrations that have their own pages in the kit (GitHub, Amazon S3). Values are fictional.

Migrating your deposits

A fresh deposit, straight from the source.

We don't copy an old upload across. We build your Codekeeper deposit from the systems you run today, so it starts current and stays current.

1

Connect the sources

Link repositories and cloud storage through 50+ integrations, or upload files by hand for anything that isn't in a repository.

2

Check and certify

An automated check confirms what's deposited, with a vault report, and a Software Resilience Certificate is issued.

3

Prove it builds

With Escrow Pro, Resilience Pro or Continuity Pro, run Agentic Verification. Anything missing is flagged, so you can add it.

4

Close out the old one

Your current agreement's exit terms decide what happens to the copy your previous provider holds. We'll go through them with you.

Step 3, the model: what you're switching to. Production's "Everything included from day one" list sold the old plan (no setup fee, unlimited deposits, monthly or annual billing). The new list is different, so this section shows the line-up (Escrow, Resilience and Continuity, with their levels) and the 6 Oct "from" prices and the agreed price logic sentence, word for word. Billing frequency and any switching discount aren't stated (MESSAGING §6). 16 Oct: Continuity Pro added (from $1,699, 11 Oct list). It gets a card of its own, so the line-up shows six cards: the three protections across, base and Pro levels down; base Continuity is now everything in Resilience, and the note 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.

What you get

Switch to more than a new custodian.

Choose what should happen when each application fails: released to you, recovered by us, or kept online while we recover.

Self-Run Recovery

Escrow

Everything you need to be protected.

Custody, release under the Escrow Agreement, an automated check and a Software Resilience Certificate.

From $199per application per month

Explore Escrow
Self-Run Recovery

Escrow Pro

Everything you need to recover.

Escrow plus Agentic Verification: proof the deposit builds, and a Recoverability Certificate.

From $449per application per month

Explore Escrow Pro
Managed Recovery

Resilience

We run the recovery.

The deposit comes to Codekeeper. If the application fails, we bring it back for you.

From $399per application per month

Explore Resilience
Managed Recovery

Resilience Pro

Proven before we need it.

Resilience plus Agentic Verification, so recovery starts from a deposit we know builds.

From $649per application per month

Explore Resilience Pro
Stays online

Continuity

Full continuity.

Everything in Resilience, plus we keep the live environment paid and switched on for an agreed period while we recover.

From $1,449per application per month

Explore Continuity
Stays online

Continuity Pro

Full continuity, proven in advance.

Continuity plus Agentic Verification, so recovery starts from a deposit we know builds.

From $1,699per application per month

Explore Continuity Pro

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. See all prices

The offer, as a question for sales to answer. Production's buyout offer is not confirmed for the new list, so the page invites the conversation without stating terms. Production's terms, for sales to confirm or retire:
  • "Start paying when your current contract ends"; "6 months of Codekeeper at no cost, on top of the cover you already bought" (calculator options 3, 6, 9, 12 and 18 months).
  • "No buyout fee, no setup fee, no charge for the overlap period". Note that the new list has a $499 setup fee ($999 for Continuity).
  • "Our in-house legal team will draft your buyout agreement within 24 hours"; "An escrow specialist will reply within one business day with your drafted agreement"; "Live in 24 hours"; "Account, agreement, and first deposit inside a single business day".
  • "Your contract details stay confidential. We never contact your current provider, and nothing changes until you sign." The first and last are kept; "we don't contact your current provider" is flagged until sales confirms it's still policy.
  • "Unlimited deposits", "Choose between monthly or annual billing", "Connect GitHub, Bitbucket, AWS, Azure, or GCP in a few minutes".
The form: production's form fields weren't captured, apart from an attachment for proof of the current contract. These fields qualify the request (end date and number of applications decide the size of any offer). Match the HubSpot form, including the file upload, which the kit has no component for. This example sends nothing.

The switching offer

Ask us about the switching offer.

Still under contract with another provider? Tell us when your current agreement ends and what it covers. Sales will confirm what we can offer for the overlap, in writing, before you sign anything.

  • Your contract details stay confidential
  • We don't contact your current provider
  • Nothing changes until you sign

Tell us about your current escrow

Enter your name.
Enter your company.
Enter a work email, like name@company.com.

We'll use these details to reply about your switch. You can unsubscribe from follow-up emails at any time. See our privacy policy.

This is where your request would go to sales.

This is an example page, so nothing was sent. In production this form submits to HubSpot, with a copy of your current contract attached.

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 sales hears from switchers, in that order. Can we move, will we pay twice, what happens to the old deposit, who has to agree, and is there a gap. The first answer follows production's agreement FAQ ("We'll review your pre-existing agreement, make updates if needed"). The pay-twice answer points to the offer conversation without stating terms. The Pro answer keeps the base level strong: Escrow is everything you need to be protected. 16 Oct: Continuity Pro added; the Pro answer names the Pro levels only.

Questions

Before you switch.

Can we move an existing escrow agreement to Codekeeper?

Yes. Send us the agreement you have today and tell us who's party to it. We'll review it, plan the move with you and your counterparties, and prepare the new agreement.

Will we pay two providers at once?

Ask us about the switching offer. Sales will confirm the terms for your situation, in writing, before you sign anything.

What happens to the deposit our current provider holds?

Your current agreement decides: its exit terms set the notice period and what happens to the materials. We'll go through them with you. Your Codekeeper deposit is built fresh from the source, so it doesn't depend on the old one.

Do our vendor and our customer need to agree?

Everyone who's party to the new agreement signs it, so we plan the move with your counterparties from the start. Two-party, three-party and multi-party agreements are all supported.

Will there be a gap in protection?

There doesn't have to be. You can set up Codekeeper before your current agreement ends, so the application is covered on both sides of the switch.

Do we have to choose Pro?

No. Escrow is everything you need to be protected: custody, release under the agreement, an automated check and a Software Resilience Certificate. If you're switching because your current deposit has never been tested, Escrow Pro, Resilience Pro or Continuity Pro add Agentic Verification, which proves the deposit builds.

More answers in the FAQ

The same close on every page. Switchers are buying an upgrade, so the close names what changes on day one: a deposit synced from the source, not an old upload. Every page ends on the same two actions in the same order: Book a demo, then the sample evidence pack.

Bring your escrow over. Keep it current from day one.

Book a demo and we'll map your current agreement to the new line-up, application by application.

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.