Selling and licensing your code: FAQ
Selling and licensing your code, answered: ownership, rights, payment within 15 days, privacy and the process. Fifteen plain answers.
Free to join. No public listing. A real estimate in minutes once Git is connected.
You license your code to AI labs and keep ownership. You sell a license, you keep the code, and licenses are non-exclusive, so you can be paid more than once, within 15 days each time a license closes.
Ownership and rights
Q.01Do I keep ownership of my code?
Yes. You grant a non-exclusive license and keep ownership. You can keep using, changing and shipping it.
Q.02Can I continue using the code?
Yes, internally and in your own products. The license does not change that.
Q.03Is the license exclusive?
No. The same repo can be licensed more than once, and you are paid each time. How often depends on demand.
Q.04Do I need to own the IP?
Yes. Only submit code you hold the rights to. Client work usually belongs to the client unless your contract says otherwise.
Q.09What am I responsible for?
Holding the rights to what you submit, and keeping third-party code and customer data out of the repos you select.
Q.12What if the code uses open source libraries?
That is fine. Third-party code is excluded from what is licensed. Your own code and history are what count.
Questions answered? See what your repos earn.
Free to join. No public listing. A real estimate in minutes once Git is connected.
Money and timing
Q.05What contributes to the value?
The token count of your source and of your git history, how deep and real that history is, tests, and buyer demand. History carries most of the value.
Q.06How long does the process take?
You see a real per-repo estimate within minutes of connecting Git. Licenses close in batches. You are paid within 15 days of the buyer paying.
Q.07When and how do I get paid?
Within 15 days each time a license closes and the buyer pays. No fees are taken from your share.
Q.13Is selling code taxable?
Licensing income is usually taxable as business income. Ask an accountant in your jurisdiction.
Process and privacy
Q.08Can I withdraw a codebase?
Yes. There is no commitment. You can withdraw a codebase at any time.
Q.10Can I review the agreement before signing?
Yes. You read it first and sign once.
Q.11Do I need the repo to be working?
No. Shelved, unfinished and abandoned code qualifies if it is real and yours.
Q.14Will my code be listed publicly?
No. There is no listing. Buyers see a scrubbed review copy.
Q.15What does "secrets stripped" mean?
Keys, tokens, credentials and personal data are removed from the review copy of both code and history and verified before a buyer sees anything. Your repository is untouched.
What is your code worth?
Request access. Connect Git. See a real per-repo estimate in minutes, then decide.
Free to join. Nothing upfront. You can withdraw a codebase at any time.