This is where, when a customer purchases the software or a service, a vendor will put their codebase into the control of a third-party with contractual terms that it can be released to the customer should the vendor cease trading.
As a customer buying in a closed-source product from a small vendor where their longevity is unclear it can be a make-or-break on a deal providing some assurance of continuity should they cease trading.
Software escrow is when you nominate a 3rd party company to take possession of your source code. They keep your code safe and don't release it to anyone.
In the event that your company ever goes bankrupt, or closes down, the escrow provider will release your source code to any clients who were using your application (who also usually will an account with the escrow provider).
You will find that if you provide software to large institutions (like Banks, etc) they are likely to demand escrow agreements so they can ensure that if in the future something goes terribly wrong in your company, they aren't left with an app that can't be supported.
Usually the escrow provider will perform some form of validation on your source code to confirm that the code you have provided is enough to produce a fully compiled and working copy of your application. Often this validation takes the form of a demonstration of the full build process from the provided media.
The cases under which the escrow provider can release your code will vary slightly from provider to provider and your specific contract with them, but will usually only be for outright company closures. They don't usually just give out your source code just because you've decided not to fix a particular bug in your next release.
With regards to whether or not escrow is something you want, it depends on which side of the fence you're on. If you are development company selling software, then only do it if you client requires it. Escrow providers charge a fee, and it can be time consuming to ensure that the escrow is kept regularly up to date (particularly if you don't have full clean build scripts).
If you are buying software, consider what would happen if the company you are buying from went bankrupt. Is the software you are buying so critical that you wouldn't just be able to switch for something new? Also, are you big enough, that you could realistically take on the cost of getting your own (or new) developers to maintain the application.
softwareescrowguide.com 距离 Google 很近。简短的版本 - 软件托管是第三方拥有软件产品源代码的副本，保证使用该软件产品的企业在供应商倒闭时可以继续开发该产品。
这是你想要的东西吗？我想这取决于你是谁以及你想要什么。
softwareescrowguide.com is but a google away. The short version - software escrow is where a third party has a copy of a software product's source code, guaranteeing that, say, a business using that software product can continue development of the product if the vendor goes under.
Is it something you want? Depends on who you are and what you want, I guess.
It's something the purchaser definitely wants. Is it something the developer wants? Probably, in that it will help make the deal. The catch is to write the contract so that you retain control as long as it makes sense for you to retain control.
Software Escrow generally refers to a provision in Software licensing agreements that allow the party the licenses the software to acquire the source code in certain circumstances, typically bankruptcy (or something similar) of the party that wrote the software. Often times a neutral third party will "hold" the code in escrow and be the arbiter of whether they should give the code to the licensee.
They tend to be used when small companies license software to big companies since big companies want to protect themselves incase of bankruptcy of a small company. In practice, these things cost money and time. A neutral third party will charge money for the service and the team the wrote the software will need to update the escrow account periodically.
As to whether you want it -
If you are a software vendor, then not unless the client asks and only then if you have to. It is a pain to manage.
If you are licensing the software, you probably don't care unless you are a large company with a lot of resources. In practice, if you need to maintaining someone else's code it not particularly practical
From a user's perspective: If the user does not have access to an application's source code, software escrow is the insurance policy that in the event of a "disaster" the escrow agent will release a copy of the source code to the user. The user needs to determine the risk associated with not being able to get the business critical or mission critical software maintained as their business needs change.
From a developer's perspective: There are two perspectives. 1) It is a tool to ensure their intellectual property (the source code) is kept in-house unless a "disaster" occurs when the escrow agent will release a copy of the source code to the user. 2) It can also be used as a tool to help marketing their application.
"Disasters" or release events are explicitly defined in the escrow agreement.
Software Escrow Guardians is an escrow agent and has been providing software escrow services for nearly twenty years. The company has an escrow agreement template suitable as a framework for an escrow service involving an individual user and a developer. It also has an escrow agreement template suitable for multiple users and a developer.
发布评论
评论（6）
在这种情况下，当客户购买软件或服务时，供应商会将其代码库置于第三方的控制之下，并签订合同条款，如果供应商停止交易，则可以将代码库发布给客户。
当客户从小型供应商处购买闭源产品时，其寿命尚不清楚，这可能是一笔交易的成败，如果他们停止交易，则可以提供一定的连续性保证。
This is where, when a customer purchases the software or a service, a vendor will put their codebase into the control of a third-party with contractual terms that it can be released to the customer should the vendor cease trading.
As a customer buying in a closed-source product from a small vendor where their longevity is unclear it can be a make-or-break on a deal providing some assurance of continuity should they cease trading.
软件托管是指您指定第三方公司来拥有您的源代码。他们保证您的代码安全，不会将其发布给任何人。
如果您的公司破产或关闭，托管提供商将向使用您的应用程序的任何客户（通常也将在托管提供商处开设帐户）发布您的源代码。
您会发现，如果您向大型机构（如银行等）提供软件，他们可能会要求托管协议，这样他们就可以确保，如果您的公司将来出现严重问题，他们不会留下一个应用程序无法支持。
通常，托管提供商会对您的源代码执行某种形式的验证，以确认您提供的代码足以生成应用程序的完全编译和工作副本。通常，这种验证采用从所提供的媒体演示完整构建过程的形式。
托管提供商可以发布您的代码的情况因提供商以及您与他们之间的具体合同而异，但通常仅适用于公司彻底关闭。他们通常不会仅仅因为您决定不在下一个版本中修复特定错误而仅仅提供您的源代码。
至于您是否想要托管，这取决于您站在栅栏的哪一边。如果您是销售软件的开发公司，那么只有在客户需要时才这样做。托管提供商会收取费用，并且确保托管定期保持最新状态可能会很耗时（特别是如果您没有完整的干净构建脚本）。
如果您要购买软件，请考虑如果您购买的公司破产了会发生什么。您购买的软件是否非常重要，以至于您无法更换新软件？另外，您是否足够大，可以实际承担让自己的（或新的）开发人员维护应用程序的成本。
Software escrow is when you nominate a 3rd party company to take possession of your source code. They keep your code safe and don't release it to anyone.
In the event that your company ever goes bankrupt, or closes down, the escrow provider will release your source code to any clients who were using your application (who also usually will an account with the escrow provider).
You will find that if you provide software to large institutions (like Banks, etc) they are likely to demand escrow agreements so they can ensure that if in the future something goes terribly wrong in your company, they aren't left with an app that can't be supported.
Usually the escrow provider will perform some form of validation on your source code to confirm that the code you have provided is enough to produce a fully compiled and working copy of your application. Often this validation takes the form of a demonstration of the full build process from the provided media.
The cases under which the escrow provider can release your code will vary slightly from provider to provider and your specific contract with them, but will usually only be for outright company closures. They don't usually just give out your source code just because you've decided not to fix a particular bug in your next release.
With regards to whether or not escrow is something you want, it depends on which side of the fence you're on. If you are development company selling software, then only do it if you client requires it. Escrow providers charge a fee, and it can be time consuming to ensure that the escrow is kept regularly up to date (particularly if you don't have full clean build scripts).
If you are buying software, consider what would happen if the company you are buying from went bankrupt. Is the software you are buying so critical that you wouldn't just be able to switch for something new? Also, are you big enough, that you could realistically take on the cost of getting your own (or new) developers to maintain the application.
softwareescrowguide.com 距离 Google 很近。简短的版本 - 软件托管是第三方拥有软件产品源代码的副本，保证使用该软件产品的企业在供应商倒闭时可以继续开发该产品。
这是你想要的东西吗？我想这取决于你是谁以及你想要什么。
softwareescrowguide.com is but a google away. The short version - software escrow is where a third party has a copy of a software product's source code, guaranteeing that, say, a business using that software product can continue development of the product if the vendor goes under.
Is it something you want? Depends on who you are and what you want, I guess.
这是购买者肯定想要的东西。这是开发商想要的吗？也许，这将有助于达成交易。问题是编写合同时，只要对您保留控制权有意义，您就可以保留控制权。
It's something the purchaser definitely wants. Is it something the developer wants? Probably, in that it will help make the deal. The catch is to write the contract so that you retain control as long as it makes sense for you to retain control.
软件托管通常是指软件许可协议中的一项条款，允许软件许可方在某些情况下获取源代码，通常是编写软件的一方破产（或类似情况）。通常，中立的第三方会“托管”代码，并成为是否应将代码提供给被许可人的仲裁者。
当小公司向大公司许可软件时，往往会使用它们，因为大公司希望在小公司破产时保护自己。实际上，这些事情需要花费金钱和时间。中立的第三方将收取服务费用，编写软件的团队需要定期更新托管帐户。
至于您是否想要它 -
如果您是软件供应商，那么除非客户要求，并且只有在必须时才需要。管理起来很痛苦。
如果您要获得软件许可，您可能不会关心，除非您是一家拥有大量资源的大公司。在实践中，如果你需要维护别人的代码，那就不是特别实用
Software Escrow generally refers to a provision in Software licensing agreements that allow the party the licenses the software to acquire the source code in certain circumstances, typically bankruptcy (or something similar) of the party that wrote the software. Often times a neutral third party will "hold" the code in escrow and be the arbiter of whether they should give the code to the licensee.
They tend to be used when small companies license software to big companies since big companies want to protect themselves incase of bankruptcy of a small company. In practice, these things cost money and time. A neutral third party will charge money for the service and the team the wrote the software will need to update the escrow account periodically.
As to whether you want it -
If you are a software vendor, then not unless the client asks and only then if you have to. It is a pain to manage.
If you are licensing the software, you probably don't care unless you are a large company with a lot of resources. In practice, if you need to maintaining someone else's code it not particularly practical
从用户的角度来看：如果用户无权访问应用程序的源代码，软件托管是一种保险政策，在发生“灾难”时，托管代理将发布源代码的副本代码给用户。用户需要确定随着业务需求的变化而无法维护业务关键型或任务关键型软件所带来的风险。
从开发人员的角度来看：有两种观点。
1) 它是一种确保其知识产权（源代码）保留在内部的工具，除非托管代理向用户发布源代码副本时发生“灾难”。 2) 它还可以用作帮助营销其应用程序的工具。
“灾难”或释放事件在托管协议中明确定义。
Software Escrow Guardians 是一家托管代理，提供软件托管服务已近二十年。该公司有一个托管协议模板，适合作为涉及个人用户和开发人员的托管服务框架。它还具有适合多个用户和开发人员的托管协议模板。
From a user's perspective: If the user does not have access to an application's source code, software escrow is the insurance policy that in the event of a "disaster" the escrow agent will release a copy of the source code to the user. The user needs to determine the risk associated with not being able to get the business critical or mission critical software maintained as their business needs change.
From a developer's perspective: There are two perspectives.
1) It is a tool to ensure their intellectual property (the source code) is kept in-house unless a "disaster" occurs when the escrow agent will release a copy of the source code to the user. 2) It can also be used as a tool to help marketing their application.
"Disasters" or release events are explicitly defined in the escrow agreement.
Software Escrow Guardians is an escrow agent and has been providing software escrow services for nearly twenty years. The company has an escrow agreement template suitable as a framework for an escrow service involving an individual user and a developer. It also has an escrow agreement template suitable for multiple users and a developer.