UK: Software Escrow Does Not Fit With Cloud - How To Work Round This

Last Updated: 16 July 2012
Article by Frank Jennings

This article was first published on CloudPro.

Many organisations use software escrow for peace of mind but this doesn't work with cloud - what options are available?

Business customers are familiar with software escrow. It can be an effective remedy where a business pays for a software licence but the vendor goes bust. But it's not really an effective answer for cloud customers.

The traditional model of proprietary software licensing has been for software supplier to license the object code to customers and hold back the source code. Without the source code and with complicated practical and legal restrictions on decompiling the object code back to source code the customer can't adapt the software to do what the customer wants. For this, the customer must rely upon the software supplier.

This works fine until the customer and supplier fall out or the supplier goes bust. The answer is escrow where, for a fee, the customer can get the source code if certain events occur. Under this arrangement, the customer will install the object code on its equipment and run it locally. The software supplier will deposit the source code of its proprietary software and relevant documents with a trusted third party – the escrow agent. The escrow agreement between the customer, supplier and escrow agent will specify that if certain "release" or "trigger" events occur, the agent will release the source code and documents to the customer.

Typically, a trigger event is where the supplier fails to maintain the software or becomes insolvent. Once it has the source code, the customer can hire a new supplier to adjust the code to do what the customer needs. That's the theory anyway. It's not a simple task to take someone else's source code and make sense of it, but at least it's an option.

Cloud is different and escrow is not the cure-all that many think. If a customer has opted for a public cloud SaaS offering, that software will likely be a standardised version offered to all customers. The supplier won't want to enter into escrow arrangements with all its customers who are paying rock-bottom prices. Even if it's a bespoke software solution, by the very nature of cloud, there is likely to be very little installed on the client's equipment. Perhaps it will be accessible by via a web browser. Therefore, the customer won't even have the object code but will have access to software run on the supplier's infrastructure.

If there is an escrow arrangement in place and the supplier goes bust, then in theory the customer can now get access to the code and can hand it over to a new supplier. At a practical level, with a traditional software licensing model the customer can still use the software while it finds a new supplier, but with SaaS that might not even be an interim option. In the meantime, with the bust supplier not paying its data centre or electricity bills, the service may have stopped. Relying upon escrow is probably not a viable business continuity strategy.

If a customer still believes escrow can be of value, then it needs to ensure it has access to its data. If the supplier is hosting the data too, then the customer needs to identify how to get this back or, at least, for a new supplier to get hold of it. Perhaps the customer should consider keeping the master or backup copies on its own site through a hybrid cloud model.
Even then, all too often upon release the source code might be out-of-date, incomplete or even defective and of no use.

So the customer will have to keep on top of this by ensuring the escrow agent verifies each deposit of code will do what it is supposed to – and a verification service is usually not cheap. Also, the customer may need to insist upon regular deposits of code as the supplier updates and maintains it. The customer should identify a third party supplier upfront who can step in at short notice. Finally, if the supplier has not gone bust but the relationship has deteriorated, the outgoing supplier might contest that there has been a release event. The escrow agent won't want to get drawn into a dispute between the customer and supplier so both sides may need to engage lawyers.

There might be another way but it will cost more and is not generally available. This would be where one supplier runs the primary service and a secondary supplier runs a back-up or failover service. If the software is proprietary then the primary supplier is unlikely to agree to this. But if the secondary supplier offers a similar service the other way round, it might be an option.

  • So what can a customer realistically do? There are other options which don't involve escrow:
  • Prevention is better than cure. The customer should evaluate its proposed cloud provider. Does it have a good track record and good finances? Does the provider have any standards accreditations such as ISO or with the Cloud Industry Forum? Does its cloud contract adopt the Cloud Industry Forum's best practice recommendations?
  • The customer should draw up a sensible business continuity plan. For example, pay for the additional backup and failover solutions from the supplier. Often, the customers who complain their business is affected by their supplier's outage are the ones who didn't pay for failover.
  • If the supplier is renting space from a data centre, can the customer bypass the supplier and deal direct with the data centre, even if just to get its data back? This is easier where the supplier is bust, but the customer should be thinking about this upfront and addressing it in its contracts.
  • Are there competing products which could provide a similar service? If so how long would it take to switch to a new supplier if the current one goes bust? Getting access to the data may be key here, so the customer should think about having a local copy or one directly accessible from the data centre.
  • The customer should evaluate whether to have a private or hybrid cloud and keep a list of other suppliers who could step in and continue if something happens to their main supplier.

Frank Jennings is chair of the code governance board of the Cloud Industry Forum, co-founder of Cloud Industry Legal Forum and partner in law firm DMH Stallard LLP.

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

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

In association with
Related Video
Up-coming Events Search
Font Size:
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
Confirm Password
Mondaq Topics -- Select your Interests
 Law Performance
 Law Practice
 Media & IT
 Real Estate
 Wealth Mgt
Asia Pacific
European Union
Latin America
Middle East
United States
Worldwide Updates
Check to state you have read and
agree to our Terms and Conditions

Terms & Conditions and Privacy Statement (the Website) is owned and managed by Mondaq Ltd and as a user you are granted a non-exclusive, revocable license to access the Website under its terms and conditions of use. Your use of the Website constitutes your agreement to the following terms and conditions of use. Mondaq Ltd may terminate your use of the Website if you are in breach of these terms and conditions or if Mondaq Ltd decides to terminate your license of use for whatever reason.

Use of

You may use the Website but are required to register as a user if you wish to read the full text of the content and articles available (the Content). 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 & conditions or with the prior written consent of Mondaq Ltd. You may not use electronic or other means to extract details or information about’s content, users or contributors in order to offer them any services or products which compete directly or indirectly with Mondaq Ltd’s services and products.


Mondaq Ltd and/or its respective suppliers make no representations about the suitability of the information contained in the documents and related graphics published on this server for any purpose. All such documents and related graphics are provided "as is" without warranty of any kind. Mondaq Ltd and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information, including all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement. In no event shall Mondaq Ltd 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 or performance of information available from this server.

The documents and related graphics published on this server could include technical inaccuracies or typographical errors. Changes are periodically added to the information herein. Mondaq Ltd and/or its respective suppliers may make improvements and/or changes in the product(s) and/or the program(s) described herein at any time.


Mondaq Ltd requires you to register and provide information that personally identifies you, including what sort of information you are interested in, for three primary purposes:

  • To allow you to personalize the Mondaq websites you are visiting.
  • To enable features such as password reminder, newsletter alerts, email a colleague, and linking from Mondaq (and its affiliate sites) to your website.
  • To produce demographic feedback for our information providers who provide information free for your use.

Mondaq (and its affiliate sites) do not sell or provide your details to third parties other than information providers. The reason we provide our information providers with this information is so that they can measure the response their articles are receiving and provide you with information about their products and services.

If you do not want us to provide your name and email address you may opt out by clicking here .

If you do not wish to receive any future announcements of products and services offered by Mondaq by clicking here .

Information Collection and Use

We require site users to register with Mondaq (and its affiliate sites) to view the free information on the site. We also collect information from our users at several different points on the websites: this is so that we can customise the sites according to individual usage, provide 'session-aware' functionality, and ensure that content is acquired and developed appropriately. This gives us an overall picture of our user profiles, which in turn shows to our Editorial Contributors the type of person they are reaching by posting articles on Mondaq (and its affiliate sites) – meaning more free content for registered users.

We are only able to provide the material on the Mondaq (and its affiliate sites) site free to site visitors because we can pass on information about the pages that users are viewing and the personal information users provide to us (e.g. email addresses) to reputable contributing firms such as law firms who author those pages. We do not sell or rent information to anyone else other than the authors of those pages, who may change from time to time. Should you wish us not to disclose your details to any of these parties, please tick the box above or tick the box marked "Opt out of Registration Information Disclosure" on the Your Profile page. We and our author organisations may only contact you via email or other means if you allow us to do so. Users can opt out of contact when they register on the site, or send an email to with “no disclosure” in the subject heading

Mondaq News Alerts

In order to receive Mondaq News Alerts, users have to complete a separate registration form. This is a personalised service where users choose regions and topics of interest and we send it only to those users who have requested it. Users can stop receiving these Alerts by going to the Mondaq News Alerts page and deselecting all interest areas. In the same way users can amend their personal preferences to add or remove subject areas.


A cookie is a small text file written to a user’s hard drive that contains an identifying user number. The cookies do not contain any personal information about users. We use the cookie so users do not have to log in every time they use the service and the cookie will automatically expire if you do not visit the Mondaq website (or its affiliate sites) for 12 months. We also use the cookie to personalise a user's experience of the site (for example to show information specific to a user's region). As the Mondaq sites are fully personalised and cookies are essential to its core technology the site will function unpredictably with browsers that do not support cookies - or where cookies are disabled (in these circumstances we advise you to attempt to locate the information you require elsewhere on the web). However if you are concerned about the presence of a Mondaq cookie on your machine you can also choose to expire the cookie immediately (remove it) by selecting the 'Log Off' menu option as the last thing you do when you use the site.

Some of our business partners may use cookies on our site (for example, advertisers). However, we have no access to or control over these cookies and we are not aware of any at present that do so.

Log Files

We use IP addresses to analyse trends, administer the site, track movement, and gather broad demographic information for aggregate use. IP addresses are not linked to personally identifiable information.


This web site contains links to other sites. Please be aware that Mondaq (or its affiliate sites) are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of these third party sites. This privacy statement applies solely to information collected by this Web site.

Surveys & Contests

From time-to-time our site requests information from users via surveys or contests. Participation in these surveys or contests is completely voluntary and the user therefore has a choice whether or not to disclose any information requested. Information requested may include contact information (such as name and delivery address), and demographic information (such as postcode, age level). Contact information will be used to notify the winners and award prizes. Survey information will be used for purposes of monitoring or improving the functionality of the site.


If a user elects to use our referral service for informing a friend about our site, we ask them for the friend’s name and email address. Mondaq stores this information and may contact the friend to invite them to register with Mondaq, but they will not be contacted more than once. The friend may contact Mondaq to request the removal of this information from our database.


This website takes every reasonable precaution to protect our users’ information. When users submit sensitive information via the website, your information is protected using firewalls and other security technology. If you have any questions about the security at our website, you can send an email to

Correcting/Updating Personal Information

If a user’s personally identifiable information changes (such as postcode), or if a user no longer desires our service, we will endeavour to provide a way to correct, update or remove that user’s personal data provided to us. This can usually be done at the “Your Profile” page or by sending an email to

Notification of Changes

If we decide to change our Terms & Conditions or Privacy Policy, we will post those changes on our site so our users are always aware of what information we collect, how we use it, and under what circumstances, if any, we disclose it. If at any point we decide to use personally identifiable information in a manner different from that stated at the time it was collected, we will notify users by way of an email. Users will have a choice as to whether or not we use their information in this different manner. We will use information in accordance with the privacy policy under which the information was collected.

How to contact Mondaq

You can contact us with comments or queries at

If for some reason you believe Mondaq Ltd. has not adhered to these principles, please notify us by e-mail at and we will use commercially reasonable efforts to determine and correct the problem promptly.