Introduction
A software licensing agreement is the legal mechanism by which the owner of software grants another party the right to use that software on defined terms. In South Africa, software licensing is governed primarily by the Copyright Act 98 of 1978 and by common law contract principles. Unlike a sale of goods, a software licence does not transfer ownership of the underlying intellectual property — it grants a permission, subject to conditions, while the licensor retains all proprietary rights.
The distinction matters because South African copyright law treats software as a "literary work" under the Copyright Act. This means that the full suite of copyright protections — including the exclusive right to reproduce, adapt, and distribute — applies to software by default. Without a licence, any person who copies, installs, or uses software without the copyright owner's permission commits an infringement. The licence is what converts what would otherwise be infringement into lawful use.
For businesses, the implications are direct. Every piece of software used in a commercial operation — from enterprise resource planning systems to developer tools to cloud-based productivity suites — is used under a licence of some kind. The terms of that licence determine what the business may and may not do with the software: whether it may be installed on multiple machines, whether it may be modified, whether it may be sublicensed to clients or contractors, and what happens to the business's data when the licence terminates. Poorly drafted or poorly understood licensing agreements expose businesses to infringement claims, data loss, operational disruption, and significant financial liability.
This guide provides a comprehensive overview of software licensing law in South Africa. It covers the principal types of software licences, the essential clauses that every licensing agreement should contain, the intellectual property framework under the Copyright Act, data protection obligations under the Protection of Personal Information Act 4 of 2013 (POPIA), and the most common mistakes South African businesses make when entering into software licensing arrangements.
Types of Software Licences
Software licences fall into several broad categories, each with distinct legal characteristics and commercial implications. The choice of licence type determines the scope of the user's rights, the licensor's ongoing obligations, and the allocation of risk between the parties. South African businesses must understand these distinctions to ensure that the licence they acquire — or the licence they grant — matches the intended commercial arrangement.
Proprietary Licences
Proprietary licences are the most common form of commercial software licence. The licensor retains full ownership of the intellectual property and grants the licensee a limited right to use the software, subject to restrictions set out in the agreement. The licensee typically receives object code only — the compiled, executable version of the software — and does not receive access to the source code.
Within proprietary licensing, several sub-categories exist. An End User Licence Agreement (EULA) is the standard consumer-facing licence that accompanies off-the-shelf software products. It is typically non-negotiable — the user accepts it by clicking "I agree" or by installing the software. Enterprise licence agreements, by contrast, are negotiated contracts between the software vendor and a corporate customer, and they typically address volume pricing, deployment scope, support levels, service level agreements, and custom terms around data handling and security.
Volume licensing programmes allow organisations to acquire multiple licences under a single agreement, often at a discounted per-unit cost. These programmes are common with major software vendors and typically include provisions for true-up audits — periodic reviews in which the vendor verifies that the number of installations does not exceed the number of licences purchased. Non-compliance discovered during an audit can result in substantial back-payment obligations and, in some cases, infringement claims.
Open Source Licences
Open source software is distributed under licences that permit users to view, modify, and redistribute the source code. However, "open source" does not mean "without legal obligations." Each open source licence imposes specific conditions that users must comply with, and failure to do so constitutes copyright infringement under the Copyright Act.
The most significant distinction within open source licensing is between copyleft and permissive licences. Copyleft licences — most notably the GNU General Public License (GPL) — require that any derivative work based on GPL-licensed code must itself be distributed under the GPL. This has significant implications for commercial software companies: if a developer incorporates GPL-licensed code into a proprietary product, the entire product may need to be released under the GPL, effectively making the proprietary code open source. This is sometimes referred to as the "viral" effect of the GPL.
Permissive licences — including the MIT License and the Apache License 2.0 — impose far fewer restrictions. They typically require only that the original copyright notice and licence text be included in any redistribution. Permissive-licensed code may be incorporated into proprietary products without triggering an obligation to open-source the proprietary code. For this reason, permissive licences are generally preferred for commercial use.
South African technology companies must conduct open source audits before distributing software commercially. An audit identifies all open source components within the codebase, maps the applicable licences, and assesses whether compliance obligations have been met. Failure to do so can result in infringement claims and, in the context of a business sale or investment, can materially affect the valuation of the company's intellectual property portfolio.
SaaS and Subscription Models
Software as a Service (SaaS) has fundamentally changed the commercial model for software delivery. In a SaaS arrangement, the customer does not install or possess a copy of the software. Instead, the customer accesses the software remotely — typically through a web browser — and the vendor hosts, maintains, and updates the software on its own infrastructure. Legally, a SaaS arrangement is not a traditional software licence at all. It is a service agreement, though it typically incorporates licensing elements.
The legal implications of this distinction are significant. Because the customer does not receive a copy of the software, copyright infringement by the customer is less of a concern. The critical issues in SaaS agreements are instead: data ownership and portability, service availability and uptime commitments, data security obligations, what happens to the customer's data upon termination, and the vendor's right to modify the software unilaterally. For South African businesses, POPIA compliance is an additional mandatory consideration whenever the SaaS platform processes personal information.
Subscription licensing — where software is installed locally but licensed on a recurring payment basis rather than a perpetual basis — is a hybrid between traditional licensing and SaaS. The customer possesses a copy of the software but loses the right to use it if the subscription lapses. This model has become dominant for major productivity and creative software suites.
Perpetual vs Term Licences
A perpetual licence grants the licensee the right to use the software indefinitely, subject to compliance with the licence terms. The licensee typically pays a one-time upfront fee. Ongoing support and updates are usually available under a separate maintenance agreement for an annual fee. If the maintenance agreement lapses, the licensee retains the right to use the existing version but does not receive updates, patches, or vendor support.
A term licence grants the right to use the software for a fixed period — commonly one to three years — after which the licence expires unless renewed. Term licences offer lower upfront costs but higher total cost of ownership over an extended period. From a legal perspective, the critical question in any term licence is what happens upon expiry or non-renewal: whether the licensee must delete all copies, whether data can be exported, and what transition period, if any, is provided.
Single-User, Multi-User, and Site Licences
The scope of a licence — how many people or machines may use the software — is one of its most fundamental commercial terms. A single-user licence (also called a "per-seat" licence) authorises one named individual or one device to use the software. A multi-user licence permits a specified number of concurrent or named users. A site licence authorises use by all personnel at a specified physical location, regardless of the number of users.
The distinction between "named user" and "concurrent user" licensing is commercially significant. A named user licence is assigned to a specific individual and may not be shared, even if that individual is not actively using the software. A concurrent user licence permits any authorised person to use the software, provided the total number of simultaneous users does not exceed the licensed number. Concurrent licensing is typically more expensive per licence but more cost-effective for organisations where not all users need access simultaneously.
Key Clauses in a Software Licensing Agreement
A well-drafted software licensing agreement must address a comprehensive set of legal and commercial issues. Each clause allocates rights, obligations, and risk between the licensor and licensee. The absence of any of the following clauses creates ambiguity — and ambiguity in a contract invariably favours the party that did not draft it.
Grant of Licence
The grant clause is the core operative provision of any software licence. It defines precisely what the licensee is permitted to do with the software. A properly drafted grant clause specifies: the scope of the licence (what the licensee may do — use, copy, modify, distribute); the territory (geographic limitations, if any); whether the licence is exclusive or non-exclusive; the field of use (whether the licence is limited to specific purposes); and the duration (perpetual, fixed term, or subscription).
Under South African law, a licence must be interpreted restrictively — rights not expressly granted are reserved to the copyright owner. This is consistent with the general principle that the copyright owner's exclusive rights under section 6 of the Copyright Act are only diminished to the extent specifically agreed. A licensee who exceeds the scope of the grant commits infringement, regardless of whether the excess was intentional.
Intellectual Property Ownership and Reservation of Rights
The agreement must expressly state that ownership of the software — including all intellectual property rights in the software and any updates, modifications, or derivative works — remains with the licensor. This clause should also address ownership of any customisations or configurations created during implementation. Without clear language, disputes can arise about whether bespoke work commissioned by the licensee belongs to the licensee or the licensor. Under section 21(1)(c) of the Copyright Act, where a work is created pursuant to a commission and payment has been made, the commissioner owns the copyright unless otherwise agreed. This default can produce unexpected results if not addressed in the agreement.
Usage Restrictions
The usage restrictions clause sets the boundaries of the licensee's rights. It typically prohibits: reverse engineering, decompilation, or disassembly of the software (except to the extent permitted by applicable law); modification of the software without the licensor's consent; sublicensing, assignment, or transfer of the licence without prior written consent; use of the software to provide services to third parties (unless specifically authorised); and removal or alteration of copyright notices or proprietary markings. In South Africa, section 15(3A) of the Copyright Act provides a limited exception permitting the making of back-up copies — a right that cannot be excluded by contract. Any usage restriction that purports to override this statutory right is unenforceable.
Payment Terms and Fee Structures
Software licensing fees can be structured in various ways, each with distinct legal and commercial implications. Common models include: per-user or per-seat fees (a fixed amount per authorised user); per-device fees (based on the number of machines on which the software is installed); usage-based fees (calculated by reference to transaction volumes, API calls, or data processed); revenue-based fees (a percentage of the licensee's revenue derived from use of the software); and flat-rate fees (a fixed amount regardless of usage). The agreement should specify the payment amount, frequency, currency, due dates, consequences of late payment (including interest and the right to suspend the licence), and whether fees may be increased during the term. VAT treatment must also be addressed — software licence fees are subject to VAT in South Africa at the standard rate.
Warranties and Disclaimers
The warranty clause typically warrants that the software will perform substantially in accordance with its published documentation for a specified period. Beyond this limited warranty, most commercial software agreements disclaim all other warranties — including implied warranties of merchantability, fitness for a particular purpose, and non-infringement — to the maximum extent permitted by law. Under South African consumer protection law, the Consumer Protection Act 68 of 2008 (CPA) applies to software transactions where the licensee is a consumer as defined in the CPA. Where the CPA applies, certain implied warranties cannot be excluded, including the right to receive software that is of good quality, in working order, and free from defects. Commercial enterprises licensing software for business purposes may fall outside the CPA's scope depending on the size of the transaction and the nature of the licensee.
Limitation of Liability
Limitation of liability clauses cap the total amount that the licensor may be required to pay in damages. A typical limitation restricts the licensor's total aggregate liability to the amount of licence fees paid by the licensee in the twelve months preceding the claim. The clause also typically excludes liability for indirect, consequential, incidental, and special damages — including loss of profits, loss of data, and business interruption. South African courts generally uphold limitation of liability clauses in commercial contracts between sophisticated parties, provided the clause is not unconscionable and does not purport to exclude liability for fraud or intentional misconduct.
Indemnification
The indemnification clause addresses who bears the risk if the software infringes a third party's intellectual property rights. In a well-balanced agreement, the licensor indemnifies the licensee against third-party claims alleging that the software, as delivered, infringes the intellectual property rights of the claimant. The licensor's obligations under this indemnity typically include: defending the claim at its own cost; paying any damages awarded or settlement agreed; and, if the software is found to infringe, either obtaining a licence for the licensee to continue using the software, modifying the software to be non-infringing, or refunding the licence fees. The licensee, in turn, typically indemnifies the licensor against claims arising from the licensee's use of the software in a manner that breaches the licence terms.
Data Protection and POPIA Compliance
Where the software processes personal information — as defined in POPIA — the agreement must include data protection provisions. If the licensor processes personal information on behalf of the licensee, the licensor acts as an "operator" under POPIA, and the agreement must constitute a valid operator agreement as contemplated by section 20 of POPIA. This requires the agreement to specify: the purpose of processing; the categories of personal information processed; the security measures the operator must implement; obligations regarding data breach notification; restrictions on cross-border transfers of personal information; and the obligations of the operator upon termination of the agreement, including the return or deletion of personal information. For a practical example of POPIA implementation, see our privacy policy.
Term and Termination
The term clause specifies the duration of the licence and the circumstances in which it may be terminated before expiry. Termination provisions typically address: termination for material breach (with a cure period); termination for insolvency or business rescue proceedings; termination for convenience (where one or both parties may terminate on notice, usually subject to a minimum commitment period); and the consequences of termination, including the licensee's obligation to cease using the software and to delete or return all copies. The agreement should also address data portability on termination — specifically, the licensee's right to export its data in a usable format within a reasonable period after termination.
Source Code Escrow
A source code escrow arrangement addresses a critical commercial risk for licensees of proprietary software: what happens if the licensor ceases to exist or becomes unable to maintain the software. Under an escrow arrangement, the licensor deposits the software's source code with an independent escrow agent. Upon the occurrence of specified "release events" — typically the licensor's insolvency, material breach, or failure to provide contracted support — the escrow agent releases the source code to the licensee, enabling the licensee to maintain the software independently or through a third party. Source code escrow is particularly important for mission-critical enterprise software where the licensee has no practical alternative.
Dispute Resolution
The dispute resolution clause determines how disagreements between the parties will be resolved. Options include: litigation in the South African courts (specifying the jurisdiction — typically the High Court of the division where the licensor or licensee is domiciled); arbitration under the rules of the Arbitration Foundation of Southern Africa (AFSA) or under ad hoc rules; and mediation as a precondition to formal proceedings. For cross-border software agreements, the choice of governing law and dispute resolution forum is critical — South African licensees should ensure that they are not subject to the exclusive jurisdiction of a foreign court without understanding the implications.
Intellectual Property Considerations
The intellectual property framework governing software in South Africa is established by the Copyright Act 98 of 1978. Understanding how the Act applies to software is essential for both licensors and licensees — it determines who owns the software, what rights exist, and how those rights can be enforced.
Software as a "Literary Work"
The Copyright Act defines "literary work" to include "computer programs." This classification is significant because it brings software within the full scope of copyright protection without the need for registration. In South Africa, copyright subsists automatically upon creation of the work, provided the work is original (in the sense that it is the product of the author's own intellectual effort and not copied from another work) and the author is a South African citizen, resident, or domiciliary, or the work was first published in South Africa.
The exclusive rights granted to the copyright owner of a literary work under section 6 of the Act include the right to: reproduce the work; publish the work; perform the work in public; broadcast the work; cause the work to be transmitted in a diffusion service; and make an adaptation of the work. In the context of software, the most commercially significant of these rights are the right to reproduce (which includes copying the software onto a hard drive or server) and the right to make an adaptation (which includes modifying the source code).
Ownership: Employer vs Contractor
Section 21 of the Copyright Act establishes the rules for determining who owns the copyright in a work. These rules are critical in the software context because they determine whether the company that paid for the software actually owns it.
Employment: Under section 21(1)(d), where a computer program is made by the author in the course of employment under a contract of service, the employer is the owner of the copyright, unless otherwise agreed. This is a clear and favourable rule for employers — provided the developer is a genuine employee working under a contract of service (not an independent contractor) and the software was created in the course of the developer's employment duties.
Commission: Under section 21(1)(c), where a work is made pursuant to a commission and payment is made (or the obligation to make payment exists), the person who commissioned the work is the owner of the copyright, subject to any contrary agreement. This means that a South African company that commissions a freelance developer or a software development firm to create bespoke software will, by default, own the copyright in the resulting software — but only if the arrangement qualifies as a "commission" and payment has been made or agreed.
The practical risk lies in the absence of a written agreement. If the relationship between the parties is ambiguous — neither clearly employment nor clearly a commission — disputes about ownership become expensive to resolve. Every software development arrangement, whether with an employee or a contractor, should include a written agreement that expressly addresses IP ownership. For companies structured under the Companies Act 71 of 2008, ensuring that IP created by employees and contractors vests in the company is a fundamental aspect of protecting the company's asset base.
Moral Rights
Section 20 of the Copyright Act grants authors certain moral rights, including the right to claim authorship of the work and the right to object to any distortion, mutilation, or other modification of the work that would be prejudicial to the honour or reputation of the author. In the software context, moral rights are less commercially significant than economic rights, but they cannot be entirely disregarded. A software development agreement should address moral rights explicitly — ideally obtaining a waiver from the developer, to the extent permitted by law, or at minimum ensuring that the developer consents to modifications of the software by the commissioner or licensee.
Registration Considerations
South Africa does not have a registration system for copyright. Copyright subsists automatically upon creation, and there is no formality requirement. However, practical steps can strengthen the copyright owner's position in the event of a dispute: maintaining version control records that demonstrate the date of creation and the identity of the author; preserving original source code and development documentation; and including appropriate copyright notices in the software. While trademarks and patents associated with software can be registered with CIPC, the copyright in the software code itself requires no registration.
POPIA Compliance in Software Agreements
The Protection of Personal Information Act 4 of 2013 (POPIA) imposes direct obligations on any party that processes personal information. In the context of software licensing and SaaS agreements, POPIA compliance is not optional — it is a statutory requirement that affects both the structure of the agreement and the operational obligations of the parties.
Responsible Party vs Operator
POPIA distinguishes between a "responsible party" (the entity that determines the purpose and means of processing personal information) and an "operator" (an entity that processes personal information on behalf of the responsible party under a contract or mandate). In a typical software licensing or SaaS arrangement, the licensee is the responsible party — it determines why and how personal information is processed — and the software vendor or SaaS provider is the operator. This classification triggers the requirement under section 21 of POPIA for a written contract between the responsible party and the operator, specifying the processing activities the operator is authorised to perform and the security measures the operator must implement.
Security Safeguards
Section 19 of POPIA requires both responsible parties and operators to secure the integrity and confidentiality of personal information by implementing appropriate technical and organisational measures. In the software context, this means the agreement must address: encryption standards (both in transit and at rest); access controls and authentication mechanisms; regular security assessments and penetration testing; incident response procedures; and data breach notification obligations. The operator must notify the responsible party — and the responsible party must notify the Information Regulator and affected data subjects — as soon as reasonably possible after a security compromise.
Cross-Border Transfers
Section 72 of POPIA restricts the transfer of personal information to third parties in foreign countries unless certain conditions are met. Where a software vendor or SaaS provider hosts data outside South Africa — which is common with global cloud providers — the agreement must ensure that the transfer is lawful under POPIA. Permissible grounds include: the recipient being subject to a law or binding agreement that provides an adequate level of protection; the data subject consenting to the transfer; the transfer being necessary for the performance of a contract; or the transfer being for the benefit of the data subject and it being impracticable to obtain consent. South African businesses using international SaaS platforms must assess where their data is stored and processed and ensure that the contractual framework addresses section 72 compliance.
Data Retention and Deletion
POPIA's retention limitation condition (Condition 5) requires that personal information must not be retained for longer than is necessary for achieving the purpose for which it was collected, unless retention is required or authorised by law. The software agreement should specify data retention periods, the process for deleting personal information upon termination of the agreement, and certification of deletion. For SaaS platforms in particular, the licensee must have contractual assurance that its data — including backups and redundant copies — will be securely deleted within a defined period after termination.
Common Pitfalls in South African Software Licensing
In practice, South African businesses — both licensors and licensees — make a consistent set of errors in their software licensing arrangements. These errors create legal exposure that is often only discovered when a dispute arises or a transaction requires due diligence. The following are the most consequential pitfalls.
Ambiguous Scope of Licence
The most common error is a licence grant that fails to define the scope of permitted use with sufficient precision. Phrases such as "the licensee may use the software for business purposes" are inadequate — they leave open questions about the number of users, the number of installations, geographic limitations, and whether the software may be used to provide services to third parties. An ambiguous scope invites disputes and, because South African law interprets licences restrictively, ambiguity generally favours the licensor. Licensees who believe they have broad rights may discover, when challenged, that their actual rights are far narrower than assumed.
Failure to Address IP Ownership in Development Agreements
South African technology companies frequently engage freelance developers, agencies, or offshore development teams to build software without a written agreement that clearly assigns intellectual property rights. The default rules under section 21 of the Copyright Act can produce unexpected results, particularly where the development is not clearly a "commission" or where the developer retains rights to pre-existing code or libraries incorporated into the deliverable. Every development engagement must include an express assignment of IP, a licence-back for pre-existing materials, and clear provisions regarding ownership of derivative works.
Inadequate Data Protection Provisions
Many software licensing agreements predate POPIA or were drafted without South African data protection law in mind. An agreement that does not address personal information processing, operator obligations, security safeguards, breach notification, and cross-border transfers is non-compliant with POPIA and exposes the responsible party to enforcement action by the Information Regulator, including administrative fines of up to R10 million and criminal liability under section 107. Existing agreements should be reviewed and updated to include POPIA-compliant data processing terms.
Missing Source Code Escrow for Mission-Critical Software
Businesses that depend on proprietary software for critical operations — and that have no access to the source code — face an existential risk if the software vendor fails. Without a source code escrow arrangement, the licensee has no ability to maintain, update, or migrate the software independently. This risk is particularly acute for South African businesses licensing software from foreign vendors with no local presence. A source code escrow agreement is an inexpensive form of insurance against this risk and should be considered for any mission-critical deployment.
Overreliance on Click-Wrap Agreements
Click-wrap agreements — where the user accepts terms by clicking a button — are standard for consumer software but are often inadequate for commercial deployments. Click-wrap EULAs are drafted by the vendor in the vendor's interests. They typically contain broad limitation of liability clauses, unilateral modification rights, and governing law provisions that may subject the South African licensee to foreign jurisdiction. For any commercial software deployment of material value, the EULA should be reviewed by a lawyer, and where the commercial relationship justifies it, replaced with a negotiated licence agreement that addresses the licensee's specific requirements.
Ignoring Open Source Licence Compliance
South African software companies frequently incorporate open source components into commercial products without conducting a licence compliance audit. The consequences can be severe: a company that distributes software containing GPL-licensed code without complying with the GPL's requirements may be compelled to release its own proprietary source code or face an infringement claim. During the due diligence phase of a business sale or investment, unresolved open source compliance issues can materially reduce the valuation of the company's IP portfolio or, in extreme cases, prevent the transaction from proceeding.
Choosing Between Licence Types
Selecting the appropriate licence structure requires balancing commercial objectives, risk tolerance, and operational requirements. There is no universally correct answer — the right structure depends on the nature of the software, the relationship between the parties, and the business context.
For Software Vendors
SaaS or subscription models provide recurring revenue and allow the vendor to maintain control over the software environment, updates, and security. They are generally preferred for cloud-native products with broad customer bases.
Perpetual licences with maintenance agreements are appropriate for on-premise enterprise deployments where the customer requires long-term certainty. They provide a large upfront payment but require ongoing support infrastructure.
Open source with commercial add-ons (the "open core" model) can accelerate adoption and community contribution while reserving premium features for paying customers. This model requires careful licence management to ensure that the open source and proprietary components are properly separated.
For Licensees and Purchasers
Evaluate total cost of ownership — a perpetual licence with annual maintenance may be more cost-effective over five years than a subscription, but the subscription eliminates the upfront capital expenditure and includes automatic updates.
Assess vendor risk — for mission-critical software from a smaller or single-product vendor, negotiate source code escrow and robust termination provisions. For established vendors with large customer bases, the risk of vendor failure is lower but the negotiating leverage is also typically lower.
Consider data portability — regardless of the licence type, ensure that you can extract your data in a usable format at the end of the relationship. Vendor lock-in is a commercial risk that is best addressed at the contracting stage, not at the point of exit.
Practical Guidance for South African Tech Companies
South African technology companies — whether they are developing software for local or international markets — should establish a licensing strategy early in the product lifecycle. This means deciding on the licence model before the first customer is acquired, not after. The licence model affects the product architecture (SaaS requires multi-tenancy; on-premise requires installer and deployment tooling), the revenue model (recurring vs upfront), the IP protection strategy (proprietary vs open source vs hybrid), and the contractual framework (standard EULA vs negotiated enterprise agreements).
Companies operating in the South African market must also consider the regulatory environment. POPIA compliance is mandatory for any software that processes personal information. B-BBEE considerations may affect procurement decisions by enterprise customers — a locally owned and operated software vendor may have a competitive advantage in public sector and large corporate procurement processes. The Electronic Communications and Transactions Act 25 of 2002 (ECTA) governs the formation of electronic contracts, including click-wrap agreements — understanding ECTA's requirements for valid electronic agreements is essential for any vendor distributing software online.
Conclusion
Software licensing is not a peripheral legal concern — it is central to how technology businesses operate, generate revenue, and protect their intellectual property. In South Africa, the legal framework is established by the Copyright Act 98 of 1978, supplemented by POPIA for data protection obligations, the Consumer Protection Act for consumer-facing transactions, and common law contract principles for the interpretation and enforcement of licence agreements.
For software vendors, a well-drafted licensing agreement protects the company's IP, defines the commercial relationship with clarity, and limits liability exposure. For licensees, understanding the terms of the licence is essential to ensure that the software can be used as intended, that data is protected, and that the business is not exposed to infringement claims or unexpected costs.
The most consequential mistakes in software licensing — ambiguous licence scope, unresolved IP ownership, inadequate data protection provisions, missing source code escrow, and overreliance on click-wrap agreements — are all preventable with proper legal advice at the contracting stage. Remedial advice after a dispute has arisen is invariably more expensive and less effective than proactive structuring at the outset.
Whether you are a software vendor structuring your first commercial licence, a business acquiring enterprise software for a critical deployment, or a technology company preparing for investment or acquisition, specialist legal advice on your software licensing arrangements is an investment in commercial certainty.
For specialist technology law advice in Pretoria and Johannesburg, see our legal services, including our technology law practice.
Read more: Corporate and commercial law services for company structuring and IP protection.
Related: Companies Act 71 of 2008 guide for IP ownership under company structures.
Need Help With Software Licensing?
Martin Kotze, attorney at MJ Kotze Inc, advises software vendors, technology companies, and businesses on software licensing agreements, IP ownership, POPIA compliance, and technology transactions across Pretoria and Johannesburg.