aibrevoGet a quote

Question12 min read

What to Do If Your Developer Disappears

Quick answer

Secure access first: get the domain, hosting, code repository, app store and payment accounts into your company's name with you as owner or admin. Then list what you actually hold, read your contract for the IP assignment and handover terms, and send one dated written request for the code and credentials. Only after a code review decide whether to finish the project or rebuild.

Reviewed by Alpit Patel, Founder and CEO · Updated November 11, 2026

On this page 10 sections
  1. What should you do first if your developer disappears?
  2. The first 48 hours: a checklist
  3. How do you check you own each piece?
  4. How do you move your app to your own App Store or Google Play account?
  5. How do you ask for your source code in writing?
  6. What if you have no source code at all?
  7. Should you finish the project or rebuild it?
  8. How do you stop this happening again?
  9. Can we take over software another developer built?
  10. Sources

Key takeaways

  1. Work in this order: secure the accounts, find out what you actually hold, read the contract, send one written request, then decide to finish or rebuild after a code review.
  2. The accounts matter more than the code on day one. Whoever is owner of the domain registrar, cloud account, repository and app store account controls the product.
  3. Only the Apple Account Holder can start an app transfer, and on Google Play the request comes from the account that holds the app. If the app sits in your developer's own account, you need their cooperation or a legal route.
  4. In the US, code from an independent contractor is generally not a work made for hire, so your rights depend on a signed written assignment. Talk to a lawyer for any dispute; this page is general information.
  5. A shipped app binary is not source code. Without the code, the live app becomes the spec for a rebuild.

Secure access before anything else. Your domain, hosting, code repository, app store accounts and payment accounts decide who controls your product, so get each one into your company’s name with you as owner or admin. Then work out what you actually hold, read your contract, send one written request for the code and credentials, and only after a code review decide whether to finish the project or rebuild it.

Not legal advice. This page is general information, checked on Nov 11, 2026 against Apple, Google, GitHub, AWS, Stripe, ICANN and US Copyright Office pages. If you are in a dispute with a developer, or your contract is unclear, talk to a lawyer.

What should you do first if your developer disappears?

Work in this order, because each step protects the next one:

  1. Secure access. Make sure you can log in, as owner or admin, to every account the product runs on.
  2. Find out what you actually hold. Source code, credentials, designs, documentation, or only a live app.
  3. Read your contract. Look for the IP assignment, the list of deliverables, and any handover clause.
  4. Send one written request. Ask for the repository, credentials and documentation by a specific date.
  5. Decide finish or rebuild after an independent code review.

Do not start with angry messages or a new developer. A new team cannot help much until you control the accounts, and messages sent in a panic tend to make a later dispute harder.

The first 48 hours: a checklist

Go through these in order. For each one, write down the login email, who the owner or admin is, and whether the developer still has access.

  1. Domain registrar. Look up your domain in ICANN Lookup, which ICANN describes as a free tool for publicly available registration data. It shows the registrar (GoDaddy, Namecheap, Cloudflare and so on). Log in there. If you cannot, the registration may sit in the developer’s account, and your first call is to the registrar. The registrant, ICANN explains, is the person or entity who registered the domain.
  2. DNS. Check where the domain’s DNS is managed. It is often a different place, such as Cloudflare or your host. Whoever controls DNS controls where your site and email point.
  3. Hosting and cloud. AWS, Google Cloud, Azure, Vercel, Netlify, Heroku, DigitalOcean or a shared host. On AWS, the root user is the email and password that created the account, and it has complete access; account settings such as the root email can only be changed by signing in as root on a standalone account. If the account was opened with the developer’s email, that is a problem to fix now.
  4. Code repository. GitHub, GitLab or Bitbucket. Check whether you are an owner of the organization or an admin of the repository. GitHub says organization owners “have complete administrative access” and recommends no fewer than two. If you can read the code, download a full copy today.
  5. Apple App Store Connect. Check your role. Apple’s roles are Account Holder, Admin, Finance, App Manager, Developer, Marketing, Sales and Customer Support. Only the Account Holder can sign legal agreements and renew the membership, and only the Account Holder can start an app transfer. An Admin can see all apps and manage users, but is not the Account Holder.
  6. Google Play Console. The account owner is the first registered account, has full access, and is the only one who can manage the payments profile. Admins can be added with all permissions. Check which one you are, or whether you appear at all.
  7. Databases and storage. Managed databases (Amazon RDS, Supabase, Firebase, MongoDB Atlas), file storage and backups. Confirm you can reach them and that a recent backup exists.
  8. Third-party services. Stripe or other payments, email sending (SendGrid, Postmark, Mailgun), SMS (Twilio), analytics, error tracking, maps and AI APIs. On Stripe, there can only be one Account Owner, and only the owner can transfer ownership.
  9. Password managers and shared docs. 1Password, Bitwarden, a shared Google Drive or Notion page. Developers often leave credentials there.
  10. Remove their access and rotate secrets, in that order. Once you hold owner or admin rights, remove the developer’s user accounts, then change shared passwords and rotate API keys and database passwords. Rotating a key the live app depends on will break it until the new key is set in the app’s configuration, so do this with someone who can update that configuration.

How do you check you own each piece?

Asset Where it lives How to check you own it If you don’t
Domain Registrar account (find it with ICANN Lookup) You can log in and the registrant is your company Contact the registrar with proof of ownership; ask the developer to move it to your account
DNS Registrar, Cloudflare or host You can edit records Recover the account, or move DNS once you control the domain
Hosting / cloud AWS, Google Cloud, Azure, Vercel and others On AWS you hold the root user email; elsewhere you are the account or team owner Ask the developer to transfer ownership; contact the provider’s support
Source code GitHub, GitLab or Bitbucket You are an organization owner or repository admin Ask for a repository transfer; GitHub requires admin access to transfer, and old links redirect
iOS app App Store Connect You are the Account Holder of the account that lists the app The developer’s Account Holder starts an app transfer to your account
Android app Google Play Console You are the account owner of the account that lists the app The developer submits a transfer request; your account owner approves
Payments Stripe or similar You are the Account Owner Only the current owner can transfer ownership; contact the provider
Database and backups Cloud provider or managed service You can log in and download a backup Recover the account it lives in first
Email, SMS, analytics SendGrid, Twilio, Google Analytics and others You are owner or admin on each Add yourself as owner, or create new accounts and update the app’s keys

Sources: Apple App Store Connect Help, Google Play Console Help, GitHub Docs, AWS IAM User Guide, Stripe Docs, ICANN. All checked Nov 11, 2026.

How do you move your app to your own App Store or Google Play account?

Both stores let you transfer a live app between developer accounts, and in both the transfer has to start from the account that holds the app. If your developer published under their own account, you need them to cooperate.

Apple. The Account Holder of the sending account initiates the transfer and the receiving Account Holder accepts it. The sender needs your Account Holder’s Apple Account and your Team ID. The app keeps its status with “Pending App Transfer” added until you accept, or the transfer expires after 60 days. Apple’s criteria include:

  • Both accounts are not in a pending or changing state, and both have accepted the latest paid and free agreements.
  • The app has at least one version released to the App Store.
  • The app is not on pre-order, and not in statuses such as Waiting for Review, In Review or Pending Developer Release.
  • In-App Purchase product IDs do not clash with products in your account. Apple Arcade apps cannot be transferred.

Ratings and reviews stay with the app, but sales data before the transfer stays with the sender, and a few items do not move, such as an Apple Pay merchant ID. Apple also does not let an individual membership’s Account Holder role be handed to someone else, except when a minor comes of age or the Account Holder has died. In practice, for an app in a freelancer’s personal account, the app transfer is the route. An app that was never released cannot be transferred on Apple, so it is set up and submitted from your own account, usually under a new bundle ID, because the old one stays registered to the developer’s account.

Google Play. The request is submitted from the original account, both accounts must be registered and active, and you need the target account’s registration transaction ID. Your account owner then approves, and Google says support reviews requests within two business days. Users, statistics, ratings, reviews and store listing move; earnings reports, test groups and older orders do not. Opening a new account to receive the app costs $25.

Sources: Apple, Overview of app transfer, App transfer criteria, Initiate an app transfer; Google, Transfer apps to a different developer account. Checked Nov 11, 2026.

How do you ask for your source code in writing?

Send one short, dated email, and keep a copy. Name what you want, where you want it, and by when. For example:

“Under section [X] of our agreement dated [date], please transfer the [project] repository to our GitHub organization [name], and send the admin credentials for [hosting, database, services] and the current documentation, by [date, about a week out]. Please also start the App Store and Google Play transfers to our accounts (Team ID [ID]).”

Keep it factual. Do not threaten, and do not withhold a payment you owe without advice first, because that can weaken your position. If the date passes with no reply, a lawyer can tell you what your contract and local law allow, from a formal demand letter onward.

What if you have no source code at all?

The app stores hold only a compiled build, and in practice you cannot rebuild a business app from it. Your server can be different: many backends (PHP, Node.js, Python, Ruby) run as readable code on the host, so have a developer copy everything there before anything else changes. After that, you have two paths, and they can run at the same time.

Recover it through the contract. In the US, copyright “vests initially in the author” (17 U.S.C. 201(a)), and a transfer of ownership is valid only in a signed writing (17 U.S.C. 204(a)). The Copyright Office’s Circular 30 says a commissioned work is made for hire only if it falls into one of nine listed categories, such as a translation or an atlas, and both sides sign a written agreement saying so. Custom app code generally fits none of them. So a freelancer’s code is usually yours only if your contract assigns it to you. If your developer was an agency, code its employees wrote belongs to the agency as their employer, so the assignment has to come from the agency. We cover this in more detail in who owns the code when you hire a developer. For a real dispute, talk to a lawyer.

Use the live app as the spec. Record every screen and flow, export your data, collect emails and messages about how features should work, and list the integrations. A new team can rebuild from that. The rebuild is rarely a line-for-line copy, which is often a chance to drop what nobody used. If the old system is large and still running, a planned legacy software modernization can replace it in stages instead of all at once.

Should you finish the project or rebuild it?

Decide after a code review. Use this as a starting point:

Factor Leans toward finishing Leans toward rebuilding
Source code Complete, in a repository you control Missing, partial, or only a build
Code quality Readable, consistent, reasonable structure Copy-pasted logic, no structure, hard-coded secrets
Tests Some automated tests that pass None, or tests that do not run
Documentation Setup and deploy steps written down Nobody knows how to build or deploy it
How far along Most features work; gaps are known Core flows are broken or unbuilt
Tech stack Current, supported frameworks and libraries Outdated or unsupported versions that need major upgrades
Build and deploy It builds and deploys from the repository It only runs on the old developer’s machine

Our judgment from reviewing other developers’ code, not a published standard.

Two or three “rebuild” answers do not force a fresh start, but the review then has to price both paths honestly. Projects often stall for the same few reasons, and why software projects fail covers them if you want to avoid a repeat.

How do you stop this happening again?

  • Accounts in your name from day one. Domain, cloud, repository, app stores, payments and email, opened by your company, with the developer invited as a user.
  • Code in your repository. In your GitHub, GitLab or Bitbucket organization, pushed often, not handed over at the end.
  • A written assignment of IP in the contract, signed, covering code, designs and documentation.
  • Documentation and handover as listed deliverables: setup, deploy, credentials list, and known issues.
  • At least two owners on critical accounts, as GitHub recommends for organizations.

When you hire the next developer, ask about these points before you compare prices; how to choose a software development company lists the other questions worth asking.

Can we take over software another developer built?

Yes, after a review. We maintain and take over software built by other developers, starting with access to the repository, hosting, domains, app store accounts and third-party services, then a review of the code, dependencies, tests, deployment and known issues. Sometimes the review shows that modernization is the better path, and we say so. Ongoing work runs under our software maintenance and support service and is quoted on scope. If your developer has gone quiet, book a free 30-minute call and bring whatever you have, even if it is only logins and a live app, and we will help you work out what you hold and what to do first.

Sources

All pages opened on Nov 11, 2026.

Related questions

Short, direct answers. Ask an engineer if yours is not here.

Ask on a free call

What do I do if my app developer disappeared?

Start with access, not the code. Check who owns your domain, hosting or cloud account, code repository, Apple and Google developer accounts, payment and email services. Get each one into your company's name with you as owner or admin, then remove the developer's access and change shared passwords and keys. After that, read your contract, send a dated written request for the code and credentials, and get a code review before deciding what to do next.

How do I get my source code from a developer who stopped responding?

First check whether you already have it: look for a GitHub, GitLab or Bitbucket repository you can open, or invites in your email. If it lives only in the developer's account, send a written request asking them to transfer the repository to your organization by a set date, quoting the ownership and handover terms in your contract. If they still do not respond, a lawyer can advise on the next step.

My app is on the App Store but I don't have the source code. What can I do?

The store holds a compiled build, not the code you need to change and maintain the app, so you cannot realistically continue from it. Your options are to recover the code from the developer through your contract, with a lawyer's help if needed, or to rebuild using the live app as the specification. Make sure the rebuilt app is published from a developer account in your company's name.

Can I move my app to my own Apple developer account?

Yes, Apple supports app transfers between developer accounts, but only the current Account Holder can start one and the receiving Account Holder must accept it within 60 days. The app needs at least one released version, cannot be in review or on pre-order, and both accounts must have accepted Apple's latest agreements. If your developer holds the account, you need them to start the transfer.

Can I transfer an Android app to my own Google Play account?

Yes. Google Play lets you transfer apps to a different developer account. The request comes from the account that holds the app, both accounts must be registered and active, and you need the registration transaction ID of the target account. The target account owner approves it, and Google says support then reviews requests within two business days. Users, ratings and reviews move with the app.

Can a new developer take over an unfinished app project?

Usually yes, if you can hand over the source code and the accounts. A new team should start with a review of the code, dependencies, tests, build and deployment before quoting, because unfinished projects often hide gaps the previous developer never documented. The review tells you whether finishing is cheaper than rebuilding. Without the source code, a takeover becomes a rebuild.

Who owns the code if my freelancer disappeared?

Under US law, copyright starts with the person who wrote the code, and a freelancer's code is generally not a work made for hire. You own it if your contract includes a signed written assignment to your company. If it does not, you may only have a license to use what you paid for. This is general information, not legal advice; ask a lawyer about your contract.

Start a project

Thinking about a build?

A free 30-minute call with one of our engineers. You leave with a first-release scope, a realistic timeline and a price range, whether or not we work together.

  • A first-release scope
  • A realistic timeline
  • A written quote, fixed-price or hourly

Written scope and quote after the call. NDA on request. You own the code.

Prefer email?

Send one question about your app, software or AI idea. An engineer replies within one business day.