Every dataset is rights-reviewed before it’s listed

Engineering data you can explain to your counsel.

We source, review, and license software engineering datasets for teams training coding models, agents, and evaluations — each with a written record of who owns it and what it may be used for.

Popular:Code & test-case pairsCode changes & PR metadataCode review & debuggingEngineering workflow traces

How it works

A managed marketplace, run by people who check the details

  1. 01Tell us what you needRequirements — data type, languages, volume, intended use — or browse listed datasets.
  2. 02 · decisionWe source and reviewVetted suppliers; rights review and technical QA recorded.
  3. 03Evaluate a sampleA time-limited sample once we approve your request.
  4. 04Sign, pay, get accessWritten licence signed online; pay by card or bank transfer; read-only access to a private copy of the repository.

Who it’s for

Two sides, one standard of evidence

For AI companies

Data you can explain to your counsel

  • Datasets described honestly — contents, checks performed, and known limitations
  • Structured rights records: owner, licences, restrictions, and permitted uses
  • Custom sourcing when the catalog doesn’t have what you need
  • Preparation to your schema: de-duplication, scrubbing, splits
For AI companies

For data owners

License engineering history you already own

  • You decide which uses you will license, and on what exclusivity
  • We handle buyer qualification, negotiation support, and contracts
  • Preparation help: secret scanning, PII removal, formatting
  • Withdraw from new licensing at any time, subject to existing agreements
For data owners

Data preparation services

From raw engineering history to training-ready data

Preparation is available to suppliers getting data ready for licensing, and to buyers who need data in a specific shape.

01

Scrubbing

Secret and credential detection, PII removal or pseudonymisation.

02

Normalisation

Consistent schemas across repositories, trackers, and review systems.

03

Filtering

Licence-based filtering and de-duplication; benchmark contamination screening on request.

04

Packaging

Train/eval splits and documentation, delivered as a private read-only repository.

Explore preparation services →

Trust, provenance, and quality

No listing goes live on a single checkbox

Rights review, technical QA, and publication are tracked as separate decisions. A dataset is listed only when both reviews have passed, and every published version is fixed — a material change creates a new version that goes back through review.

We never infer that public or open-source code can be relicensed for any purpose. We check the licences, contributors, and agreements that apply to each source and each intended use, and we record what our review did and did not cover.

How our review works →

Recorded for every dataset version
Legal owner
Who holds the rights
Authority
Submitter’s authority to license
Inbound licences
Open-source and third-party terms
Restrictions
Employer, client, NDA obligations
Permitted uses
Pre-training, fine-tuning, evaluation…
Review scope
What was — and wasn’t — reviewed

FAQ

Common questions

What kind of data do you provide?
Software engineering data for coding models, AI agents, and evaluation: issue-to-fix histories, code changes and pull-request metadata, review and debugging examples, code–test pairs, evaluation suites, and authorized engineering workflow traces. Availability depends on what suppliers can license; we also source to specification.
Is the data legally cleared?
Every listing goes through a documented rights review of ownership, licences, restrictions, and permitted uses, and the scope of that review is recorded. A review reduces risk; it is not a legal guarantee. Your licence agreement sets out the warranties that apply.
Do I upload my repositories?
No. You connect the GitHub or GitLab repository that holds the data from your account, read-only, and we never change it. Reviews, the buyer sample and the copy licensees receive are all taken from it. Never send data or source code by email.
How am I paid?
You receive at least 70% of each licence fee, as set out in the supplier agreement, paid by Stripe transfer or bank transfer after the buyer has paid. We do not promise any level of earnings.
Open-source code is public — can’t it be used for anything?
Not necessarily. Open-source licences carry conditions, and code may include third-party material or be subject to contributor, employer, or client obligations. We assess these for each source and intended use.

All questions →

Tell us what your models need to learn.

Share your requirements and we’ll come back with sources, samples, and a written proposal — or tell you honestly if we can’t help.