Analytics and monitoring decision
Numbers Game Limited
A small self-hosted replacement is realistic for one competent developer using open-source prior art (listed) to implement ingestion, analytics, storage, and basic UI; the vendor's likely polish, integrations, and data deals would be the primary losses.
Visit website↗Open-source builds that already do this
Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need - the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship. All Numbers Game Limited alternatives, with the arithmetic →
What a replacement has to do
- Ingest match/league data, compute per-player and per-team statistics, store results, render interactive charts/reports, export/share reports.
What it still won’t have
- Polished UX and design polish
- Any proprietary data licensing or paid data feeds
- Built-in integrations with fantasy platforms or one-click imports
- Brand, user base, and ongoing product support
What remains hard
- Product polish and ongoing maintenance
First-year cost
No published price
Numbers Game Limited does not publish a price we could read, so there is nothing to compare against. What building costs is below.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a minimal self-hosted football stats web app using Node.js (Express) + Postgres + React. Core features in scope: CSV/upload ingestion and normalization; input validation and mapping to a canonical match/player schema; background jobs to compute per-player, per-team, and weekly aggregated stats; REST API plus React UI with basic charts (Chart.js) and table views; CSV and PDF export of reports; basic auth (email/password). Out of scope: paid data-feed integrations, multi-tenant billing, and mobile apps. Include error handling, input validation, automated tests for ingestion and computation, and a Docker Compose setup for local development and production deployment.
How we checked
How the score was reached
- Build verdict base78
- An open-source build was found+5
- 3 cited sources+3
- Evidence score86
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.
How scoring works →Cited sources · 3
Every page the run actually retrieved.
- official productNumbers Game | Football Stats Made Easy
- open sourceuberfastman/fantasy-football-metrics-weekly-report
- open sourcejoeyagreco/leeger
Integrity checks
What held up, and what did not.
