Who owns the code of my app? Why it matters even if you never write code

What owning your app’s code means, how it protects you if a tool shuts down or you hire a developer, and what to ask before you start.

The Deployflix team

·

Own your app's code: cover of the Deployflix blog post

‘Who owns the code of my app?’ is a question most people ask too late: after a tool raises its prices, an agency stops answering the phone, or a developer says ‘send me the code’ and there is nothing to send. The short answer is that you should own it, and you can, even if you never read or write a line of it.

Owning your app’s code means the files that make up the app sit in a repository in your own account, usually on GitHub, in your name or your business’s name, with a full history of every change. If the tool or the people who built the app disappear tomorrow, you still have everything another developer needs to keep it running and change it.

What does owning your app’s code actually mean?

Every app is a set of text files: its screens, its rules, the shape of its data. Whoever controls where those files live controls the app’s future. Owning them comes down to three things.

A repository in your own account. A repository, or ‘repo’, is a folder for one project that remembers every change made to it. Yours should sit in a GitHub account or organisation that you opened, with your email and your password. A repository in the builder’s or agency’s account, with you ‘added’ to it, is theirs, not yours.

Every change as a pull request. A pull request is a proposed change you can see before it becomes part of the app: which files changed, what was added and removed, and a note saying why. You don’t have to understand every line. What matters is that changes arrive in your repository, where they are recorded, rather than happening somewhere you can’t see.

Versions you can go back to. Every accepted change is kept in the history, so the app as it was last Tuesday is still there. If a change breaks something, the earlier version can be brought back.

Notice the difference between access and ownership. Logging in to a dashboard to look at your app is access. Having the files in an account you control is ownership.

Who holds the legal rights to the code is a separate question, decided by your contract or the tool’s terms of service. Read them, and for a business, check with your lawyer. This article is about the practical side: having the code where you can reach it.

Why does code ownership matter if you don’t write code?

You may never open the repository yourself. Owning it is still worth it, for the same reason you keep the papers for your shop.

If the tool or the agency shuts down

Software companies close, get bought or drop a product. Small agencies lose the one developer who knew your project. If your app’s code lives only in their systems, your app can go with them. If it lives in your repository, no change in someone else’s business can delete it.

If you want a developer later

One day you may want a freelancer to add a feature, connect your accounting software, or look over the app’s security. The first thing any developer asks for is the code. With a repository in your account, you invite them as a collaborator in a few clicks and remove them when the work is done. Without one, they start from nothing and you pay for the app twice.

If the price or the terms change

When your app can only live in one place, you accept whatever that place decides next year. Owning the code doesn’t mean you will move. It means you could.

What happens to your app if a tool shuts down?

It depends on where three things live: the code, the data, and the accounts the app runs on. Here is the difference that owning the code makes.

SituationCode only inside a platformCode in your own repository
The tool shuts down, or you leave itThe app may stop, and rebuilding starts from scratchA developer can take the code and set the app up elsewhere
You hire a developerThey can work only inside that platform, if at allYou invite them to the repository and they see the full history
A change breaks somethingYou rely on the platform’s own undo, if it has oneEvery earlier version is in the history and can be restored

One honest caveat: code in a repository is not a running app. If the service that hosted your app closes, someone still has to put the app on a server, connect its database and point your domain at it. That is ordinary work for a developer, and far smaller than starting again, but plan for it.

The same applies to everything else the app depends on. Keep your domain name in your business’s name, with a login you hold. Make sure you can export your data: customers, orders, records. Keep any Google Play and App Store developer accounts in your own name, and open your payment gateway account in your business’s name, so payments reach your bank directly.

GitHub for non-developers: what you need to know

GitHub is a service that stores code and its history, and it is where most developers will expect to find yours. To use it as an owner you need an account, a few words of vocabulary and a sensible setup, not programming.

Opening an account is free. GitHub’s own documentation says its free plan for personal accounts includes unlimited public and private repositories, so keeping your app’s code there need not cost anything. Choose private for your app, so only the people you invite can see it.

The words you will meet: a repository is the project folder with its history. A commit is one saved change, with a note and a date. A pull request is a proposed change waiting to be accepted; once accepted, it is merged into the app. A collaborator is someone you have invited to work on a repository, and you can remove them at any time.

Set it up once, properly. Open the account with a business email address you will keep, not a staff member’s personal one, and turn on two-factor sign-in. If more than one person runs the business, create a GitHub organisation so the repositories belong to the business, and give a second person you trust owner access, so you are never locked out.

What should you ask a builder or agency before you start?

Ask these before you pay anything or approve any work, and get the answers in writing.

  1. Where will the code live: in a repository in my own GitHub account from the first day, or only on your systems?
  2. Will every change reach me as a pull request I can see?
  3. Can I go back to an earlier version if something breaks?
  4. If I stop working with you, what exactly do I get: the code, the database contents, the images and files?
  5. Who holds the rights to the code under the contract or terms? (Have your lawyer read this part.)
  6. Whose name are the domain, hosting, app store accounts and payment gateway in?
  7. Could another developer work on the app later without your help?

Good answers are short and specific: ‘It’s in your GitHub from day one, and here is how you will see each change.’ Vague answers, such as ‘we take care of all that’, deserve a follow-up question. With an agency it is fair to agree that the code moves to your repository as each invoice is paid, as long as it is written down.

Our own answers, since we are asked too: with Deployflix you connect your own GitHub and the code lives in your own private repository, every change arrives as a pull request you can read, and every version is kept. You don’t need GitHub to start, only when you want the code in your own repository. See our integrations page and security page.

How can you check that you own your app’s code today?

If you already have an app, this takes a few minutes. Ask whoever built it for the repository’s link. The address shows whose account it is in: github.com, then the account name, then the project. If that name is the agency’s or the tool’s, ask for the repository to be transferred to your account; GitHub lets a repository’s owner transfer it.

Next, open the history. The latest changes should be there: a repository last updated a year ago, for an app that changed last week, is an old copy. Check that your role is owner, not just collaborator. Then go through the rest: the domain, a data export, the store accounts and the payment gateway. Fix whatever is not in your name now, while everyone is still friendly.

If you are starting a new app, make ownership part of the plan from day one. A founder building a startup’s first web app and a firm building a client portal for an accountancy or law practice need the same thing: code somewhere they control. A team should keep it in the organisation’s GitHub, not one employee’s; see Deployflix for teams. And to see the whole path from description to finished app, read how Deployflix works.

Questions

Do I need to know how to code to own my app’s code?

No. Owning the code means the files sit in a repository in your account. You need a GitHub account and a little vocabulary, not programming skills. A developer can read the code whenever you need one.

Is it safe to keep my app’s code on GitHub?

Keep the repository private so only people you invite can see it, turn on two-factor sign-in, and remove collaborators when their work is done. Passwords and payment keys should never be written into the code; ask whoever builds the app how they are kept.

Can a developer take over an app made with an AI app builder?

If the code is in your own repository, yes: it is ordinary code, and a developer can work on it like any other project. They may need to set up hosting and the database if the app moves away from the tool that runs it.

Who owns the code an agency or freelancer writes for me?

It depends on your contract. Some contracts give you the rights on payment, some keep them with the agency. Ask for the terms in writing before work starts, and have your lawyer check them.

Describe your app

Write what you need in your own words. Deployflix writes a one-page plan with its cost, and builds only after you approve it.