KRIDAXA
Book | Connect | Rise
A two-sided marketplace for sport. On one side, players find and book venue slots, join open matches, organise groups and buy coaching. On the other, venues and coaches get the scheduling, pricing, invoicing and settlement machinery that makes any of it possible.
The problem it solves
Most venues run their bookings on a phone, a notebook and a group chat. That works until two people are promised the same pitch at the same hour, or a refund is owed and nobody can say how much, or the month ends and the numbers do not reconcile.
KRIDAXA replaces that with a system of record. A slot is either held or it is not. A cancellation applies a stated policy and produces a figure before anyone commits. Every rupee that moves leaves an invoice and a settlement line behind it.
Why it is the portfolio piece
It is not a demo. It handles real bookings and real money, which means it has had to survive the parts that are easy to describe and hard to build: contention, partial refunds, GST-compliant invoice numbering, payouts that carry forward, and the long tail of rules an operator actually has.
One platform, three jobs
Each side of the marketplace needs something different, and a booking product that only serves one of them does not survive contact with a real venue.
Players
Find a slot near you, see what is genuinely free, book and pay. Join an open match if you are short of players, or run a group and invite the regulars. Join a waitlist when it is full and get the spot when one opens.
Venues
Publish grounds and pricing, control availability, block maintenance windows, set cancellation terms. See utilisation and earnings, and receive payouts with a statement that reconciles against the bookings behind it.
Coaches
List offerings and availability, sell session packages and recurring series, track attendance. Earnings settle as sessions are delivered, not when a pack is sold, so nothing is recognised before it is earned.
Five layers, one API
Scroll to pull it apart
The parts that were hard
Any booking product can show a calendar. The difficulty is in the rules underneath it, and those are where the engineering actually went.
Slots have to be held correctly when two people tap at once. Refunds have to follow a policy the customer was shown beforehand. Invoice numbers are a regulated sequence and cannot be spent on a document that evidences no supply. Payouts carry balances forward. Group bookings hold several seats that can be released individually.
None of that is visible in a screenshot, which is exactly why it is worth saying on this page.
- StatusLive, taking real bookings and real payments
- SurfacesPlayer, venue, coach and admin — plus a native app
- PaymentsCollected through an authorised payment gateway
- InvoicingGST-compliant numbering, commission and refund handling
- SchedulingRecurring series, group seats, waitlists, reschedules
- Built byPEGVIX Technologies Private Limited
See it for yourself
KRIDAXA is live. Have a look, and if the same shape of problem exists in your business, tell us about it.