Lorixen.
EN

Who controls your app's code? Repos, accounts and access

Short answer: Whatever your contract says about ownership, in practice you control your app only if the accounts that hold it are in your business's name: the code repository, the hosting or cloud account, the domain, the app store developer accounts, and the keys for every service it talks to. Put the code in a GitHub or GitLab organisation your business owns, with your developer added as a member, and get the build instructions written down. Check it now, while the relationship is good, not on the day you need to change developers.

Contracts decide who legally owns the code, and that's a question for your agreement and your adviser. This article is about the practical side, which causes far more trouble: plenty of businesses that technically own their app couldn't get a working copy of it tomorrow if their developer disappeared.

Why this goes wrong

It usually starts innocently. The developer sets up the repository in their own account because it's quicker. The hosting is on their card "for now". The domain was registered by a previous agency. The app store account is in a freelancer's name. Years later, the business wants to change developers or add a second one and discovers it holds the website address and nothing else.

None of that requires bad intent. It just requires nobody asking.

The access checklist

Work through each item and note who holds it, in whose name, and whether you can log in yourself.

1. Code repository

  • [ ] The code lives in a repository owned by your business's organisation, not the developer's personal account.
  • [ ] At least one person from your business is an owner of that organisation (not just a member).
  • [ ] Your developer has access as a member or outside collaborator, with the permissions they need.
  • [ ] All the code is there: website, app, back end, any scripts or infrastructure files.

GitHub describes organisations as shared accounts where businesses collaborate across projects, with security and administrative features; each person still signs in with their own personal account. GitHub notes organisations can be used for free with GitHub Free, with limited features on private repositories, and paid plans add more. GitLab offers the same idea with groups, and its project docs explain how to transfer a project into a different group.

If the code is currently in a developer's personal account, it can be moved. GitHub's transfer guide covers the details:

  • The person transferring needs admin access, and to transfer into an organisation they need permission to create repositories there.
  • Issues, pull requests, wiki, stars and watchers move with it, and Git history including contributions is preserved.
  • Links to the old location redirect automatically, though GitHub recommends updating local clones.
  • The original owner is added as a collaborator after the transfer, so remove or adjust their access afterwards if that's intended.
  • Webhooks, services, secrets and deploy keys remain associated after the transfer. That's convenient, but it also means you should review them (see item 5).
  • Moving a private repository to a free account can lose features such as protected branches.

2. Hosting and cloud accounts

  • [ ] The hosting, server or cloud account is in your business's name, billed to your business.
  • [ ] You have your own admin login (not a shared password).
  • [ ] The developer has their own user with appropriate permissions, which you can remove.
  • [ ] You know where backups are stored and who can restore them.

Most hosting and cloud providers let an account owner invite other users with limited roles. That's what you want: you own the account, the developer works inside it.

3. Domain and DNS

  • [ ] The domain is registered to your business, with your email as the contact.
  • [ ] You can log in to the registrar.
  • [ ] You know where DNS is managed (sometimes not at the registrar) and can log in there too.
  • [ ] Auto-renew is on, with a current card.

A lost domain takes your website and email with it, so this one matters even if nothing else on the list does.

4. App store accounts

  • [ ] Your app is published under developer accounts in your business's name on Apple and Google.
  • [ ] You hold the owner role; the developer has a team role.

If an existing app sits in someone else's developer account, moving it between accounts is its own process in each store.

5. Keys, secrets and third-party services

Apps talk to payment providers, email services, maps, analytics, AI APIs and more. Each has an account and keys.

  • [ ] Each service account is in your business's name, or you know whose it is.
  • [ ] You have a list of every external service the app uses.
  • [ ] Keys are stored in a password manager or secrets store you control, not only in the developer's head or laptop.
  • [ ] After any change of developer, keys are rotated so old ones stop working.

6. Documentation and build instructions

Code you can't build is close to useless. Ask for a short document covering:

  • [ ] How to run the project locally and what software versions it needs.
  • [ ] How to deploy a new version (step by step, or the automated pipeline).
  • [ ] Environment settings needed (names, not secret values).
  • [ ] How the app store builds are produced and signed.
  • [ ] Known quirks and anything unusual.

A good test: could a new developer get the project running from this document in a day?

7. Data

  • [ ] You know where customer data lives and can export it.
  • [ ] Database backups exist, and you've seen one restored at least once.

How to raise it with your developer

Most developers are happy to set things up properly; many prefer it, because it makes their role clear. A simple message works: "We'd like all accounts for the app in the business's name, with you added as a user. Could we move the repository into our organisation and put together a short handover doc?" Offer to pay for the time; it's real work.

If you're starting a new project, put it in the brief from day one: business-owned organisation, business-owned hosting, developer added as a user.

A hypothetical example

A Brisbane café chain has a loyalty app built by a freelancer. On review, they find the code in the freelancer's personal GitHub account, hosting on the freelancer's card, the domain in the café's name, and the Google Play account in the café's name but the Apple account in the freelancer's. The fix takes an afternoon: the café creates a GitHub organisation, the freelancer transfers the repository, the hosting is moved to a new account billed to the café, keys are rotated, and the Apple app transfer is started as a separate process.

FAQ

If I paid for the app, don't I own the code?

Your agreement decides that. Practically, though, you need access to the accounts and files to use that ownership.

Is a zip file of the code enough?

It's better than nothing, but it goes stale with every change. A repository in your organisation always has the latest version and its history.

Will moving the repository break anything?

GitHub redirects links and Git commands to the new location, and connected services like webhooks stay associated. Test deployments afterwards and update any local copies.

What if my developer refuses?

Start with the items in your name already (domain, app store accounts), document what's missing, and raise it in writing. Most stand-offs are avoided by asking early.

When you're not sure who holds the keys to your app, we can audit the accounts with you and plan a clean handover.

Sources

WhatsAppLet’s talk