United States: Source Code Escrow: Are You Just Following The Herd?, CIO.com

Last Updated: March 12 2008
Article by Shawn C. Helms

Growing up, mothers train their children to resist mindlessly following their peers by asking the glib question: "if your friend jumped off a bridge, would you?" This simple question is packed with insight. Independent thought that questions others' habits, beliefs and actions is a hallmark of maturity. However, today's business culture sometimes fails this childhood test.

Take source code escrow. Without truly considering it, many organizations have a standing policy to require software developers to escrow source code of products the organization is licensing. If organizations would carefully analyze the risk / return investment, the business case for source code escrow arrangements would almost always come up negative. Dealmakers and lawyers spend countless hours negotiating escrow terms and conditions and pay escrow agents like Iron Mountain thousand of dollars to maintain the escrow account. This time and money is often a wasted investment, as the potential benefits are marginal. Customers should be skeptical of expending valuable time and money on an arrangement that is largely ineffective at accomplishing the very purpose for which it was created. Before explaining why, let's first discuss what software source code escrow is and why it has become a common part of many software transactions.

What is "Source Code" and Why is it Escrowed

Every day, companies around the world license and implement custom software applications that are critical to the operation of their businesses. Development and implementation can cost millions of dollars. Because these applications are critical, software development and maintenance contracts often require the software developers to store the "source code" of the software and explanatory documentation in an escrow account. Source code is the sequence of logical statements and operations written in a human-readable computer programming language that controls the processing of data and the functionality of software. The source code itself can be hundreds of thousands of lines of code and is normally designed and written by software programmers in programming languages such as C++, Java or Visual Basic. When completed, the source code is compiled into "executable code" that can be downloaded, installed and run on a computer. However, with only the executable code, customers have no ability to see how the software is processing data or performing functions and, for the most part, have no ability to change the operation of the software.

Because repairing problems or changing functionality is only possible with the source code, the escrow of source code is common in large software transactions involving custom developed or operationally critical applications. In a source code escrow arrangement, the source code and documentation are held in escrow by a trusted third party, the escrow agent. The source code and related documentation are to be released upon the occurrence of a "release event" such as the software developer filing bankruptcy or failing certain obligations under the license.

Following a release event, the promise of a source code escrow is that the customer can obtain the code to maintain the software without the original developer. This maintenance involves fixing bugs, ensuring compatibility with other system upgrades and adding the functionality required in the customer's changing business.

Software maintenance is essential to enterprise applications. Because the customer has no assurance that the software developer will always be around to perform software maintenance, and since such maintenance cannot be performed without the source code, escrow is considered a necessary part of certain software deals.

Why Escrow is an Ineffective and Costly Mechanism

For the reasons described above, escrowing source code of critical business software seems to be a prudent business decision for customers. However, for various reasons, the time, legal fees and other resources spent establishing and maintaining escrow accounts provide little protection for the customer.

1. Only a Small Percentage of Escrows are Ever Released

First, only a small percentage of escrowed software is ever released. Iron Mountain, the dominate escrow agent in the United States, has thousands of escrow accounts and more than 45,000 customers worldwide that have stored their software and intellectual property with Iron Mountain, including over 75 percent of the Fortune 500 (http://www.ironmountain.com/ipm/escrow/). Over the ten year period from 1990 to 1999, Iron Mountain released 96 escrow accounts, less than 10 per year (http://www.ironmountain.com/knowledge/ipm/deposit.asp). While it is unclear how many are typically released in a given year, these low release rates are indicative of the fact that rarely does a release event occur and, when it does, customers often find it easier to find an alternative software provider.

2. Most Escrowed Source Code is Defective

While some customers may view a source code escrow as an insurance policy to protect themselves in the slight chance that a release event occurs, often source code escrows fail to provide adequate protection because, upon release, the source code is frequently outdated, defective or otherwise fails to meet the customer's needs. According to Iron Mountain, 97.4% of all analyzed escrow material deposits have been found incomplete and 74% have required additional input from developers in order to be compiled (www.ironmountain.com/resources/escrow/IMD_DS_TechVerification.pdf).

Take, for example, what happened to Radisson Hotels Worldwide. Several years ago, Radisson hired a third party software company to maintain its mission critical reservation system. The software vendor agreed to escrow the Radisson software code. The code was eventually released as a result of the software vendor going out of business. But upon release, Radisson found that the source code in escrow could not even perform the fundamental and critical task of booking guests at Radisson's hotels. The released code was missing many components and the escrow account did not contain any documentation developed after the initial escrow of the software (http://www.bankruptcy.rutgers.edu/source_code_escrow.pdf). This unfortunate discovery is not atypical in source code escrow arrangements, especially when the customer has not been vigilant in continually monitoring and auditing what is being stored with the escrow company.

3. Customers Lack Expertise to Use the Released Source Code

Even if the customer has been diligent and the released source code is properly updated, well-documented, and fully operational, most customers lack the resources or capability to utilize the code upon release. In most cases, source code has been escrowed because customers are licensing software from a vendor that is providing technology and expertise that the customer does not possess internally. Thus, once the software is released from escrow, the customer often is in no position to properly implement the software, train its employees on maintaining and supporting the software, or purchase the necessary hardware and third party software. In addition, this process of bringing such software in-house can be lengthy and demanding on a company's resources. Further, the customer will likely be faced with a shortage of available talent knowledgeable on the released software, especially because many software license agreements prohibit customers from soliciting the vendor's employees upon termination of the licensing arrangement. All of these factors combined make it extremely difficult for a customer to utilize source code upon release, even if the code is in pristine condition. The only alternative for the customer is to hire a third party software company. This is an expensive alternative and is often no better than moving to an alternative product. Furthermore, with this decision, the customer is back to where it started – relying on a third party to properly maintain the code.

4. Significant Delays and Legal Battles Often Accompany a Release

Another problem is that software vendors have the ability to prevent the timely release of the escrowed code and customers have limited recourse to prevent such a delay. It is not unusual for an escrow agreement to require the vendor's approval before the source code is released; thus, even if the customer demands the escrow agent to release the software upon a release event, the escrow agent is prohibited from doing so until it receives the approval of the vendor. Delays in the release of the software are problematic because vendors may not keep the software properly updated during the period of time that the parties are disputing the release of the software.

Adding to the delay, escrow agreements often require parties to participate in alternative dispute resolution proceedings, such as arbitration or mediation, in the event of a dispute regarding the release of the source code. A commonly disputed issue is whether a release event has actually occurred. Although parties strive to clearly and completely define the triggers for a release of the software in software license agreements and escrow agreements, the language in these agreements may be ambiguous as to whether certain circumstances qualify as a release event. Therefore, the vendor can almost always dispute that such an event has occurred. A prime example of this can be found in the recent court case between Vemics, Inc. and Radvision, Ltd. (Vemics, Inc. v. Radvision, Ltd., No. 07-CV-0035, 2007 WL 1459290 (S.D.N.Y. May 16, 2007)). In this case, Vemics purchased a software license from First Virtual Communications (FVC), and the parties entered into a license agreement requiring the software to be placed in escrow and released upon specified release conditions. The parties also entered into a separate escrow agreement with the escrow agent, Iron Mountain. FVC filed for bankruptcy on March 11, 2005, and Radvision became the successor in interest to FVC's rights and obligations under the license agreement and escrow agreement with Vemics. Vemics demanded Iron Mountain to release the source code in January 2006, claiming that FVC's bankruptcy constituted a release event. Interestingly, even though parties typically enter into source code arrangements to, at a minimum, protect the customer's interest in the software in the specific event of the vendor's bankruptcy, Radvision argued that FVC's bankruptcy was not a valid basis for release of the software. Over two years have passed since Vemics demanded the release, with the parties still at odds over whether the source code will ever be released. Even if it is finally released, the long delay and expensive legal battle have been a costly investment for Vemics.

5. Utilizing an Escrow can be Expensive

Another obvious cost consideration is that the expenses related to the opening and maintenance of an escrow account are typically borne by the customer. These fees can amount to thousands of dollars. In addition to the fees paid to the escrow agent, the customer will often incur significant legal expenses related to the drafting and negotiation of escrow agreements. Software developers are resistant to provide their source code to anyone in fear of inadvertent or unnecessary release. Therefore, escrow arrangements are often intensely negotiated. However, these legal expenses pale in comparison to those that the customer will be forced to spend if the vendor disputes the customer's claim that a release event has occurred. The costs of resolving such a dispute can range from thousands of dollars in alternative dispute resolution proceedings to hundreds of thousands (or even millions) of dollars in protracted litigation. A point of great frustration for customers is that these added costs will not change the fact that the customer has no assurance that the source code is useable and has little control over the time period of release.

For these reasons, customers should consider whether or not it makes sense to ever enter into source code escrow arrangements. Despite their appearance of importance, source code escrow arrangements are almost completely ineffective at protecting customers from failing software companies and carry with them significant costs and risks.

The content of this article is intended to provide a general guide to the subject matter. Specialist advice should be sought about your specific circumstances.

To print this article, all you need is to be registered on Mondaq.com.

Click to Login as an existing user or Register so you can print this article.

Authors
 
In association with
Related Topics
 
Related Articles
 
Up-coming Events Search
Tools
Print
Font Size:
Translation
Channels
Mondaq on Twitter
 
Register for Access and our Free Biweekly Alert for
This service is completely free. Access 250,000 archived articles from 100+ countries and get a personalised email twice a week covering developments (and yes, our lawyers like to think you’ve read our Disclaimer).
 
Email Address
Company Name
Password
Confirm Password
Position
Mondaq Topics -- Select your Interests
 Accounting
 Anti-trust
 Commercial
 Compliance
 Consumer
 Criminal
 Employment
 Energy
 Environment
 Family
 Finance
 Government
 Healthcare
 Immigration
 Insolvency
 Insurance
 International
 IP
 Law Performance
 Law Practice
 Litigation
 Media & IT
 Privacy
 Real Estate
 Strategy
 Tax
 Technology
 Transport
 Wealth Mgt
Regions
Africa
Asia
Asia Pacific
Australasia
Canada
Caribbean
Europe
European Union
Latin America
Middle East
U.K.
United States
Worldwide Updates
Registration (you must scroll down to set your data preferences)

Mondaq Ltd requires you to register and provide information that personally identifies you, including your content preferences, for three primary purposes (full details of Mondaq’s use of your personal data can be found in our Privacy and Cookies Notice):

  • To allow you to personalize the Mondaq websites you are visiting to show content ("Content") relevant to your interests.
  • To enable features such as password reminder, news alerts, email a colleague, and linking from Mondaq (and its affiliate sites) to your website.
  • To produce demographic feedback for our content providers ("Contributors") who contribute Content for free for your use.

Mondaq hopes that our registered users will support us in maintaining our free to view business model by consenting to our use of your personal data as described below.

Mondaq has a "free to view" business model. Our services are paid for by Contributors in exchange for Mondaq providing them with access to information about who accesses their content. Once personal data is transferred to our Contributors they become a data controller of this personal data. They use it to measure the response that their articles are receiving, as a form of market research. They may also use it to provide Mondaq users with information about their products and services.

Details of each Contributor to which your personal data will be transferred is clearly stated within the Content that you access. For full details of how this Contributor will use your personal data, you should review the Contributor’s own Privacy Notice.

Please indicate your preference below:

Yes, I am happy to support Mondaq in maintaining its free to view business model by agreeing to allow Mondaq to share my personal data with Contributors whose Content I access
No, I do not want Mondaq to share my personal data with Contributors

Also please let us know whether you are happy to receive communications promoting products and services offered by Mondaq:

Yes, I am happy to received promotional communications from Mondaq
No, please do not send me promotional communications from Mondaq
Terms & Conditions

Mondaq.com (the Website) is owned and managed by Mondaq Ltd (Mondaq). Mondaq grants you a non-exclusive, revocable licence to access the Website and associated services, such as the Mondaq News Alerts (Services), subject to and in consideration of your compliance with the following terms and conditions of use (Terms). Your use of the Website and/or Services constitutes your agreement to the Terms. Mondaq may terminate your use of the Website and Services if you are in breach of these Terms or if Mondaq decides to terminate the licence granted hereunder for any reason whatsoever.

Use of www.mondaq.com

To Use Mondaq.com you must be: eighteen (18) years old or over; legally capable of entering into binding contracts; and not in any way prohibited by the applicable law to enter into these Terms in the jurisdiction which you are currently located.

You may use the Website as an unregistered user, however, you are required to register as a user if you wish to read the full text of the Content or to receive the Services.

You may not modify, publish, transmit, transfer or sell, reproduce, create derivative works from, distribute, perform, link, display, or in any way exploit any of the Content, in whole or in part, except as expressly permitted in these Terms or with the prior written consent of Mondaq. You may not use electronic or other means to extract details or information from the Content. Nor shall you extract information about users or Contributors in order to offer them any services or products.

In your use of the Website and/or Services you shall: comply with all applicable laws, regulations, directives and legislations which apply to your Use of the Website and/or Services in whatever country you are physically located including without limitation any and all consumer law, export control laws and regulations; provide to us true, correct and accurate information and promptly inform us in the event that any information that you have provided to us changes or becomes inaccurate; notify Mondaq immediately of any circumstances where you have reason to believe that any Intellectual Property Rights or any other rights of any third party may have been infringed; co-operate with reasonable security or other checks or requests for information made by Mondaq from time to time; and at all times be fully liable for the breach of any of these Terms by a third party using your login details to access the Website and/or Services

however, you shall not: do anything likely to impair, interfere with or damage or cause harm or distress to any persons, or the network; do anything that will infringe any Intellectual Property Rights or other rights of Mondaq or any third party; or use the Website, Services and/or Content otherwise than in accordance with these Terms; use any trade marks or service marks of Mondaq or the Contributors, or do anything which may be seen to take unfair advantage of the reputation and goodwill of Mondaq or the Contributors, or the Website, Services and/or Content.

Mondaq reserves the right, in its sole discretion, to take any action that it deems necessary and appropriate in the event it considers that there is a breach or threatened breach of the Terms.

Mondaq’s Rights and Obligations

Unless otherwise expressly set out to the contrary, nothing in these Terms shall serve to transfer from Mondaq to you, any Intellectual Property Rights owned by and/or licensed to Mondaq and all rights, title and interest in and to such Intellectual Property Rights will remain exclusively with Mondaq and/or its licensors.

Mondaq shall use its reasonable endeavours to make the Website and Services available to you at all times, but we cannot guarantee an uninterrupted and fault free service.

Mondaq reserves the right to make changes to the services and/or the Website or part thereof, from time to time, and we may add, remove, modify and/or vary any elements of features and functionalities of the Website or the services.

Mondaq also reserves the right from time to time to monitor your Use of the Website and/or services.

Disclaimer

The Content is general information only. It is not intended to constitute legal advice or seek to be the complete and comprehensive statement of the law, nor is it intended to address your specific requirements or provide advice on which reliance should be placed. Mondaq and/or its Contributors and other suppliers make no representations about the suitability of the information contained in the Content for any purpose. All Content provided "as is" without warranty of any kind. Mondaq and/or its Contributors and other suppliers hereby exclude and disclaim all representations, warranties or guarantees with regard to the Content, including all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement. To the maximum extent permitted by law, Mondaq expressly excludes all representations, warranties, obligations, and liabilities arising out of or in connection with all Content. In no event shall Mondaq and/or its respective suppliers be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use of the Content or performance of Mondaq’s Services.

General

Mondaq may alter or amend these Terms by amending them on the Website. By continuing to Use the Services and/or the Website after such amendment, you will be deemed to have accepted any amendment to these Terms.

These Terms shall be governed by and construed in accordance with the laws of England and Wales and you irrevocably submit to the exclusive jurisdiction of the courts of England and Wales to settle any dispute which may arise out of or in connection with these Terms. If you live outside the United Kingdom, English law shall apply only to the extent that English law shall not deprive you of any legal protection accorded in accordance with the law of the place where you are habitually resident ("Local Law"). In the event English law deprives you of any legal protection which is accorded to you under Local Law, then these terms shall be governed by Local Law and any dispute or claim arising out of or in connection with these Terms shall be subject to the non-exclusive jurisdiction of the courts where you are habitually resident.

You may print and keep a copy of these Terms, which form the entire agreement between you and Mondaq and supersede any other communications or advertising in respect of the Service and/or the Website.

No delay in exercising or non-exercise by you and/or Mondaq of any of its rights under or in connection with these Terms shall operate as a waiver or release of each of your or Mondaq’s right. Rather, any such waiver or release must be specifically granted in writing signed by the party granting it.

If any part of these Terms is held unenforceable, that part shall be enforced to the maximum extent permissible so as to give effect to the intent of the parties, and the Terms shall continue in full force and effect.

Mondaq shall not incur any liability to you on account of any loss or damage resulting from any delay or failure to perform all or any part of these Terms if such delay or failure is caused, in whole or in part, by events, occurrences, or causes beyond the control of Mondaq. Such events, occurrences or causes will include, without limitation, acts of God, strikes, lockouts, server and network failure, riots, acts of war, earthquakes, fire and explosions.

By clicking Register you state you have read and agree to our Terms and Conditions