Continuity Escrow
Not the code — the running service. Hosting configuration, access credentials and the third-party services the product cannot run without.
Protection scope:Running services
What is deposited
- Hosting and infrastructure configuration, as code where it exists
- DNS records, certificates and domain control
- Access credentials for the operating accounts, sealed and held separately from the deposit itself
- The third-party services the product depends on, with their contracts, account references and renewal dates
- The takeover procedure, written down and tested — who does what, in which order, within which hours
How it comes back out
- 01
The same trigger events as Escrow apply, plus the ones you add on the contract sheet.
- 02
Your customer applies and the release procedure runs exactly as it does for code.
- 03
Credentials are handed over sealed, with a record of what was opened and when.
- 04
The takeover procedure is handed over with them, so somebody can follow it under pressure.
What we owe — and what we don't
We owe
- The pull at the agreed frequency
- Encrypted storage inside the EEA only
- A checksum over each package and each file
- A dated record of every pull to both parties
- The notices
- Running the release procedure to the letter
We do not owe
- That the material is complete, correct, current or authentic
- That it builds, runs or is free of defects or malware
- That it fits the purpose the beneficiary has in mind
- That third-party rights in it exist or are transferable
Every escrow agent's terms say this. Most of them say it on page nine. It is the whole reason Verification exists as a product you can buy.
About VerificationWho it is for
A product that cannot simply be rebuilt from source, because what matters is who holds the keys. Regulated customers ask for this first and for the code second.
What it is not
From €450 per month
Single, Multi and All plans, the setup fee and the add-ons are on the pricing page.
- No release fee
- Inside the EEA only
- Held by a lawyer in Vienna
FAQ
Common questions.
How is it different from SaaS Escrow?
SaaS Escrow holds the code behind the service and what it takes to rebuild it elsewhere. Continuity Escrow holds what keeps the running service running: who holds the keys, the domains and the operating accounts.
How are the credentials held?
Sealed, and separately from the deposit itself. At a release they are handed over sealed, with a record of what was opened and when.
Is the takeover tested?
The takeover procedure is written down and tested — who does what, in which order, within which hours — so somebody can follow it under pressure.