Software Licensing in South Africa: How to Protect Your Code and Commercialise It Properly

A software licensing agreement in South Africa is one of the most important – and most neglected – documents in any technology business. Here is a scenario that plays out regularly: a Cape Town developer spends eight months building a custom inventory management system for a logistics client. The project gets completed. The client pays. The developer moves on – without a written software licence or development agreement in place. A year later, the client sells their business. The acquirer assumes they are buying the software outright. The developer assumed they retained ownership and the right to licence the same codebase to other clients. Neither assumption was documented. What began as a successful project becomes a costly ownership dispute.

Software licensing is the legal mechanism through which developers and companies control their code. It covers how developers distribute, use, modify, and commercialise the code. Without a properly drafted software licence agreement, developers risk losing control of their intellectual property. Businesses risk using software they have no legal right to use. Moreover, both parties risk finding themselves in disputes with no contractual framework to resolve them. In South Africa, a copyright and IP framework that differs in important ways from the US and UK models compounds these risks.

This guide covers what a software licence agreement is and the different types of licences used in the South African market. It also addresses the key clauses every software licence must include. The specific issues facing developers, software houses, and businesses procuring custom-built software are covered too. Whether you run a Cape Town startup, a software consultancy, or a business procuring enterprise software, getting your licensing right matters. It protects your investment and your commercial relationships.

Why a Software Licensing Agreement Matters in South Africa

What Is a Software Licence Agreement and Why Does It Matter in South Africa

A software licence agreement is a contract between the software owner (the licensor) and a person or entity that wants to use it (the licensee). It sets out the terms on which the software may be used – what the licensee can do and what they cannot. The agreement also covers how many users can access the software, whether modification is permitted, and what happens if the agreement ends. A licence is permission to use, not a transfer of ownership. The licensor retains ownership of the underlying code, the intellectual property, and all rights not expressly granted to the licensee.

In South Africa, software is protected as a literary work under the Copyright Act 98 of 1978. Copyright attaches automatically the moment a developer creates original software. South Africa has no copyright registration system. No formalities need completing for protection to attach. This means a developer’s code receives protection from the moment they write it. In practice, however, documenting ownership and licensing rights in writing is essential for commercial certainty. Without a written software licence agreement, general contract principles and copyright law resolve disputes about permitted use and ownership. The results often surprise both parties.

Licence vs Assignment – Owning the Code vs Permitting Its Use

The distinction between a software licence and a software assignment is fundamental and frequently misunderstood. A licence permits the licensee to use the software under specified conditions, while the licensor retains ownership. An assignment transfers ownership of the copyright from the assignor to the assignee. After an assignment, the original developer no longer owns the code and cannot use it without the new owner’s permission. For developers, assigning copyright in a bespoke project means they cannot reuse that code or those modules in future projects without the client’s consent. For clients, receiving only a licence means the developer can licence the same or similar software to competitors. Consequently, getting the right structure requires precise drafting. Working with a technology lawyer in Cape Town makes a material difference to the outcome.

The Legal Framework: Copyright Act and South African IP Law

The Copyright Act 98 of 1978 is the primary statute governing software IP protection in South Africa. It protects software as a literary work. Key provisions relevant to software licensing include the rules around first ownership of copyright. These determine who owns code written by employees vs contractors. The rules around moral rights affect what licensees can do when modifying or adapting software. The rules around permitted acts set out what users can do with software even without an express licence. Understanding how these rules apply to your specific situation requires legal analysis, not just a generic template.

Types of Software Licence Agreements Used in South Africa

Notably, not all software licences are the same. The appropriate licence type depends on the nature of the software, the scale of deployment, and the business model of the developer. The commercial relationship between the parties also shapes the choice. Understanding the main licence types is the starting point for structuring an agreement that works for your specific situation.

Perpetual Licences vs Subscription Licences

A perpetual licence grants the licensee the right to use a specific version of the software indefinitely, in exchange for a one-off licence fee. This is the traditional model for enterprise software and remains common in some sectors. A subscription licence grants the right to use the software for a defined period, with access conditional on ongoing payment of a recurring fee. Indeed, the subscription model now dominates the SaaS space and is increasingly common for all types of commercial software. Each model has different commercial and legal implications. Perpetual licences typically treat updates and support as separate arrangements. Subscription licences need careful provisions around data and access rights. These must cover what happens if the subscription is cancelled or the licensor ceases to operate.

Single-User, Multi-User, and Enterprise Licences

Specifically, licence scope is a critical commercial variable that must be addressed with precision. It covers the number of users, devices, and instances the agreement permits. A single-user licence permits use by one named individual. A multi-user or seat-based licence permits use by a specified number of users. An enterprise or site licence permits use by all users within an organisation, or within a defined part of it. For South African businesses procuring software for internal use, the scope of the licence must match actual usage patterns. Undershoot, and users are operating in breach of contract. Overshoot, and the business is paying for capacity it does not need. Moreover, software developers and companies have a legitimate right to audit licence compliance. The agreement should include provisions giving the licensor that right.

Open Source Licences and Their Risks

Open source software makes its source code publicly available under a licence permitting use, modification, and redistribution – subject to certain conditions. Importantly, those conditions vary significantly between licence types. Some (like the MIT and Apache licences) impose minimal restrictions. Others (like the GPL family) impose copyleft obligations. These require any software incorporating the open source component to carry the same open source licence terms. For South African software developers incorporating open source components into commercial products, copyleft obligations can be commercially catastrophic. They can force a developer to make their entire proprietary codebase available as open source, destroying the product’s commercial value. For that reason, determining which open source licences are present in a codebase is essential due diligence for any acquisition or investment transaction. A Cape Town technology lawyer with software IP experience should be involved in this from the outset.

Key Clauses Every South African Software Licence Agreement Must Include

Regardless of the type of licence or the commercial arrangement, every South African software licence agreement should include a core set of provisions. Specifically, these provisions define permitted use, protect IP, allocate risk, and set out what happens when the relationship ends. These provisions define permitted use, protect the licensor’s IP, allocate risk between the parties, and set out what happens when the relationship ends.

Scope of Licence and Permitted Use

The scope of licence clause is the most commercially important provision in any software agreement. It defines precisely what the licensee may do with the software. This includes which users can access it, on how many devices, for what purposes, in which geographies, and for how long. It should also make explicit what is not permitted: sublicensing to third parties, reverse engineering, decompiling, modifying the source code, and creating derivative works. Without a clear and specific scope clause, disputes about the licensee’s rights are, therefore, almost inevitable. Your commercial law adviser can ensure the scope clause accurately captures your commercial intentions and is enforceable under South African law.

Intellectual Property Ownership and Pre-Existing IP

The IP ownership clause should confirm that the licensor retains ownership of the software, the source code, the underlying algorithms, and all associated intellectual property. It should also address pre-existing IP – code, libraries, or frameworks the developer owned before the project. Any IP created specifically for the client during the project also needs covering. In bespoke development agreements, for instance, a developer who incorporates their standard component library into a client’s custom project must make one thing clear. The client receives a licence to use those components, not ownership of them. Equally, a client paying for bespoke development must understand clearly what they are receiving. Is it a licence to use finished software? Or an assignment of the copyright in the code written for them?

Warranties, Disclaimers, and Limitation of Liability

Software licence agreements typically include limited warranties from the licensor. For example, a warranty that the software will perform substantially in accordance with its documentation for a specified period. They also include broad disclaimers of all other warranties. These disclaimers need careful drafting for a South African context. The Consumer Protection Act restricts how much liability a business can disclaim in consumer-facing agreements. A liability cap – limiting the licensor’s total liability to the licence fees paid over a specified period – is standard in commercial software agreements. But the cap must be proportionate and clearly expressed to be enforceable. For South African software businesses serving both local and international clients, working with a lawyer who understands both CPA constraints and international enterprise expectations consequently adds genuine value. Nicholas Bent & Associates provides exactly this kind of dual-perspective guidance through its international law practice.

Software Licensing for Developers and Software Houses in South Africa

For software developers and development companies, licensing issues arise not just in client agreements. Internal arrangements that determine who owns the code being built are equally important. Getting IP ownership right within the development organisation – employees, contractors, and third-party contributors – is as important as getting the client-facing licence right. It is far more commonly overlooked.

Bespoke Software Development Agreements

A bespoke software development agreement governs the relationship between a developer or development company and a client who has commissioned custom software. It must address the development process (milestones, deliverables, acceptance testing), IP ownership, payment terms, and confidentiality obligations. It must also cover what happens if the project is abandoned, delayed, or delivered with defects. For clients, IP ownership is usually the most important provision. They need to know the agreement provides the rights they actually need. This might be a broad licence or an outright assignment of the copyright in the code written for them. For developers, the most important provisions protect their pre-existing IP and limit their liability for defects, delays, or consequential loss. Getting specialist advice on a bespoke software transaction before work begins prevents disputes that are far more expensive to resolve after delivery.

Who Owns the Code – Contractor vs Employee

This is one of the most commercially significant and least understood aspects of South African copyright law. An employer owns software that an employee creates in the course of their employment – not the employee – unless a written agreement provides otherwise. However, when an independent contractor creates software, the contractor owns it by default – not the client who commissioned and paid for it. This differs fundamentally from the United States, where work-for-hire principles can give clients automatic ownership of commissioned work.

In South Africa, a client who pays a freelance developer to build custom software owns nothing more than what the development contract expressly provides. Without a written agreement assigning copyright or granting an appropriate licence, the client may have paid for software they have no legal right to use. For businesses across South Africa, this is a routine risk that a short, well-drafted development agreement eliminates entirely.

Source Code Escrow

In practice, source code escrow is a commercial arrangement in which a neutral third party (the escrow agent) holds the software’s source code. Specifically, the agent releases it to the licensee if a specified trigger event occurs. Typical triggers include the licensor’s insolvency, cessation of business, or failure to maintain the software. Escrow matters whenever a business is dependent on software it does not own and has no access to the source code. Without an escrow arrangement, the business faces the risk that software it relies on becomes unsupported or inaccessible if the licensor fails. Indeed, escrow arrangements are increasingly standard in enterprise software procurement. For South African businesses evaluating software from smaller local vendors or early-stage technology companies, escrow is a practical tool for managing continuity risk.

International Software Licensing Agreements: What South African Businesses Need to Know

South African software companies that licence their products internationally face a range of issues that do not arise in purely domestic transactions. The same applies to South African businesses procuring software from international vendors. Getting these right is particularly important for South Africa’s growing technology export sector. Many of these companies contract regularly with customers and partners in the UK, EU, and US.

Licensing to International Customers

A South African software company licensing its product to a customer in the UK, EU, or US needs to consider several questions. Will the governing law clause be respected in the customer’s jurisdiction? Do local consumer protection or data protection laws in the customer’s jurisdiction impose additional obligations? Do the limitation of liability and warranty disclaimer provisions meet the standards required under applicable local law? In the EU, consumer protection legislation imposes obligations on software providers that may apply regardless of what the governing law clause says. Working with a lawyer who understands both South African law and the key requirements in target markets is a genuine commercial advantage. Nick Bent is qualified in both South Africa and the UK. That dual-jurisdiction perspective is exactly what he brings to technology law engagements.

POPIA and Data Protection in Software Agreements

Any software that processes personal information – which includes most business applications – creates data protection obligations under POPIA. The software licence agreement or a linked Data Processing Agreement must address what personal information the software processes. It must state the basis on which processing occurs and the security measures in place. The respective obligations of licensor and licensee if a breach occurs must also appear. For SaaS products, these provisions are particularly important. The licensor typically processes personal information on behalf of the licensee. This makes the licensor an “operator” under POPIA and the licensee a “responsible party.” As a result, getting this classification right has become a standard expectation across South Africa. Ensuring the agreement reflects the correct POPIA obligations is equally important.

Governing Law and Jurisdiction

A software licence agreement should specify the governing law and the forum for resolving disputes. For South African software companies, this typically means South African law and South African courts, or arbitration under South African rules. For international transactions, the governing law choice must account for a practical reality. Enforcing a South African judgment in a foreign jurisdiction requires recognition of that judgment. This varies significantly between countries. For this reason, many international software agreements include arbitration clauses – arbitral awards are more readily enforceable across borders than court judgments. Nicholas Bent & Associates works with technology businesses across South Africa and internationally, with clients in Cape Town and served remotely nationwide and beyond. Contact us or call +27 78 728 4498 to discuss your software licensing requirements.

Frequently Asked Questions About Software Licensing Agreements

What is a software licensing agreement in South Africa?

A software licensing agreement in South Africa is a contract between the software owner (the licensor) and a person or company that wants to use it (the licensee). It sets out the terms on which the software may be used. Beyond defining what is permitted and what is not, the agreement covers user access, modification rights, and what happens when it ends. South African copyright law protects software as a literary work under the Copyright Act 98 of 1978. As a result, a written licence agreement is essential to make ownership and usage rights commercially certain.

Do I need a software licence agreement if I give my software away for free?

Yes. A software licence agreement controls how your software gets used. It has nothing to do with whether you charge for it. Even if you distribute software free of charge, without a licence you have no legal basis to restrict users. They can copy it, modify it, distribute it to others, or incorporate it into competing products. Even so, a licence for free software – even a simple one – establishes that you own the copyright. It defines what users may do and provides a legal basis for enforcement if those terms are breached.

What is the difference between a software licence and a software assignment?

A licence permits the licensee to use the software under specified conditions – the licensor retains ownership. An assignment transfers ownership of the copyright from the developer to the client. After an assignment, the developer no longer owns the code and cannot use it without the new owner’s permission. For developers, assigning copyright means losing the right to reuse the same code in future projects. For clients, receiving only a licence means the developer can licence the same software to competitors. A technology lawyer in Cape Town can advise on which structure best fits your specific situation.

Who owns software developed by a contractor in South Africa?

Under the Copyright Act 98 of 1978, an independent contractor owns any software they create by default. The client who commissioned and paid for it does not. In other words, a client who pays a freelance developer to build custom software owns nothing more than what the development contract expressly provides. Without a written agreement assigning copyright or granting an appropriate licence, the client may have paid for software they have no legal right to use. A written development agreement addressing IP ownership is essential for any custom software engagement.

What are open source licence risks for South African businesses?

The most significant risk is copyleft obligations. Certain open source licences (such as the GPL family) require that any software incorporating the open source component carry the same open source terms. If a commercial software product incorporates a copyleft-licensed component, the developer may need to make their entire proprietary codebase publicly available. This destroys the product’s commercial value. Furthermore, auditing which open source licences appear in a codebase is essential due diligence for any software acquisition or investment. Therefore, complete this audit before signing a transaction.

How do I protect my software’s intellectual property in South Africa?

Under the Copyright Act 98 of 1978, South African copyright arises automatically on creation. No registration is needed. Practical steps include written IP ownership clauses in all development agreements, whether with employees or contractors. Use written licence agreements with all customers. Add confidentiality provisions protecting source code and architecture. Audit your open source licences. Register trade marks associated with your software brand. Additionally, for software companies considering investment or acquisition, a formal IP audit conducted with the help of a commercial lawyer is a worthwhile investment.

Can a software licence agreement limit my liability for bugs or failures?

Yes – limitation of liability clauses are standard in commercial software licences and are generally enforceable in South African law, subject to important constraints. The Consumer Protection Act restricts liability disclaimers in consumer-facing agreements and requires limitations to be fair, reasonable, and prominent. In B2B agreements the constraints are less restrictive, but blanket exclusions of all liability are still unlikely to be fully enforceable. A well-structured limitation clause caps aggregate liability at a specified amount and excludes consequential loss. This approach is far more defensible than attempting to exclude all liability entirely. Get in touch with Nicholas Bent & Associates to discuss structuring these provisions correctly.

What should I include in a bespoke software development agreement?

A bespoke software development agreement should address several key areas. First, the scope of work and deliverables. Second, development milestones and payment terms. Third, intellectual property ownership – who owns the finished code, pre-existing components, and anything created during the project. Fourth, acceptance testing criteria and the defect resolution process. Fifth, confidentiality obligations on both sides. Sixth, warranties and liability limitations. Seventh, the process for managing scope changes. And finally, termination rights, including what happens to work in progress. Above all, for any engagement involving significant investment by either party, a written development agreement should be in place before a line of code is written.