GSS Tech
Our own products / CricScoreApp

CricScoreApp

Live and open for registration

Open ground cricket, scored properly — not a generic scorer with the wrong rules bolted on.

Live ball-by-ball scoring, full scorecards and complete player stats for the open ground game — a full field and a rope boundary. Free for players, with no login needed to follow a match.

Why the open ground game needed its own scorer

Open ground cricket is scored the way you already call it at the ground — a full field, a rope boundary, and squads that are not always eleven. Generic scorers make you work around their assumptions. This one starts from yours.

01

Rope boundaries

Fours and sixes come off the rope, scored the way you already call them, rather than inferred from a fixed ground model.

02

Byes and leg byes kept straight

Both recorded separately and kept off the bowler’s analysis, so the scorecard adds up without anyone doing sums afterwards.

03

Eight to eleven a side

Overs per innings and squad size are set per tournament, not fixed. Eleven is only the default.

04

Ball-by-ball truth

Every delivery is stored on its own, so scores, extras and statistics are all derived rather than hand-tallied.

Why it is free for players

Somebody has to pay for a portal like this, and it will not be the players. No player fees, no match fees, and no subscription to look up your own cricket — scorecards and statistics stay open to everyone, with nothing obstructive covering the score while a match is being watched.

The paid edge is narrow and deliberate: organisers who want a private, invite-only competition pay for that option, and there is team merchandise for sides who want it. That is the whole model.

Two formats, one platform

CricScoreApp is for the open ground game. BoxCricScore is for box cricket, where the walls are part of the field of play and scoring works differently.

They share a codebase. The format rules, the branding and the domain differ per product, which meant building a genuinely multi-brand platform rather than forking one and letting the two drift apart. That is the same problem we are usually hired to solve for a client with several brands on one system — we had the incentive to get it right here first.

What it does

Ball-by-ball scoring from a phone

One tap per ball at the ground. Wides, no-balls, free hits and every dismissal type, captured as they happen.

Works without signal

Keep scoring when the network drops. Every ball is queued in order and syncs the moment you reconnect, so nothing is lost and nothing arrives out of sequence.

Live scores with no login

Send one link. Followers watch the score update ball by ball — no app, no account, no limit on how many of them there are.

Overlay for a live stream

Point OBS at a single URL and the live score sits on the broadcast, updating itself.

Tournaments end to end

League and knockout stages, fixtures generated in one go, a points table with net run rate, and qualification odds.

Rules per tournament

Overs, squad size and bonus scoring are set per competition, and players can read them on the tournament page.

Statistics that build themselves

Scorecards, player profiles, the points table and an MVP, all derived from the balls that were scored.

A gallery per tournament

Every tournament keeps its own photos, so the moments from the ground stay attached to the competition.

Under the hood

How it is built

  • One platform, two products. CricScoreApp and BoxCricScore run from the same codebase, with the format rules, branding and domain differing per product — which is the same multi-brand problem we solve for clients, solved on our own product first.
  • The scoring engine is isolated and independently testable, so each format’s rules live in one place rather than scattered across the interface.
  • Live scores are pushed over SignalR rather than polled, keeping every follower’s device current without hammering the server.
  • The offline queue preserves ball order rather than just retrying failed requests, because a scorecard that reassembles in the wrong sequence is worse than one that waits.
Frontend Next.js, React, TypeScript, Tailwind CSS
Backend .NET Web API, layered clean architecture
Data Entity Framework Core with code-first migrations
Real-time SignalR, pushing live scores rather than polling for them
Auth ASP.NET Identity with JWT and OTP-based passwordless login
Security Tokens held in httpOnly cookies via a backend-for-frontend layer
Observability Serilog structured logging plus entity-level audit logging

Who it is for

  • Local league and tournament organisers running league or knockout competitions
  • Club, village and corporate teams who want their cricket recorded properly
  • Players who want full batting and bowling statistics, not just the top of the table
  • Spectators and family following a match they cannot attend
  • Organisers streaming matches who want a live score overlay on the broadcast

Built by the team that would work on yours

Same stack, same people, same engineering standards. Tell us what you are building.

Start a conversation