Know a company with years of records? Refer it and earn up to $100K
Source code

Source Code Escrow vs Licensing Code for AI Training

Source code escrow explained: deposits, release conditions and verification, and how licensing code with git history to AI companies differs.

Short answerChecked

Source code escrow is a three-party arrangement in which a software vendor deposits its code with an escrow agent, who hands it to a customer only if agreed events happen, such as the vendor failing to support the product. Licensing code for AI training works the other way round: an AI company gets a copy now, often with git history and tickets, under a written license, and pays for it. Escrow protects a customer; a training license can earn the owner money.

A laptop showing a code diff with a sprint board behind
Key points
  • An escrow deposit stays the vendor's property; the customer only gets it if a release condition in the escrow agreement is met.
  • Typical release conditions are insolvency, failure to support or maintain the software, end of a SaaS service and, in some agreements, a change of ownership.
  • Verification ranges from a check that the deposit is readable to a full independent rebuild of the application.
  • A license for AI training grants rights now, under 17 U.S.C. 106 and 201(d), and buyers value commit history and linked tickets, not just the latest code.

Source code escrow and code licensing: the rules side by side

Escrow and licensing rest on the same legal base: the vendor owns the copyright in its code and decides who may copy it, when and why. The difference is timing and purpose. An escrow agreement promises a copy later, if something goes wrong. A license grants a copy now, for a stated use.

Rule or sourceWhat it saysWhat it means for youDate checked
17 U.S.C. 106The copyright owner has the exclusive rights "to reproduce the copyrighted work" and "to prepare derivative works"Copying code into an escrow vault or a training set needs the owner's permission20 Nov 2026
17 U.S.C. 201(d)Any of the exclusive rights "may be transferred" and owned separatelyYou can license one right, such as copying for AI training, and keep the rest20 Nov 2026
17 U.S.C. 201(b)For a work made for hire, the employer "is considered the author"Code written by employees on the job usually belongs to the company20 Nov 2026
11 U.S.C. 365(n)A licensee may retain its rights under the license "and under any agreement supplementary to such contract"An escrow agreement tied to a license can survive the vendor's bankruptcy20 Nov 2026
King County escrow form (public RFP exhibit)The deposit "shall remain the exclusive property of the Licensor"Escrow is a promise of access, not a transfer of the code20 Nov 2026
US Copyright Office, Circular 61Copyright does not protect "the functional aspects of a computer program"Your expression is protected; your algorithms and logic need trade secret care20 Nov 2026

Sources: 17 U.S.C. 106, 17 U.S.C. 201, 11 U.S.C. 365, King County's escrow form and Circular 61. General information, not legal advice.

What is source code escrow, and how does a software escrow agreement work?

Source code escrow, also called software escrow, protects a customer that depends on software it cannot fix itself. The vendor, the customer (the licensee) and an independent escrow agent sign a source code escrow agreement. The vendor deposits its source code and documentation with the agent and updates the deposit as new releases ship. The agent holds the material and releases it to the customer only when a listed event happens. If none happens, the deposit is returned or destroyed when the license ends.

A public example shows the moving parts. King County, Washington, published a source code escrow agreement as an exhibit to a software tender. The vendor promises to supplement the deposit "with all revisions, corrections, enhancements, or other changes", and the agent keeps the code in safekeeping until it receives a notice under the agreement. The agent is a custodian, not a reviewer: the form says it "shall not be obligated or required to examine or inspect the Source Code".

A source code escrow clause in the main license usually does three things: it obliges the vendor to sign an escrow agreement with a named agent, it says which product versions must be deposited and how often, and it lists or refers to the release conditions. The separate escrow agreement then carries the detail. Services sold as source code escrow services or software escrow services add verification, online deposit tools and dispute handling on top.

What does a source code escrow deposit hold?

Enough for someone else to keep the software running. The King County form asks for a full source language statement of the program plus "all other material necessary to allow a reasonably skilled third party programmer or analyst to maintain or enhance the Product without the help of any other person". That is the right test for any deposit: could a stranger build and support this?

For hosted software the code alone is not enough. NCC Escode, an escrow agent, lists what a SaaS escrow deposit should hold: "Source code Build instructions Deployment scripts Infrastructure configuration API documentation Technical documentation". A modern deposit is often an automated copy of the repository plus infrastructure-as-code files and a runbook. Sources: King County and NCC Escode on SaaS escrow.

  • Source code for the release the customer runs, in a form that can be compiled.
  • Build scripts, dependency lists with exact versions, and compiler or toolchain notes.
  • Deployment scripts and infrastructure configuration for hosted products.
  • Database schemas, API documentation and an architecture overview.
  • Credentials and keys stay out of the deposit; the agreement says how they are handed over at release.

What are the release conditions in a source code escrow agreement?

Release conditions are the events that let the customer take the deposit. They are negotiated, so they differ from one agreement to the next. The King County form lists five kinds of default, including a vendor that "is unable to discharge any of its maintenance obligations" and one that "becomes insolvent, makes a general assignment for the benefit of creditors, files a voluntary petition of bankruptcy".

NCC Escode's list for current agreements adds two that matter for SaaS companies: "Discontinuation of service", which covers "decommissioning of the platform or application", and "Merger or acquisition risk", where a change of ownership affects the vendor's ability or willingness to support the software. A SaaS company being acquired should read its escrow agreements before signing the deal.

Release is rarely instant. The escrow agent's process "includes written notice, a supplier response window, and a clear route for approval or dispute", in Escode's words. In the King County form the vendor can stop a release by filing an affidavit stating that no default has occurred, which sends the dispute to mediation or court. Sources: NCC Escode on release conditions and King County.

What do escrow verification levels check?

A deposit nobody has opened may be empty, outdated or impossible to build. Verification is the paid service that checks it. Escode describes levels "from basic deposit reviews through to full build and deployment testing". The basic level confirms the files are present, readable and free of viruses. Build verification "confirms the source code can be compiled into a working application". The top levels rebuild the whole production setup in a clean environment run by the agent, which is the only way to know a release would really work. Source: NCC Escode on verification.

For a vendor, a verified deposit is a sales asset: large customers and regulated buyers often ask for it. It also produces a side benefit worth noting below. A team that can hand an outsider a buildable repository, with documented dependencies, already holds code in the shape an AI company wants to license.

How is licensing code for AI training different from source code escrow?

Escrow is insurance bought by a customer. A source code license agreement for AI training is a sale of rights by the owner. The table sets them side by side.

QuestionSource code escrowCode license for AI training
Who asks for itA customer that relies on the softwareAn AI company that trains or tests coding models
Who paysUsually the vendor or customer pays the escrow agentThe AI company pays the code owner
When the code movesOnly after a release conditionAt signing, on an agreed delivery date
What movesThe current release and build materialsCode with commit history, often tickets, reviews and test results
Rights grantedUse to support and maintain the licensed productUse to train or evaluate models, usually a non-exclusive license
What the owner keepsEverything; the deposit stays its propertyOwnership, and every use not granted

Code licensing for AI does not stop you selling or supporting the product. A non-exclusive license leaves you free to license the same code to others, and you keep running the business.

What does a code license for AI include: git history, tickets, security logs and cloud bills?

More than an escrow deposit. Escrow wants the latest buildable release; AI buyers want the story of how the code got there. Researchers who built the CommitPack dataset described the value of "the natural structure of Git commits, which pair code changes with human instructions". The SWE-bench benchmark was built from "software engineering problems drawn from real GitHub issues and corresponding pull requests". In both, the link between a written problem and the code change that solved it is the useful part. Sources: CommitPack and SWE-bench.

That is why a B2B SaaS company with 500 to 2,000 staff holds more than code. Git history shows every change and its author. Tickets in Jira or a helpdesk explain why each change was made. Code reviews, CI results and incident postmortems show what failed. Security logs and cloud bills record how the system behaved in production; our guide to audit log examples shows what those files contain. Each needs its own check for customer data before it leaves the building.

Who owns the source code, and what does escrow not change?

Code written by employees within their jobs is normally the company's: under 17 U.S.C. 201(b) the employer "is considered the author" of a work made for hire. Code from contractors and agencies belongs to them unless a signed assignment says otherwise, so check every outside developer's contract. Open-source components stay under their own licenses, and code a customer paid you to build may belong to that customer.

Escrow changes none of this. The deposit "shall remain the exclusive property of the Licensor", as the King County form puts it, and a released deposit gives the customer a right to use the code for its own support, not to resell or license it. So a vendor with code in escrow can still license the same code for AI training. Read each escrow agreement and customer contract for confidentiality terms first; some customer contracts restrict how code written for them can be used.

Shutting down or being acquired: escrow, license or both

Both events touch escrow. A wind-down can trigger release conditions such as discontinuation of service, so customers may receive deposits. An acquisition can trigger change-of-control clauses. Neither prevents a training license, but timing matters: the code, history and tickets have to be exported while the systems and the people who understand them are still there.

In bankruptcy, 11 U.S.C. 365(n) lets a licensee keep its rights under the license "and under any agreement supplementary to such contract", including "any right to obtain such intellectual property (or such embodiment) from another entity". Mayer Brown advises licensees to "obtain an escrow of tangible embodiments of the licensed intellectual property (e.g. source code)" for that reason. For the sale of the product itself, see how to sell an app and SaaS valuation multiples. Sources: 11 U.S.C. 365 and Mayer Brown.

What is your code worth to AI companies?

AI companies pay $20K to $5M for company records, depending on volume, history, rights and how clean the data is. For code the drivers are size, languages, years of commit history, how well tickets link to commits, and clean ownership. Our guide on selling source code for AI training covers what buyers value, the ownership checks and how to describe a code base without sharing it.

We help you license your data. Origin Data Partners is an independent data partner that helps business owners value and license their company records: the company pays Origin nothing, and a buyer may pay Origin when a deal completes. Start with a description, not a copy: repositories, languages, years of history, the ticket system and what you are sure you own. Then check what your code and records may be worth. Not the owner? Advisers can introduce the company.

How we checked this

We read every source on this page on 20 November 2026: the copyright statute (17 U.S.C. 106 and 201) and the bankruptcy statute (11 U.S.C. 365) on Cornell's Legal Information Institute, the US Copyright Office's Circular 61, a public escrow agreement published by King County, Washington, an escrow agent's own service pages, a Mayer Brown client note, and two research papers on code datasets.

What we could not verify: the fees escrow agents charge, because the agent we read publishes no price list; how often release conditions are triggered in practice; and the terms of private escrow agreements, which are not public. Escrow fees are set by the agent and agreed between the parties.

Common questions

What is the source code escrow clause?

A source code escrow clause is the part of a software license that requires the vendor to deposit its code with an independent escrow agent. It names the agent or how one is chosen, the versions to deposit and how often, who pays, and the events that let the customer take the code. The detail usually sits in a separate escrow agreement signed by all three parties.

What is a 3rd party escrow?

A third-party escrow has three signers: the software vendor, the customer and an independent escrow agent. The agent holds the deposit for the customer's benefit and releases it only under the terms all three agreed. Because the agent is independent, neither the vendor nor the customer can take the code alone, and disputes about a release go to the process the agreement sets, such as mediation or court.

Who owns the source code?

Usually the company whose employees wrote it, because work made for hire belongs to the employer under 17 U.S.C. 201(b). Contractors own what they write unless a signed agreement assigns it. Escrow does not move ownership: the deposit stays the vendor's property, and a release only lets the customer use the code to support its own system. Check outside developers' contracts before licensing anything.

Can source code be copyrighted?

Yes. The US Copyright Office says protection for a computer program extends to all of the copyrightable expression in it, and you register a program by depositing its source code, with trade secret parts blocked out if needed. Copyright does not cover algorithms, logic or system design. Those functional parts are protected, if at all, by keeping them confidential, which is one reason escrow and licenses carry strict confidentiality terms.

How much does source code escrow cost?

Escrow agents set their own fees, usually a yearly charge for holding the deposit plus extra charges for each verification test and for releases. The agent we read publishes no price list and quotes on request. Agreements say who pays: in the King County form the agent receives a fee agreed by the parties, paid by the vendor. Full build verification costs more than a simple deposit check.

Can a B2B SaaS company sell or license its source code and engineering data to AI companies? Who buys it and what does it pay?

Yes, if it owns the code and checks its customer contracts. AI developers license private code bases, with commit history and linked tickets, to train and test coding models. AI companies pay $20K to $5M for company records, depending on volume, history, rights and how clean the data is. The deal is usually a non-exclusive license, so the company keeps its product. Our guide on selling source code for AI training explains what buyers value.

What can a SaaS company that is shutting down or being acquired do with its codebase and engineering tickets?

Several things at once. It must honor escrow agreements, which may release deposits to customers. It can sell the product, or license the code base and tickets for AI training under a non-exclusive license. It should export repositories, ticket history and documentation before systems are switched off. Check employee and contractor assignments, open-source licenses and customer confidentiality terms first.

Who helps a software company license its codebase and git history to AI companies?

Three kinds of help are usually involved. A data partner such as Origin Data Partners helps value the code base and license it, at no cost to the company. A lawyer checks the ownership chain, open-source obligations and the license terms. The engineering team prepares a clean export of repositories, commit history and linked tickets, with secrets and customer data removed. Describe the code base first.

Sources and further reading

What is your company’s data worth?

AI companies pay $20K to $5M for company records. Six questions, no files.