Source Code Escrow Account Levels

A one-size-fits-all escrow rarely fits the deal in front of you. The right account level reflects how many parties you are protecting and how their relationships differ, and choosing it well affects both your security and your cost. The first question is simple: how many beneficiaries are involved?
The short version. The dividing line is the number of beneficiaries. A single-beneficiary agreement is the simplest. Multiple-beneficiary agreements come in three forms: separated products (MB-SP), separate escrows (MB-SE), and a minimum-service version (MB-Min-SP). More parties and more customization mean more administration and cost.
Start with the beneficiary
A beneficiary is the party that stands to gain from a release, usually the licensee who needs the code for continuity if a trigger condition (bankruptcy, closure, discontinued support) occurs. The primary distinction between account levels is whether your agreement protects a single beneficiary or several.
Single-beneficiary agreements
One licensor, one beneficiary. These are the least complex and simplest to manage, with triggers specific to the one vendor-customer relationship. They suit bespoke software or a single customer that needs assurance. Example: a company running on proprietary software negotiates a single-beneficiary agreement so it can access the code if the vendor cannot support it. See the single-beneficiary structure.
Multiple-beneficiary agreements
One licensor, several beneficiaries. These address the rights, obligations, and release conditions of multiple parties, so they carry more administration and cost, and terms can differ by beneficiary. They suit a vendor with a broad customer base that wants uniform protection across clients. Example: a vendor with many enterprise customers sets up one multi-beneficiary agreement that assures all of them. See multi-beneficiary and multi-vendor structures.
The three multiple-beneficiary types
| Type | What it is | Best suited to |
|---|---|---|
| MB-SP (separated products) | One agreement covering many beneficiaries, with materials organized by product; only the relevant product releases to a given beneficiary | Vendors offering several products to different clients, with less admin |
| MB-SE (separate escrows) | A distinct agreement and deposit for each beneficiary, with unique terms and release conditions | Vendors licensing customized versions; highest control, higher cost |
| MB-Min-SP (minimum service) | MB-SP without advanced services; may exclude full verification, testing, or detailed reporting, with confirmations to the owner only | Budget-conscious coverage with basic service |
Separated products vs separate escrows
The choice between the two main multi-beneficiary forms comes down to centralization. Separated products (MB-SP) is a centralized arrangement: one agreement for all beneficiaries, less administrative burden, and only the product relevant to a beneficiary releases under its conditions. Separate escrows (MB-SE) gives each beneficiary its own agreement, deposit, and terms, which is more complex and typically more expensive but offers the highest customization and control, ideal for vendors licensing tailored versions to different clients.
How to choose
Count the beneficiaries, weigh how much their relationships differ, and balance customization against cost. A single beneficiary points to the simplest agreement; many similar clients point to MB-SP; clients needing distinct terms point to MB-SE; a tight budget with basic needs points to MB-Min-SP. Each is a starting point that source code escrow agreements customize further, and the structure also shapes the cost.
Frequently asked questions
What is the difference between single and multiple beneficiary escrow?
A single-beneficiary agreement protects one licensee and is simplest to manage. A multiple-beneficiary agreement protects several licensees under one vendor, which adds administration, cost, and potentially different terms per beneficiary.
What is MB-SP escrow?
Multiple Beneficiary with Separated Products: one agreement covers many beneficiaries, with materials organized by product, so only the product relevant to a given beneficiary is released to them.
What is MB-SE escrow?
Multiple Beneficiary with Separate Escrows: each beneficiary has a distinct agreement and deposit with unique terms. It offers the highest control and customization but costs more to administer.
What is MB-Min-SP escrow?
A minimum-service version of MB-SP that omits advanced services such as full verification, testing, or detailed reporting, with account confirmations going to the owner only. It suits basic, budget-conscious coverage.
How do I choose the right escrow account level?
Count the beneficiaries and weigh how much their relationships differ against cost. One beneficiary points to a single agreement; many similar clients to MB-SP; clients needing distinct terms to MB-SE; basic budget needs to MB-Min-SP.
Match the structure to your deal.
See how single and multiple-beneficiary agreements work, and which level fits the parties you need to protect.
See how source code escrow works → Or talk to our team