Catalogue No. 001By asset typeVerified 2026-10-10Licensing open

Can I sell Android app source code?

Sell Android app source code by licensing it to AI labs. Kotlin and Java apps qualify, live or shelved. Keep the app and get paid each time.

Free to join. No public listing. A real estimate in minutes once Git is connected.

Lot 026Company ownedSpecimen

Android delivery app, shelved 2023

41,700 lines. The courier app of a regional delivery startup, shelved when the service closed in two cities.

Languages
Kotlin
Lines of code
41,700
Commits
2,240
Source tokens
0.5M
History tokens
14.0M
Last commit
Oct 2023
Source 0.5M · 3.4%History 14.0M · 96.6%
Commits per quarterActivity stopped Q4 2023
Per license, USD0.5M × $100 + 14.0M × $40≈$610recurring
Illustrative lotNot a live listing
Quick answer

Yes, Kotlin and Java Android apps you own can be licensed to AI labs, whether they are live, shelved or never launched. You sell a license and keep the code and the app, and a typical repo earns about $1,000 to $1,500 per license, each time it is licensed.

Applies to code you own Currency USD Verified 2026-10-10
§ 01Who this is for

Can I license an Android app I built?

Yes, if you or your company own it. Android apps make good training code because they mix several kinds of work in one repo: Kotlin or Java, layouts, Gradle builds, background jobs and API clients, all changed over years of OS updates. Labs want that mix.

The app can stay on Google Play. Licensing the code changes nothing about the listing or the users, and nobody else publishes it.

Does the app need to still be on Google Play?

No. Apps that were unpublished, suspended or never submitted qualify the same way. The store listing has no bearing on value. What counts is the code you wrote and the history behind it, including the backend and any internal tools that supported the app. If you built the app with a cross-platform framework, the shared code counts too.

Long-lived Android apps often hold years of changes made to keep up with new OS versions, permissions and libraries. That kind of maintenance history is valuable to labs, because it shows how real apps adapt over time.

Qualifies
  • Kotlin and Java apps, live or shelved
  • Jetpack Compose and older XML layouts
  • Apps removed from Google Play
  • The backend repos behind the app
Stays out
  • Apps a client or employer owns
  • Signing keys and store credentials
  • Third-party SDKs, which are excluded
§ 02What it is worth

How much is Android app source code worth?

Value per license is source tokens at $100 per million plus history tokens at $40 per million. A shelved delivery app like the specimen lot above, with a few years of commits, sits in the typical band at about $1,000 to $1,500 per license. Licenses are non-exclusive, so the same repo can be licensed again and you are paid each time.

Signing keys and API secrets committed to the repo are stripped from the review copy for you. For the method, read how much is my code worth. For why labs pay, read sell code for AI training.

Per-repo ballpark by depth, per license, USD
DepthLooks likePer repo, per licenseLog scale, $100 to $10k
LightShort history, small repo$400 to $700
TypicalA real product, a few years of commits$1,000 to $1,500
DeepLong-lived, deep history, tests$2,500 to $4,000

Illustrative, conservative · What you take home, per license · Verified 2026-10-10

Rate A · Source code

$100/M

per million tokens

Rate B · Git history

$40/M

per million tokens

Value per license = source tokens × $100/M + history tokens × $40/M

Rates can change on 30 days' notice, never retroactively · Paid within 15 days of the buyer paying

Illustrative, conservative · Last verified 2026-10-10

Find out what your repos earn.

Get a valuation

Free to join. No public listing. A real estimate in minutes once Git is connected.

§ 03The IP question

“But this is proprietary code.”

And it is yours, which is exactly what makes it licensable. You decide what is shared: only the repos you choose, only code you hold the rights to. Secrets, customer data and third-party code stay out. Within the repos you submit, secrets and personal data are stripped from the review copy before anything reaches a buyer.

  1. Fact 01You pick what is shared.
  2. Fact 02You keep full ownership.
  3. Fact 03Secrets are stripped for you.
§ 04What to do next

What do I do next?

No clean-up needed. Submit the repos as they are. Secrets and personal data are stripped from the review copy for you.

  1. Step one

    Request access

    Say who you are. You get set up and sent everything you need. Once you connect Git, you see a real per-repo estimate.

    Time A few minutes
  2. Step two

    Sign and connect

    Read the agreement and sign once. Give read-only access to GitHub, GitLab or Bitbucket and pick only the repos you want to license. Submit them as they are.

    Access Read-only
  3. Step three

    Get paid, repeatedly

    Your code is scrubbed and graded on the review copy, then taken to buyers in batches. Each time a license closes and the buyer pays, you are paid within 15 days.

    Payout Within 15 days
§ 05Questions

What else do owners ask?

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.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.

§ 07  ClosingCatalogue No. 001Licensing open

What is your code worth?

Request access. Connect Git. See a real per-repo estimate in minutes, then decide.

Get a valuation

Free to join. Nothing upfront. You can withdraw a codebase at any time.

Get a valuation