A scorebook nobody
can take away
from your club
Open Innings is developed in the open. You can read how it scores, disagree with it in public, fix it, and run your own copy for your league. No licence key sits between you and your own matches.
| 01 | Source | Public | App, sync server and the follower web view |
| 02 | Issues and discussion | Open | Scoring disagreements are welcome and usually become fixes |
| 03 | Pull requests | Open | Rule toggles, translations, format support |
| 04 | Self-hosting | Supported | Run the sync server yourself; no ads, no subscription |
| 05 | Your data | Exportable | The whole ball log, not a summary |
Licensed AGPL-3.0 — clubs may self-host without asking, and any hosted fork must publish its own source in turn.
Every league scores a wide slightly differently
Byes off a wide. Whether a no-ball brings a free hit. Whether the last man bats alone. These are not edge cases in club cricket, they are Sunday.
When the rule is in readable code rather than a support article, your league can point at the line, argue about it, and change it. That is a faster route to a correct scorebook than any feature request queue.
Run the sync server
One small service holds the ball logs and serves the follower links. Point the app at your own host and your league's data never leaves it.
No ad server, no ads
A self-hosted build has nothing to serve an ad from, so there is nothing to remove and nothing to pay for.
Fork it for your rules
If your competition scores something its own way, change it in a fork rather than waiting for a toggle. Upstream the ones others would want.