Who Owns the Code When You Hire a Dev Agency?

You paid for the build, so the code is yours. That is what almost every founder assumes, and in the United States it is not automatically true. Under copyright law the person or company that writes the code owns it by default, even after you have paid for it, unless a written contract says otherwise. That single gap has cost founders their product, their leverage, and in a few cases the ability to move to a different developer at all. This guide explains, in plain language, how code ownership actually works when you hire an agency, what "you own the code" should really include, and the exact contract terms that make sure your MVP stays yours.

This is general information for founders, not legal advice. For a specific deal, have a lawyer review the contract. The point here is to know what to look for before you sign.

The short answer: it depends on your contract

Ownership of custom software is governed by intellectual property law and by the agreement you sign, not by who paid the invoice. Absent a clear clause transferring ownership to you, the developer can retain the copyright to what they wrote. You may have a license to use the running product without owning the underlying code, which means you cannot freely move it, modify it with another team, or stop the original developer from reusing it.

The good news is that this is entirely solvable with one well-drafted document. Reputable agencies expect to assign ownership to you and will put it in writing without a fight. The risk is not that ownership is hard to get. It is that founders never ask, and the contract stays silent, and silence defaults against them.

Work-for-hire versus license: the two models

When you commission software, the contract usually falls into one of two shapes. Knowing which one you are being offered tells you almost everything.

A quick note on "work-for-hire", a phrase you will see in contracts. It is a legal concept where the commissioning party is treated as the owner from the start. It applies cleanly to employees but is narrow and unreliable for independent contractors and agencies. That is why good contracts do not lean on work-for-hire alone; they add an explicit assignment clause that transfers all rights to you, closing the gaps the doctrine leaves open. If a contract mentions work-for-hire but has no assignment clause, treat that as incomplete.

What "you own the code" should actually include

Ownership is not one thing. It is a bundle, and an agency can hand you some of it while quietly keeping the rest. Here is the full checklist of what real ownership looks like at the end of an MVP project. If any box is unchecked, you do not fully control your product.

• The source code itself, not just a running app. Human-readable code, not a compiled black box.
• Admin access to the code repository (for example on GitHub or GitLab) under an account you own, with the full commit history.
• The right to deploy and host it yourself, or move it to any provider, without the agency in the loop.
• Every account and credential in your name: the domain, the hosting, the database, and any third-party API keys the product depends on.
• A written IP assignment transferring all intellectual property in the work product to you on payment.
• No lock-in to proprietary tooling that only the agency can operate or that stops working if you leave.
• Basic handover documentation: how to run it, build it, and deploy it, so a different developer can pick it up.

That last group, the accounts and credentials, is where most founders get quietly trapped. If your product runs entirely on the agency's hosting account and their database, you can own the copyright on paper and still be unable to touch your own product without them. Ownership of the code and control of the infrastructure have to travel together. Our guide to what a good MVP development company looks like covers how to confirm both before you sign.

Red flags that mean you do not really own it

These are the warning signs we tell founders to watch for. Any one of them is worth a direct question before money changes hands.

1. The contract is silent on IP. No assignment clause means the default applies, and the default is not in your favor.
2. They will only give you a login, not the repository. A running app with no source access is a rental, not ownership.
3. Everything runs on their accounts. Hosting, domain, and database in the agency's name is leverage they can use later.
4. They reserve the right to reuse "components" or "frameworks". Some shared tooling is normal, but read exactly what they are keeping.
5. They cannot answer the ownership question clearly. A team that builds for founders should have a crisp, confident answer.
6. Ownership is offered only as a paid extra at the end. This is a classic way to convert a normal expectation into a surprise upsell.

Several of these overlap with the broader warning signs we cover in red flags when hiring a development agency, and they are exactly the kind of thing worth raising in your first conversation. Our list of questions to ask before hiring an MVP developer includes the ownership questions to put on the table early.

What to put in the contract

You do not need to draft this yourself, and you should have a lawyer review anything you sign, but you should know the terms to insist on so you can recognize whether they are present:

• An IP assignment clause: "All work product and intellectual property created under this agreement is assigned to the client upon payment."
• Source code delivery: code lives in a repository you own throughout the project, not handed over as a zip file at the end.
• Accounts in your name: domain, hosting, and third-party services set up under your accounts from day one.
• A confidentiality clause, so your idea and data are protected regardless of the ownership terms. If you are weighing that separately, see our piece on whether you need an NDA for MVP development.
• Clear handover terms that survive the end of the engagement, so you are not dependent on goodwill.

How SquadPrime handles ownership

We think the ownership question should never be a question at all. At SquadPrime you own 100% of the code and the repository, and that is written into the agreement from the start, not offered as an upsell at the end. It is a fixed price, built by a senior-only team, delivered to a repository in your name. You could take the code to another developer the day after launch and lose nothing, and honestly, a build you fully own is the only kind worth paying for. If you want to compare how different routes handle this, our overview of how much an MVP costs in 2026 lays out the tradeoffs across freelancers, networks, app builders like Bubble, and fixed-price agencies.

FAQ

Do I automatically own code I paid a developer to build?

Not automatically. In the United States, under copyright law the person who writes the code owns it by default, even if you paid for it, unless your written contract assigns the intellectual property to you. This surprises most founders. The fix is simple but essential: a signed agreement with a clear IP assignment clause that transfers ownership of all work product to you on payment.

What is a work-for-hire agreement?

Work-for-hire is a legal concept where the party who commissions the work is treated as the owner from the start. It applies cleanly to employees but is narrow and unreliable for independent contractors and agencies. Because of that, well-drafted contracts do not rely on work-for-hire alone. They add an explicit assignment clause that transfers all rights to you, which covers the gaps work-for-hire leaves open.

What should I get at the end of an MVP project?

Full ownership of the source code, admin access to the code repository, the ability to deploy and host it yourself, and every account and credential the product runs on (domain, hosting, database, third-party keys) in your own name. If you receive only a running app on the agency's infrastructure with no repository access, you do not truly own or control your product.

Can an agency hold my code hostage?

It happens, usually when the code lives only on the agency's accounts and the contract is silent on ownership and handover. If a dispute arises, they control the leverage. You prevent this up front by requiring, in writing, that source code sits in a repository you own, that all accounts are in your name, and that IP transfers to you on payment. Insist on these terms before signing, not after a dispute.

This article is general information for founders and not legal advice; laws vary by jurisdiction and change over time, so have a qualified lawyer review any contract before you sign. Any price ranges reflect our own experience and are typical, not guaranteed. Spotted something outdated or inaccurate? Email talk@squadprime.com and we'll correct it promptly.

Related: How to protect your idea when hiring developers · Do you need an NDA for MVP development? · Red flags when hiring a development agency