Building Lily SportOS: a SaaS for sports clubs

Lily SportOS is a platform for sports clubs in Ukraine that I design and build myself. Here is why it exists and the decisions behind it.

Where the idea came from

Sports clubs deal with a lot of people: athletes, parents, coaches, competition organisers. Yet most of their processes live in spreadsheets, group chats and paper logs. Payments are tracked by hand, an athlete’s history is scattered across different places, and organising a tournament takes a huge amount of time.

I wanted one system that covers all of this, built not for a single club but for many.

Multi-tenant from day one

The key architectural decision: every club gets its own workspace with separate data, settings and roles. To the user it feels like their own system; for me it is one platform that I can update for everyone at once.

Setting up this architecture from the start is harder than building for a single client. The payoff is that nothing needs rewriting when the second, third and tenth club arrive.

What the platform does

Payments. Online payments via Monobank Acquiring with automatic status tracking, no more checking transfer screenshots.
Tournaments. Organising competitions, including events that bring several clubs together.
Athlete passports. Each athlete’s history and achievements in one place.
Admin panels. A club manager sees everything that is going on and runs it without technical knowledge.
Telegram Mini Apps. No separate app to install: everything opens right inside Telegram.

Infrastructure

The platform runs on my own VPS in Docker Compose containers. That means control over the data, predictable costs and fast deployment of updates.

What this means for clients

When you build your own product, you are responsible for everything: architecture, stability, usability and support. I bring that experience into client work. Even a simple bot is designed so it can grow into a complete system without starting from scratch.

You can read more in the case study.