Who Owns Your Custom Software and Source Code?

Who Owns Your Custom Software and Source Code?

If you pay for custom software, you should own it, but that only happens if your agreement says so and you actually receive the code, database and account access. Many businesses discover too late that their developer holds the source code, app store accounts or hosting, leaving them unable to change supplier or even keep the system running.

What you should own

  • Source code for the app, website and admin system, ideally in a repository with its history.
  • The database and all your data.
  • Hosting and server accounts, in your business’s name.
  • Domain names.
  • Apple and Google developer accounts for any mobile apps.
  • Third-party service accounts, such as email, SMS, maps and payments.
  • Designs and documentation.

What you might not own

Some parts belong to others and are licensed rather than owned: frameworks, plugins, paid components and software-as-a-service tools. That is normal. What matters is knowing which these are, what they cost and whether they can be transferred.

Why ownership matters

  • You can switch developers if you need to.
  • You are protected if your developer stops trading.
  • Your apps stay in the stores under your name.
  • You control your customer data.
  • The software adds value to your business if you sell it.

What to check before you sign

  1. Does the contract transfer ownership of the code to you on payment?
  2. Will you receive the source code and database at handover?
  3. Whose name will the hosting, domain and app store accounts be in?
  4. Which third-party components are licensed, and at what cost?
  5. Is there documentation another developer could use?

Our approach

When we complete a project, clients receive the software, source code, database code and everything involved in the build, and are free to use another developer for future work. That applies to every project, from staff systems like Force One and Terry’s Fire Survey System to customer apps like EZE Shoring, Spa Specials and MySpec.

If you do not have your code

Ask your developer for it in writing, check your contract and seek advice if needed. If the code cannot be recovered, the system may need to be rebuilt. See supporting software when the original developer has left.

A handover checklist

  • Source code repository access.
  • Database copy and backup access.
  • Hosting and domain logins in your name.
  • App store accounts in your name.
  • List of third-party services and costs.
  • Setup and deployment notes.

Keep these details somewhere safe that more than one person in your business can access.

How we work

We start by talking through how your business works today, then agree the scope, cost and timing in a written proposal. Before development, we design the screens so you can see how the system will work and suggest changes. We build in phases, handing over working sections for you to test, and at completion you receive the software, source code and database, with a month of support.

Common questions

Can we ask for ownership after the project?

You can ask, but it is much easier to agree before work starts.

Does paying for software mean I own it?

Not automatically. Ownership depends on the agreement, so check it before work starts.

Can a developer keep the app store account?

They can if it was set up in their name. Ask for it to be in your business’s name from the start.

What format should the code be handed over in?

Ideally a code repository, such as GitHub, with the full history and setup notes.

Next step

If you are unsure who owns your software, book a free 15-minute software review.

Want to discuss your business requirements with Digital Solutions?

Contact Us