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

Can I sell iOS app source code?

Sell iOS app source code by licensing it to AI labs. Swift and Objective-C iPhone apps qualify. Keep the app and get paid each time it is licensed.

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

Lot 022Founder ownedSpecimen

iOS fitness app, paused 2022

26,400 lines. A workout tracker with 9,000 downloads. The founders took day jobs and the repo went quiet.

Languages
Swift
Lines of code
26,400
Commits
4,180
Source tokens
0.3M
History tokens
30.5M
Last commit
Sep 2022
Source 0.3M · 1.0%History 30.5M · 99.0%
Commits per quarterActivity stopped Q3 2022
Per license, USD0.3M × $100 + 30.5M × $40≈$1,250recurring
Illustrative lotNot a live listing
Quick answer

Yes, Swift and Objective-C iPhone apps you own can be licensed to AI labs, live or paused. You sell a license and keep the code and the App Store listing, 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 iPhone app's source code?

Yes, if you hold the rights. iOS repos are useful to AI labs because Swift code is less common in public training data than web code, and real apps carry years of changes through new iOS versions, devices and APIs.

The app stays yours. Your App Store listing, users and updates are unaffected, and the code is never published. It suits the fitness tracker that went quiet when its founders took day jobs as well as apps you still ship.

Do I need to keep my Apple developer account?

No. Licensing works on the code in your Git repos, so it does not matter whether your developer membership lapsed or the app was removed from the App Store. Keep the repos and their history, and keep any shared code such as a backend or a companion web app. Certificates, provisioning profiles and keys that were committed are stripped from the review copy before a buyer sees it.

Apps that moved from Objective-C to Swift are especially useful, because the history shows a real migration done by a real team. Keep that history intact. Do not squash it or start a fresh repo before you connect.

Qualifies
  • Swift and SwiftUI apps
  • Older Objective-C apps
  • Apps paused or removed from the App Store
  • Watch, widget and extension targets
Stays out
  • Apps built for a client who owns them
  • Certificates and provisioning profiles
  • Third-party pods and packages, which are excluded
§ 02What it is worth

How much is iOS app source code worth?

Value per license is source tokens at $100 per million plus history tokens at $40 per million. The specimen lot above, a paused Swift fitness app with four years of commits, shows the working. A typical repo earns 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.

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