Rovify
An operating system for youth sports institutions.
Read by Clubs, leagues, and federations that run youth sports competition and need to trust each other's records.
- Clubs
- Leagues
- Federations
A record that travels with the athlete, not the club.
The problem
A youth athlete's history, which club they played for, which season, what position, what standing, usually exists as a patchwork of team sheets, league spreadsheets, and institutional memory.
Youth sports institutionsA youth athlete's history, which club they played for, which season, what position, what standing, usually exists as a patchwork of team sheets, league spreadsheets, and institutional memory. None of it travels with the athlete.
When an athlete moves to a new club or league, the receiving institution has no reliable way to verify what the previous one is telling them. It either takes the claim on faith or starts the athlete's record over from zero, and neither option serves the athlete or the sport.
What we built
Rovify
Afrikabal designed and built Rovify as an operating system for the institutions that run youth sports: verified athlete records, league and season management, a tournament engine, and governance for how a transfer between institutions happens.
- 01
Verified athlete records, signed and timestamped so a history can be checked by the institution receiving it, not just asserted by the one that wrote it.
- 02
League and season management for the ongoing administrative structure a competition runs on.
- 03
A tournament engine for organizing competition within a season.
- 04
Transfer governance: a defined process for moving an athlete's record from one institution to another.
Engineering notes
Signed and timestamped records
Portability was the actual requirement, not storage. A record that only the club that wrote it can vouch for isn't portable, it just moves the trust problem to a phone call. Signing each record and timestamping it means a receiving institution can verify who asserted what and when, without needing to contact the previous club to confirm it.
Mobile-first for low-bandwidth conditions
Coaches and administrators entering match and season data are often on inconsistent connections, sometimes with a low-end device as the only computer they have. That ruled out a heavy web console as the primary interface and pushed the design toward a mobile-first client built to work with intermittent connectivity: writes queue locally and sync when a connection is available, rather than failing outright.
Transfer as a governed process, not a field update
Moving an athlete between institutions isn't just changing a value in a database. It carries real consequences: eligibility, standing, sometimes a dispute between clubs. Modelling transfer as its own governed workflow, with its own state and approval steps, keeps that change itself part of the auditable record instead of an untracked overwrite.
Building something like this?
The first conversation is a fit assessment: what you are trying to enable, where we could plug in, and whether the shapes match. No sales script.