micro1
$100K entry tier
Engineering workflows, bug tracking and code documentation. 30+ full-time staff. Pays within 30 days of acceptance.
AI labs and their data suppliers license private repositories, review threads and issue history. We tell you which buyers fit your codebase and what each one publishes about pay, rules and exclusions.
Agit log
a41f2c9 fix: retry webhook on 502
dana@acme-billing.io
PR #812 review by @mkhan
"move the backoff into the client"
CI passed · 214 tests
.env AWS_KEY=AKIA4F...Bscrubbed
a41f2c9 fix: retry webhook on 502
author_014
PR #812 review by reviewer_03
"move the backoff into the client"
CI passed · 214 tests
.env removed, key rotatedClicensed
Dpaid
< 21 days
Labelbox Prism's own claim for first call to wire.
micro1 pays in full within 30 days of acceptance.
Invented example. The commit, names, email and key are made up.
Two routes
A running company licenses copies of its history and keeps building. Programs for live companies set staff minimums. A closed company realizes its code on the way out, usually bundled with workspace exports, and the first question is who may sign.
Operating company
License the history, keep the product
Staff floors: none at Prism, 20 US W-2 at Nyne, 30 at micro1, 40 preferred at Scale AI.
Wound-down company
Code plus Slack, Drive, Notion and Figma
Lenders, investors or an ABC assignee may stand between the founders and the signature line.
What's in, what's out
Your public packages are already downloadable. The private history, the arguments in review and the path from ticket to fix are not. Every buyer listed here promises to strip personal data; scrub it yourself first anyway.
repo-contents.diff
The paper you sign
Most operating companies license; most outright sales come from wound-down companies or their assignees. Exclusivity and field-of-use clauses decide how much a license really leaves you.
License
Sale
Each set of terms comes from the buyer's own site. The full comparison adds personal data handling and payment timing.
$100K entry tier
Engineering workflows, bug tracking and code documentation. 30+ full-time staff. Pays within 30 days of acceptance.
From about $50K
Traces of code being written and edited. No size threshold. Cash at signing, then a revenue share; exclusive by default.
$10K to $1M+, illustrative
Jira, Confluence, docs and chat. Ideally 40+ people. Will not take credentials or repo access.
$100K and up, usually
Jira and Asana projects, tickets and CRM. Twenty-plus US W-2 staff and a 3-year record.
Repos with their docs and tests, plus the workspace around them. Each dataset is scrubbed for personal data before licensing. For founders closing their company with SimpleClosure; no pay figures published.
Disclosure: some of these companies pay referral fees, and one could pay us after a deal with a company we introduced. That has no say in which buyers appear here or how we describe them.
Usually less than the headline numbers, which describe whole-company partnerships with staff minimums.
Published and reported figures only, never an offer; real license fees often come in far lower. The code value tool filters them by team size, history and what your repos hold.
01Repos, years, committers, and the signed agreement behind every contractor. Tag anything third-party or client-owned.
02Rotate and purge secrets, pull customer records out of fixtures, drop vendored packages before a single file leaves.
03Learn what the buyer wants and how it strips identities. Scale works on your side and asks you to approve each package.
04License or assignment, scope, field of use, exclusivity, term. Your counsel marks it up before anyone signs.
05Data moves on the agreed terms, then payment follows on each buyer's schedule.
None of them is about price.
You can only license code the company owns or may license. Staff work under an invention assignment normally counts; contractor work counts only where the contract assigns it.
Open-source packages remain under their own licenses and fall outside anything you grant.
So does customer personal data, unless your contract and the applicable law both permit it.
Investors, lenders and acquirers, most often after a wind-down. Read the financing papers.
Buyers de-identify too, but only your pass happens before anything leaves.
Every agreement goes to your own counsel before signature.
Short answers. The blog and the buyer comparison go into each in depth.
Yes, provided the company holds title to it. A live company tends to license history and engineering records (micro1 and Labelbox Prism both list that kind of material). A closed one can go through SimpleClosure AssetHub, which handles code and workspace exports in a wind-down. Your open-source packages and anything a client owns never form part of the deal.
On the buyers' own pages, entry points sit near $50K at Labelbox Prism and $100K at micro1, both aimed at companies above a staff minimum. Press coverage gives one closed-startup price: about $25,000, reported by MIT Technology Review. Treat every figure as a ceiling to test, never an offer; real license fees often come in far lower. The code value tool lines them up for your case.
A private repo, yes, if the company owns the code. What buyers pay for is what could never be scraped: the commit history, review threads and issues that run from report to fix. Public packages are already downloadable, and code a client owns stays out. Most buyers work from exports you deliver rather than access to the repo itself.
Not if you license. micro1 states plainly that the seller keeps ownership of the underlying data. The clause to watch is exclusivity, which Prism makes its starting position. Selling the IP outright is a different deal, usually made by a wound-down company or its assignee.
Often, yes. SimpleClosure AssetHub takes repos together with the Slack, Drive, Notion and Figma exports during a wind-down, and micro1 keeps a track for defunct companies. The first question is who may sign: the holder of the IP, which could be the company, a secured lender, an ABC assignee or a buyer of part of the business. Selling a shut-down startup's code.
You can license the code your company wrote and owns. The packages you depend on stay under their authors' licenses, so you have nothing to grant in them, and that includes snippets pasted into your own files. Have your own counsel read the agreement. Open source and licensing.
Not necessarily. Scale AI does its anonymizing on your infrastructure, and repo access and credentials are on its refusal list. Other buyers work from exports you deliver. Get the method in writing before you add anyone to the org.
ZIP, contact, then eight multiple-choice questions about the repos. Your answers get held up against every buyer's published rules, and the matches come back to you by email, by name.
No code, repo URLs, exports or samples here, please. Answers only; we do not want your data.
We run an introduction service, and a buyer you end up signing with may pay us for the introduction. You are not charged.