Support Reep
Fund the open Register, partner on identity, or commission private work.
The Reep Register is open infrastructure: complete, dated snapshots of the provider-ID crosswalk, free to everyone. Keeping it true is continuous work. Support pays for that work, and every number on this page is one the register produced about itself.
Three ways in
Sponsor, partner, or commission.
The first two fund the open register and are acknowledged on this page. The third is private work, kept apart from the register by design.
Sponsorship
Fund the upkeep.
Individuals sponsor on GitHub from a few pounds a month. Organisations sponsor by invoiced agreement, with a named contact and a logo on this page.
Organisations: from about £500 a month; £1,500–2,500 for a founding sponsor.
Indications for sizing a budget, not a price list.
Data partnership
Make your IDs interoperable.
Contribute identifiers, source access or an API allocation. Your IDs resolve into the same identity layer your customers already use, and the quality feedback comes back to you.
In-kind support is acknowledged exactly like cash.
Contributed identifiers are published only with explicit permission, under the same evidence rules as everything else.
Consultancy
Work with Loom.
Commission identity resolution against sources you control or license: private crosswalks, audits, source onboarding, migration, bespoke rulebooks, operated deployments.
Private deliverables. No change to the public Register.
Priced as work, never as access to data.
Case study
What a data partnership looks like in practice.
First official data partner
SkillCorner asked for an outside view of its identity metadata, then acted on it.
In July, SkillCorner did something most data companies leave in-house. It opened its player and team registry to an independent check. Not the tracking data or physical outputs it sells, but the identity metadata underneath: the names, dates of birth and identifiers that decide which player a row of tracking belongs to. Every provider resolves that layer on its own, and none has an outside view of where it drifts.
What Reep brought was cross-provider triangulation: because their register resolves the same entities from several independent sources, they could point us at specific records rather than general suspicions.
- 853 → 102
- duplicate name-and-birthday groups
- 811
- dates of birth corrected
- 0
- new duplicates created
What support pays for
Four kinds of continuous work.
1,878,719 entities, 6,187,645 provider bridges, 56 provider surfaces, 1,421 competitions. None of it stays correct on its own.
Publication
Cutting and publishing releases.
Every release is generated, gate-checked, measured and promoted weekly. The dated snapshot is what everyone downstream depends on.
Repair
Finding and fixing identity errors.
Duplicates merged, wrong merges split, retired identifiers kept forwarding so nothing that ever pointed at the register breaks.
Coverage
Adding competitions, sources and history.
Coverage grows by finding corroboration across independent sources, never by lowering the evidence bar.
Assurance
Measuring accuracy, hosting the result.
Precision and recall are estimated from independently verified samples and gate each release. Files and API are served free.
Assurance
Accuracy is measured, not asserted.
Random samples drawn from the release and independently verified. The interval is the honest range for the sample size.
Precision
98%95% CI 96.2%–99.3% · n=300Sampled entities that are correct: no two real people fused into one record. Drawn 9 Aug 2026.
Recall proxy
91%95% CI 83.8%–95.2% · n=100Sampled source records that reached the register rather than waiting for corroboration. Drawn 9 Aug 2026.
Corrections
4,030plus 6,039 retiredRecords merged into a survivor, the retired identifier forwarding for good. History is superseded, never deleted.
The upkeep record
Every published release, on the record.
7 releases since the ledger opened on 21 Jul 2026. This is the receipt.
| Release | Published |
|---|---|
| 2026-09-07 20:10Z | 7 Sept 2026 |
| 2026-09-03 12:39Z | 3 Sept 2026 |
| 2026-09-02 08:12Z | 2 Sept 2026 |
| 2026-08-26 22:10Z | 26 Aug 2026 |
| 2026-08-26 18:03Z | 26 Aug 2026 |
| 2026-08-20 10:34Z | 20 Aug 2026 |
| 2026-07-20 23:52Z | 21 Jul 2026 |
Current release 2026-09-07 20:10Z, built from 31 sources across 429 competition slices. Generated from the release, not entered by hand.
Data partners
What a provider gets, and what stays yours.
A data partnership makes your identifiers resolve alongside everyone else's. You get the quality feedback. You keep your content.
Easier adoption of your IDs.
Customers already hold Opta, Wyscout, Transfermarkt, StatsBomb and internal IDs. Yours resolve into that layer instead of becoming one more mapping table they maintain.
External identity QA, free.
Suspected duplicates, stale IDs, date-of-birth conflicts and role confusion found in your data come back as private correction packets. They are yours to keep.
Coverage gaps that matter.
Gaps tied to countries, competitions and entity types, not a flat list of missing names. A roadmap input, not a scorecard.
We never republish your content.
No scouting data, ratings or evaluated positions. Only the identifying facts that resolve an entity: names, nationalities, participation, basic match details.
What only you cover stays private.
Entities no one else carries cannot be cross-referenced, so by default we hold them privately. Being the open source-of-record is your choice.
The public surface is only the mapping.
ID-to-ID bridges plus facts corroborated across independent sources. Raw mirrors, review evidence and provider payloads never leave the private layer.
Publication needs your permission.
Open bridges are distribution, not leakage. Contributed identifiers go public only when you say so.
First data partner. Sanctioned API access to SkillCorner's identity registry; Reep returns regular data-quality findings. Named here as a provider sponsor for the whole term; the partnership never delays or softens a notice or correction concerning SkillCorner.
Read the case study
Acknowledgement
Who supports the register.
Organisations
- SkillCornerprovider sponsorin kind
In use
What people using it say.
This really helps going forward in our id mapping process. I really appreciate the work of your platform — I think this is something that the whole football data community needs.
Independence
Support never buys control.
Sponsors, partners and clients get acknowledgement and updates. Register decisions follow the published evidence rules, whoever funds the work.
- Favourable identity, confidence or correction decisions.
- Suppression or advance private handling of a public correction.
- Exclusive fields, provider bridges or earlier release access.
- Exclusion or demotion of another provider.
- Coverage work designed for one supporter's private advantage.
- A provider sponsor is named as such, and its support never delays or softens a provider notice or public correction about it.