What do I do if my developer has the only access to my code?

Start with password resets on every service where your business email is the account owner — GitHub, hosting providers, domain registrars. Most platforms will transfer ownership to the account holder even if a team member set it up. If the developer set up accounts in their own name, you'll need to negotiate access or escalate through the platform's support.

Can I sue my developer for disappearing?

Possibly, but it's usually not the most useful first step. Your immediate priority is securing access to your code and infrastructure. Legal action is slow and you have a product to rescue. Document everything — screenshots, messages, contracts — but focus on recovery first.

How long does it take to take over an abandoned software project?

A basic handoff stabilization — access secured, codebase understood, deployments working — typically takes 1–2 weeks. Getting back to active development depends on the state of the codebase and the complexity of what's left to build. Most projects we've taken over reach stable operation within the first week.

My Developer Disappeared: What To Do in the Next 72 Hours

Your developer hasn't responded in days. Messages are going unread. The project is sitting half-finished and you don't know where anything is.

This happens more often than anyone in the industry likes to admit. Here's what to do — in order — starting now.

If your developer has gone silent and your project is stalled right now, we can help you secure access and get an honest read on what's salvageable. We run these rescues every month and start with a free code audit before you commit to anything.

Talk to us about a rescue or call +91 90358 61690

Trusted by VMAC Industries, TKD Logistics, Astitva Jewellery & more · Fixed-price · No obligation

The first 72 hours: secure everything

Before you make any decisions about what to do with the project, you need to control it. You can't assess what you don't own.

1. List every service the project uses

Write down every tool, platform, and service connected to your project. Typical list:

Version control: GitHub, GitLab, Bitbucket
Hosting: Vercel, AWS, DigitalOcean, Heroku, Railway, Render
Domain: GoDaddy, Namecheap, Google Domains, Cloudflare
Database: Supabase, PlanetScale, MongoDB Atlas, AWS RDS
Email service: SendGrid, Postmark, Resend, Mailgun
Payment processor: Stripe, Razorpay
Analytics: PostHog, Mixpanel, Google Analytics
Monitoring: Sentry, Datadog, LogRocket
Communication: Slack workspace, Notion, Linear

2. Check what you own vs what they own

For each service, answer: Is the account registered to your business email or theirs?

If yours: reset the password immediately, revoke their access, and enable 2FA.
If theirs: contact the platform's support with proof of business ownership (incorporation documents, domain ownership records). Most platforms have a process for this.
If unclear: assume it's theirs until proven otherwise, and treat it as a recovery item.

3. Secure your domain first

Your domain is your most critical asset. If you lose it, you lose your email, your website, and access to any services that use your domain for verification.

Log into your domain registrar and confirm:

You are the account owner
The domain is not about to expire
Transfer lock is enabled

If the domain is registered under the developer's personal account, contact the registrar's support immediately with proof of business ownership.

4. Get a copy of the code

If you have access to the GitHub/GitLab repository, clone the entire codebase right now. Even if you can't run it, you want a local copy that exists independently of any platform that might become inaccessible.

git clone https://github.com/your-org/your-repo

If you don't have access to the repository, this is your most urgent recovery item.

Assessing the damage

Once you've secured what you can, you need to understand what you have.

What does the codebase contain?

You need answers to:

Is there a README? Does it explain how to run the project?
Is there a .env.example or environment variable documentation? You'll need this to run it anywhere
Is there a deployment setup? Dockerfile, CI/CD configuration, Vercel/Netlify config?
When was the last commit? What was being worked on?
Are there tests? Do they pass?

If you can't answer these questions yourself, you need a developer who can audit the codebase and give you a clear picture.

What's the live application's state?

Is it currently running and accessible to users?
Is there a database with real user data in it?
Are there active integrations (payments, email) that could break?

A live application with real users has different urgency than a half-built product with no production deployment.

What was left to build?

Compare the contract or spec to what exists. This tells you:

How much was delivered vs paid for
How much work remains
Whether what exists is a foundation worth continuing from

If you can't answer the questions above on your own — which is normal, most non-technical owners can't — the fastest way to get a clear picture is to

start with a free code audit →

Your options

Once you've assessed the situation, you have three paths:

Option 1: Hire a new developer to continue Best when the codebase is in reasonable shape, well-documented, and the remaining work is straightforward. This is the fastest path if you have the right candidate.

Risk: A new developer who doesn't understand the existing codebase may slow down before they speed up. Budget 1–2 weeks for onboarding and assessment before real progress starts.

Option 2: Hire a team to rescue and continue Best when the codebase has problems the original developer left behind, the documentation is poor, or the architecture needs assessment before continuing. A team brings context from similar rescues — they've seen these patterns before.

This is typically faster to productive output than a solo developer coming cold to an undocumented codebase. If this is your path, here is how we take over your software project: secure access first, then audit, stabilize and continue.

Option 3: Assess whether to rebuild If the codebase is in bad shape — no tests, no documentation, unclear architecture, significant security issues — continuing from it may cost more than starting fresh with a proper foundation.

This is counterintuitive but often correct. A 3-month-old bad codebase might cost more to rescue than a 6-week rebuild done properly. Our guide on whether to fix or rebuild your software gives you a scoring framework for this call.

Hunchbite Service

Software Rescue & Recovery

Failing project, runaway bugs, or a developer who vanished? We stabilise it — starting with a free technical audit.

See how rescue works

What to have ready before you talk to anyone

When you talk to a developer or agency about taking over the project, have ready:

Repository access or a zip of the codebase
List of all services used (from your 72-hour audit above)
The original spec or project brief
A list of what was supposed to be done and what you believe is done
Any contracts or payment records with the original developer
Credentials for services you've already reclaimed

The more context you can provide, the faster an honest assessment can be made.

How Hunchbite handles developer disappearances

We've handled this situation many times. The pattern is consistent: secure access in week one, audit and stabilize in week two, resume development in week three.

We start with a free technical audit — we review the codebase and tell you what exists, what state it's in, and what it would take to get to a working product. You don't commit to anything until you have that picture.

→ Get a Free Audit and Take-Over Assessment

Call +91 90358 61690 · Book a free call · Contact form