Build & automate
Hiring a developer in South Africa: contracts and IP
The thing that catches South African business owners out is simple: paying for software does not mean you own it. You can commission a developer, pay every invoice, ship the product, and still not hold the copyright in the code. Ownership in South Africa turns on the contract, not the payment. Here is the plain version of what the law says and what your agreement must do about it.
Who legally owns the code
South African copyright is governed by the Copyright Act 98 of 1978, and a computer program is a protected category of work. The rule that matters is this: the author, the person who creates the work, is the first owner of the copyright. So a freelancer or independent contractor owns the copyright in the code they write by default. The exception runs the other way for staff: an employee’s work created in the course of employment belongs to the employer. Get that distinction right before anything else, because it decides who starts out holding the rights.
Why paying isn’t enough
This is the gap most people fall into. South Africa has no automatic US-style “work made for hire” for commissioned software, so paying a developer does not move the copyright to you. The commissioned-work exceptions that do exist in the Act, for things like photographs, portraits, engravings, films and sound recordings, do not cover custom software. To own the code you need a written assignment of copyright, signed by the developer as the assignor, because the Act requires an assignment to be in writing and signed. In a contract, that is the IP-assignment clause. Without it, you have paid for a copy and left the rights behind.
What typically goes wrong
When the contract is thin or missing, the same problems recur:
- IP disputes, where the developer reuses or resells code you thought was yours, because they still own it.
- Abandonment mid-project, leaving you with no working source and no remedy.
- Scope creep, where “just one more thing” has no agreed boundary or price.
- No source-code handover, so you hold a running product but not the code behind it.
- Undisclosed open-source or third-party code, baked in under licences you never agreed to.
What your contract must say
A solid Software Development Agreement does the protective work for you. These are the clauses to insist on.
| Clause | What it protects | Why it matters |
|---|---|---|
| IP assignment (on creation or full payment) + moral-rights waiver | Ownership of the copyright | Without a written, signed assignment the developer keeps the code under the Copyright Act 98 of 1978 |
| Scope, deliverables, acceptance + milestones | What is being built | Kills scope creep and gives you a clear yardstick for “done” |
| Source-code + documentation handover | The actual code and how it works | A running product is useless if you cannot maintain or move it |
| Warranties (original work, non-infringing, fit for purpose) | Quality and clean provenance | The developer stands behind the work being theirs to give |
| Confidentiality / NDA | Your data, logic and plans | Keeps sensitive business information from leaking or being reused |
| Reasonable non-compete / non-solicit | Your position and your people | Stops the developer turning your build straight into a rival’s |
| Payment milestones with holdbacks | Your money | You never pay far ahead of delivered, accepted work |
| Termination + remedies | Your exit | A clean way out, and consequences, if it goes wrong |
| Indemnity | Your downside | The developer covers you against third-party IP-infringement claims |
| South African governing law | The whole agreement | Disputes are decided under the law the contract is written for |
Protecting yourself in practice
The contract sets the rules; a few habits make them real.
- Stage payments with holdbacks so you are never paying ahead of delivered, accepted work, which also softens the blow if the developer walks.
- Use source-code escrow for high-value builds, so an independent party holds a copy you can recover if the developer disappears.
- Require disclosure of open-source or pre-existing IP, with clear licensing, so nothing unexpected is baked into your product.
- Apply POPIA if the developer handles personal data, and handle that data lawfully and securely throughout.
- Keep it a genuine independent-contractor relationship. Misclassifying a contractor as a de-facto employee carries labour and tax consequences, so either keep the relationship a true independent-contractor one or employ the person properly.
Where Zaiq fits
We are an AI engineering studio in South Africa, and we make this part boring on purpose. You own the IP from day one, the source code and documentation are handed over, and the price is fixed, so the contract questions above are answered before we start. There is no abandonment risk, because you are dealing with a studio, not a freelancer who might go quiet. The point was never the AI; it is that you own the result outright, source code, documentation and accounts included. If you want the build without the ownership headache, bring us the problem at zaiq.ai/work and we will tell you straight how it will work.
This is general guidance, not legal advice. For your specific contract, confirm with a South African IP or commercial lawyer.
Related guides
Questions people ask
Who owns the code if I hire a South African freelancer without a contract?
The freelancer does. Under the Copyright Act 98 of 1978 the author, the person who creates the work, is the first owner of the copyright, and a computer program is a protected work. With no written assignment, an independent contractor keeps the copyright in the code they wrote, even though you commissioned and paid for it. You hold a copy, not the rights.
Does paying a developer transfer the copyright in South Africa?
No. Payment buys the work, not the copyright. South Africa has no automatic US-style "work made for hire" for commissioned software, so the developer stays the owner unless the copyright is assigned to you in writing and signed by them. An IP-assignment clause in the contract is what actually moves ownership across.
What must a software development contract include?
At a minimum: IP assignment on creation or full payment, plus a moral-rights waiver; scope, deliverables and acceptance with milestones; source-code and documentation handover; warranties that the work is original and non-infringing; confidentiality; a reasonable non-compete or non-solicit; payment milestones with holdbacks; termination and remedies; indemnity; and South African governing law.
Can a freelance developer reuse or resell my code?
If they still own the copyright, potentially yes, which is the risk of having no assignment. Once the copyright is assigned to you in writing under the Copyright Act 98 of 1978, they cannot reuse or resell it without your permission. Pair the assignment with a warranty of original work and a disclosure clause for any open-source or pre-existing code they bring in.
What happens if my developer disappears mid-project?
Without the right contract, you can be left with no source code, no rights, and no remedy. Protect against it up front: stage payments with holdbacks so you are never far ahead, require source-code and documentation handover at each milestone, and spell out termination and remedies. For high-value builds, source-code escrow gives you a copy if the developer vanishes.
Do I need an NDA with a developer?
Usually yes. A developer often sees customer data, business logic and plans, so a confidentiality or NDA term is standard in a software development agreement. If they touch personal information, POPIA applies on top, so handle that data lawfully and securely. Keep the confidentiality obligation running after the project ends, not only during it.
Does it matter if the developer is an employee or an independent contractor?
It matters a lot. Under the Copyright Act 98 of 1978 an employee's work created in the course of employment belongs to the employer, while an independent contractor owns their work by default and must assign it. Keep a contractor a genuine independent contractor: misclassifying one as a de-facto employee carries labour and tax consequences.