Back to Projects
Booking · Business Systems · SaaS
KSTS — Multi-company Bus Booking Platform
A business-focused booking and operations platform designed around shared inventory, multi-office workflows, schedules, trips, passengers, and role-based access.
Shared inventory architectureMulti-office workflowsRole-aware data boundariesReal-time availability design
Overview
KSTS is being developed as a centralized platform for bus-ticket operations. The architecture is designed so authorized offices and sales channels work against the same booking inventory instead of maintaining disconnected seat data.
Current Status
Active development
The Problem
- Booking operations can become difficult to coordinate when different offices maintain separate availability information.
- Seat inventory needs to remain consistent when multiple users interact with the same trip.
- Different organizations and roles require different access boundaries and workflows.
The Solution
- A centralized PostgreSQL-backed application with role-aware access and shared operational data.
- Trip and seat inventory concepts designed for concurrent booking workflows.
- A modular Next.js application structure so booking, fleet, routes, offices, agents, passengers, tickets, and audit capabilities can evolve independently.
Architecture & Engineering
Next.js application layer with server-side business logic and API/server-action boundaries.
PostgreSQL data model for companies, offices, buses, seats, routes, trips, bookings, passengers, and audit records.
Supabase Realtime planned/used as the real-time synchronization layer for seat availability.
Prisma repository/data-access layer for structured database operations.
Technologies
- Next.js
- React
- TypeScript
- PostgreSQL
- Supabase
- Prisma
- Tailwind CSS
Key Features
- Multi-office booking operations
- Bus and seat-layout management
- Routes and trip scheduling
- Seat selection, hold, confirmation, and cancellation workflows
- Role-based access
- Passenger and ticket records
- Agent and commission foundations
- Audit trail architecture
Challenges & Decisions
- Designing booking flows that reduce the risk of conflicting seat state.
- Keeping the data model flexible enough for multiple bus companies and office workflows.
- Separating platform-level permissions from company-level operational access.