NewEscrow Pro, Resilience, Continuity and Agentic Verification: from holding the code to proving it comes back.The new line-up is here.See what's new
Why this page looks like this. Production sells Backup as "Set-and-forget software backups built for compliance teams", with three verification tiers on top. In the new model Backup is a peer protection with a lighter job: daily backups of systems you run yourself, which you restore when you choose. It isn't a cheaper Escrow, so the page compares it by job, never by price.
  • Headline: the canonical Backup line, "Your systems, backed up and restorable."
  • Prices: production economics exactly as MESSAGING.md §6 states them: $99 per application per month billed annually, $129 monthly, $249 setup. The FAQ on production's /pricing/software-backup page says $89 and $119. Confirm which is right before launch.
  • Dropped from production: "Live in 24 hours" (no source), the Validated, Verified and Certified tiers (replaced), "military-grade" and "Unlimited deposits".
  • Visual: a Backup dashboard mock that shows the job in one glance: daily sync, the three latest versions, restore.
Software Backup

Your systems, backed up and restorable.

Daily backups of the applications you build and run yourself: code, data, configuration and documents, kept outside your production environment. When something breaks, restore a recent version from your dashboard.

Book a demo Get the sample evidence pack

From $99. Per application per month, billed annually. Setup $249.

  • Trusted by 3,500+ teams
  • ISO/IEC 27001:2022 certified
  • Software Resilience Certificate included
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
Step 1, the exposure, for systems you run yourself. Production's three problems (data loss, failed audits, slow recovery) are kept and written calmly. Production's "Ransomware attacks typically target backup systems first" has no source, so it's left out; add it back only with one. The lead names the real gap Backup closes: copies outside production, and evidence they exist.

The exposure

Backups run. Showing you can restore them is harder.

In-house systems fail in ordinary ways: a bad deployment, a deleted repository, an attack on production. Most teams have backups. Fewer keep copies outside production, with a record an auditor can check.

Data loss

Corruption, deletion or ransomware can reach production systems, and sometimes the backups kept next to them.

Audit questions

Auditors ask where your copies are kept, how recent they are and how you would restore them. Every gap costs time.

Slow recovery

When code, data and configuration live in different places, getting back to a working system takes far longer than planned.

Steps 2 and 3: the shift and the model, in three steps. The differentiator from production is kept: you restore whenever you choose, with no release event and no approval. That's what makes Backup a different job from Escrow, not a smaller one. The suggested film follows the same three beats (connect, sync, restore), as planned in MESSAGING.md §10. "50+ integrations" and daily sync are confirmed facts.

How it works

Connect once. Back up daily. Restore when you choose.

No release terms and no one else's approval. The backups are yours to restore.

1

Connect your systems

Link repositories and cloud accounts through 50+ integrations, or upload files by hand.

2

Back up daily

Codekeeper syncs a fresh copy every day and keeps the three latest versions, outside your production environment.

3

Restore when you need to

Pick a version in your dashboard and download it. There's no release event to wait for.

Suggested film Backup in 60 seconds About 60 s. Open on an in-house application and connect a repository and a cloud account. The first daily sync lands in the vault and the three latest versions appear. Something breaks in production; a developer restores yesterday's version from the dashboard. Close on the Software Resilience Certificate and Book a demo.
Step 3 in detail: what a backup holds. These are production's five asset types, reworded, plus manual uploads (production's "Automated and manual uploads"). Production also says "Unlimited storage included" in this section while the plan shows 1 TB; this page uses 1 TB everywhere. Confirm before launch.

What's in a backup

Everything you'd need to restore the application.

A backup only helps if it holds the whole application. Software Backup covers the code, the data and the files that turn them into a working system.

Source code

The complete codebase with its version history, ready to restore after corruption or deletion.

Application data

Databases and the business records that keep operations running.

Deployment assets

Build scripts, environment files and configuration settings needed to rebuild a working environment.

Documents

Technical specifications, runbooks and business-critical files, each stored with a timestamp.

Technology and designs

Proprietary designs and technical work, held outside your own systems.

Anything else, by hand

Files that don't live in a connected system can be uploaded manually and are kept with the rest.

Step 4, the proof that Backup carries. Production says a Software Resilience Certificate is included with Backup, and MESSAGING.md §4 confirms it for Backup "on production". The certificate copy matches §4: the backups are held, and an automated check with a vault report confirms what's in them. Confirm that the automated check and vault report apply to Backup in the new model. The activity record and hands-on setup help come from production ("Immutable audit trails", "Hands-on implementation support"); "immutable" is left out until someone confirms it. Production names ISO 27001, SOC 2 and GDPR; the copy says "evidence for your file" and carries the assessment line, never "compliant".

Evidence for your file

Show your auditor the backups exist, and what's in them.

Software Backup includes a Software Resilience Certificate. It shows the backups are held, and that an automated check, with a vault report, has confirmed what's in them.

  • A record of every backup, with timestamps and version tracking
  • Evidence that supports your ISO 27001 or SOC 2 assessment, without gathering it by hand
  • Help from our team to set up your first backups

Codekeeper's evidence supports your assessment. Whether it meets a specific requirement is for you and your assessor to decide.

Remove the security objection with named standards. ISO/IEC 27001:2022 (audited by BSI), AES-256 at rest and TLS in transit are confirmed facts. Production's "AES256/512" and "military-grade" are dropped. Multi-factor authentication and separation from production networks come from production ("Multi-factor authentication", "Backup isolation from production networks"); confirm both before launch. Production's "Zero-trust access" badge is left out until it's defined.

Security

Kept apart from production. Encrypted at rest.

A backup kept next to the system it protects can be lost with it. Yours sit in Codekeeper's vaults, outside your own networks and accounts.

Outside production

Copies are held away from your own infrastructure, so an incident there doesn't reach them.

Encrypted

AES-256 encryption at rest and TLS in transit.

Controlled access

Multi-factor authentication and role-based permissions decide who can restore what.

Audited security

Codekeeper is ISO/IEC 27001:2022 certified, audited by BSI. Trust Center

Step 3, the model: when to choose Backup, Escrow or Resilience. This is where Backup is placed as a peer with a different job, not a lesser Escrow. Each card says whose software it is and who restores or recovers it. The line underneath is the agreed price logic sentence, followed by the route to Agentic Verification for anyone who needs proof an application rebuilds. Backup's "From $99" sits on its card like the others; the job, not the price, is the point of comparison. Resilience is offered for in-house and vendor applications (applications → protections model, 27 Sep 2026).

Which protection?

Choose by the job, not the price.

Backup is for systems you run yourself. Escrow and Resilience are for applications you depend on but don't control, or would rather not recover alone. One account can hold all three.

You're here

Backup

Your systems→Backed up daily→You restore

Choose it for applications you build and run, when you want your own copies outside production and evidence they exist.

From $99

Released to you

Escrow

Vendor deposits→Released to you→You recover

Choose it for vendor software. When the agreed conditions are met, the deposit is released to you. Explore Escrow

From $199

Recovered by us

Resilience

Deposit→Comes to us→We recover

Choose it when you'd rather Codekeeper ran the recovery, for vendor software or your own. Explore Resilience

From $399

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. Need proof an application rebuilds? Escrow Pro, Resilience Pro and Continuity include Agentic Verification.

Three situations, one line each. Production speaks only to compliance teams. Backup is also bought by engineering, and it's often the first protection in an account that later adds Escrow for vendor software, so the third card makes that path explicit.

Who it's for

For teams that run their own software.

Compliance and risk teams

Evidence that backups exist, where they're kept and what's in them, ready for the next audit.

Engineering and IT

An off-site copy of code, data and configuration that you restore yourself, without waiting for an approval.

Teams that also rely on vendors

Start with Backup for in-house systems and add Escrow for vendor software, in the same account. Escrow

Step 5 starts here: the price, plainly. Production economics, as MESSAGING.md §6 states them: $99 per application per month billed annually, $129 billed monthly, $249 setup, 1 TB, the three latest versions kept. Backup isn't re-priced with the new list, so it isn't put in the Escrow price grid. To confirm before launch: the production plan-page FAQ says $89 (annual) and $119 (monthly); production's Backup page says "Unlimited storage included" while the plan shows 1 TB. Production's annual toggle says "Save up to 12%"; left out, as the brief asks.

Pricing

One plan, priced per application.

Your systems, backed up and restorable

Software Backup

From$99per application per month, billed annually

Or $129 per application per month, billed monthly. One-time setup $249.

  • Daily sync through 50+ integrations, plus manual uploads
  • 1 TB of storage
  • The 3 latest versions kept, ready to restore
  • Restore and download from your dashboard
  • Software Resilience Certificate

Backup is priced on its own because it does a different job from Escrow, Resilience and Continuity. See all prices

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, in the order they ask them. Production's FAQ answers are kept and reworded: what backups are, versions kept, restore speed, and whether you need Backup with a DR plan. Production's "Recovery happens immediately" becomes a description of what happens (download from the dashboard). Production says the "complete immutable history" is retained for audit purposes; the versions answer says only that each backup is recorded, so confirm the retention wording. The Backup-or-Escrow answer reuses production's own line from How it works ("Backups protect internal systems. Escrow protects access to software you don't control").

Questions

Before you switch it on.

What is Software Backup?

Daily copies of the applications you run yourself: source code, databases, configuration and documents, kept by Codekeeper outside your production environment. You can restore any of the three latest versions from your dashboard.

How is Backup different from Escrow?

Backup protects systems you run yourself, and you restore them whenever you choose. Escrow protects software you depend on but don't control: the vendor deposits, and the deposit is released to you under an Escrow Agreement when its conditions are met. Many accounts use both.

How many versions do you keep?

The three latest versions, ready to restore. Each backup is also recorded with a timestamp, so you have a history to show your auditor.

How quickly can we restore?

Whenever you need to. Choose a version in your dashboard and download it. There's no release event and no approval to wait for.

How much storage is included?

The plan includes 1 TB. If you need more, talk to us.

Do we need Software Backup if we already have a disaster recovery plan?

A plan says how you'll recover. Software Backup gives you a recent copy outside production to recover from, and a certificate that shows it exists. Together they turn the plan into evidence for your file.

Does Backup prove the application rebuilds?

Backup includes an automated check of what's backed up and a Software Resilience Certificate. Rebuilding an application to prove it works is Agentic Verification, which comes with Escrow Pro, Resilience Pro and Continuity.

What does it cost?

From $99 per application per month, billed annually, or $129 billed monthly, plus a one-time $249 setup. See pricing

Is our data safe with you?

Codekeeper is ISO/IEC 27001:2022 certified. Backups are encrypted with AES-256 at rest and TLS in transit, and access is controlled with multi-factor authentication. See the Trust Center.

The same close on every page. The close repeats the canonical Backup line, so the page starts and ends on the same job. Every page ends on the same two actions in the same order: Book a demo, then the sample evidence pack.

Your systems, backed up and restorable.

See it on the systems you run. We'll walk through what to back up and how a restore works.

Book a demoGet the sample evidence pack