Your Software Vendor Goes Bankrupt. What Does Your Contract Actually Give You?
A software agreement can contain extensive protections while leaving one important question unresolved. If the provider can no longer maintain the application, what can the customer actually do?
In April 2026, S&P Global Market Intelligence reported that private US IT companies recorded 30 bankruptcy filings during 2025. Application software businesses accounted for half of those filings.
The research also identified two bankruptcy filings involving private application software companies during the first quarter of 2026.
These findings concern a defined segment of the US market. They do not establish the financial condition of software providers in South Africa or predict the failure of any particular business.
They do, however, offer a useful reason to examine something that can be overlooked during software procurement.
Does your contract provide the rights and practical resources required if your software provider can no longer perform?
What Happens to Your Contractual Protection When the Provider Cannot Perform?
Commercial software agreements commonly address service levels, support obligations, maintenance commitments and remedies for non-performance.
These provisions serve important purposes.
However, their practical usefulness depends on the circumstances, the applicable agreement and the resources available to the customer.
Consider a business that relies on a specialised application developed and maintained by an external provider.
The application supports an important operational function. The provider holds the source code, controls the development environment and employs the specialists responsible for maintenance.
If the provider enters financial distress and can no longer deliver the required support, the customer may face an immediate operational problem.
A contractual remedy may address aspects of the provider’s failure to perform.
But what does that remedy enable the customer to do about the software itself?
Can the customer appoint another developer?
Does it have the technical information needed?
Would the relevant intellectual property rights permit the required work?
The answers depend on the contract and the technical arrangements.
The Source Code Question
Access to source code can be relevant when an organisation needs to maintain software independently of its original developer.
But access alone may be insufficient.
The organisation may also need technical documentation, information about dependencies, build requirements, relevant updates and people with the appropriate skills.
The distinction matters when evaluating continuity arrangements.
An organisation might know that source code exists without knowing whether it has been deposited, whether the deposited version is current or whether the materials have undergone Technical Verification.
Even where verification has been performed, the outcome must be considered according to the actual tests and scope.
There is a significant difference between knowing that specified material has been deposited and having evidence that it can support a particular technical objective.
The appropriate level of assurance depends on the criticality of the application and the intended continuity response.
What Software Escrow Can Provide
Software escrow allows defined software materials to be held by an independent escrow provider under an agreed contractual arrangement.
The agreement establishes relevant obligations and the conditions and procedures governing release.
Depending on the service and agreement, the materials may include source code, technical documentation and relevant updates.
Technical Verification can provide additional evidence about specified aspects of those materials.
For hosted Software as a Service applications, the assessment may also need to consider dependencies involving infrastructure, configurations, databases, interfaces and operational processes.
Escrowsure provides software escrow, Technical Verification and, where applicable, SaaS continuity arrangements.
The exact arrangements depend on the software dependency being addressed, the agreed technical scope and the applicable contractual terms.
The existence of an escrow arrangement does not itself establish that an application can be recovered or that business operations will continue without interruption.
The control needs to be evaluated against its intended purpose.
The Question to Ask Before Your Next Contract Renewal
A software provider’s financial stability is relevant to procurement and supplier risk assessment.
Yet financial due diligence cannot eliminate uncertainty about future circumstances.
For business-critical software, it is worth establishing the consequences if support becomes unavailable and whether the organisation has an appropriate response.
That assessment should consider the criticality of the application, its replacement difficulty, the provider’s technical role and the controls already in place.
For some applications, existing arrangements or straightforward replacement options may be sufficient.
For others, particularly where the customer is materially dependent on a specialist provider, software escrow may deserve consideration.
The decision should be proportionate to the actual risk.
Before renewing a critical software agreement, establish what your organisation would be entitled and technically able to do if the provider could no longer maintain the application.
Escrowsure helps organisations assess material third party software dependency and provides software escrow and related continuity arrangements where an independent control is appropriate.
To discuss the continuity requirements of an important software application, contact Escrowsure.
Source and Further Reading
S&P Global Market Intelligence, 22 April 2026, Application software leads private IT sector bankruptcy filings.



