During the initial setup of a software escrow key aspects of the agreement need to be discussed and agreed upon. When should the escrow materials be released? What can the licensee do with the escrow materials once they are released? How often will the materials be updated? What testing should be conducted on the materials?
Download a sample agreementAfter the software escrow is setup, the escrow materials should be promptly delivered to EscrowTech. These materials should contain, but are not limited to: source code, documentation and any other important materials required to get the software running in the event of a release. Here is our suggested list of escrow materials.
EscrowTech makes the submission process easy with submission methods such as escrow synchronization, automated submission scripts via sftp, manual online submission and manual offline submission.
How to Update a software escrowOnce EscrowTech has received the source code and other materials, we will store it safely in our secure escrow vaults awaiting a mutually agreed upon release condition to occur. These release conditions are often bankruptcy or failure to maintain the software.
Sample Release ConditionsAs new versions of the software are developed corresponding updates to the escrow occur.
EscrowTech can automate this process which keeps the escrow updated without requiring excessive time from the software owner's team.
Escrow SynchronizationA release condition such as the software vendor's bankruptcy has occurred and now the licensee needs the source code to continue using the critical piece of software.
EscrowTech will promptly release the materials to the licensee following the terms agreed upon in the escrow agreement.
If a software license terminates without a release condition occurring then the materials can either be returned to the software vendor or destroyed depending on the software vendor's wishes.
When negotiating a software license at one point a prudent licensee will ask, "What happens if the software vendor goes out of business?" What usually follows is a request to access the source code and any other critical materials used to maintain the software.
From the software vendor's perspective, giving the licensee access to the source code and other confidential materials is a risk to its business. How does the software vendor know the licensee will keep the source code safe and secret and will not prematurely use it? What if dozens of licensees demand the source code?
From the licensee's perspective, not having access to the source code and other materials needed to maintain and update the software is a risk to its business. How will the licensee continue to use and maintain software, it heavily depends on, if the software vendor goes out of business, fails to meet its obligations or any other number of unforeseen events?
For nearly a quarter of a century EscrowTech has helped thousands of customers all over the world with their software escrow needs.
When our standard agreements don't fit your unique situation, our in-house counsel can work with your attorney to customize them.
Is the software escrow clause holding up your software license agreement? If so, EscrowTech can help you quickly set up an escrow in as little as one day.
We employ our own internal developers allowing for a higher level of specialized technical capability.
Upload source code, view account documents, pay bills and more all from the convenience of your web browser.
For nearly a quarter of a century Escrowtech has securely stored over half of the fortune 500's materials at our two secure escrow vaults.
Source code is securely stored at two separate physical locations. This approach ensures that your source code is never lost and is always available in the event of a release.
Predictable, fair and no unpleasant surprises.