Score once. Store once. Calculate once. Show everywhere.
CricketOps is a real-time cricket operations, scoring engine, and broadcast platform engineered by SpideyTech. It replaces manual scorebooks, disconnected spreadsheets, and manually manipulated streaming graphics with an authoritative, ledger-backed data engine.
In local, corporate, academy, and district cricket across Bangladesh, scoring is often fragmented. Scorers grapple with unreliable cellular connectivity, tournament administrators struggle to calculate net run rates accurately, and live streamers waste effort hand-updating score bugs in OBS.
SpideyTech engineered CricketOps to resolve this foundational issue: treat cricket scoring as a financial-grade transactional ledger, not a loose set of database records.
Every ball bowled is a permanent, immutable ledger entry. Live scores, career figures, bowling economies, partnership graphs, template commentary, and OBS broadcast overlays are derived directly from this single source of truth. If a delivery is corrected or undone, the engine leaves an auditable trail and recalculates downstream aggregates without silent data loss.
- Authoritative Ball-by-Ball Delivery Ledger: PostgreSQL-backed scoring engine with row-level locks, idempotency keys, and optimistic version checks to eliminate ghost deliveries or duplicate counts.
- Real-Time Synchronization: Django Channels publishes live WebSocket events to all clients in sub-second latency only after the database transaction commits.
- Plug-and-Play OBS Overlays: Dedicated, low-overhead browser sources for OBS Studio and PRISM Live Studio, rendering clean TV-style score bugs with custom team logos and sponsor spaces.
- Offline-Resilient Mobile Scoring: Built with Flutter, allowing scorers on fragile mobile networks to queue commands locally and synchronize without state drift.
- Configurable Rule Profiles: Versioned rulesets supporting Limited Overs (T20, ODI), Tape-ball, and customized local tournament conditions.
- Audited Correction Engine: Undo and edit past balls safely with complete recalculation of strike rotation, bowler figures, and over boundaries.
- Tournament & Operations Hub: Fixtures, points tables, net run rates, player claim verification, and integrated local commerce (SSLCommerz).
CricketOps is designed as a modular monolith, keeping domain boundaries clean without the unnecessary operational overhead of premature microservices:
+-------------------------------------------------------------+
| Client Layer |
| • Next.js Web (Public Scorecards & Admin Portals) |
| • Flutter Mobile App (Scorer Console & Fan Center) |
| • OBS / PRISM Studio (Live Browser Source Overlays) |
+------------------------------+------------------------------+
| HTTPS / WebSockets
v
+-------------------------------------------------------------+
| Django ASGI Application Core |
| +-------------------------------------------------------+ |
| | REST API (DRF) Django Channels Consumers | |
| +-------------------------------------------------------+ |
| | Scoring Domain Engine • Rule Profile Matcher | |
| | League Administration • Billing & Entitlements | |
| +-------------------------------------------------------+ |
+---------------+-----------------------------+---------------+
| |
v v
+-------------------------------+ +-------------------------+
| PostgreSQL 16 (Primary) | | Redis 7 In-Memory |
| • Delivery Ledger | | • Channels Layer |
| • Audited Corrections | | • Ephemeral Cache |
| • Relational Identities | | • Celery Task Broker |
+-------------------------------+ +-------------------------+
Owner & Maintainer
Developed and Maintained by SpideyTech
Lead Engineer & Architecture: Md. Masum Billah
Dhaka, Bangladesh