Source code escrow

From Wikipedia, the free encyclopedia - View original article

 
Jump to: navigation, search

Source code escrow is the deposit of the source code of software with a third party escrow agent. Escrow is typically requested by a party licensing software (the licensee), to ensure maintenance of the software. The software source code is released to the licensee if the licensor files for bankruptcy or otherwise fails to maintain and update the software as promised in the software license agreement.

Necessity of escrow[edit]

As the continued operation and maintenance of custom software is critical to many companies, they usually desire to make sure that it continues even if the licensor becomes unable to do so, such as because of bankruptcy. This is most easily achieved by obtaining a copy of the up-to-date source code. The licensor, however, will often be unwilling to agree to this, as the source code will generally represent one of their most closely guarded trade secrets.[1]

As a solution to this conflict of interest, source code escrow ensures that the licensee obtains access to the source code only when the maintenance of the software cannot otherwise be assured, as defined in contractually agreed-upon conditions.[2]

Escrow agreements[edit]

Source code escrow takes place in a contractual relationship, formalized in a source code escrow agreement, between at least three parties:

The service provided by the escrow agent – generally a business dedicated to that purpose and independent from either party – consists principally in taking custody of the source code from the licensor and releasing it to the licensee only if the conditions specified in the escrow agreement are met.[2]

Source code escrow agreements provide for the following:

Whether a source code escrow agreement is entered into at all, and who bears its costs, is subject to agreement between the licensor and the licensee. Software license agreements often provide for a right of the licensee to demand that the source code be put into escrow, or to join an existing escrow agreement.[4]

Bankruptcy laws may interfere with the execution of a source code escrow agreement, if the bankrupt licensor's creditors are legally entitled to seize the licensor's assets – including the code in escrow – upon bankruptcy, preventing the release of the code to the licensee.[6]

Free software[edit]

The escrow agreements described above are most applicable to custom-developed software which is not available to the general public. In some cases, source code for commercial off-the-shelf software may be deposited into escrow to be released under a free software or open source license when the original developer ceases development and/or when certain fundraising conditions are met. This model is also called ransomware. The Blender graphics suite was released in this way following the bankruptcy of Not a Number Technologies; the widely used Qt toolkit is covered by a source code escrow agreement secured by the "KDE Free Qt Foundation".

References[edit]

  1. ^ Heusler, Bernhard; Mathys, Roland (2004). IT-Vertragsrecht (in German). Zürich: Orell Füssli. p. 177. ISBN 3-280-07030-9. 
  2. ^ a b c Heusler/Mathys, p. 178.
  3. ^ a b Heusler/Mathys, p. 179.
  4. ^ a b c Heusler/Mathys, p. 180.
  5. ^ a b Heusler/Mathys, p. 181.
  6. ^ Heusler/Mathys, p. 182.

Further reading[edit]