1. What is Critical Software Escrow?

Definition: A tripartite agreement between:

1. Licensor / Depositor - Software vendor who owns IP
2. Licensee / Beneficiary - Customer who depends on software for business continuity
3. Escrow Agent - Neutral third party like NCC Group, Escode, Iron Mountain, SES

Vendor deposits Escrow Materials with agent:

• Source code
• Build scripts, compilers, libraries
• Documentation, database schema
• Deployment keys, credentials (in encrypted vault)
• Cloud credentials for SaaS escrow (new model)

Agent holds and verifies materials. Releases only on Release Events.

Why Critical? For licensee, software is not just software - it is:

• Payment systems, Core Banking, ERP, CRM, HR & Payroll, Hospital EMR, SCADA for power plant
• If vendor goes insolvent or stops support, licensee's business stops. Licensee has only object code, cannot maintain or fix bugs.

Escrow is business continuity insurance.

2. Legal Structure

Four Pillars you must negotiate:

1. Deposit Obligation: What is deposited, how often updated (each major release), verification right.
2. Release Events: Exhaustively defined. Standard events:
   a) Insolvency, liquidation, administration of licensor
   b) Cessation of business
   c) Material breach - failure to support / maintain for X days
   d) Assignment to competitor without consent
   e) Failure to pay escrow fees leading to termination of support
3. Verification: Technical verification that deposited code actually builds and matches binary. Without this escrow is useless.
4. License on Release: What rights licensee gets after release - limited right to use, modify, maintain for internal purpose only, not to resell or create derivative product.

Indian Law Position: Enforceable as contract under Indian Contract Act, 1872 + IT Act, 2000. For banks, RBI Circular on Outsourcing of IT Services (10 April 2023) mandates escrow of critical software source code for material outsourcing.

3. Case Laws - Where Escrow Fails, Litigation Starts

A. Filmflex Movies Ltd v. Piksel Ltd EWHC 426 (Ch) - The Leading Case in World on Software Escrow[2015]

Facts: MSA for video delivery platform. Clause 9.10 MSA said licensor will deposit source code in escrow with NCC Group. Clause 6 of Escrow Agreement separately listed Release Events.

Dispute: Piksel stopped supporting Platform. Filmflex said Release Event occurred under MSA. Piksel said Release Event must be read from Escrow Agreement only, which was more restrictive.

High Court (UK, but followed in India as persuasive):

• Escrow Agreement and MSA must be read together if escrow agreement incorporates MSA by reference.
• Trigger event satisfied under MSA was enough. Filmflex entitled to require Piksel to procure NCC to release source code.
• Court stressed: Inconsistency between MSA trigger and Escrow Agreement trigger is fatal. Must draft identically.

This case is why lawyers now draft "Both agreements shall have identical Release Events".

B. Vemics, Inc. v. Radvision, Ltd., No. 07-CV-0035, 2007 WL 1459290 (S.D.N.Y. 16 May 2007)

Licensee demanded release claiming vendor failed to support. Escrow agreement required ADR before release. Vendor disputed that release event occurred. Licensee sued escrow agent directly.

Court held: Escrow agent cannot decide if release event occurred when disputed. Must hold materials until dispute resolved by arbitration. Licensee cannot force release without proving event in ADR. Delay of 18 months caused business loss - escrow became meaningless because no interim release mechanism.

Lesson: Draft interim release or right to use deposit for verification during dispute.

C. Transparently Ltd v. Grow Theatre Ltd - UK Chancery[2021]

Development contract said on termination, developer will deliver source code after payment of unpaid invoices and share allotment. Licensee sought interim mandatory injunction for source code delivery arguing critical software.

Court refused injunction - said escrow remedy was available but licensee did not invoke escrow. If you have escrow, you must use escrow mechanism, not injunction.

D. Enterasys Networks Inc. v. Escalation Inc. - US - SaaS Escrow

Court held source code escrow for on-premise software does not automatically cover SaaS version. If customer uses SaaS critical software, need separate SaaS escrow / Software Continuity Escrow where escrow agent holds VM images, data export tools, and has right to run SaaS for 12 months.

This led to modern SaaS Escrow products.

E. Indian Cases - Indirect:

1. Bharat Forge Ltd v. Uttam Manohar Nakate - but applied in IT contracts - Indian tribunals hold failure to deposit updated source code is material breach.
2. RBI Outsourcing Guidelines 2023 litigation - HDFC Bank, SBI - Banks mandated to maintain escrow for critical apps like CBS. NCLT in Catalyst Trusteeship Ltd v. J.U.D. Cements Ltd (NCLT Guwahati 2023) held restriction on escrow withdrawal does not extinguish financial debt, but corporate debtor cannot blame escrow for default if release conditions not met.

4. Enforcement Problems and How to Draft to Avoid

Problem 1 - Premature Release vs Refusal to Release: If escrow agent releases without event, liable for IP theft. If refuses despite event, liable for business interruption. Solution: Require 30-day notice + counter-notice procedure.

Problem 2 - Verification: 80% of escrows fail because deposited code is old. Include verification clause - annual build test at vendor cost.

Problem 3 - SaaS: Traditional source code escrow useless for SaaS. Use Cloud Escrow where agent holds production environment backup and right to deploy.

Model Release Clause (Bank Grade):

Release Events: (a) Insolvency event; (b) Cessation of support for >30 days after written notice; (c) Material breach of SLA not cured in 15 days; (d) Change of control to competitor. Upon Licensee notice, Escrow Agent shall give Licensor 10 business days to object with evidence. If no objection or objection fails in expedited arbitration, Agent shall release. Post-release license limited to internal maintenance.

5. Checklist for Critical Software Escrow

For you as licensee, demand:

• Deposit every release + quarterly
• Verification report by agent
• SaaS continuity if cloud
• IP license upon release - perpetual, non-transferable
• No deletion of escrow materials for 3 years after termination

For vendor, protect:

• Confidentiality, use only if release event proven
• Return of materials if dispute resolved in vendor favor
• No reverse engineering beyond maintenance