Developer Abandoned Project? How to Take Back Your App

By Jitendra Chavda, Co-founder · 13 November 2026

Take back access in order. Secure your domain and the email account tied to it first, because those control password resets for every other service. Then move the code repository, hosting and database under accounts you own, followed by app store listings. Leave fixing or rebuilding until a new developer can open the code and explain what it does.

Your developer stopped replying two weeks ago. The app is live, a few customers are using it, and something just broke. You open your inbox to find the login for the server and realise every account was set up under their email, not yours.

If you are searching "developer abandoned project" right now, you are in one of the most stressful places a founder can land, because the problem is not the code. It is access. We will not tell you this is quick, but it is fixable if you work through it in the right order, starting with the accounts that can lock you out for good.

What does an abandoned project usually look like?

Here is a hypothetical example, built from a pattern that is common when apps change hands. A founder hires a freelancer to build a booking app. The freelancer registers the domain, opens the hosting account and creates the GitHub repository, all under their own name, because that was faster. Payments go through on time and the app launches.

Then the freelancer takes a full-time job, or gets sick, or simply moves on. Nobody is being malicious. But the founder now owns a business running on accounts they cannot open. The renewal email for the domain goes to someone who no longer reads it.

This is predictable because, at the start, founders care about the product, not the plumbing. Account ownership feels like admin. It only becomes urgent when the person holding the keys is gone.

Do you own the code if you paid for it?

Not automatically. This section is general information, not legal advice, and the rules differ by country, so check with a lawyer where you are based. Under US law, the U.S. Copyright Office's guide to works made for hire says that ordinarily the author is the person who actually created the work.

A commissioned work only counts as made for hire if it fits one of nine listed categories and there is a written agreement, signed by all parties, that expressly says so. If any of those requirements fails, it is not a work made for hire. For most freelance software, that means you want a written, signed assignment of rights, not just an invoice marked paid.

If you have a contract, find it now and look for words like "assignment", "intellectual property" or "work made for hire". If you have nothing in writing, the cleanest fix is to ask the developer to sign a short assignment, even if they have gone quiet. A polite, specific request often gets a signature where a vague one does not.

Which accounts should you take back first?

Work in order of how badly each loss would hurt. A lost domain can take your whole business offline. A lost repository slows you down but rarely ends you.

How do you get your domain back?

Start with a lookup of your domain's registration record at its registrar, the company the domain was bought through. ICANN's guide to its transfer policy explains that only the registered name holder, the administrative contact, or someone explicitly authorised by either of them can start a transfer. If the developer is listed as the holder, you need their cooperation, so contact them before anything else.

You will also need an authorisation code, sometimes called a transfer code. ICANN says registrars either let you create it yourself or must provide it within five calendar days of your request. Watch out for the 60-day lock: you generally cannot move a domain to a new registrar within 60 days of changing its contact details, though some registrars let you opt out of this lock. Change ownership first, then plan the registrar move after the lock ends.

How do you move the code and the app store listings?

For code on GitHub, the developer needs to transfer the repository to you. A repository is the online folder that holds your app's code and its full history of changes. GitHub's documentation on transferring a repository says the person sending it must have administrator access, and that when it goes to another personal account, the new owner gets a confirmation email that expires if not accepted within one day. Be ready to click it the moment it arrives.

One detail founders miss: GitHub notes that webhooks, secrets and deploy keys stay attached after the transfer. These are the hidden links and passwords that let your code talk to servers and other services. Treat every one of them as compromised and replace them once the repository is yours.

Mobile apps are slower. Apple's app transfer overview says the current Account Holder starts the transfer and the receiving Account Holder accepts it, and the app keeps its reviews and ratings while users continue to get updates. On Android, Google Play's transfer guide says users, download statistics, ratings and reviews move with the app, but earnings and payout reports do not, so download them first. Both require a working developer account in your own name before anything can move.

Should the next developer fix the app or start again?

Decide after you have the accounts, not before. A new developer cannot judge code they cannot open, and any opinion given without access is a guess. Once everything is under your name, ask them to explain in plain English what the app does today, what is fragile and what is missing.

If the core flow works and customers use it, keeping the app and fixing it is usually the calmer path. If you cannot get the code back at all, you are rebuilding whether you like it or not, so use the time to cut scope. Our post on why most MVP feature lists are too long is a good place to start that cut.

The Uncomfortable Truth About Abandoned Projects

Most abandoned projects were set up to fail long before the developer left. The founder let someone else hold every key because it saved a day at the start. That is not a character flaw. It is a gap that nobody pointed out.

The fix is a habit, not a better freelancer. You can hire the most reliable developer in the world and still lose access if they get ill and every account sits in their inbox.

Try This: Open a spreadsheet today and list every service your app uses: domain, email, hosting, database, repository, app stores, payments, email sending, analytics. Next to each, write whose email owns it. Any row that is not yours is your first job this week.

What should you set up before you hire the next developer?

1. Accounts: create every account under a company email you control, then invite the developer as a team member.
2. Contract: include a signed clause that assigns all code and design rights to your company.
3. Passwords: store shared credentials in a password manager you own, not in chat messages.
4. Handover notes: ask for a short written guide covering how to deploy, where data lives and which keys exist.
5. Milestones: agree written scope and milestones before work starts, so progress is visible if someone leaves.

For more questions to ask before you sign, read our guide on MVP agency red flags to watch for before you sign. Bring the checklist above to that first conversation and ask each item out loud.

How We Handle Ownership at SlashEasy

SlashEasy is an AI-powered MVP development studio based in Ahmedabad, India, that builds fixed-scope MVPs, web apps and mobile apps for founders in 2–3 weeks. Our rule on ownership is simple: the client owns all code, repositories and accounts from day one. We work inside accounts you control, so there are no keys to hand back when the project ends.

Before development starts, you get written scope and milestones, and a short video demo at every milestone. At the end of our 21-day MVP framework, we deploy to your domain, walk you through the product for an hour and leave handover docs, followed by 14 days of support. If another developer joins later, the handover docs are already in your hands.

If you are stuck on an abandoned project and want to talk through the order of steps for your situation, you can Book a Free Call from our homepage. Bring your list of accounts and whose email owns each one.

The rule we hold ourselves to.

Your product, your accounts, your keys, from the first day.