The freelancer went dark. You don't have the code.
Freelancers going silent with your code, your credentials, or your deployed application is unfortunately common. The immediate priority is limiting damage: secure your accounts, revoke access, and assess what you actually have. The rebuild comes after.
Freelancer went dark with the source code, credentials, or deployed application — the product may still be running but you can't make changes or hand it off
When a freelancer goes dark with your project, the damage varies:
Scenario 1: Code is in their private repository, app is still running. Priority: change all credentials the freelancer had access to (AWS, Vercel, Stripe, database) before they can cause damage. The app runs from the deployed version; the source code will need to be rebuilt.
Scenario 2: Code is in a repository you own (GitHub org), freelancer has disappeared. You have the code. The crisis is less severe. Onboard a new developer with repository access; they can read the code and continue.
Scenario 3: Freelancer controls the hosting (Vercel under their account, AWS under their account). This is the worst case. The application is running on infrastructure you don't own and can't access. Legal options exist; practical options include: contact the freelancer's payment platform to escalate, file a legal claim, and rebuild from scratch.
Immediate checklist when a freelancer disappears:
- Revoke all API keys and credentials you can access
- Change passwords on any accounts they had access to
- Remove them from any repositories or deployment platforms where they have access
- Check if the app is still running (temporary — once the running deployment stops, it's gone without the code)
- Assess what you actually own
The contractual issue:
Most freelancer contracts specify that the client owns the work product. If you have a contract with this clause, you have legal standing to demand code delivery. Upwork's terms also include provisions for this scenario.
Recovered access to what can be recovered, clear assessment of what needs to be rebuilt, and a rebuilt application owned entirely by you
Access recovery
guidance and checklist
Code audit
of any recovered codebase
Full rebuild
from scratch when the code is unrecoverable
Infrastructure migration
to accounts you own
One honest number to start.
Fixed-scope, fixed-price. The number below is the starting point — final scope is built from your brief.
Recovered access to what can be recovered, clear assessment of what needs to be rebuilt, and a rebuilt application owned entirely by you
Three steps, every time.
The same repeatable engagement on every project. No surprises, no mystery, no billable ambiguity.
Brief & discovery.
We send you questions, then get on a call. Output: a written scope with every step, feature, and integration listed.
Build & ship.
Fixed schedule, weekly reviews. No scope creep unless you change the scope — and if you do, we reprice it transparently.
Warranty & retainer.
30-day warranty on every launch. Most clients stay on a monthly retainer for ongoing features and maintenance.
Why Fixed-Price Matters Here
Rebuild scope is definable from the original requirements. Fixed price; you own everything.
Questions, answered.
Yes, if you have a contract that assigns code ownership to you and the freelancer hasn't delivered. Small claims court is viable for amounts under $10,000 in most states. Consult a lawyer for larger amounts.
Upwork's dispute resolution process is the first step. File a dispute; Upwork will mediate. If the freelancer delivered nothing and you paid for a specific deliverable, you have a strong case.
Tell Ryel about your project.
Describe what you’re building and what outcome you need. You’ll have a written, fixed-price scope within the week.