← Texas Business Law Glossary

Texas Business Law · Glossary

Software License Agreement

A negotiated commercial license under which the licensor grants the licensee specified rights to install, access, and use software, typically on the licensee's own infrastructure. Distinct from a SaaS agreement (services-based, vendor-hosted) and a consumer EULA (form, non-negotiated). Key terms: scope of license, seats/users, deployment environment, support and maintenance, source-code escrow, warranty, indemnification, and limitation of liability.

A software license agreement is a negotiated commercial contract under which the licensor grants the licensee specified rights to install, access, and use software, typically on the licensee's own infrastructure ("on-premise") or hosted by the licensee in a third-party cloud. The software license agreement is distinct from a SaaS agreement (services-based, vendor-hosted) and a consumer EULA (form, non-negotiated). It is the principal commercial document for enterprise software transactions where the licensee will run the software in its own environment.

License grant and scope

The license grant defines (1) permitted uses, install, copy, run, modify, integrate, internal-only, restricted to specific affiliates; (2) the user metric, named users, concurrent users, CPU cores, instances, or capacity-based; (3) the environment, production, development, testing, disaster recovery; (4) territorial restrictions; and (5) duration, perpetual, term, or subscription. Each enumerated right is a separate grant; rights not granted are reserved.

Support, maintenance, and service levels

Most software license agreements include a separate exhibit or appendix governing support and maintenance, typically a recurring fee equal to 18-22% of the license fee per year. Support exhibits define severity levels, response time SLAs, escalation procedures, and the version/release support window. The licensor's right to discontinue support of older versions is a critical negotiation point for licensees with long deployment cycles.

Source-code escrow

Source-code escrow protects the licensee against the licensor's bankruptcy, acquisition, or discontinuation of the product. Source code is deposited with a neutral escrow agent (typically Iron Mountain, EscrowTech, or NCC Group), updated on each major release. Release events, defined contractually, trigger delivery of the source code to the licensee for limited maintenance purposes. Standard release events: licensor bankruptcy, cessation of business, material breach of support obligations, or acquisition followed by support discontinuation.

Warranty and limitation of liability

Standard licensor warranties cover (1) ownership and authority to grant the license; (2) limited media warranty (90 days, replacement remedy); (3) general performance warranty for a defined warranty period (typically 90 days, replacement remedy); and (4) IP non-infringement, with carve-outs for licensee modifications, combinations, and post-knowledge use. Limitation of liability typically caps damages at fees paid in the preceding 12 months, with carve-outs for IP indemnification, breach of confidentiality, and gross negligence/willful misconduct.

Practical context

Enterprise software license agreements have evolved as SaaS has become dominant. On-premise software licensing is now most common for (1) heavily regulated industries with data-residency or sovereignty requirements; (2) industrial control systems and manufacturing software; (3) legacy enterprise applications; and (4) software with extreme performance requirements unsuited to multi-tenant SaaS. Texas businesses negotiating these agreements should pay particular attention to source-code escrow, support discontinuation rights, and IP indemnification carve-outs.

Related Terms
License Agreement· SaaS Agreement· End User License Agreement· Open-Source License· Master Service Agreement
Referenced by
Click-Wrap Agreement
Last updated: August 14, 2026