Blog

Who pays for software escrow services?

The question of who should pay the escrow fees—the licensor or the licensee—has no right or wrong answer, and there is no established standard practice.

On the one hand, there are certainly instances when the beneficiary pays the escrow agent directly. For the most part, however, it’s actually the licensor who is responsible for payment of escrow fees. This is something that is often considered an expected cost of running a licensing business.

But even though the licensor may pay the fees, the licensee ultimately reimburses the licensor, more often than not. In fact, they may even pay a greater fee to the licensor at the outset to cover both escrow fees and the licensor's administrative expenses.

The main reason that we see the beneficiary covering the cost of the escrow in some way, shape, or form is that the escrow is set up in their best interest. If a licensor were to go out of business for any reason, they wouldn’t be as concerned over what happens to the system that they’ve licensed out to clients. 

So even if the beneficiary doesn’t directly cover the cost of the escrow by paying the escrow agent, they will still be paying that fee through their licensor’s service charge.

Tip: To read more about who should pay for source code escrow (and how much), check out this article.

Although software escrows have been used since the 1970s, they are becoming increasingly more common and necessary as a practice for modern enterprises. As a result, there are a number of software escrow solutions on the market today, and some of them have been around for decades.

However, not all software escrow providers offer the same services, the same level of quality and security, and the same ease of use. And then there’s pricing, of course, which is an important aspect in and of itself.

So whether you’re a licensor or licensee on the hunt for your next software escrow, it’s important that you examine all of these factors to be able to choose a solution that meets your needs while providing top-notch security and flexibility.

Codekeeper, in particular, was born out of a need for source code escrow that is simple to set up and use, fully automated and integrated into developer workflows, and last but not least, transparent and fair with pricing.

In this article, we will consider the current situation in the software escrow market both in terms of use and pricing. We will also look into how Codekeeper’s modern automation technology allows us to offer a superior service at a much lower price when compared to other providers on the market.

What are some examples of release conditions?

So we’ve caught up on Software Escrow and all the ins and outs. But what are some release conditions that can be incorporated in a Software Escrow agreement?

Parties to the agreement are free to negotiate any release terms that can be validated independently by the escrow agent. Most commonly, however, these terms revolve around the licensor's financial or operational standing. A release may be triggered if, for example, the licensor enters voluntary or involuntary bankruptcy, or if the licensor fails to operate in the ordinary course of business (OCB). 

Two other very common “custom” release terms that are requested by beneficiaries are that the material in escrow be released in case the vendor is acquired by another company, or if the provider fails to fix an error in the system within a given time frame.

Are you aware that you need to implement software escrow in your licensing agreements, but don’t know the best way to start? Then this is exactly the article for you.

Below you will find information on what a software escrow is, why you need them in your licensing agreements, and what the best way to use them is.

Why is having access to source code so important?

In the case of typical, off-the-shelf software, only object code (i.e., executable code) is licensed out to the end-user. In commercial licensing deals, however, the licensee may have a legitimate interest in object code, as well as source code as an assurance that their mission-critical systems will remain functional. Accessing source code allows the licensee to see how the software is processing data or performing functions, and can even allow the licensee to change the operation of the software if necessary.

In that sense, source code is the DNA of a software application. It is code that is written in a programming language that is readable (and modifiable) by humans, and without it, developers can’t debug or upgrade software applications. In other words, they can’t ensure that the system will continue working as intended.

So if, for instance, a software vendor goes out of business, without modifiable source code, the software is as good as dead. Depending on how critical the software is to your business, the effects of losing access to the source code could be nothing short of devastating. Later in the ebook, we will examine some of the risks that software escrow helps mitigate, as well as the benefits that it offers to both licensors and licensees.

Software verification is an essential step in the process of deploying new and updated software. This article goes over what exactly software verification is, how to know if you’re doing it and doing it properly, and how to recognise your own inefficient practices and turn them around for better deployments.

Let’s get started with pinpointing precisely what is meant by software verification.