Cloud Services Agreement vs Software Licence Agreement
One gives your customers access to software in the cloud. The other gives them a copy to install and run themselves. Understanding the difference is critical to choosing the right contract for your business.
Same Software, Different Contracts
The way software is delivered fundamentally changes the contract you need. Using the wrong agreement type creates legal gaps that can expose your business to unnecessary risk.
A Cloud Services Agreement (also called a SaaS Agreement) governs access to software hosted by the provider. The customer never receives a copy of the software - they log in through a browser or app and use it as a service.
A Software Licence Agreement grants the customer the right to install, copy, and run software on their own infrastructure. The customer receives the software (in binary or source form) and operates it themselves.
These are fundamentally different legal arrangements. A licence transfers certain IP usage rights. A cloud services agreement provides access to a service. Each demands different contract terms.
Quick Decision Framework
Software hosted in the cloud, accessed via browser?
You need a Cloud Services Agreement (SaaS Agreement)
Customer installs software on their own servers?
You need a Software Licence Agreement
Offering both cloud and on-premise options?
You need both agreement types - one for each delivery model
Customer needs to own a perpetual copy?
Software Licence Agreement with perpetual terms
Customer data stored on your infrastructure?
Cloud Services Agreement with DPA and SLA
Customer wants source code access?
Software Licence with escrow or source code addendum
Cloud Services Agreement (SaaS Agreement)
The contract for software delivered as a service - hosted by the provider, accessed over the internet, paid by subscription.
How It Works
In a SaaS model, the provider hosts the software on their own infrastructure and the customer accesses it remotely. No copy of the software is transferred - the customer pays for the right to use the service, not to own the software.
Access, not ownership
The customer accesses software hosted on the provider's infrastructure via the internet - no copy is installed locally
Subscription-based pricing
Recurring monthly or annual fees, typically per-user or per-tier, rather than a one-time purchase
Provider manages everything
Hosting, maintenance, updates, security patches, and backups are all the provider's responsibility
Automatic updates
All customers receive the latest version simultaneously - no manual upgrades or version fragmentation
Data lives in the cloud
Customer data is stored on the provider's servers, making data protection, privacy, and portability critical contract terms
When to Use a Cloud Services Agreement
- You offer software accessed through a web browser or mobile app
- You host and maintain the software on your own (or third-party cloud) infrastructure
- Customers pay recurring subscription fees rather than a one-time purchase
- You process or store customer data on your infrastructure
- All customers use the same version of the software simultaneously
Don't Use a Licence Agreement for SaaS
A common mistake is using a licence agreement for cloud-delivered software. A licence implies transferring IP usage rights (the right to copy, install, modify) which are irrelevant when the customer never receives the software. This creates legal confusion and leaves critical SaaS terms (uptime, data processing, service credits) unaddressed.
Key Terms in a Cloud Services Agreement
Because the provider hosts the software and stores customer data, the contract must address service availability, data protection, and business continuity in ways a licence agreement doesn't need to.
Service Level Agreement (SLA)
Defines uptime commitments (e.g. 99.9% availability), performance benchmarks, planned maintenance windows, and service credits when the provider fails to meet targets.
Data Processing Agreement (DPA)
Governs how the provider processes personal data on behalf of the customer. Addresses POPIA and GDPR obligations, data breach notification, sub-processors, and data subject rights.
Data Ownership & Portability
Explicitly confirms the customer retains ownership of all uploaded data. Defines export formats, migration assistance, and data return or deletion obligations upon termination.
Subscription & Renewal Terms
Covers pricing tiers, user limits, auto-renewal provisions, price escalation caps, and the process for upgrading, downgrading, or cancelling the subscription.
Security & Compliance
Specifies encryption standards (at rest and in transit), access controls, penetration testing, compliance certifications (SOC 2, ISO 27001), and audit rights.
Software Licence Agreement
The contract for software delivered as a product - installed on the customer's own infrastructure, with a licence granting usage rights.
How It Works
In a traditional licensing model, the vendor grants the customer a licence to install, copy, and run the software on their own hardware. The customer receives the software (typically in compiled binary form) and is responsible for running it in their own environment.
A copy is delivered
The customer receives a copy of the software to install and run on their own servers or devices
Perpetual or term-based
Licences can be perpetual (use forever) or time-limited, with optional annual maintenance and support fees
Customer manages infrastructure
The customer is responsible for hosting, hardware, security, backups, and applying updates
Manual updates and patches
The customer decides when to install updates - often requiring separate maintenance agreements and professional services
Data stays on-premise
Customer data remains on their own infrastructure, giving them full control over data residency and security
When to Use a Software Licence Agreement
- The customer installs and runs the software on their own servers or devices
- The customer requires a perpetual right to use the software, even if the vendor relationship ends
- Data sensitivity or regulatory requirements mandate on-premise hosting
- Deep customisation or integration with existing on-premise systems is required
- The customer wants source code access or a source code escrow arrangement
Source Code Escrow: Protecting Your Investment
When licensing on-premise software, consider requiring a source code escrow arrangement. A neutral third party holds the source code and releases it to you if the vendor goes bankrupt, abandons the product, or fails to provide agreed maintenance. This is your insurance policy for business continuity.
Key Terms in a Software Licence Agreement
Because the customer receives and operates the software themselves, the contract must carefully define what they can and cannot do with it, who owns the IP, and how ongoing support works.
Licence Grant & Scope
Defines exactly what the customer can do with the software - number of users, devices, locations, whether sublicensing is permitted, and any geographic restrictions.
Intellectual Property Ownership
Reinforces that the vendor retains all IP rights to the software, source code, algorithms, and documentation. The customer buys the right to use the software, not the software itself.
Source Code Escrow
A third-party escrow agent holds the source code. If the vendor goes bankrupt, abandons the product, or fails to maintain it, the source code is released to the customer for self-maintenance.
Maintenance & Support
Separate from the licence itself - defines the vendor's obligations for bug fixes, patches, version upgrades, and technical support. Often sold as an annual maintenance fee (15-22% of licence cost).
Warranty & Acceptance Testing
Specifies a testing period where the customer verifies the software meets agreed specifications. Includes warranty provisions for defects, performance standards, and remedies for non-conformance.
Cloud Services Agreement vs Software Licence at a Glance
A quick comparison to help you decide which agreement type fits your business model.
Delivery model
Hosted by provider, accessed via browser
Installed on customer's own servers/devices
Payment structure
Recurring subscription (monthly/annual)
One-time fee + optional annual maintenance
Data location
Provider's cloud infrastructure
Customer's own infrastructure
Updates & maintenance
Automatic, included in subscription
Manual, often requires separate maintenance contract
Customisation
Configuration within platform limits
Deep customisation, source code access possible
Upfront cost
Low (subscription fees only)
High (licence fee + infrastructure + implementation)
Total cost (5+ years)
Higher (ongoing subscription)
Potentially lower (one-time + maintenance)
Scalability
Instant - upgrade plan or add users
Requires infrastructure investment
Vendor dependency
High - no access if subscription lapses
Lower - perpetual licence persists
Key contract terms
SLA, DPA, data portability, uptime
Licence grant, IP rights, escrow, acceptance testing
Regulatory focus
Data protection (POPIA, GDPR)
IP and copyright compliance
Business continuity risk
Provider outage or shutdown
Vendor abandonment (mitigated by escrow)
The Hybrid Model
Many software vendors now offer both cloud and on-premise deployment options - and need both contract types to match.
SaaS as Primary Offering
Most new customers use your cloud platform with a standard Cloud Services Agreement. The subscription model provides predictable recurring revenue and lower customer acquisition costs. This is the default for most modern software businesses.
Licensed for Specific Customers
Certain customers - particularly in regulated industries, government, or financial services - require on-premise deployment. For these customers, offer a Software Licence Agreement with separate maintenance and support terms.
Both Models, One Customer
Some enterprise deals combine both: a cloud subscription for most users plus an on-premise licence for sensitive environments. This requires careful contract structuring to avoid conflicts between the two agreement types.
Legal Considerations for SA Businesses
Both agreement types have specific implications under South African law.
Cloud Services Agreements
POPIA compliance
Any SaaS provider processing personal information of South African data subjects must comply with POPIA. Your DPA should address the provider's obligations as an 'operator' under the Act.
ECT Act recognition
The Electronic Communications and Transactions Act recognises electronic agreements, supporting the validity of online SaaS contract acceptance.
Cross-border data transfers
If customer data is hosted outside South Africa, the agreement must address POPIA's restrictions on trans-border information flows (Section 72).
Software Licence Agreements
Copyright Act considerations
Software is protected under the Copyright Act 98 of 1978. Exclusive licence grants must be in writing and signed by the licensor - an advanced electronic signature may be required.
IP ownership clarity
South African courts enforce copyright strictly. The licence must clearly state that the vendor retains all IP rights and the customer receives only a usage licence.
Consumer Protection Act
If the licensee qualifies as a 'consumer' under the CPA, certain terms (such as unfair contract terms) may be unenforceable regardless of what the licence says.
Related Guides
Continue learning with these related resources.
Ready to Manage Your Software Agreements?
Whether you're offering SaaS subscriptions or licensing on-premise software, MyContracts gives you the tools to create, negotiate, and manage every agreement type from one platform.