One customer, one agreement.
The most direct structure: one beneficiary protected under one escrow agreement, covering a single critical software dependency.
The simplest structure.
One agreement, one beneficiary. The cleanest fit when a single party needs to protect a single dependency.
A single licensee securing a critical vendor, or a vendor satisfying one enterprise buyer's escrow requirement. The release conditions are written around that one relationship, and verified to the level the risk calls for.
Two ways it fits.
The same clean structure answers two different needs, from two sides of the same deal.
Protect one dependency.
You depend on one critical vendor and want a documented, recoverable fallback for it.
Satisfy one buyer.
A single enterprise buyer made escrow a condition of signing. This is the structure that answers it.
Verified to the one risk.
Verification is a menu matched to the single risk you are covering, from a file listing up to a full build. You choose the depth.
EscrowTech does not verify every deposit by default, and the top of the ladder is never standard or included. The depth is the one you choose, matched to what this dependency is worth to you. See verification options →
Two vaults. One in a granite mountain.
Deposits are held in two physical, US-based vaults, one inside a granite mountain, monitored around the clock. The provider has to satisfy the people who approve the deal, and EscrowTech is the one their legal teams already recognize.
Single-beneficiary escrow, answered.
The questions licensees, vendors, and their counsel ask most often.
What is a single-beneficiary software escrow?
A single-beneficiary software escrow is the simplest structure: one beneficiary protected under one escrow agreement. A neutral third party holds the vendor's source code and the materials needed to rebuild the software, and releases them to that one beneficiary only if a condition written into the agreement is met.
Who is a single-beneficiary escrow agreement for?
Two buyers, mainly. A licensee protecting one critical vendor dependency, and a vendor satisfying a single enterprise customer's escrow requirement. When only one relationship needs covering, a single-beneficiary escrow agreement is the cleanest fit.
What is the difference between single-beneficiary and multi-beneficiary escrow?
A single-beneficiary escrow covers one beneficiary under one agreement. A multi-beneficiary escrow covers many of a vendor's customers under one managed deposit, without re-depositing for each. Single-beneficiary is the more direct structure when only one party needs protection.
What is included in a single-beneficiary escrow agreement?
The two parties and EscrowTech's neutral role, the deposited materials, the release conditions, the verification level, and the beneficiary's rights on release. EscrowTech drafts the escrow agreement around that one relationship, not the underlying commercial contract.
What are the release conditions in a single-beneficiary escrow?
The triggers that release the deposit to the beneficiary, such as the vendor ceasing business, filing for bankruptcy, or failing to support the software. They are written around your one relationship, to fire in the situations you are actually worried about.
Who drafts the single-beneficiary escrow agreement?
EscrowTech's in-house counsel drafts the escrow agreement and stays neutral between the two parties. It drafts the escrow arrangement only, not the commercial contract between the vendor and the beneficiary.
Is the deposit verified in a single-beneficiary escrow?
Only to the depth you choose. Verification is a menu of options, from a file listing up to a full build, matched to the one risk you are covering. EscrowTech does not verify every deposit by default, and the top of the ladder is never automatic or included.
How long does a single-beneficiary escrow take to set up?
Most single-beneficiary agreements are drafted, reviewed, and signed in about two weeks. With one beneficiary and one agreement, there is little to slow it down. Escrow being the slow part of a deal is usually a provider problem, not an escrow problem.
Priced to your structure.
A single-beneficiary escrow starts at $1,595 a year, custom-priced to your structure and how far you verify, so you know what you are committing to before you begin. See pricing →
Covering many customers instead? See multi-beneficiary → · Back to software escrow →
Make it safe to depend on.
Tell us about the dependency you are protecting. We'll structure the single-beneficiary escrow around it.
Thanks, we've got it.
A member of our team will be in touch shortly.