What to Do When Your Developer Disappears

Secure access before you do anything else

Silence from a developer is uncomfortable but not usually catastrophic. Losing access to the accounts your product runs on is catastrophic, and it happens quietly while you are still sending polite follow-up emails.

Work through the list below today, regardless of whether you expect them to come back. Nothing on it is hostile — it is ordinary ownership hygiene that should have been in place from the start.

• Domain registrar: confirm the domain is in an account you control, and that the renewal card is yours.
• Code repository: confirm your account is the owner, not a collaborator on their personal account.
• Hosting and database: check whose email receives the billing.
• Payment provider, email delivery, storage, analytics: check each individually.
• Any app store listings, which are the hardest of all to recover after the fact.

What you can recover if the code is gone

If the repository turns out to be theirs and inaccessible, the situation is worse but rarely fatal. Whatever is deployed and running still exists, and a competent engineer can usually retrieve a working codebase from the running system.

The database is the part that genuinely cannot be reconstructed, which is why hosting access is more urgent than repository access. Get a backup taken and stored somewhere you control before anything else.

Do not send the final payment yet

If money is outstanding, it is the only leverage you have, and paying it in the hope of prompting a reply almost never works. Offer it explicitly in exchange for the handover: repository transfer, credentials, and a short written note on how to run the project.

Put that offer in writing, keep it civil, and give a deadline. It converts an emotional standoff into a transaction, which is far more likely to produce a result.

Why they usually vanished

It is almost never malice. The common causes are that the developer took on more than they could deliver and could not face saying so, that the project became unprofitable after they underquoted it, or that they hit a technical problem they could not solve and stopped answering rather than admit it.

That matters practically: it predicts what you will find in the code. Expect the last third of the work to be incomplete rather than the whole thing to be fabricated, and expect one specific hard problem sitting unsolved somewhere near where they stopped.