How One Founder Builds a Live Sports Platform Without a Database Team
Gabriel Gil Graña is building Xeito, a live sports platform, without turning database infrastructure into the work.
Xeito started as a small script for coordinating squash matches in Malta. Less than a year later, Gabriel Gil Graña is building a live sports platform for clubs, teams, and players.
The product already handles leagues, match results, standings, payments, player workflows, and live scoring. During league nights, referees submit points from the court while players watch the standings change.
That is a serious data product. But Xeito does not have a database team behind it. Gabriel is keeping the product moving by letting Prisma handle the defaults that would otherwise eat his build time.
I really wanted to spend time creating features and not having to deal with memory, pool connections, storage limits, replicas, backups.
That is the core of the story: Xeito needs a real data layer, but Gabriel's attention belongs on the product.
What Xeito is building
Xeito helps racket-sports communities manage the work around a match: availability, rosters, leagues, scores, standings, registrations, payments, and events.
In the demo, it already looked far beyond a scheduling tool.
The live referee workflow is the technical proof point. Xeito sends many queries that need fast responses while players are watching the standings update.
Prisma has always been able to cope quite well without me having to worry about anything that happens in the background.
For a small team, that matters. Sports software looks simple from the outside, but the data model keeps growing: clubs, players, teams, rosters, calendars, lineups, matches, points, standings, payments, notifications, and live streams.
Why Prisma
Gabriel had used Prisma professionally before, but Xeito was the first time he used Prisma for the data layer in one of his own products.
The deciding factor was not a long checklist. It was the way Prisma keeps the data model visible, explicit, and connected to the application.
Prisma for me was the winner because of the schema. The way of modeling the data kept very, very tight with the code.
With Prisma ORM, the schema becomes the place where Gabriel defines how the product works. The model translates into migrations, and the generated client keeps application code strongly typed as the product changes.
That matters because Xeito keeps expanding. A tournament workflow adds registrations and schedules. A live scoring workflow adds points and standings. AI coaching will add match analysis, statistics, heat maps, and recommendations.
Prisma Postgres gives Gabriel a managed path for the database layer, while Prisma ORM keeps the model close to the code. The combination lets him spend more time on Xeito and less time managing database operations by hand.
The stack
Xeito runs on a simple, modern stack:
- App: Next.js on Vercel
- Data access: Prisma ORM
- Database: Prisma Postgres
- Prisma's role: Keep schema, migrations, typed queries, pooling, backups, and database defaults off the critical path
That last part is the value. The database is still critical, but it does not become the work Gabriel has to sell to users.
What comes next for Xeito
Next comes tournament software: brackets, schedules, venue screens, organizer controls, and notifications. After that comes AI coaching: match analysis, player statistics, heat maps, and recommendations.
Both depend on the same thing: a data layer that stays easy to change as the product gets more ambitious.
Build the product, not the database team
Xeito is a good reminder that "small team" does not have to mean "small product."
For Gabriel, the priority is clear: work on features, make the product better for players and clubs, and let Prisma handle the database defaults every serious product needs.
That is the platform promise Prisma should make to builders: make me successful by default, keep the escape hatches visible, and let me keep building.
Building a data-heavy product with a small team?
Start with Prisma ORM and Prisma Postgres. If you want the app and database in one Prisma project, explore Prisma Compute. If you want to see where Prisma's type-safe data layer is heading next, try Prisma Next.
Keep reading
Deploy Prisma Apps with create-prisma
create-prisma now scaffolds Compute-ready Prisma apps with prisma.compute.ts, compute:deploy, Prisma Postgres, and Prisma Skills add-ons.
Introducing Create-Prisma: Start a Prisma App With One Command
create-prisma is a new CLI that creates an app with Prisma set up, a starter schema, seed data, database scripts, and optional Prisma Postgres setup.
Build your next app with Prisma
Start free. Scale when you’re ready.