The commute starts before the car arrives
Recurring schedules, route fit, pickup points and preferences live across separate conversations. Hamraah is being designed to bring those decisions into one clear plan.
Concept · discovery
Hamraah / shared commute
A recurring carpooling concept for riders and drivers, paired with an employer commute programme. From the first match to the last-mile update, every handoff has a clear next step.
For India and the Middle East · initial corridor and service model under validation
The buyer problem
Sharing a car is only one moment. The service has to coordinate expectations before pickup, respond when reality changes, and give programme owners a responsible way to learn.
Recurring schedules, route fit, pickup points and preferences live across separate conversations. Hamraah is being designed to bring those decisions into one clear plan.
When a driver is late or a pickup changes, riders need a timely update and a practical alternative—not another thread to monitor.
Transport and workplace teams need a way to understand demand, seat use, punctuality and safety exceptions without exposing every personal journey detail.
Proposed capabilities
The concept connects the rider, driver and employer experience without treating them as the same user or giving them the same information.
Set home and work anchors, arrival windows, weekly days and return journeys as one repeatable routine.
Explore matches by route, timing, available seat and stated preferences, including women-only options where supported.
Keep the agreed meeting point, vehicle details, live trip status and driver-rider messages in one place.
A late-driver scenario can trigger an update, revised arrival estimate and an alternative offer for the rider to review.
A separate operational view for demand, seat utilisation, punctuality and safety exceptions—with programme measures still under validation.
The operating flow
Six connected moments make the service legible to the person travelling and the team responsible for the programme.
Choose recurring days, route anchors, arrival window and preferences.
Review a proposed shared journey with route, time and seat context.
Confirm the pickup and keep both sides aligned as the trip approaches.
See a delay, receive the update and choose any offered alternative.
Complete the trip, review the illustrative cost split and leave feedback.
Let authorised employer teams review programme-level patterns and exceptions.
Safety & trust
These are product requirements being explored, not claims about a live safety service. Market-specific processes and response ownership remain discovery work.
Verified identity is a core product requirement. The verification method and eligibility rules remain subject to market validation.
Trip sharing, visible vehicle and driver details, and clear pickup records are part of the proposed experience.
SOS and in-trip support are designed into the journey, not buried in settings. Response ownership must be proven before launch.
Matching can account for stated preferences, including women-only journeys, while preserving clear user choice and control.
A view for each role
A suitable recurring match, a clear pickup, timely exception updates and accessible support.
A planned route and schedule, understood pickup details, clear rider coordination and trip review.
A programme-level operating view with access, privacy and useful measures defined through discovery.
What we are validating
No public launch, service coverage or performance outcome is being claimed. The roadmap begins with a bounded question and earns each next step.
Testing the proposition with commuters, drivers and employer teams; mapping real commute routines, trust requirements and exception ownership.
Problem interviews · corridor selection · service blueprintOne employer or commute corridor, with manual operational support where needed and success measures agreed before a pilot begins.
Match quality · pickup reliability · support workload · participant trustValidate transport, cost-sharing, insurance, payment, privacy and safety obligations for the chosen jurisdiction with appropriate professional review.
Reviewed operating procedures · validated economics · go / no-go decisionQuestions, answered honestly
The concept is a starting point for discovery, not a promise of a finished service.
No. Hamraah is a Concept · discovery product. The experience on this site illustrates the proposed service; it is not a live booking or matching service.
The concept focuses on recurring shared commutes and employer commute programmes. It is not positioned as an on-demand taxi service. The initial operating model is intentionally narrow so route fit, reliability and support can be studied in context.
The concept includes programme-level views of demand, seat utilisation, punctuality and safety exceptions. Exact measures, access controls and employee privacy boundaries are discovery questions, not committed capabilities.
Verified identity, trip sharing, SOS, in-trip support and clear exception handling are design requirements. Verification partners, support staffing, escalation paths and jurisdiction-specific obligations still need to be validated before any service launch.
We welcome conversations with employers, commuters, drivers and mobility practitioners in India and the Middle East. Bring one concrete commute problem, its constraints and the outcome you would want to measure.
Explore the proposed service
See the rider, driver and employer concept, or help shape the questions a real-world pilot would need to answer.