Built on the pool deck, not in a boardroom

Hajos started with a simple frustration: the software that runs high school swimming is clunky, expensive, and stuck decades in the past. Every step was an export and an import. Entries lived in tools only one person understood. At a pool with no timing system, results sat until whoever had the file got around to exporting them. And parents paid a subscription to watch their own kid’s time show up on an app that barely worked. Results from a public high school meet, behind a paywall.

So I rebuilt it, from the water up.

I coach high school swimming, and I built Hajos because everything lived on someone else’s laptop. The meet ran on a Windows machine only one person could open. Collaboration happened in email threads. Event requests came in through a Google Form. If something was wrong on the deck, I couldn’t fix it from my phone. And years of results sat locked on a computer that belonged to whoever ran the meet, not to the team. None of it needed to be that way. Now it’s all online, and it belongs to the team, the school and the district, not to the coach who happened to have the file.

What we hold to

01

We’ve run the meet

Every feature is shaped by someone who’s stood on deck at 6am, not just read a ticket.

02

Fair by default

The public side is free. We don’t charge families to watch their swimmers race.

03

Fast where it counts

On race day, seconds matter. The tools stay out of the way and just work.

04

Made with care

Down to the mascot. If we’re going to put our name on it, it should feel good to use.

There’s a reason for the name

Alfréd Hajós won the first Olympic swimming gold in 1896, then spent his life building pools and stadiums. We’re named after him.

Why we’re called Hajos →