Home / About
About CricketLogic
CricketLogic builds cricket software from ball-by-ball data. We make three things: the open-source CricketLogic engine (this site) — a Python library that turns Cricsheet ball-by-ball YAML into a queryable DuckDB warehouse; IPLTracker, the IPL companion whose every number is computed first-party by that engine; and Crichit, our arcade cricket games. The engine exists so developers and analysts can work with delivery-level cricket data in SQL — and so the companion and the games run on data we compute ourselves.
Who is it for?
Data engineers, analysts, fantasy modellers, researchers and anyone building a cricket stat or companion site who needs clean, structured, reproducible cricket data.
What it is not
- → Not a live scores or odds feed — it works on Cricsheet historical ball-by-ball data.
- → Not affiliated with the BCCI, the IPL, ESPNcricinfo or Cricsheet.
- → Not a hosted API you pay for — it runs locally on your own DuckDB file.
Key facts
| Project | CricketLogic |
|---|---|
| What it is | Open-source Python library — DuckDB cricket data warehouse |
| Language | Python (>= 3.11) |
| Storage engine | DuckDB |
| Data source | Cricsheet ball-by-ball YAML / JSON |
| Install | pip install cricketlogic |
| License | MIT |
| Repository | https://github.com/cricketlogic/cricketlogic |
Data credit
Ball-by-ball match data is sourced from Cricsheet.org. Analytics are computed by the CricketLogic engine. Storage and querying are powered by DuckDB.
Maintained by Dipankar Sarkar · me@dipankar.name · GitHubLast updated 2026-07-02