Who owns the code when you pay a developer to build software?
Short answer. In Australia, when you engage a contractor or agency, the developer usually owns the copyright in the code it writes unless a written agreement assigns it to you. Paying for the work is generally not enough on its own. Before work starts, get a contract that assigns the IP, delivers the source code, and puts the repository, cloud account, domain and data in your name.

In this guide · 6 minute read
What the law says by default
Under the Copyright Act 1968, computer programs are protected as literary works, and the first owner of copyright is generally the author. There is an important exception: when an employee writes code as part of their job, their employer usually owns it. A contractor, freelancer or agency is not your employee, so unless something in writing says otherwise, the copyright in the code they write for you generally stays with them, even though you paid for it.
Courts can sometimes find that a client has an implied licence to use what it paid for, for the purpose it was commissioned. That is a weaker position than ownership. A licence may not let you change the code, give it to another developer, sell it with the business or stop the original developer reusing it. Relying on an implied licence means relying on an argument, which is the last thing you want during a dispute or a sale.

What to put in the contract
The fix is simple and cheap compared with a dispute: put it in writing before the work starts. An assignment of copyright has to be in writing and signed by the person assigning it, so a line in a proposal or an email saying “you'll own it” may not be enough. Ask for clauses that cover each of the following, and have your own lawyer review the contract before you sign.
- 01Assignment of intellectual property: the copyright and other IP in the work created for you passes to your business, on creation or on payment, as the contract sets out.
- 02Source code delivery: the full source code, build scripts and configuration, delivered as the work progresses to a repository you control. A zip file at the end is too late to check.
- 03Access to accounts: the code repository, cloud hosting, domain names and any app store accounts registered to your business, with the developer added as a user.
- 04Third-party and open-source components: a list of the libraries, services and tools the system depends on, and their licence terms. These are licensed to you, and nobody can assign you ownership of them.
- 05Pre-existing tools: if the developer reuses its own earlier code, a clear, permanent licence for you to use, change and transfer it as part of your system.
- 06Moral rights consents: where relevant, written consents from the individual programmers, so later changes to the code don't raise a moral rights issue.
- 07Data and documentation: your business data and the system's documentation stay yours, and are handed over or deleted when the engagement ends.
Assignment or escrow?
Source code escrow is an arrangement where a developer deposits its code with an independent third party, who releases it to you if certain events happen, such as the developer going out of business or stopping support. It suits software the developer licenses to many customers and won't assign to any of them, such as a packaged product your business depends on.
For software built specifically for your business, escrow is usually the weaker option. You only see the code if a release event happens, the deposit may be out of date by then, and you still don't own it. An assignment, with the code in your own repository as it's written, gives you the code, the right to change it, and the freedom to hand it to another developer whenever you choose.
★★★★★
“One of the BEST companies our business has worked with.”
What “you own it” should mean in practice
A clause in a contract is only half of ownership. The other half is practical control: if your developer disappeared tomorrow, could another team pick up the system next week? That depends on whether your business holds each of the following in its own name, with its own admin logins, rather than borrowing access from the people who built it.
- 01The code repository, with its full history.
- 02The cloud account the system runs in, billed to your business.
- 03The domain names and DNS settings.
- 04The database and its backups, with a tested way to export them.
- 05Documentation of how the system is built, deployed and configured.
- 06Admin access to every connected service, such as Xero, Stripe, email and SMS providers.
- 07App store developer accounts, if there's a mobile app.

How Hypex handles it
Hypex assigns the intellectual property, the code and the data to the client, and the system runs in the client's own cloud account. If we stopped working together, the system, its data and the right to change it would stay with you. Open-source libraries inside any system, ours included, stay under their own licences. This guide is general information, not legal advice: whichever developer you choose, have your own lawyer read the contract before you sign it.
Terms in this guide