Ask Leo! by Leo A. Notenboom

What is Software Escrow?

Search First! Then browse: Categories | Full Archive | By Date | Newsletter

Home » General Computing

I was arranging for some a custom software package to be written for my organization, and someone asked if I'd arranged for "software escrow". What is that, and why would I want it?

Getting someone to write software for you can result in a wonderful, custom solution to your problem. It can also incur a significant amount of risk if things go wrong.

Software escrow is one way of protecting you in certain types of projects when certain things go wrong.

When you contract out for software to be written for you, there are several decisions that are part of the process. One that's often overlooked is whether or not you get a copy of the source code when the project is done.

The source code is the collection of written instructions that the programmer actually writes to create a program. For many types of programs, the source code is then transformed into the "executable" that you actually run. For example "notepad.exe" is a executable program that comes with Windows. Somewhere back at Microsoft they keep the written instructions, or source code, that the programmers used to create it.

Open source software projects make the source code publicly accessible. Anyone with enough knowledge can create the software executable using the source code. Closed source, or "proprietary" software is just the opposite ... the source code is not available publicly, only the executable. Companies use this approach to retain their intellectual property, and trade secrets.

When you contract with someone to write software for you one decision, implied or explicit, is whether the source code belongs exclusively to the developer, or whether you get a copy. If you do, you have the safety of being able to have someone else make changes or fix bugs in the future, but the developer is giving up some of his or her potential control of that software. If the developer retains the source code and you don't have access to it, then you are dependant on the developer for all future updates. Typically developers will charge more if you get the source code.

It's common to opt for the cheaper option, or to have the developer simply not give you the option.

So what happens if your developer goes out of business? What if all of the source code simply disappears?

That's where software or source code escrow comes into play.

As part of arranging for your software to be written, you and the developer can agree that a copy of the source code will be given to a neutral third party - an escrow agent. The agreement would then specify under which conditions that agent would be allowed to release the source code to you. For example one of the conditions might be the developer's bankruptcy or going out of business for other reasons. By using software escrow, the developer is protected as long as it makes sense for them to retain control, and you are protected should the developer disappear. (Naturally other conditions might trigger the release, but the developer's going out of business is a clear example.)

Software escrow is not fool proof. For example, what happens if the escrow agent goes away? And escrow typically adds some cost to your transaction.

But I think of it as an insurance policy.

Article C2402 - August 10, 2005

Was this article helpful? «Yes» «No»

Helpful? Get new articles weekly by email in my FREE newsletter!

Your Name:
Your Email:


Why Subscribe?

Recent Comments
9 Comments

Right now, during these extraordinary times, as we see the money supply dry up, we're going to more and more software supplies stop operating. A verified software escrow is the insurance that is needed. More detailed information located at http://www.innovasafe.com.

Posted by: Rick Archer at September 25, 2008 12:11 PM

Because of the uncertainty in the economy and recent Wall Street meltdown, the stability of software companies is increasingly volatile. There is great concern about software companies being able to maintain important and Mission Critical software. For more Frequently Asked Questions about Software Escrows visit http://www.escrowtech.com/software_escrow_FAQ.php

Posted by: Logan Smith at October 8, 2008 11:55 AM

i would recommend reading http://www.escrow101.net/source-code-escrow-are-you-just-following-the-herd.php to read about the bad sides of software escrow - it's not all white.

Posted by: mandy at February 3, 2009 3:20 PM

My background is 25 years in IT. I recently did a site http://www.SoftwareEscrowGuide.com/ that business users might find useful. Cheers. Frank Vipond [email address removed]
I'm neutral - not in the escrow business myself.

Posted by: Frank Vipond at May 16, 2009 8:18 AM

I think one of the most important things is to consider references and testimonials. Ask around business networks you will soon get an idea of who is good and who is poor within your local area.
[link removed]

Posted by: bhavna at July 27, 2009 6:02 AM

Post a comment on "What is Software Escrow?":






(Email Address will not be published.)

Remember Me?

By popular demand...
my tip jar
Cuppa Joe
Buy Leo a Latte!

(you may use HTML tags for style)

RSS feed Subscribe to the RSS Feed specifically for comments on this article.

Before commenting, please...

  • Read the article at the top of this page. If your comment shows you didn't, it'll be deleted and ignored.

  • Comment only on this article. Use the Google search box at the top of the page if you have a question about something else.

  • Don't include personal information in the comment. No email addresses. No phone numbers. No physical addresses.

  • Don't spam. Excessive links to unrelated sites within a comment or across multiple comments will cause all such comments to be removed.

  • Don't ask me to recover lost passwords or hacked accounts. I can't, and those comments will be deleted.

  • I can't respond to every comment. And I can't vouch for the accuracy of others who do.

Please wait. Your comment is being processed ...


Question? Ask Leo!