Futsalaki
A futsal court booking platform for Cyprus — and the matchmaking layer that fills the empty slots.
Cyprus has futsal courts sitting empty and players with nobody to play against. Futsalaki closes both halves of that gap: venue owners list and manage their pitches from a web dashboard, players book from their phone, and when a team can't fill a slot the app finds them an opponent instead of letting the booking die.
It's one product with two clients — a mobile app for players and a web dashboard for venues — built as a monorepo so they can never drift apart.
The problem
Futsal venues in Cyprus were managing bookings over the phone and losing money on empty slots, while players who wanted a game had no way to find an opponent. Two sides of the same market, neither served.
What I built for each side
Venue owners got a web dashboard — pitches, pricing, calendar, customers — so a booking takes seconds instead of a phone call. Players got a mobile app to book, build teams and get matched against other teams at their level when they can't fill a squad.
What it changes
A half-empty booking becomes a real game instead of a cancellation, payments split automatically between the platform and the venue, and the venue's calendar fills itself. Live today on the App Store and Google Play.
- One monorepo (npm workspaces + Turborepo) holds the mobile app, the venue dashboard and shared packages for types and the database client — a schema change and both clients that depend on it ship in the same commit, so the two ends of the product can't fall out of sync.
- The data is relational on purpose: teams, members, matches, venues and bookings reference each other constantly, so it's PostgreSQL with foreign keys rather than a document store I'd have to keep consistent by hand.
- Business rules that must never disagree between clients live in the database itself as functions — joining a team by invite code, generating a fresh code, resolving a match score — instead of being re-implemented in two codebases.
- The score system assumes people will disagree: both captains report independently; matching reports auto-confirm through a database function, mismatches escalate to review, and no submission ever silently overwrites the other. If one side never responds, the reported score stands after a window.
