Increase the value of your software escrow
Even with the best intentions, vendors are human — escrow materials can arrive corrupted, incomplete, password-protected, or hard to use. EscrowTech's verification tiers confirm your deposit is complete, clean, and ready when you need it.
A deposit is only as valuable as it is usable
Even with the best intentions, software vendors are human and prone to error. As a result, escrow materials may contain files or components that are corrupted, incomplete, password-protected, difficult to use, or contain viruses.
To resolve this, EscrowTech offers different levels of verification — from a free standard inspection on every deposit to full build and live test plan verification — so customers can match their level of protection to the criticality of the software.
Common deposit issues we catch
- Corrupted or unreadable files
- Missing passwords or encryption keys
- Viruses or malware in deposit materials
- Incomplete source code or documentation
- Missing 3rd-party dependencies
- Build instructions that no longer reproduce a working binary
Standard verification — free
Every time EscrowTech receives escrow materials, a trained escrow technician runs the following checks. If any test fails, we reach out to the software vendor and remedy the problem.
Readability check
A trained escrow technician verifies materials are readable before they enter long-term storage.
Password & encryption check
Confirms materials aren't accidentally locked behind a password or encryption key that's missing from the deposit.
Virus scan
Materials are scanned to ensure they're clean and free of viruses before vaulting.
Five tiers of protection
Choose the level that matches the criticality of the software and your recovery objectives.
File Listing Verification
A full directory listing of the escrow materials so the licensee can perform deeper due diligence on a specific software product.
- File name
- File size
- File type
- Cryptographic hash (MD5 and SHA1)
Deposit Analysis Verification
A trained software engineer reviews the deposit and delivers a detailed report on what may be missing or incomplete — with concrete suggestions.
- Documentation analysis
- Source code check
- 3rd party dependency review
Build Verification
A trained software developer creates an executable from the deposited source code following the vendor's build instructions and configuration.
- Setup & configure a build environment
- Compile sources
- Execute tests
- Package executables
Binary Comparison Verification
Everything in the Build Verification, plus comparing the produced executables against the binaries currently used in production by the licensee.
- Full build verification
- Binary diff against production executables
- Detailed reconciliation report
Test Plan Verification
A software engineer and server architect stand up a production environment, load the source, and run smoke tests — optionally opening it up to the licensee.
- Setup & configure a production environment
- Load and configure source code
- Perform licensee-provided smoke test
- Optional licensee-driven testing
Trained escrow technicians
Every deposit is reviewed by a real human, not just a script.
Detailed reports
Findings, missing pieces, and remediation suggestions delivered to vendor and licensee.
Continuous improvement
Issues are documented and remedied so each new deposit is stronger than the last.
How can we help you?
Tell us about your software and we'll recommend the right verification tier — or design a custom plan around your release scenarios.