For AI companies
Engineering data with a paper trail.
For coding-model developers, agent companies, evaluation providers, and enterprise AI teams that need data they can explain — to their researchers and to their counsel.
Where this data is used
Each use has its own licence scope, so you only pay for — and are only bound by — what you need.
Coding models
Pre-training and fine-tuning on real change histories, reviews, and tests from commercial codebases.
Coding agents
Trajectories and issue-to-fix loops that show how engineers navigate, edit, and verify.
Evaluation
Held-out, executable task suites kept out of public corpora to limit contamination.
Reward modelling
Review outcomes and accepted-vs-rejected revisions as preference signals.
Enterprise AI
Domain-specific engineering data for internal assistants, licensed for internal use.
Research
Scoped research licences for studying code-model behaviour.
From requirements to delivery
- 01RequirementsData types, languages, volume, intended use
- 02 · decisionSourcing & reviewSuppliers matched; rights and QA recorded
- 03Sample evaluationTime-limited access once we approve your request
- 04LicenceWritten scope, term, exclusivity, and price; signed online
- 05AccessPay the invoice, then read-only access to a private copy of the repository
What you receive
Every engagement comes with a documented record
- A dataset card on the listing: contents, schema, version, and known limitations
- The rights review on the listing: source, restrictions, permitted uses, and review scope
- The quality checks run on the licensed version (counts shown only when verified)
- A written licence defining scope, term, exclusivity, and permitted uses
- Read-only access to a private copy of the reviewed repository, for the GitHub or GitLab accounts you choose
- Catalog licence
- License a listed dataset version on agreed terms
- Custom sourcing
- We find suppliers and data to your specification
- Preparation
- Scrubbing, normalisation, filtering, splits
- Recurring
- Ongoing refreshes where suppliers can provide them
Our commitments
What we will and won’t say
We will
- Describe what we reviewed and what was out of scope
- Show limitations alongside strengths
- Tell you when we can’t source what you need
We won’t
- Promise model performance improvements
- Claim a review is a legal guarantee
- Publish record counts or quality scores we haven’t verified
Questions buyers ask
What kind of data do you provide?
Can I see data before committing?
How is pricing set?
Do you guarantee the data will improve my model?
Is the data legally cleared?
Start with your requirements.
A short form, then a conversation. No commitment until there’s a written proposal you’ve agreed to.