Paying a software agency does not automatically make you the owner of the code. Under Indian copyright law the author is the first owner, and an outside agency is not your employee, so ownership usually passes only through a written, signed assignment that states the rights, duration and territory. Get that assignment in the contract before work starts.
This guide is general information about how software ownership works. It is not legal advice. Have a lawyer review any contract, particularly the intellectual property clauses, before you sign.
Most people assume that if they pay for software, they own it. In practice, ownership is decided by law and by the contract, not by the invoice. A surprising number of companies discover this years later, when they try to move an app to a new developer, sell the business, or raise investment, and find that they hold only a licence to use their own product. This guide explains the default position under Indian copyright law, what "owning the code" really covers, and the clauses and habits that make ownership real.
Who owns the code? Payment does not transfer ownership
Software source code is protected as a literary work under the Copyright Act, 1957. Section 17 of the Act makes the author the first owner of a work, with a few exceptions. The one that matters most for software is work made by an employee in the course of employment under a contract of service, where the employer is the first owner unless the parties agree otherwise.
A software agency or freelancer is normally engaged under a contract for services, not as your employee. So the people who write the code, or the agency that employs them, start as the owners. Commentary on Indian law notes that the Act's "commissioned work" rule for the person who pays covers specific kinds of work, such as photographs, paintings, portraits, engravings and cinematograph films, and does not list software. The practical conclusion is that ownership has to be transferred, and the transfer has to be in writing.
What "owning the code" actually includes
Ownership is wider than a copyright clause. When a founder says "we own our app", they usually mean they hold all of the following. It is worth checking each one:
- The source code in a repository you control, with the full history.
- The legal rights to it, through an assignment or an equivalent licence.
- The cloud accounts it runs on (hosting, databases, storage, email), registered in your company's name.
- The domain names and DNS accounts.
- The app store accounts, such as Apple and Google developer accounts, under your organisation.
- Design files and assets, including source files and brand assets, not only exported images.
- Documentation and credentials: architecture notes, setup instructions, API keys, signing keys and deployment scripts.
- Third-party licences the product depends on, which should be in your name or transferable.
A contract that assigns copyright but leaves your production database in the agency's cloud account is only half a handover.
What Indian law says about assigning copyright
Section 19 of the Copyright Act sets out the rules for a valid assignment. Reading the text of Section 19 alongside commentary, the key points are:
- It must be in writing and signed by the assignor, or by their authorised agent. An email promise or a verbal understanding is not enough.
- It should identify the work and state the rights assigned, the duration and the territorial extent.
- If the duration is not stated, the law treats it as five years from the date of the assignment.
- If the territory is not stated, it is presumed to extend only within India.
These defaults matter. In the Delhi High Court case summarised by Khurana and Khurana, a software assignment that said nothing about period or territory was treated as lasting five years and applying within India. Whether the defaults apply to a particular assignment can depend on its wording and facts, which is exactly why a lawyer should draft or review yours. The sensible lesson for a client is simple: never leave duration and territory silent. Ask for rights that are perpetual and worldwide.
Commentary such as the SpicyIP analysis of software copyright and commissioned works covers the same ground from the commissioning party's side.
Assignment or licence: the difference that decides everything
Contracts often use the word "licence" where the client believes they are getting ownership. The two are very different.
| Option | What you get | Watch out for |
|---|---|---|
| Assignment of copyright | You become the owner and can modify, sell or hand the code to anyone | Must be written, signed, and state rights, duration and territory |
| Exclusive licence | Only you may use the code, but the agency still owns it | Often limited by time, field or territory; may not allow transfer |
| Non-exclusive licence | You may use the code; the agency can reuse and license it to others | Weakest position; the agency can build the same thing for a competitor |
If ownership matters to your business, ask for an assignment of all deliverables, with rights that are perpetual and worldwide, and treat any licence as a fallback only for specific components.
Open-source and third-party components
No agency can assign rights it does not hold. Modern software is mostly assembled from components written by others, and the agency can only pass on what it is licensed to pass on.
- Open-source libraries come with their own licences. Permissive licences such as MIT and Apache 2.0 are generally easy to live with. "Copyleft" licences, such as the GPL family, can impose conditions on how your own code is distributed, so ask which licences are used and why.
- Proprietary SDKs and services (payments, maps, analytics, AI APIs) are licensed to whoever signs up for them. Make sure the accounts and keys are yours.
- Fonts, stock images and icons have licences too, and some are tied to the person who bought them.
A reasonable request is a list of third-party components and their licences (sometimes called a software bill of materials), delivered with the code.
Pre-existing tools and reusable code
Agencies often bring their own libraries, starter kits and internal frameworks. They will usually refuse to assign these, since they use them for every client, and that is a fair position. The usual compromise has two parts: the agency keeps ownership of its pre-existing "background" tools, and grants you a perpetual, irrevocable, worldwide licence to use, modify and maintain them as part of your product. Make sure the contract lists these tools by name or category, so you know exactly what you are licensing rather than owning.
Clauses to look for in the contract
When you read a software development agreement, look for language that does the following:
- Assigns all intellectual property in the deliverables to you, using clear words of present assignment.
- States the rights, duration and territory (perpetual, worldwide), rather than leaving defaults to apply.
- Says when ownership passes. Some contracts transfer ownership only after final payment. That can be reasonable, but check that you receive a licence to use the work in the meantime.
- Requires delivery of source code at agreed milestones, not only at the end.
- Includes a warranty of originality, meaning the agency promises it has not copied code it has no right to use.
- Gives an indemnity if the work infringes someone else's rights.
- Covers confidentiality of your data, designs and business rules.
- Provides handover support if the relationship ends, such as documentation and a transition period.
- Names any subcontractors and requires them to sign matching assignments.
Where the work is done by individual developers, the agency needs signed assignments from its own staff and freelancers. Ask how it ensures that, because a gap upstream becomes your problem.
How to keep control during the project
Good contracts help, and good habits make them enforceable. These steps are cheap and reduce risk a great deal.
- Create the repository in your own organisation account on day one, and give the agency's developers access. The code then lives with you from the first commit.
- Register cloud, domain and app store accounts in your company's name, and add the agency as a collaborator rather than the owner.
- Take regular deliveries. Merge milestones into your repository, so you are never dependent on a single final handover.
- Keep credentials in a shared password manager you control, and rotate them at handover.
- Ask for documentation as you go. A setup guide that has been tested by someone outside the team is worth more than a long document written on the last day.
- Revoke access when a developer leaves the project, and when the project ends.
Red flags
- The contract says nothing about intellectual property.
- The agency "licenses" the finished product to you and calls that ownership.
- Source code is "available on request" or delivered only for an extra fee.
- Production systems are in the agency's own cloud account, with no plan to transfer them.
- The agency will not name third-party components or their licences.
- Ownership passes only after a payment you cannot yet calculate, such as an open-ended maintenance fee.
How Anekant Tech approaches ownership
At Anekant Tech, clients receive 100% of the source code, along with documentation and access to the infrastructure the product runs on, with no licences or lock-in. That is a business commitment you should still see written into the contract, using the clauses above. Whichever company you work with, the question to ask is the same: if we parted tomorrow, could another team pick this up? A clear software project brief makes the deliverables, and so the assignment, easier to define. If you are scoping a project and want ownership terms discussed up front, contact us or read about our custom software development and Flutter app development work.