Enterprise & Workflow · Conversational AI, health, gaming, doc-scanning, ed-tech, travel, restaurant SaaS, HR-tech…

Organisational Supply: 14 Company Codebases + Ops Data

Codebases and operational data from 14 companies across conversational AI, health, gaming, ed-tech, travel and HR-tech.

CODE + ENTERPRISE · 14 ORGS · ~580 REPOS · 16.7M LOC
AvailabilityLead (metadata only)
14companies
~580repos
~16.7MLOC
Request sampleRequest custom version
Rights pending
01

Preview

Company AConversational AI · code, call recordings
Company BHealth · code, Jira, DB
Company CGaming · code, Slack
Company DDoc-scanning · code, DB
Company EEd-tech · code, video
Company FTravel · code, email
Company GRestaurant SaaS · code, DB
Company HHR-tech · code, Slack, Jira
Companies I-N6 more, details on request
Preview · anonymised cards
02

At a glance

Volume~580 repos, ~16.7M LOC; ops data est. up to hundreds of TB (email, Slack, Jira, DBs, call recordings, video)
FormatsGit repos · workspace exports · DB dumps
LanguagesTypeScript, JavaScript, Java, Python, Go, Kotlin, Swift, PHP, Dart
AnnotationSealed repo-quality reports
Licence statusRights pending
AvailabilityLead (metadata only)
Date addedOct 12, 2026
Update cadencePer company on clearance
03

Provenance ledger

Rights / consentPending
PII handlingScrub before preview
QA statusNot started
LicenceRights pending

No supplier, broker, client or personal names appear on this page or in its samples. Previews are Perit-owned copies with container metadata stripped.

04

Schema and anonymised sample record

{
  "repo_id": "PD-020-r007",
  "primary_language": "TypeScript",
  "lines_of_code": 58214,
  "commits": 4113,
  "first_commit": "2016-04-02",
  "last_commit": "2026-08-19",
  "test_files": 212,
  "ci_configured": true
}

The record above is synthetic: the field list and types are the real delivery schema, the values are not from the set. Full field documentation, including every optional column, ships with the pilot batch so you can write the loader before the data lands.

05

How delivery works. Four steps, and the first one is a request.

01 · Day 0RequestTell us the set, the use and the volume.
02 · 48 hoursSpec and quoteWritten spec, rights summary and price.
03 · 1-2 weeksPilot batchA QA'd slice in your data room to test against.
04 · OngoingDelivery to your bucketFull set or scheduled drops, same schema.
06

Related datasets

Enterprise & Workflow · PD-028Enterprise Workflow Data (Slack / Email / Tickets)ENTERPRISE · JSONL · EN · COLLECTINGCollectingCode & Agentic RL · PD-009Agentic & Long-Horizon Benchmark TasksENV · 11 FAMILIES · ZIP · GRADEDSample availableCode & Agentic RL · PD-014Logistics & E-commerce Production Code ExcerptsCODE · JAVA · PYTHON · 1,443 LOC SAMPLELead (metadata only)
Access

Tell us the run, and we will tell you what clears for it.

Written spec, rights summary and price inside 48 hours, and a straight answer on anything still in review, including when the answer is that it will not clear.

Request this setBack to the catalogue