🗄️ Data Sources
Criclytics is powered entirely by open, publicly available cricket data. No proprietary feeds. No paywalled subscriptions.
All data is fetched periodically and cached locally. Criclytics does not stream live data in real time — match results and rankings refresh on a scheduled basis.
Historical match data
| Source | What it provides | Licence |
|---|
Cricsheet
cricsheet.org |
Ball-by-ball JSON data for every T20I, ODI, and Test match in the database. This is the backbone of Criclytics — player career statistics, venue analytics, head-to-head records, and the ML training dataset are all derived from Cricsheet data. Updated by the Cricsheet team within days of each match completing. |
CC BY-SA 4.0 |
Live, recent & upcoming fixtures
| Source | What it provides | Access |
|---|
| Cricbuzz via RapidAPI |
Live match list, recent results, upcoming fixtures, venue details, and series metadata. Fetched weekly and merged with the local match cache. |
RapidAPI · Free tier |
| ICC Calendar |
A curated list of confirmed upcoming international fixtures used as a fallback when the live API returns limited data. |
Static / public |
Rankings
| Source | What it provides |
|---|
| ICC Official Rankings |
Team and player rankings for batting, bowling, and all-rounder categories across T20I, ODI, and Test. Scraped from the ICC website and cached locally. Refreshed on demand. |
Player images
| Source | What it provides |
|---|
| CricAPI |
Headshot images for confirmed senior international players. Images are hotlinked from CricAPI's public CDN under their free-tier terms. |
| Wikipedia |
Thumbnail images for additional players via the Wikipedia REST API (/page/summary/). Used as a supplementary source for players not available in CricAPI. |
UI assets
How the data flows
Raw data is fetched from these sources, processed into structured JSON datasets, and served through a local REST API. The frontend reads exclusively from this API — no data is fetched directly from third-party sources in the browser.
- Fetch — Weekly scripts pull live fixtures and rankings from the sources above.
- Process — Historical Cricsheet data is parsed into per-player, per-venue, and per-team analytics datasets.
- Serve — A lightweight Flask API serves the processed data to the frontend.
All third-party data is used in accordance with the respective source's terms. Cricsheet data is used under the Creative Commons Attribution-ShareAlike 4.0 licence. If you have a data attribution concern, please contact us.