
Quick answer
Who owns the source code of custom software built for my business?
Who owns the source code of custom software depends on your written agreement with the developer. Paying for the work does not always mean you own the code. Ask for a clause that transfers code ownership to you after payment, and make sure you receive the full code, database, logins and documents at handover.
Key takeaways
- Paying for software does not always mean you own the code.
- Write code ownership clearly in the agreement.
- Ask for code, database, logins and documents at handover.
- Keep domain, hosting and app store accounts in your name.
- Ready-made parts and open-source tools have their own licences.
- Clear ownership protects you if you change vendors later.
Who owns the source code of custom software you pay for?
The owner of the source code is whoever your written agreement says it is. If the agreement is silent or unclear, there can be confusion and disputes later, so the safe step is to write it down before work starts.
Many business owners in Mohali and the Tricity hire a company, pay in parts and get a working app or web portal. Everything seems fine. Then one day they want to change vendors or add a feature, and they find they do not have the code. Sometimes they do not even have the server login.
This happens more often than it should. It is not always bad intent. Often, nobody talked about ownership at the start. This guide helps you avoid that gap.
Why does source code ownership matter for a small business?
Source code ownership decides whether you are free to fix, grow or move your software later. Without it, you depend on one vendor for every small change.
- You can hire a new team if the first one becomes slow or closes.
- You can add features as your business grows, without starting again.
- You can move the software to a new server or cloud provider.
- You can show the software as a business asset to investors or buyers.
- You can fix urgent problems even if the old vendor is not available.
Think of a Mohali clinic with a custom booking system. If the vendor stops replying, the clinic cannot add a new doctor or fix a broken payment link without the code. With the code and logins, another team can step in quickly.
When we take on software development in Mohali, we treat ownership as part of the plan, not an afterthought.
What are the common ownership models in software projects?
There are three common models: full transfer to the client, a licence to use, and a shared model where the vendor keeps reusable parts. Each one suits a different kind of project.
| Model | What it means | Good for | Watch out for |
|---|---|---|---|
| Full transfer | You own the custom code once you pay as agreed | Custom software made only for your business | Make sure payment terms and handover are clear |
| Licence to use | Vendor owns the code; you pay to use it | Ready-made or white-label software | You may not be able to change or move it |
| Shared or mixed | You own your custom parts; vendor keeps its reusable modules and gives you a licence for them | Projects built on a vendor's base framework | Check the licence is permanent and covers future changes |
| SaaS subscription | You use software online; you own your data, not the code | Standard tools like accounting or email | Make sure you can export your data at any time |
None of these is wrong. A licence can be fine for ready-made tools. But if you are paying for software built around your own process, full transfer of the custom code is usually what you want.
If you are building a product to sell to others, read our page on SaaS development, because ownership matters even more there.
What should the agreement say about code ownership?
The agreement should clearly say who owns the custom code, when ownership moves to you, and what is delivered at handover. Simple, specific words work better than vague promises.
Clauses to look for
- Ownership of all custom code, designs and database structure moves to the client after the agreed payment.
- A list of what is delivered: source code, database, documents, logins and build files.
- Which parts are third-party or open-source, and under which licences.
- Whether the vendor can reuse your custom code for other clients.
- A confidentiality clause covering your business data and ideas.
- What happens to code and data if the contract ends early.
- Who owns the domain, hosting, app store and cloud accounts.
If the agreement only says "the client gets the software", ask for clearer words. Getting software to use is not the same as owning its code.
Unsure what to ask? Our technology consulting team can go through a vendor proposal with you and point out gaps in plain language.
Need help with your project?
Talk to the SI Company Mohali team. Free first call, simple advice, clear quote.
What should you receive at software handover?
At handover you should receive the full source code, the database, all logins, setup notes and basic documents. Ask for this in writing, and check it before the final payment is closed.
| Item | Why you need it |
|---|---|
| Full source code in a code repository | So any developer can read, fix and change the software |
| Database and its structure | Your records live here; without it, the code is not enough |
| Server and hosting logins | So you can move, renew or check the server |
| Domain account access | So your website or app address stays under your control |
| App store accounts | So your mobile app stays live under your business name |
| Third-party keys | For services like UPI payment gateway, SMS or WhatsApp API |
| Setup and deployment notes | So a new team can install and run the software |
| User and admin guides | So staff can learn and train new joiners |
A quick handover test
Ask a second developer, even a freelancer, to look at the code for an hour. Can they understand how to run it? If yes, the handover is in good shape. If not, ask the vendor for missing notes before you close the project.
For mobile apps, it matters a lot whose name the app is listed under. For mobile app development, we advise that apps are listed in the client's own developer account.
What about ready-made parts and open-source code?
Most custom software uses some open-source libraries or paid third-party tools. You can use these, but you do not own them. They come with their own licence rules.
This is normal and saves time and cost. No team writes every line from zero. A login system, a chart library or a PDF tool may come from open-source projects that thousands of developers use.
Why ready-made parts help
- Faster delivery for common features
- Tested by many users
- Lower build cost for standard parts
What to check
- Some licences have conditions on sharing changes
- Paid tools may need yearly renewal in your name
- Very old or unsupported libraries can cause security issues
Ask your vendor for a simple list of main third-party parts and their licences. A good vendor will share this without fuss.
How do you avoid vendor lock-in?
You avoid vendor lock-in by keeping key accounts in your own name, getting regular code copies, and making sure the software uses common, well-known technology.
- 1
Register accounts yourself
Buy the domain, hosting or cloud account and app store accounts in your business name. Give the vendor access, not ownership.
- 2
Ask for code access during the project
Keep the code in a repository you can see, or ask for a copy at each milestone, not only at the end.
- 3
Prefer common technology
Software built on widely used languages and frameworks is easier for a new team to pick up.
- 4
Get basic documents
Ask for setup notes and a short guide to how the system is built.
- 5
Keep your data exportable
Make sure you can download your customer, sales and stock data in a common format like Excel or CSV.
- 6
Plan support separately
Sign a support plan if you want, but keep it separate from ownership. You should be free to choose support from anyone.
Good cloud solutions are set up so the account belongs to you, with the vendor added as a user. That one step removes a lot of risk.
Does code ownership affect the cost of a project?
Ownership terms can affect the quote. Software built fully for you and handed over with full rights is different from licensing a vendor's ready-made product.
We do not list prices here. You get a clear quote after a free call. These factors usually shape it:
- Whether the software is fully custom or built on a vendor's existing product.
- Whether the vendor can reuse parts of the work for others.
- The level of documents and handover support you need.
- Paid third-party tools that must be licensed in your name.
- Support and upkeep after launch.
Our page on software development cost in Mohali explains more of what decides a quote.
Which questions should you ask a software company before signing?
Ask direct questions about ownership, handover and accounts before you sign. A clear vendor will answer them easily and put the answers in writing.
- Will I own the full custom source code after payment?
- Which parts are your own reusable modules, and what licence do I get for them?
- Will you share the code during the project or only at the end?
- In whose name will the domain, server and app store accounts be?
- What exactly will I receive at handover?
- Can I hire another team later to work on this code?
- How can I export all my data if I stop using the software?
At SI Company Mohali, powered by Shivah Web Tech, we talk about ownership, handover and accounts on the first call, and write the terms into the agreement. Our in-house team works from Mohali, Monday to Friday, 9:30 to 6:30 IST. We serve businesses in Mohali, Kharar, Zirakpur and Chandigarh. If you run a business there, see our note on software for Zirakpur businesses. To discuss your project, contact us for a free call.
Frequently Asked Questions
If I paid for my software, do I automatically own the source code?
Not always. Ownership depends on what your written agreement says. Some agreements give you only the right to use the software, while the vendor keeps the code. To be safe, ask for a clause that clearly moves ownership of the custom code to you after the agreed payment. Ask a lawyer to check the wording if you are unsure.
How do I get the source code from my old developer?
First, check your agreement for any handover or ownership clause. Then ask the developer in writing for the full code, database, logins and setup notes. Keep the request polite and specific. If they built it on accounts in their name, ask them to transfer those accounts to your business. If there is a dispute, take legal advice.
Can a software company reuse my code for other clients?
It depends on your agreement. Many vendors reuse general building blocks, such as login screens or report tools, across projects. That is normal. But your business logic, data and special features should stay yours. Write in the contract which parts the vendor may reuse and which parts belong only to you.
Do I own my data if I use SaaS software?
With most SaaS tools, you own your business data but not the software code. The key point is whether you can export your data easily, in a common format like Excel or CSV. Before you sign up, check the export option and what happens to your data if you stop paying or close the account.
Whose name should my domain and hosting be in?
Your domain, hosting, cloud and app store accounts should be in your business name. You can then add the developer as a user with the access they need. This way, if you change vendors, you keep control of your website, app and data without needing anyone to transfer accounts back to you.
What is source code escrow, and do small businesses need it?
Source code escrow means a neutral third party holds a copy of the code and gives it to you if the vendor closes or fails to support the software. It is more common in large deals with licensed software. Most small businesses with custom software can simply ask for regular code copies and full handover instead.
How does SI Company Mohali handle source code ownership?
We discuss ownership on the first call and write it clearly into the agreement before any work starts. The agreement lists what you will receive at handover, such as code, database, logins and setup notes. If any part uses a licensed third-party tool, we tell you upfront. You can ask any question about these terms before you sign.


