Hiring a Developer in South Africa: Contracts and IP

The thing that catches people out when hiring a developer in South Africa is simple: paying for software does not mean you own it. You can commission a developer, pay every invoice, launch the product and still not hold the copyright in the code. Ownership turns on the Copyright Act and your contract, not on the payment. Here is the plain version of what the law says, and what your agreement must do about it.

Who owns the code when hiring a developer in South Africa

South African copyright is governed by the Copyright Act 98 of 1978. Computer programs were added as a protected category by an amendment in 1992, which defines a computer program as a set of instructions that, when used in a computer, directs its operation to bring about a result.

Three rules decide who starts out owning the code:

• The author owns it first. Section 21 says copyright vests in the author. For a computer program, the 1992 amendment defines the author as the person who exercised control over the making of it.
• Employees are different. When a work is made in the course of the author’s employment under a contract of service or apprenticeship, the employer owns it.
• Commissioning software is not enough. The Act does give a commissioning client ownership of some paid-for works, but that rule covers photographs, portraits, gravures, films and sound recordings, not computer programs.

Why paying is not enough

South Africa has no general rule that software belongs to the client who paid for it. To own the code, you need an assignment of copyright, and section 22(3) of the Act says an assignment has no effect unless it is in writing and signed by or on behalf of the assignor, the developer. In a contract, that is the IP-assignment clause. The Act also allows copyright in future work to be assigned, so the clause can cover code that has not been written yet.

What typically goes wrong

When the contract is thin or missing, the same problems come up:

• IP disputes, where the developer reuses or resells code you thought was yours.
• 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 have a running product but not the code behind it.
• Undisclosed open-source or third-party code, included under licence terms you never agreed to.

Software development contract in South Africa: clauses to insist on

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.
• Keep the code in a repository you control, updated at each milestone, so a handover is never a favour.
• Consider 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 and pre-existing code, with its licences, so nothing unexpected is built into your product.
• Apply POPIA if the developer handles personal information for you: section 20 requires them to keep it confidential, and section 21 requires a written contract that obliges them to keep it secure.

For example, a Gqeberha logistics company commissioning a dispatch app could ask for the IP assignment, the repository access and the open-source list before the first payment, and tie each payment to a demonstrated milestone. If the developer stops responding halfway, the company still owns what was built and can hand the code to someone else.

Employee or independent contractor?

The difference matters twice. Under section 21, work an employee makes in the course of employment belongs to the employer, while a contractor’s work does not follow that rule, so contractors need an assignment. Labour law also has a presumption about who counts as an employee (section 200A of the Labour Relations Act and section 83A of the Basic Conditions of Employment Act), so a “contractor” who works like an employee may be treated as one. Get advice on how you engage people.

If you hire a studio rather than a freelancer, ask for the same things: a fixed price for a written scope, the IP assignment and the source-code handover. As one reference point, Zaiq’s published prices start from R8,000 for a focused build and state that you own the result. For the checks to run before you sign, see the freelance developer vetting checklist.

This is general guidance, not legal advice. For your contract, speak to a South African IP or commercial lawyer.