How Omevision is bringing Sunbenc's travel operations together — collapsing three disconnected applications and two databases into a single, role-aware platform built for buses, shuttles, and conductor-led commute services.
Each part of the operation lives in its own tool, with its own login, its own database, and its own engineering pipeline. That fragmentation has a real cost — in maintenance, in onboarding, and in the data you can't see across.
This single diagram is the entire programme. Three operator apps and two databases collapse into one role-aware mobile app, one web dashboard, and one unified Postgres. Your existing Keshless customer and vendor apps stay connected to the same database they already use today — nothing on their side changes.
Each piece of the operation lives in its own tool with its own data store.
Built on a single platform that already powers Keshless Travels today.
The Keshless Customer App and the Keshless Vendor App continue to talk to PostgreSQL exactly as they do today. The API contracts they depend on stay backwards-compatible. No customer-side changes. No vendor retraining. The consolidation happens entirely on the operator side.
The unified mobile app isn't four apps stitched together — it's a single codebase that recognises who's logging in and shows them only what they need. Every operator, their own focused experience.
A daily-commute trip and a cross-border trip share almost no operational steps. The unified app handles both natively — the conductor's screen rearranges itself to match the kind of route they're working.
Daily commuter routes and cross-border long-distance services have nothing in common operationally — and yet they share owners, vehicles, drivers, and compliance. The unified platform handles both, natively.
Pick-and-drop. No pre-booking. Passengers tap an NFC card or pay cash onboard, and the conductor opens the trip when leaving the rank and closes it at the end of the route — exactly like Malaysia's Touch-n-Go experience, purpose-built for khumbi operations.
Pre-booked seats, manual on-the-spot bookings at the terminal, baggage tagged with QR codes, passenger manifests, real-time GPS, and compliance tracking — built for the long-distance bus services running to South Africa and Mozambique.
The programme spans backend platform, mobile application, web dashboard extensions, shared infrastructure, and the migration itself. Each line below is a concrete piece of work being delivered.
Each phase has a clear deliverable and a clear handover. The work moves quickly — the platform being built on is mature, the team has shipped consolidations like this before, and the programme runs against the existing Keshless Travels infrastructure rather than starting from scratch.
Confirm operational requirements with the client team, finalise the unified data model, and lock down role definitions and trip-mode behaviour.
Build the PostgreSQL schema, migrate data from MongoDB, and ship the new API surface area covering vehicles, passengers, payments, baggage, GPS, compliance, and association management.
Build the role-aware mobile app and integrate the device-side capabilities — NFC tap-to-pay, QR scanning, Bluetooth thermal printing, and offline sync.
Surface fleet, compliance, association administration, and live tracking on the web dashboard for desktop users.
Roll out to a hand-picked group of pilot operators and conductors. Gather real-world feedback, harden offline edge cases, refine flows that only show up in the field.
Train operators, drivers, conductors, and association administrators on the new platform. Run the parallel period and execute the cutover.
Stabilisation, support, and handover. Your team takes over with full documentation, runbooks, and monitoring already in place.
One mobile app to install. One login per role. One unified source of truth across every operator, vehicle, and trip. Onboarding new associations and operators becomes a single workflow instead of three. The whole platform is easier to evolve once it sits on a single codebase and a single database.
The Keshless customer app still books trips. The Keshless vendor app still sells tickets at the counter. The consolidation happens behind the scenes — the apps your customers and vendors already know stay exactly as they are today.