Mobile and web app code

Sell my app source code: which AI buyers take app code

Updated

On the board, read up to 2026-10-22, the buyers that take code (DataVendor, Grepped, Mercor, aitrainer.work and Turing among them) ask for repositories, not apps. DataVendor is the one showing mobile code among its listings, and Google has been reported asking Play Store developers for theirs.

Describe my codebase

Who pays for an app's source code?

DataVendor runs a marketplace for private repositories and software projects. One of the example listings on its home page is a Mobile SDK suite of 420k lines for iOS and Android at $95k, which shows the kind of code it lists, not what your app would fetch.

Source: Codebase buyer terms and prices board

RuntimeWire, in a report dated 2 June 2026, says Google emailed a select group of Google Play app developers about a confidential content offer pilot covering production codebases, archived projects, prototypes and side projects. The same report says payout sizes are still undisclosed.

Source: RuntimeWire on Google's Play Store code pilot

The Google page that email reportedly linked to talks about paying for closed and offline datasets. It does not mention app code, a licence or a price.

Source: Google, partnerships to improve our AI products

Do I keep my app if I license its code?

As reported, Google's pilot leaves developers with 100% of their intellectual property and takes a non-exclusive license, so the same code could be offered to another buyer afterwards.

Source: RuntimeWire on Google's Play Store code pilot

Turing's Project Lazarus says it is for operating and winding-down companies, so an app does not have to be shut down before its code and records are offered.

Source: Codebase buyer terms and prices board

What does app code sell for?

8 of the 15 buyers on the board print a figure of any kind, and none of them is a price for your app. Turing's Project Lazarus, for one, offers a single payout of up to $1M for a company's whole operating record, of which the source code is one part.

Source: Codebase buyer terms and prices board

What do buyers want with an app's code?

  • aitrainer.work: code that reads like production software, built over years by more than one person, with the tickets, design docs, tests and deploy history kept.
  • Turing: the source code with the reviews, tickets and iteration history behind what shipped.
  • Mercor: a GitHub connection, so the pull requests and issues come with the code.
  • DataVendor: private repositories and software projects, with the history and context around the source.

Source: Codebase buyer terms and prices board

Code without its history is less than these pages ask for. If your app's repository still carries its commit history and issue tracker, keep them: aitrainer.work, Turing, Mercor and Grepped all name that history alongside the code.

Source: Codebase buyer terms and prices board

Is this the same as selling the app?

No. This page is about licensing an app's code to buyers who train or test AI on it. Selling the app as a running product, with its users and store listing, is a different sale with different buyers.

Tell us about the codebase

Describe the code, its history and who owns it. We tell you which buyers on the board take that kind of codebase and what to settle before you talk to one.

The code you own

What kind of codebase is it?

  • No repository access asked for
  • Every buyer answer quotes its own page

Holding years of repositories you no longer ship?

Describe the code, its history and who owns it. We tell you which buyers on the board take that kind of codebase and what to settle before you talk to one.

Sources

This site's own dataset, every figure quoted from its source and dated:

Describe my codebase