Source Code Escrow – It Happens All The Time!
With all of the new applications that are coming out every day now, there is an increasing demand for a balanced and fair way for developers to deal with the customers of the software market. Normally this calls for an agreement of some kind to be drawn up that ensures honesty on both sides of the transaction. Too often one person sees the other as ‘the big bad wolf’ at the end of the day when really there was just a simple misunderstanding that could have been avoided through a source code escrow clause.
Source Code Escrow is an excellent way to achieve this level of honesty and integrity between the developer and the customer. Just like an escrow agent in real estate is appointed to serve the best interests of the buyer and seller of a home, the source code escrow agent also has a very similar role.
Too often in the fast moving modern world of business folks tend to become a tad dishonest in their dealings and fall short of their promises. In this arrangement the chances for this type of scenario are greatly reduced seeing that a third party is in possession of the source code.
Source Code – Software Escrow Companies and Source Code Escrow Agreements
Iron Mountain source code escrow service is well known and okay to use although there are many. You should be sure to look at and check out as many options as you can, but some of the main points you want to explore are the following:
* Does the software source code escrow agreement have a source code escrow audit procedure? This is a procedure that is used to determine whether or not the source code that is in escrow is a valid copy of the original code that is being used by the customer. This is important should the source code escrow be released to the customer in the event the developer could no longer keep on updating the software because of business issues, sickness, or any other trigger that could put the customers use of the software in jeopardy.
* Does the source code escrow agreement contain a clause that deals with possible bankruptcy on the part of the developer? If it doesn’t it should. The reason why is because if for some reason the customers legal representative finds that he/she (the developer) has rights to the code even after they declare bankruptcy, this could leave the customer ‘high and dry’ with no recourse. Not good.
* Does the source code escrow agreement have a clause that allows for third party developers to work on it and update it? Just in case the developer gets lazy and does not provide the needed updates to the application during its use by the customer, this clause will serve as a list of things the customer can do to recover. If this states ‘non-compete’ then the source code would have to be released to the customer in order for them to be able to hire an outside hand to help with its development and needed maintenance and updates.
* Does the agreement allow for the customer to continue the software’s development in the event that the developer loses his shirt and goes out of business? If it doesn’t the customer runs the risk of not being able to carry on using the software and will most likely have to go with someone else. This could mean losing a bunch of money and time (ouch and…ouch).
* What are the fees for the source code escrow agreement? You really want to shop around to get the best price and not necessarily go with the first deal you come across. A good number is 3. Get 3 estimates and contracts/agreements and have your attorney look them over for accuracy. When everything shakes out if there should be a problem, you do not want to be on the receiving end in this case for sure!
Source Code Escrow and Conclusion
Source code escrow is becoming more and more a staple in the online development community and is a necessary regulatory tool for the future. It properly outlines the relationship between the customer and the developer and provides for a stable and honest way to do business online.
It is also important to remember that the risk isn’t just on the side of the customer. If for instance you were a developer and put thousands of man hours into developing an application to serve the best interests of say physicians, you would want every last thing outlined in the agreement and nothing to be left unclear or ambiguous. Absolutely everything is contained in one of these agreements as to prevent an all too common misunderstanding and a possible subsequent lawsuit.
This way, everyone who is a party to the software or source code transaction understands their duties and and is overseen and monitored for compliance. These agreements are becoming more and more standardized as the software market evolves but it is all in the service of keeping everyone on the path to a smooth and satisfying transaction that is good for the customer and the developer.
