For IT service firms and software houses
Sell your IT company's code and ticket data to AI labs
Coding agents learn from real repositories with their history: the ticket that asked for a change, the design doc, the commits and the review. IT service firms and software houses hold years of exactly that. Lodex licenses a cleaned copy to AI labs.
What is your data worth?
IT services
What AI labs buy
Private repositories with history
Commits, branches, pull requests and review comments, so a model can see how code changed and why.
Tickets linked to code
Issues with reproduction steps that link to the commit that fixed them. Labs turn these into training tasks for coding agents.
Design docs and decision records
Architecture documents, technical specs and the decision records that explain trade-offs.
Incidents, postmortems and runbooks
What broke, how the on-call engineer found it, how it was fixed and what changed afterwards.
Service desk resolutions
How your first and second line solve requests and escalate them, from internal tickets and knowledge base articles.
Migration projects
Legacy systems moved to a new stack, with the plans, test results and fixes along the way.
Payouts
What a sale can pay
The size of a payout follows the data: how many teams, how many years, how hard it is to find elsewhere.
From €10K
One team, standard workflows
A single workspace or department: tickets, deals, invoices, documents.
€50K+
Several teams or years of history
Multiple departments, or a long, consistent record of how work got done.
€250K+
Specialised operations
Expert work AI labs can't source elsewhere: niche processes, regulated workflows, rare skills.
What drives the price
Code with its context is worth more than code alone. A repository where tickets, reviews and commits link up lets labs build tasks from it. Long history, real tests, less common languages and platforms such as COBOL, ABAP or embedded C, and comments or tickets in a language other than English all raise the price.
Payouts range from €10K–€600K. The final offer depends on your sources, their volume and quality, and our review.
- Companies from 10 people
- Built for European companies
- In 8 languages
- GDPR-first: personal data removed before packaging
How it works
- 01
1 minute
Get your estimate
Enter your headcount, founding year and revenue. Your range updates as you type.
- 02
20-minute call
Book a call
We go over your sources with you and agree in writing what's in and what's out.
- 03
Read-only access
Secure handover
We connect read-only to the sources you approve and strip customer details during processing.
- 04
7 days
Get paid
Once your data passes review, the money is in your account within 7 days. Nothing more to do.
What we promise
You keep your data and you decide what goes. Here is exactly what we promise.
It's data you already have
Years of records already sit in your tools. Selling a copy costs you nothing and changes nothing about how you work.
Nothing goes out unpaid
Buyers see redacted samples only. The full package is released after they pay.
Never to your competitors
We license only to AI labs and research teams, under contract. Nothing is ever published.
Cleaned before it leaves
Names, customer details and other identifiers are removed during processing. Buyers never learn who your customers are.
Secure end to end
Read-only, encrypted connections. Originals are deleted once processing is done.
You decide, in writing
You approve every source and sign the terms first. Nothing is sold without your sign-off.
What stays out
Client-owned code
Code where the client holds the rights, or where your contract forbids reuse, stays out. Many service contracts transfer rights to the client, so we check this first.
Secrets and credentials
API keys, passwords, tokens, connection strings and certificates are detected and removed from code and history.
End-user data in logs and tickets
Names, email addresses, IP addresses and other personal data in logs, test data and tickets are removed.
Third-party and open-source code
Vendored libraries and copied code are excluded. You can only license what your company wrote.
Questions
We build software for clients. Who owns that code?
It depends on the contract. Many agreements transfer the rights to the client. Internal tools, frameworks, scripts and products you own outright are usually yours. We go through this with you before anything is scoped.
Do you need write access to our repositories?
No. We connect read-only to the repositories and projects you approve, and access is revoked when the project ends.
What about secrets that were committed by mistake?
We scan the full history and remove them before packaging. We still recommend rotating any key that was ever committed, whether or not you sell data.
Can we include tickets from managed services clients?
Ticket content often contains your client's staff and data, and you may handle it as a processor. Your own runbooks, knowledge base articles and internal tickets are easier to include.
Is internal tooling worth anything?
Yes. Deployment scripts, infrastructure code, test suites and internal tools show how real teams work, which public code often does not.