European Union
Global standards
US
UK
Australia
Netherlands
SaaS escrow. Keep the SaaS you depend on recoverable, down to the last credential.
A SaaS application needs more than its code to come back. Escrow keeps the code, data, infrastructure, and credentials in a neutral vault, synced daily. Escrow Pro proves the deposit builds.
From $279 /mo
- ISO/IEC 27001:2022 certified
- 50+ integrations, synced daily
How SaaS escrow worksBooking Hub · SaaS · Escrow ProDeposit current- The vendor depositsCode, data, infrastructure, and credentialsSynced daily
- Codekeeper holds itIn a neutral vault, checked every monthVault Report
- Codekeeper's AI agents rebuild itEscrow Pro · Codekeeper AI Verification LabPassed
- The customer receives itIf a release condition is metOn release
Example. Names are fictional.
Trusted by 3 500+ teams in over 150 countries, from regulated enterprises to fast-growing SaaS vendors
Why SaaS escrow
Prepare the cloud stack your business runs on for a supplier failure.
The cloud lets your business run faster and leaner, with less to manage in-house. But when a vendor fails, everything built on its service can go down with it. SaaS escrow lets your team recover the entire cloud environment, ready to run again.
Your own cloud
Booking Hub, in your account
- CodeRestored
- DataImported
- InfrastructureProvisioned
- CredentialsHanded over
Escrow for hosted applications
What is SaaS escrow?
SaaS escrow is an agreement between a cloud software vendor, their customers, and a neutral escrow agent such as Codekeeper. Because the vendor runs the application for their customers, the deposit goes beyond source code: it holds the infrastructure, data, credentials, and connected services the application needs, synced to the vault every day. Vendors use it to clear their customers' procurement and vendor risk reviews. If a release condition is met, customers receive the deposit to bring the service back, or to move it to cloud accounts of their own.
Want the longer answer? Read our introduction to SaaS escrow
SaaS escrow guards against
Lost access.
Get the service's code and data back after a shutdown or an acquisition.
Recovery from scratch.
Start from the deposit, not from reverse-engineering a system you never had the code for.
Stalled enterprise deals.
Give procurement and auditors the continuity plan they ask for before they sign.
What SaaS escrow holds
Code alone won't bring a SaaS application back.
Installed software runs on your own servers, so its code and build files carry most of a recovery. A SaaS application runs in the vendor's cloud, so the deposit has to hold every layer under it.
Source code
Learn about source code escrow- What goes in
- The services, scripts, and libraries the application is built from.
- Without it
- There's nothing to rebuild the service from, and no way to fix or change it.
Infrastructure and deployment
Learn about deployment assets escrow- What goes in
- Infrastructure definitions, deployment packages, and the configuration that stands the application up on servers.
- Without it
- The code arrives with no record of the environment it runs in.
- What goes in
- Database exports and datasets, so the service comes back with its records.
- Without it
- The application comes back empty.
Credentials and access
Learn about credentials escrow- What goes in
- The passwords, access keys, and cloud account access needed to deploy, manage, or restore the application.Kept beside the code in an access-controlled vault.
- Without it
- Nobody can get into the cloud accounts the service runs in.
Third-party services
Learn about third-party dependency escrow- What goes in
- The outside services and packages the application calls to work as built, such as payments, email, and search.
- Without it
- The service starts, but the features that rely on outside services don't work.
Documentation
Learn about document escrow- What goes in
- How the application is set up and maintained, from architecture notes to runbooks.
- Without it
- A recovery team has to rediscover what the original engineers knew.
Repositories, cloud platforms, and SaaS tools such as Stripe, Shopify, and Chargebee connect once, through 50+ integrations, and sync every day after that. See all integrations
How a recovery works
What happens when a SaaS vendor stops.
Two things are at stake: the deposit your team recovers from, and the live service your people still use every day. Escrow takes care of the first. Continuity is for the second.
-
1
Every day before
Nothing has gone wrong yetThe depositSynced and checkedThe deposit syncs daily, and a monthly check documents which agreed items are there. On Escrow Pro, Codekeeper's AI agents also rebuild it when you choose.
The live serviceOnlineThe vendor runs it, in the vendor's cloud accounts, on the vendor's bills.
The live serviceOnline · mappedThe vendor still runs it. We map its live environment at setup and keep that map current.
-
2
The vendor stops
Insolvency, discontinued support, or a material breachThe depositReleased to youIf a release condition in your agreement is met, we check the request against it and hand the deposit to your team.
The live serviceAt riskThe bills stop with the vendor. Suspended hosting or a lapsed domain can take the service offline.
The live serviceKept onWe keep the mapped environment paid and switched on for an agreed period.
-
3
While it's recovered
Self-Run Recovery, by your teamThe depositRecovered by your teamYour team redeploys the service from the deposit, into cloud accounts you control. On Escrow Pro, it starts from the last passed run's exit workbook and tested isolated compile.
The live serviceNot coveredNothing keeps the vendor's environment on, so your people may wait until the redeployed service is up.
The live serviceStill switched onThe environment stays on, so the service can keep running while your team recovers it.
Choose who runs the recovery, and whether the service stays on.
Self-Run RecoveryEscrow This page
For the software your own team can bring back. Guard every layer of a critical SaaS application in a neutral vault, and let your own team redeploy it when a release condition is met.
From $299
Managed RecoveryResilience
For the software you can't risk rebuilding yourself. Relaunch a critical SaaS application after a failure, with Codekeeper's engineers rebuilding the service for you. Explore Resilience
From $499
Full ContinuityContinuity
For the services that just can't go offline. Shield the live service from a vendor's lapsed bills while it's recovered, with its hosting and accounts kept on for an agreed period. Explore Continuity
From $1,599
Escrow or Escrow Pro
The same deposit. Escrow Pro proves it builds.
Escrow and Escrow Pro hold the same layers and release them to your team. The difference is proof: Escrow Pro rebuilds the deposit, so gaps show up early, and every passed run adds evidence to your file.
Escrow
From$299per month
Everything you need to be protected.
Included
- A copy of your software in a neutral vault
- Daily sync through 50+ integrations
- Monthly checks for missing files
- Released to your team to recover
Escrow Pro
RecommendedFrom$649per month
Test the rebuild before you need a recovery.
Everything in Escrow, plus
- Agentic Verification: up to four rebuilds a year, on supported technology stacks
- Codekeeper's own AI, off public models
- Missing files flagged in each rebuild
- A tested isolated compile, ready to deploy
- An exit workbook for the recovery
- Recoverability Certificates and SBOMs
EscrowEscrow CertificateShows the deposit is held and what's in it. Example values.
Escrow ProRecoverability CertificateDocuments the rebuild and its result. It doesn't grant release rights; those come from the agreement. Example values.Every SaaS escrow plan
Kept current, however often your service changes.
Agreements for your deal.
Choose a two-party (bipartite), three-party (tripartite), or multi-party agreement, under the governing law you choose. Our in-house counsel drafts the terms and negotiates them for you.
One deposit, many customers.
Vendors can add customers to the same deposit as they sign, each under the release conditions agreed with them, without a new deposit each time.
Daily syncs, plus uploads.
50+ integrations keep the deposit in step with the live service, and runbooks or environment files can be added by hand at any time.
Tamper-proof versions.
Each snapshot is encrypted with AES-256, behind MFA, in immutable storage, so what's released matches what was last checked.
A full audit trail.
Every change, sync, and access request on the deposit is logged, and each version keeps the date and time it landed.
Release requests, any hour.
Ask for a release by phone, chat, or email, 24/7/365. Our team confirms the condition is met before anything leaves the vault.
Other applications
Protecting a different kind of system?
Software escrowRunning installed software? Hold its source code, data, and documentation.From $199- AI escrowBuilt around a model? Hold the models, agents, prompts, and workflows that run it.From $649
Software BackupHosting a service you built yourself? Keep versioned copies of its code, configuration, and data.From $89
Give every critical subscription a second life.
Talk to a SaaS escrow specialist about what your services would need to come back.
Frequently asked questions
SaaS escrow, answered.
Questions about setup, agreements, or releases in general? See the full FAQ
What is SaaS escrow?
SaaS escrow gives the customers of a cloud application a way back to it if the vendor can't continue. The vendor deposits the application's code, infrastructure, data, credentials, and service details with a neutral escrow agent, such as Codekeeper, who holds them for both sides and releases them if a condition in the agreement is met.
What does a SaaS escrow deposit hold beyond the code?
Beyond the code, a SaaS escrow deposit holds everything the application runs on: infrastructure definitions and deployment packages, data exports, the credentials and access for its cloud accounts, a record of the third-party services it calls, and its documentation. The agreement lists each item, and the monthly check documents what's in the vault.
How is SaaS escrow different from software escrow?
SaaS escrow is different from software escrow in what the deposit has to capture. Software escrow covers applications installed on your own servers, where the code, build files, and documentation carry most of a recovery. SaaS escrow also has to capture what the vendor runs on your behalf: the cloud infrastructure, the data, and access to the accounts the service lives in.
What triggers a release of a SaaS deposit?
A release of a SaaS deposit is triggered by the release conditions written into your agreement, such as the vendor's insolvency, discontinued support for the service, or a material breach, plus any terms the vendor and their customers add. Our team confirms the condition before anything is released.
Can the service stay online during the recovery?
Yes, the service can stay online during the recovery with Continuity. We map the live environment at setup and keep that map current. If the vendor stops, we keep the environment paid and switched on for an agreed period while the service is recovered, and recharge the bills at cost. Continuity sits on the Escrow or Resilience recovery you choose.
Does Escrow Pro need anything from the vendor?
Escrow Pro only needs something from the vendor when an item is missing. Codekeeper's AI agents rebuild the deposit up to four times a year, on supported technology stacks, and flag gaps mid-run, such as an absent environment variable. The vendor's team adds the missing piece before the next run. Tell us what your service is built with, and we'll confirm the stack is supported before you start.
Who pays for SaaS escrow?
Who pays for SaaS escrow is agreed between the vendor and their customers. Vendors often fund SaaS escrow to clear vendor risk assessments on larger accounts, and customers often fund it because their own operations depend on the service.
How much does SaaS escrow cost?
SaaS escrow costs $299 per month on Escrow and $649 on Escrow Pro, for one SaaS application, plus a setup fee of $499, paid once per agreement. Each agreement includes one beneficiary, and more can be added as an add-on. If a release is ever requested, release processing is $199 per hour. See Escrow pricing.
Do we need SaaS escrow if we have a disaster recovery plan?
Yes, you need SaaS escrow even with a disaster recovery plan, for services you subscribe to. A disaster recovery plan restores the systems you run, but the code and configuration behind a hosted service sit with its vendor. For a service you build and host yourself, Software Backup is the closer fit.