Company archives
Sell your company's archive directly to AI labs
Don't let a broker take all the upside. List your code and documents on Graunt yourself, keep the right to sell them again, and get paid every time someone buys.
Why AI labs want it
AI labs train coding agents on how real teams build software. Your code, its history and the documents behind it show that in a way public code can't. It doesn't matter whether the company is still running or has closed, or whether it was a team of fifty or just you.
What you can list
- Your source code. Upload the repository as a .zip, without its .git folder.
- Its history. Every commit's diff and message, with each author shown as Person 1, Person 2 and so on.
- Your documents. Specs, design docs, runbooks and READMEs.
Before you upload
- Take out credentials. Remove .env files, private keys and keystores. Graunt holds a listing that includes one until it's gone, and an example file such as .env.example is fine.
- Make sure it's yours to sell. If the company is still running, it has to agree. If it has closed, whoever owns its assets now does, whether that's you, a buyer of the company's assets, or the person winding it down.
Export your history
Run these four lines in your repository's folder. They give each author a stand-in, write history.patch with the stand-ins in place, and delete the list of who each person is, which they keep in a temporary file outside your repository.
map="$(mktemp)"
git log --all --reverse --format='%aE' | awk '!seen[tolower($0)]++ { n++; printf "Person %d <person%d@example.invalid> <%s>\n", n, n, $0 }' > "$map"
git -c mailmap.file="$map" log --all --reverse --use-mailmap -p --format='commit %H%nAuthor: %aN%nDate: %aI%n%n%B' | grep -viE '^(co-authored-by|signed-off-by|reviewed-by|acked-by|reported-by|tested-by|cc):' > history.patch
rm "$map"Or ask your coding assistant: Export this repository's git history to history.patch with every commit's diff, date and message. Replace every author with Person 1, Person 2 and so on, in the order they first committed, and remove Co-authored-by, Signed-off-by and other lines that name people. Keep the list of who each person is outside the repository, and delete it when you're done. Then list any names or contact details still in the messages or diffs, so I can take them out.
The stand-ins replace each commit's author and its sign-off lines. A name or contact detail written into a commit message or the code stays as it is, so read history.patch for those and take them out before you upload it with your code.
Price it
You enter the price when you list it, and every buyer pays the price you list.
Graunt or a broker
A broker or data buyer usually pays a company once, often takes the right to resell its data, and sells it on to labs at a markup it doesn't share. Many work only with companies of 20 people or more. On Graunt you list it yourself, keep the right to sell it anywhere else too, and get paid on every sale. It's free to list, and you only pay a fee when it sells. Fees
Questions
Is it private until I list it?
Yes. Your upload and draft stay private until you publish, and you can take a listing down at any time. Buyers keep what they've already bought.
Does Graunt run my code?
No. Graunt reads your files as text so buyers and their agents can search them, and delivers them unchanged. Compiled programs aren't accepted.
Can I sell it somewhere else too?
Yes. Listing on Graunt isn't exclusive.
How do I get paid?
Your earnings from each sale are paid out to your bank account through Stripe once your payout account is set up.