We UC
Back to blog
·7 min read·We UC Team

The developer who built our app has left: who can take it over in the UK?

What to collect from a departed developer, how to check that the app and its accounts are really yours, and who can take over and maintain the app in the UK.

The developer who built our app has left: who can take it over in the UK?

A UK software company, a freelancer or a small agency can take over an app whose developer has left, and the first step for any of them is the same: read access to the code and to the hosting, so they can write down what is there before anyone changes it. You can usually start before you have everything, but you do need to know which accounts the app runs on and whether they are in your name. At We UC we do this with a fixed-price Rescue audit, and afterwards you can have us fix and run the app or take the written plan to someone else.

What do I need to get from the developer who is leaving?

Ask for four things, in this order: the code repository, the hosting and database accounts, the domain and email accounts, and every outside service the app talks to, such as a payment provider or a sending service for email. The repository is the folder of code the app is built from, usually kept on GitHub or a similar site. Hosting is where the running app lives, and the database is where your customers' records sit. If the developer set these up under their own login, you want each one moved to an account you own or at least shared with you as an owner, because an account that only they can open is the single thing most likely to stall a handover.

Then ask for the part that is easy to forget, the secret keys. An app that takes payments or sends email usually holds passwords for those services in a settings file or in the hosting dashboard, and a new developer cannot run the app without them. Ask the person leaving to list where each one lives rather than to send them in a message.

Who owns the code if the developer built it for me?

You own the code only if ownership was agreed in writing, and you may not own it just because you paid for it. The UK government's guide to protecting your creative work says that a person commissioned to create a work will usually own the copyright unless the contract says otherwise, so the developer can be the first owner of what they wrote for you. Under section 90(3) of the Copyright, Designs and Patents Act 1988, "an assignment of copyright is not effective unless it is in writing signed by or on behalf of the assignor". If you have a contract, look for a sentence that says the code belongs to you. If you don't, a short signed assignment from the developer is worth asking for before they leave, while the relationship is still friendly. We aren't lawyers, so for an app the business depends on, have a solicitor read what you have.

Can a new developer take over an app built with AI tools?

Yes, and the fact that it was built with Lovable, Bolt, Cursor, Replit or Claude changes what the reviewer looks at, not whether they can help. You got something working in front of real users, which is further than most ideas get. Someone taking over an AI-built app will usually look at how customers are kept apart from each other's data, where the payment checks happen, whether the keys are stored safely, and whether the code is organised so that one change doesn't break another part. Our piece on how to tell whether a vibe-coded app is secure goes through five of those checks in plain words.

What happens during a takeover audit?

During a takeover audit the new team reads the code and the hosting, changes nothing, and gives you a written report with a priced plan. That is how our Rescue audit works: we need read access to the code and hosting, we change nothing while we look, and you get a report covering security, data, hosting, code, payments, integrations and running costs, followed by a walkthrough call. The fee is £2,500 + VAT, fixed, and it is deducted from the first phase if you go ahead with us on the fix. The report is yours either way, so you can use it to brief a freelancer or another team. The reasoning behind that price is in our article on what a code audit costs for an AI-built app.

Who can maintain the app afterwards?

Maintenance can come from the same people who audited it, from a freelancer working from the written plan, or from a team on a monthly retainer, and which of these suits you depends on how much money passes through the app. For a small internal tool, a freelancer on call may be enough. For an app that customers pay through, the risk we would weigh is that it again depends on one person, so a named team with documentation and a second engineer on each change is the safer arrangement. Our piece on choosing a freelancer or an agency sets out five questions to put to either.

At We UC, Run is the ongoing option: monitoring, security updates, fixes and small changes from a named team on a monthly retainer, for software we built or rescued. We don't publish a Run price, so you would ask us for one. Our main engineering team is in Southampton, with some engineers offshore in Ukraine and Eastern Europe, and an engineer reviews every change before it ships.

What should I do this week if the developer is already gone?

Make a list of every account the app touches and note who can sign in to each one today. Start with the hosting, the database, the repository, the domain name, and the payment provider, since those are the ones you cannot work around. If one is held only by the developer, ask them to add you as an owner, and if they can't be reached, the provider's own account recovery process is the usual route, which is slower when the account is in someone else's name. Don't ask a new developer to start fixing things before they have read access, because a change made without a written picture of the app is where a working but fragile system most often stops working.

Common questions

Can someone take over my app without the original developer's help?

Often yes, provided you control the accounts it runs on. A new team can read the code and the hosting without the original developer, but a developer's notes on why things were built a certain way save time, so ask for a short call or a written handover if they are willing.

Do I have to rebuild the app if the developer has left?

No. Whether to fix or rebuild is a separate decision that a written audit settles, and usually a lot more can be kept than people fear. Our article on whether to fix or rebuild a vibe-coded app covers how to decide.

How long does a takeover take?

We can't give you a figure that holds for every app, because it depends on how large the app is and how many of the accounts you can already reach. Tell us what you have and we'll agree the scope with you before the audit starts.

Does We UC maintain apps it didn't build?

We maintain software we built or rescued, so the usual route is the Rescue audit first, then a fix, then Run if you want ongoing care.

If the person who built your app has gone and real customers or payments depend on it, you can book a Rescue audit, or tell us what you have and we'll say whether an audit is the right first step.