Choose a sale when you are finished with the code; choose a license when you still need it. Licensing makes sense if you keep running or reusing the code, or if several customers will each pay to use a component you maintain. For a product that has stopped, it usually means years of contract management for an uncertain income, while an outright sale gives one price and a clean exit.
Ownership moves in a sale; permission is all a license grants
In an outright sale, you assign the copyright in the code to the buyer. You stop being the owner. In the US, a transfer of copyright ownership is not valid unless it is in writing and signed by the owner, and in the UK an assignment is not effective unless it is in writing signed by or on behalf of the assignor. That is why a fair sale always comes with a signed written agreement. Contract wording decides which one you actually have, so this is general information, not legal advice.
In a license, you remain the owner and give someone permission to use the code on terms you agree: for how long, for what, in which countries, and whether others may use it too. You can license the same code many times, or once exclusively. The relationship lasts as long as the license does.
Nine points where sale and license part ways
| Point | Outright sale | License |
|---|---|---|
| Who owns the code afterwards | The buyer | You |
| How you are paid | One price; with us, cash only, paid on transfer | Upfront fee, recurring fees or royalties |
| How long you are involved | Until transfer | For the whole license term |
| Monitoring and enforcement | None | Yours: checking use, invoicing, chasing breaches |
| Liability and support | Set by the sale agreement’s warranties | Often ongoing, depending on the license |
| Can you use the code yourself | No | Usually yes, unless exclusive |
| Effect on a later sale | Not applicable | Existing licenses travel with the code and must be disclosed |
| Tax character (varies by country) | Depends on who created it and how it was held | Often treated as rental or royalty income |
| Best fit | Code you are finished with | Code you still run, reuse or maintain |
Licensing keeps you in the business of the code
Licensing sounds like owning an asset that pays rent. In practice, it is a small business of its own. Someone has to negotiate terms, invoice, check that the licensee stays within scope, answer questions about how the code works and decide what happens when the licensee stops paying. With old code, there is often also a question of who fixes security problems, and the licensee will likely ask.
The income is also less certain than it looks. Recurring license fees depend on the licensee continuing to need the code. For code from a product that has ended, there is rarely a queue of licensees, and the one that appears may well want an exclusive license, which leaves you with ownership in name only. You also keep the paperwork: the contract, its renewal dates and, in many countries, the question of how each payment is taxed. A sale settles all of that at once.
How tax treatment can differ
Tax rules turn on what the contract actually does, and they vary by country. A few published examples show why this matters:
- US. The IRS treats payments for the use of personal property as rental income, but payments for granting exclusive use of a copyright are treated as received from the sale of property. The same publication lists a copyright created by your personal efforts as a noncapital asset, so if you personally wrote the code, selling it usually produces ordinary income, not a capital gain; whether your code counts is a question for a tax adviser.
- Germany. Income from the time-limited provision of rights is rental and leasing income under § 21 EStG.
- Australia. Assessable business income includes royalties for the use of copyrighted material.
This is general information, not legal or tax advice. Ask an accountant how either route would be taxed in your case, and see our guide to taxes when you sell source code for more country detail.
When licensing wins
License rather than sell when:
- You still use the code. If your company runs it or builds other products on it, you cannot sell it outright without losing it.
- It is a reusable component with several potential users. A maintained library or engine can earn from more than one licensee.
- You plan to come back to it. A license keeps ownership with you for a future restart.
- The product is still running. A licensing deal is a business activity; we do not buy software that still makes money in any case.
When an outright sale wins
Sell outright when the product has ended and you want to be done. You get one agreed price, the rights move under a signed agreement, and after transfer there is nothing to monitor, invoice or enforce. With us, there are no earn-outs and no royalties tied to anything you cannot control.
A sale also keeps things simple on the other side. Odys AI Labs, the research and development arm of Odys, uses the code for AI training and R&D, and we may also work on it with research partners. We never use your brand or name, never relaunch the product as yours, and keep the deal confidential. Our guide to what is in a source code purchase agreement explains assignment, warranties and payment on transfer in plain English.
Two ways the same code could go: an illustration
Suppose a small studio owns the code of a booking platform it retired two years ago. A former partner asks to license it, paying a fee each quarter to run a private version for its own customers. Separately, the studio asks for an offer to sell the code outright.
The license looks attractive at first: the studio keeps ownership and gets paid over time. But it also commits to answering technical questions, deciding who patches security issues in old dependencies, checking the partner stays within scope and chasing late payments. If the partner stops using the platform after a year, the income stops too, and the studio still owns code that is now a year older.
The outright sale is one price, paid on transfer, after which the studio has no further obligations. Neither option is wrong. The question is whether the studio wants to stay in the business of this code. For most owners of a product that has ended, the honest answer is no.
Can you do both?
Not with the same code, at least not to us. An outright sale transfers ownership, so you can no longer license the code to anyone afterwards. The reverse needs care: any license you granted in the past, for example to a former client, may continue after a sale and limit what the buyer receives. List every license you ever granted, check who owns the code in the first place, and disclose both before signing. A lawyer should look at any old license that could be exclusive.
Which to choose
- Do you or your company still run or build on this code? License, or keep it.
- Is there a realistic licensee who will pay over time, and are you willing to manage that? License.
- Is the product finished and do you want a clean exit? Sell outright.
What to do next
- Find every contract that ever touched the code: licenses, client agreements, contractor assignments.
- Decide whether you still need to use the code yourself in the future.
- To see what an outright sale would look like, describe the product for a free code valuation.
Frequently asked questions
What is the difference between selling and licensing code?
Selling, usually called an assignment, transfers ownership of the copyright to the buyer, and you no longer own the code. Licensing gives someone permission to use the code on agreed terms while you remain the owner. A license can be exclusive or non-exclusive, limited in time or scope, and paid once or over time. Ask a lawyer to check which one a contract really creates.
Does Odys AI Labs license code or buy it?
It buys it. The terms are cash only, one agreed price, paid on transfer, with no earn-outs. The offer comes after a review based on what you tell us, with no obligation, and the rights are transferred under a written agreement signed before any code changes hands. Odys AI Labs uses the code for AI training and R&D.
Is an exclusive license the same as a sale?
Not legally, but it can come close, and tax authorities may look past the label. The IRS, for example, says payments for granting exclusive use of a copyright are treated as received from the sale of property. What a contract does matters more than what it is called. This is general information, not legal or tax advice.
I licensed my code to a client years ago. Can I still sell it?
Possibly. An old license does not automatically stop a sale, but it may limit what you can transfer, and the buyer needs to know about it. Read the old agreement for exclusivity, ownership and transfer clauses, list every license you ever granted, and mention them on the call. Have a lawyer review anything unclear before signing.
Find out what your old code is worth right now.
Tell us about the product in about a minute. No code needed. We review the details and come back with a cash offer or a plain no.
Get my free code valuation →