You may know that ttechnology escrow (also known as software escrow) is a best practice for safeguarding your software source code in case there is ever an issue where a software vendor fails to meet expectations. But, who really uses technology escrow and how do escrow releases work? This Executive Viewpoint has the answers.
By securely storing your software source code, build instructions, third-party tools, databases, and other proprietary information with a neutral third party you have the peace of mind that you can recover your software if it is needed in the future. Issues like mergers and acquisitions, a vendor’s bankruptcy or insolvency, or failure to support the application are all reasons we frequently see for escrow releases. But we often get questions about the nitty-gritty of an escrow release.
So, what happens when source code is released from escrow?
Our Executive Viewpoint: The Case for Technology Escrow provides both business and legal perspectives on the topic. The Q&A with Iron Mountain’s Vice President for Intellectual Property Management, John Boruvka, and award-winning attorney, Frank McGinn, will take you through the ins and outs of an escrow release. They’ll answer questions such as:
- What benefits do companies realize from escrow releases?
- What are some common mistakes in the release process?
- What are companies allowed to do with the released source code?
Some of the most compelling arguments for technology escrow come from our customers who have had software source code released to them. Here’s what they have to say:
“The big thing about owning the source code at this point is that we now have more options.”
— IT Director, Healthcare Industry
[Fortunately, with the release of the source code], we continue to actively sell and market the solution that is critically dependent upon [the developer’s] product.”
— Sr. VP of IT, Publishing Industry
Interestingly, even if you don’t get to the point where you request an escrow release, technology escrow is a key strategy for software licensees that gives organizations leverage to demand better SLA compliance – and protect against a potentially dangerous total loss of support.