My developer left and I cannot get the code. What now?

By Ranjit Bhinge, founder of Blur Studio · Updated · 10 min read

Short answer: Start with access, not code quality. In the first 48 hours, list every account the app depends on (code storage, hosting, database, domain, payments, email, app stores), find out whether each one is in your name or the developer's, and move or secure each one. Only after that should you pay for an audit and choose between fixing what exists and rebuilding. Many abandoned projects can be recovered, and a lot of avoidable damage comes from panic changes made before anyone knows what is where.

Ranjit Bhinge

Your developer has gone quiet or gone for good, and you need to know what you still control and what to do before anything else breaks.

I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.

If your developer left and you cannot reach the code, take a breath. This is a common situation, it is often fixable, and the order you do things in matters more than how fast you do them. The order is: secure access, make a copy of everything, audit, then decide. This guide walks you through each step in plain words. It is practical information, not legal advice. If there is a dispute about money or ownership, talk to a lawyer.

The first 48 hours: find out what you control

Do not start by hiring someone to "look at the code". Start with a list. An app is rarely one thing. It is usually several separate services stitched together (the table below lists eight common ones), and the developer may have set up each one under their own login. Write down each row below and mark who owns the account: you, the developer, or you do not know.

What it isPlain meaningWhere to look
Code storageWhere the source code and its history live. Often GitHub, a website that stores code and tracks every change made to it.Ask: is there a repository, and whose account is it under?
HostingThe service that runs the app on the internet, such as Vercel, Netlify, Render (companies that run websites and apps for a monthly fee) or a cloud server (a rented computer in a data centre).Look at your card statements and email receipts for the company name.
DatabaseWhere your customers, orders and files are stored. Often Supabase, a hosted database and login service.Receipts, or the settings in the hosting account.
DomainYour web address, held by a registrar.Look the domain up in a public WHOIS lookup (a free search of who registered a web address) to see the registrar.
PaymentsStripe or PayPal, services that take card payments and pay the money out to a bank account.Your own bank deposits show where money lands.
Email and notificationsThe service that sends receipts and password resets.Check the sender address in an email the app sent you.
App storesApple and Google developer accounts, if there is a phone app.The "seller" name shown on the store listing.
Other keysMaps, AI, SMS and analytics services the app calls.Ask the developer, or find them in the hosting settings.

The one that matters most is who owns each account. If the account is in your company's name and you hold the login, you are in good shape. If it is in the developer's name, that is not a disaster, but you need to move it. The next section covers how. My guide on how to check who owns your website code and get access goes deeper on the website version of this.

Step by step: secure access without breaking anything

  1. Send one calm, written message to the developer. Ask for: repository access, hosting and database logins or an ownership transfer, domain registrar details, all third-party keys, and a list of anything running on their personal accounts. Keep it short and put a date on it. Even if they never reply, you now have a record.
  2. Do not delete, cancel or reset anything yet. Cancelling a hosting plan or a database project can erase data, so check what the provider deletes before you cancel. Stopping payment to a service you do not understand is a quick way to turn a stalled project into a lost one.
  3. Get a copy of the code. If you have a way in, download it. If the code is on GitHub under the developer's account, ask them to add you as an owner, or to transfer it. GitHub's own documentation says that when a repository is transferred, the new owner can administer its contents, issues, settings and more straight away, and the old owner is kept on as a collaborator. If it is under a GitHub organization (a shared company account), the documented route is to add the new person as an owner, update the billing details, and only then have the old owner remove themselves.
  4. Move hosting and the database into accounts you own. Most services support this. Vercel documents moving a project between teams, and says the project's domains, aliases and environment variables (the stored settings and secret keys the app needs) come along and are listed before you confirm. Supabase documents moving a project to another organization and notes you must be at least a member of the target organization. Apple documents app transfer between App Store Connect accounts, and says the app keeps its reviews, ratings and bundle ID (its permanent technical name) while it stays on the store. Check each service's current page for steps, because they change.
  5. Change the passwords you do control, and switch on two-step login. The developer may still hold keys to your systems. Once you own an account, change the password, remove their access, and rotate (replace) any secret keys. Do this after you have a working copy, not before.
  6. Back up the database. Even a rough export of your customer and order data is better than nothing. If you cannot make one yourself, this is the first thing to ask a new developer to do.

If you are giving a new person temporary access, use limited roles rather than sharing your own login. My guide on giving a freelancer limited access to your website host shows how.

What if the developer will not hand over the code

This is where the contract matters. In the United States, a transfer of copyright ownership is not valid unless it is in writing and signed by the owner (17 U.S.C. section 204). That means that if you hired a contractor and nothing was signed saying the code is yours, the developer may legally hold the copyright even though you paid for the work. Rules differ by country, and the details are slippery, so ask a lawyer before you act on any of this. Our companion guide, who owns custom software code you paid for, lists the clauses to look for.

Practical routes, in the order I would try them:

  • Look for a working copy you already have access to. The live site runs somewhere. If you own the hosting account, the deployed code is in there. If the app was built with a tool like Lovable, Bolt, Replit or Cursor (AI app builders you chat with to generate apps), the project may sit in your own account on that tool, and exporting the code may be a button click.
  • Check the contract. Look for an "assignment" or "work for hire" clause, a handoff clause, and any note about final payment. If you paid in full and the contract says you own the work, send that clause to the developer in writing.
  • Ask the host or registrar. If the account is in your company's name but the login is the developer's email, ask the service's support team whether they will change the login owner if you can prove the business is yours. Policies differ, so expect to be asked for company documents and a recent invoice, and expect that some will say no.
  • Last resort: rebuild from what is visible. If the code is truly gone, you still have the live product, your database and your designs. A rebuild from a clear description is slower and costs more than a handover, but it is possible. Keep the database, because that is your real asset.

Audit the work in plain words

Once you have the code and the accounts, pay a developer for a short, fixed-scope audit before you decide anything. A few days of review is a sensible size to ask for. Ask them to report on these eight things in a form you can read:

CheckHealthy signWarning sign
Does it run from a clean start?A new developer can set it up from written steps in a day.It only works on the old developer's laptop.
Is there a test version separate from the live one?Yes, with its own database.Everything is edited live.
Who can see whose data?Each user only sees their own records.Any logged-in user can open another's data by changing a number in the address.
Where are secrets kept?In the hosting settings.Passwords and keys written into the code.
Does payment work end to end?Refunds, failed cards and plan changes tested.Only the happy path works.
Is the code readable?Clear folders and names, some notes.One giant file, copied blocks, unexplained leftovers.
Are there backups?Automatic database backups you can restore.None, or nobody has ever tried a restore.
Known security gaps?Checked against the OWASP Top 10, a widely used list of the most common web security risks.Not checked.

The audit should end with three numbers: hours to make it safe, hours to finish it, and hours to rebuild it. Without those you are guessing. If the app was made mostly with AI tools, read why AI-built apps break first, because the same eight gaps tend to show up.

Rebuild or continue: a decision rule

Here is the rule I use. It is my own judgment, not an industry law. Continue if the app runs from a clean start, the data layout makes sense, and the audit estimate to fix and finish is under about 60 percent of the rebuild estimate. Rebuild if the data layout is wrong at the root, the code cannot be set up by anyone else, or fixing costs more than about 60 percent of starting again. Above that line you are paying to keep code you will not trust. For an AI-built app, use a decision rule for rebuild or fix.

Worked example (made-up figures, for illustration only). A six-person physiotherapy clinic had a booking app that was about 70 percent done when the developer stopped replying. The audit says: 40 hours to make it safe and stable, 60 more to finish the missing screens, so 100 hours to continue. A clean rebuild of the same scope is estimated at 190 hours. The continue path is 100 of 190, or 53 percent, so the clinic continues. If the audit had said 140 hours to continue, that is 74 percent, and the clinic would rebuild, keeping the customer database and the designs. At an assumed rate of $100 an hour, the two paths cost $10,000 and $19,000. Change the rate and the sizes to match your own quotes, but the 60 percent test works at any rate.

Whichever way you go, ask for a fixed price for each phase in writing. Hourly rates with no cap are how a rescue becomes a second failed project. My custom software development cost guide explains what drives these numbers.

Getting a new developer up to speed

A new developer can start fast if you give them a single folder with these items:

  • The access list from the first step, with who owns each account.
  • The original brief, quotes, invoices and every message about scope. These show what you were promised.
  • A screen recording of the app, from sign-up to a paid order, narrated by you.
  • A list of what is broken, ordered by what costs you money first.
  • Your database export and any design files.

Ask the new developer to write a short handover note as they go: how to run the app, how it is deployed, where each secret lives. That note is your insurance against going through this again. See also how to hand your app to a developer without starting over.

Choosing who rescues it

Look for someone who asks about your accounts and data before they talk about code, offers a fixed-price audit, and is happy for you to own every account. Be careful of anyone who says "it all needs rewriting" before reading a line, wants admin access to your personal accounts, or will not put scope and price in writing. If the app came from an AI builder, read how to hire a Lovable, Bolt, Replit or Cursor developer for what to ask. Moving a half-working prototype to a safe live setup is its own skill, covered in how to move an AI-built app to production.

Stopping this happening again

  • Open every account yourself, under your company name, and invite the developer as a user. Never the other way round.
  • Put an assignment clause in the contract: all code is yours once paid, and the developer hands over the repository, accounts and a written setup note at the end.
  • Pay in stages tied to working delivery you can click through, with code handed over at each stage.
  • Have a second person, even a part-time one, who knows where the logins are.

How I'd approach this

I would not touch the code in week one. I would spend the first two days on the access list and a backup, because that is where the real risk is, and it costs almost nothing. Then I would pay for a fixed-scope audit with the three numbers and apply the 60 percent rule. Owners can lose weeks arguing about whether the old code was "bad" when the only thing blocking them is a domain login sitting in a stranger's inbox.

If you want help, Blur Studio fixes and finishes start around $1,500, with a fixed price agreed in writing before any work begins. What you pay for you own, you get the accounts and a written handover note at the end, and if the better move is to leave it alone or buy a ready-made software subscription, I will tell you that before you spend anything.

Questions people ask

How soon should I act after a developer goes quiet?

Send your written request for access the same day you start worrying, then work through the account list. Waiting for a reply for weeks is how hosting plans lapse and domains expire. Taking inventory costs you nothing and does not break anything.

Can I legally use the code if the developer left and I paid them?

It depends on your contract and your country. In the US, a transfer of copyright must be in writing and signed by the owner, so a missing clause can leave the developer holding the rights even after you paid. Read the contract, then ask a lawyer. See who owns custom software code you paid for.

What do I do if the developer holds the hosting login?

Ask them in writing to transfer it or add you as an owner. If they do not reply, contact the hosting company's support with proof the business is yours, such as company documents and invoices. Do not cancel the plan, because that can erase the app and its data.

How much does it cost to take over an unfinished project?

The audit is the smaller cost, since it is a short, fixed-scope piece of a developer's time. The fix or rebuild depends on the audit's hour estimates, so get those in writing first. My custom software development cost guide shows what drives the figure.

Should I rebuild or continue with the old code?

Continue if the code runs from a clean start and the fix estimate is under about 60 percent of a rebuild. Rebuild if the data layout is wrong at the root or nobody else can set the app up. That 60 percent line is my own rule of thumb, so test it against the quotes you get.

Does it matter if the app was built with an AI tool?

It changes where to look, not what to do. The project may sit in your own AI builder account, which makes exporting easier, but the same checks on data access, secrets and payments apply. See why AI-built apps break.

How do I stop this happening with my next developer?

Open every account in your own name and invite the developer in. Put a handover clause in the contract, pay in stages against working delivery, and ask for a short written setup note at each stage.

More in this topic: Problem solving: custom software (22 guides) →

Sources

Ready for the next step?

A 30 minute call. If you do not need me, I will tell you.

Ranjit Bhinge You talk to me, Ranjit. I reply within a few hours.

Not sure what you need? Tell me what is going on. I will point you the right way, even if it is not me.

Blur Studio · 30 minute call

Book a 30 minute call

You talk to me, Ranjit. If you do not need me, I will tell you.

  • We talk about your business and what is going on.
  • You leave with a clear next step, even if it is not me.
  • I reply to every message within a few hours.
Loading the calendar…