How Do I Get My Source Code Back From a Developer?

How do I get my source code back from a developer?

Start by asking in writing for a complete handover: the code repository, hosting, domain, app store accounts, API keys and database backups. Check your contract to see what you were promised. If the developer stalls or refuses, document everything and speak with a Florida attorney about your options.

Most people in this spot are not locked out of one thing. They are missing several: the code, the place it runs, and the accounts that tie it together. The checklist below covers each one, so you can see exactly what you have and what you lack.

What should I ask for, step by step?

Ask for six things: the code repository, the hosting account, the domain registrar login, the app store developer accounts, every third-party API key, and the database with a recent backup. Work through them in this order, and write down who currently controls each.

• • Code repository. The project's history lives in a system such as GitHub, GitLab or Bitbucket. Ask for the full repository with its history, not a zip of the latest files. Better still, ask to be made an owner of the account or organization that holds it. A common first answer from people who ask online is that someone on the team should still have access to the repo.
• • Hosting and cloud. This is where the live site or app runs. Ask for owner access to the account, not a shared login. Note who pays the bill.
• • Domain registrar. Your web address is registered somewhere. Look up the registrant of your domain and check that it is you or your company. Ask for the registrar login or a transfer.
• • App Store and Google Play accounts. If you have a mobile app, find out whose Apple Developer and Google Play accounts it is published under. An app published under the developer's personal account is theirs to control.
• • API keys and third-party services. Payment processors, email senders, maps, analytics, AI services. Ask for a list of every service the app uses and for the accounts to be moved into your name.
• • Database and backups. Ask for access to the production database and a current backup. Without the data, the code alone does not bring the product back.

Add two more items if they apply: any design files, and the written documentation or setup notes, if any exist.

How do I ask the developer for it?

Send a short, calm written request that lists each item and sets a reasonable date. Quote the section of your contract that covers ownership or handover, if there is one. Keep it factual and keep all replies. A written paper trail helps whatever happens next.

A simple structure works well:

• • State that you are requesting a handover of the project assets.
• • List the six items above and ask for each to be confirmed or delivered.
• • Give a date, and ask for a reply in writing.
• • Keep the tone neutral. Avoid accusations. You want the assets, and a hostile message gives the developer a reason to stop replying.

Save every email, message and invoice. If you have no contract, the emails, chats, invoices and milestone descriptions serve as the record of what was agreed.

What can I do right now without the developer?

Check what you can see without anyone's permission. Look up your domain registrant, check which accounts receive your hosting and app store emails, search your inbox for invoices from hosting or cloud providers, and list the logins you already hold. This often shows that you control more, or less, than you thought.

• • Run a public domain lookup to see the registrant and registrar.
• • Search your email for receipts from hosting, domain and app store providers. Those show which account pays.
• • Ask your team whether anyone else was added to the repository or cloud account. Someone may already have access.
• • Take screenshots of the live site, the admin screens and the app store listing as they are today.

This inventory is also the first step of a Project Health Check, which includes an ownership and access checklist for the repository, hosting, domain, app store accounts, API keys and database.

What if the developer refuses or stops replying?

Keep a record, and talk to a Florida attorney before you escalate. A demand letter, a dispute with your payment provider, or a court claim each have different rules, deadlines and costs. We are a software studio and cannot tell you which path fits your case.

Here are the facts that tend to matter when people look at their options. We list them as reference points, not advice.

Two more notes. If you hired through Upwork or Fiverr, those platforms have their own dispute processes with their own time limits, so check them early. And card dispute windows are short, so if you paid recently, look at the date today.

An attorney may also ask for a neutral technical record of what exists and what does not. That is where an independent review helps, because it turns "I think it is not finished" into a written list of facts.

How do I stop this from happening again?

Put every account in your own name from day one. You create the repository organization, the hosting account, the domain registration and the app store accounts, and you invite the developer in as a collaborator. Then ownership never depends on anyone's goodwill.

Use this short list at the start of any software project:

• • You own the accounts. Repository, hosting, domain, Apple and Google developer accounts, payment processor, all in your company's name, with your email.
• • Developers are guests. Give them the access they need and remove it when the work ends.
• • The contract says who owns the code. Include handover of source code, documentation and credentials on completion and on termination.
• • Pay against milestones. Tie payments to delivered, working pieces you can see, not to calendar dates.
• • Get regular access to the repo. Check in on the commit history every few weeks. It takes five minutes and shows that work is happening.
• • Keep your own backups. A copy of the code and a database backup stored where you control them.

Where does Cuanto Labs fit?

If your developer stopped or did not deliver, the Project Health Check is built for this moment. It is $1,500 flat for up to about 50K lines of code, $2,500 for larger codebases, and takes 5 business days. It starts with the ownership question: who controls each piece today.

You get whether it builds and runs, a table of deliverables against your contract or SOW, the ownership and access checklist, the top code and security issues, a commit timeline against your invoices, and a fix-or-rebuild estimate. It is independent. We do not require you to hire us for the fix. If you want a deeper look at an inherited codebase, see our Code Audit, from $4,000 and about 2 weeks. To talk it through first, book a call.

This article is general information, not legal advice. Cuanto Labs is a software studio, not a law firm.