Private mobility platform · White-label SaaS
Replace fragmented commuting, ad-hoc shuttles, and parking pressure with a managed, white-label pooling platform — your brand, your fleet, your rules, your data. Built for universities, corporations, government agencies, and communities across Malaysia.
One platform — carpooling is just the beginning
Who it's for
Your riders just tap and go — the platform is sold to, configured by, and answerable to the institution behind them. Anywhere people share an origin, a destination, and a clock:
Student transportation without a bus fleet — pooled cars timed to the class timetable.
Employee transport that cuts parking demand and shuttle spend, timed to shift starts.
Worker mobility across estates, batched to factory shift changes — fewer vans, fuller seats.
Staff movement across large medical campuses, day and night, with full manifests.
Inter-agency pooling within administrative precincts like Putrajaya, with audit-ready records.
A resident mobility amenity — pooling to KTM/LRT stations, offices, schools, and malls.
A municipal shared-mobility layer with complete trip data for planners.
Landside staff transport pooled across terminals and cargo zones.
Your operations portal
Fleet, drivers, zones, slots, fares, manifests — everything your operations and compliance teams need, in your own tenant portal.
Manage vehicles, drivers, service hours, departure slots, peak windows, and fares — every operating rule is yours to set, per organization.
Institution vans, member-owned cars, and solo motorbikes side by side — with vetting records, approval gates, and payout rules per driver.
Every booking is an immutable record, separate from the live route plan. Passenger manifests and GPS history export for your compliance files.
Your site boundary, pickup points, and internal roads become a mapped zone with real driving distances — surveyed once, reused on every dispatch.
Only verified members can book. Memberships expire automatically — on graduation or contract end — so access stays current without manual clean-up.
Set base fares, peak windows, and off-peak uplifts; choose percentage or fixed driver payouts — collected, split, and ledgered automatically.
The rider experience
This is what your members get: a WhatsApp message in, a seat in a shared car out. The timeline below is a real campus dispatch — the same clock works for a train departure or a shift start.
Type carpool, pick a departure slot and a pickup point. Confirmed in four taps — no new app to install.
Every request in the slot is batched together, so the system plans for the whole community, not one rider at a time.
Riders are packed into vehicles with live seat counts, per-rider ride-time caps, and real road distances — the lake gets routed around, not through.
Cars run in parallel — one per residential zone — so the shared arrival deadline holds for every rider on board.
One engine, any corridor
The optimizer doesn't care what's at the end of the road. Give it a shared destination and a hard arrival time, and it fills the cars — and the train corridor runs both ways:
Students from the east-campus colleges pooled across the connector road, timed to the class timetable.
DEADLINE 08:00 · CLASS STARTSColleagues and neighbours heading to the same workplace share the ride in — matched by route, timed to the shift roster.
DEADLINE 09:00 · SHIFT STARTSResidents pooled to the platform before the train leaves — departure slots aligned to the actual rail timetable, cars refilling for the next service.
DEADLINE 07:45 · TRAIN DEPARTSWhen the evening train pulls in, arriving neighbours pool the ride home — matched on the spot in a short hold window, solo if no one fits.
TRIGGER 18:32 · TRAIN ARRIVESDual-mode dispatch
The morning rush and a quiet mid-afternoon are different problems. The platform runs a different matcher for each — and your admins draw the line between them.
Bookings collect into fixed slots aligned to whatever drives your demand — a class timetable, a shift roster, or the rail schedule — then the whole slot is optimized at once.
A short hold window matches riders heading the same way; if nobody fits, the ride simply runs solo.
White-label SaaS
Your organization gets its own address, its own booking portal, and its own operations dashboard — powered by JomRides underneath. Tenant isolation is enforced at the data layer, so one organization can never see another's riders.
Compliance by design
Community transport sits inside a real legal frame. The platform is shaped around it, and our onboarding checklist walks your organization through every clearance before go-live.
Pilot data is hosted in-country on Malaysian infrastructure, with the application and database co-located. Your organization stays the data controller.
A service cannot go live until licensing, insurance, road status, and driver vetting are confirmed on file — the launch flag is locked until the checklist is complete.
Built by a team already operating APAD/eVP-compliant e-hailing, with the licensing questions for closed-community pooling mapped out in the onboarding pack.
Start with a pilot
We start small — a single corridor at your busiest hour — and prove the numbers on your site before scaling. The preparation checklist tells your team exactly what's needed, from fleet details to regulatory clearances.
Book a demo Get the preparation checklist