Escrow
The source code for software your customer has installed, held by a lawyer in Vienna and released to them only when something has actually gone wrong.
Protection scope:Installed software
What is deposited
- The program code itself, with its version history, branches and tags
- Build scripts and the build, packaging and deployment configuration, including the toolchain
- Every library and dependency needed to build and run, with the complete dependency manifests
- Build documentation good enough that nobody has to call you to use it
- Interface definitions, data model structures and database access descriptions
- Configuration files, environment variables, encryption methods, and credentials, keys and certificates listed by designation, purpose and location
- The register of third-party components with their licenses
- System documentation: architecture, data flows, network topology, operations manual
The standard is not a list, it is an outcome: a competent third party must be able to build, install, configure, operate, maintain and debug the product from the deposit, without you.
How it comes back out
- 01
A trigger event occurs — insolvency, liquidation, the end of support, an uncured material breach.
- 02
Your customer applies, with a court or register document, or with evidence.
- 03
For register facts we release within seven business days, with no objection procedure. For contestable grounds you have fourteen days to object, and a court-certified IT expert decides.
- 04
The deposit is handed over with its checksums, and the license your contract provides takes effect at that moment.
Release procedure
Application 0041-R1
Ground: support discontinued
- 1
Release application received
2026-10-23
- 2
Copy sent to the Depositor within three business days
2026-10-24
- 3
Objection period of 14 calendar days
until 2026-11-07
- 4
Release or expert determination
from 2026-11-07
9 of 14 calendar days remaining
A bare denial is not an objection.
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
Software installed at the customer's own site, under a license and a support contract. The classic case, and the one procurement departments ask about by name.
What it is not
From €150 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.
Who decides whether a trigger event has occurred?
For register facts such as insolvency or liquidation, the document decides: we release within seven business days and there is no objection procedure. For contestable grounds, such as the end of support or a breach, you have fourteen days to object, and a court-certified IT expert decides.
Does my customer see the code before a release?
No. Until a release, your customer receives the dated record of every pull with its checksums, not the code.
Does a deposit prove that the material works?
No. The checksum proves that what was transferred arrived intact — nothing about completeness or whether it runs. Whether a deposit can be built and deployed is a separate test, ordered as the Certified add-on.