In development
Onyx Route
Digital mobility products for more connected journeys, fleets, and cities.
The division
A journey is more than a booking screen. Fragmented urban movement experiences mean a rider, a driver, and a dispatcher each see a different trip. Limited fleet and trip visibility means the person assigning work cannot see what is already moving, so a decision is a guess. Mobility products that do not reflect how people actually travel look complete in a demo and then fail the trip people take every day. Dependable movement is an operating network: trips, fleets, riders, and the teams who serve them, on one picture.
OnyxNexus Mobility focuses on the systems that make movement services more dependable for riders, drivers, fleet operators, and cities. It treats mobility as an operating network, not just a booking interface. The division's work is digital mobility products for more connected journeys, fleets, and cities. The work covers mobility platforms, fleet operations, rider experience, and movement intelligence. A platform is where the trip is held. Fleet operations are how vehicles and crews are seen and assigned. Rider experience is the digital journey a person actually follows. Movement intelligence is the trip and fleet context that makes a dispatch decision better.
Onyx Route is in development. A mobility operating system for fleets, riders, and service teams that need clearer movement data and reliable dispatch. It connects trips, fleets, and dispatch into shared context so operators can decide with a clearer picture and riders can get more dependable journeys. Dispatch with live trip and fleet context, simpler digital journeys, and movement data that can inform local transport are what the division builds. StyleRide is a separate name in this division. A mobility product in development, connecting riders with vetted private drivers and approved luxury vehicles on regular routes. StyleRide is in development. It is not a public service. StyleRide is not Onyx Route.
How a journey is held
This is how mobility operations are organised in general, and it is the path Onyx Route builds. Route is in development. StyleRide is in development.
A booking screen is one view of a trip, not the operation around it. The division's role is an operating network for riders, drivers, fleet operators, and the institutions that depend on movement.
Dispatch holds when the person assigning work can see the trip and the fleet together. Dispatch decisions with live trip and fleet context are part of Onyx Route.
Rider experience is a digital journey a rider and a service team can both follow. Simpler digital journeys for riders and crews are the work. StyleRide is in development.
Limited fleet and trip visibility is one of the problems the division takes on. Movement intelligence replaces that gap with context an operator can use.
A mobility product fails when it ignores the trips people actually repeat. The problem is products that do not reflect how people actually travel. Route is built around real operating conditions.
Onyx Route is the operating layer for fleet, rider, and dispatch context. StyleRide is the mobility product for riders, vetted private drivers, and approved luxury vehicles on regular routes. StyleRide is in development.
Mobility
Talk to the Group about trips, fleets, rider experience, or dispatch context.
Who it serves
OnyxNexus Mobility focuses on the systems that make movement services more dependable for riders, drivers, fleet operators, and cities. It treats mobility as an operating network, not just a booking interface.
The problem. Fragmented urban movement experiences. The rider and the driver can be on the same trip and still be working from different information.
How the division helps. A mobility product in development, connecting riders with vetted private drivers and approved luxury vehicles on regular routes. StyleRide is in development. It is not a public service. Simpler digital journeys are also part of Onyx Route.
The problem. Limited fleet and trip visibility. Assignment happens without a shared view of what is already moving, so dispatch is harder than it needs to be.
How the division helps. Onyx Route puts dispatch decisions on live trip and fleet context. Route is in development.
The problem. Movement data that never becomes a decision. An institution can see that people are travelling and still lack a picture clear enough to plan against.
How the division helps. One outcome is movement data that can support better local transport decisions. That data is part of Onyx Route.
Outcomes
These are the outcomes of the work. Onyx Route is in development, and StyleRide is a product in development.
Improve dispatch decisions with clearer trip and fleet context. Live trip and fleet context is part of Onyx Route, in development.
Create simpler digital journeys for riders and service teams. StyleRide is in development. It connects riders with vetted private drivers and approved luxury vehicles on regular routes.
Build movement data that can support better local transport decisions. That data can inform local transport. No volume or coverage figure is attached to it.
Example scenarios
A generic example, not a client story.
Example scenario
Problem. Vehicles and trips are coordinated from separate notes. The person dispatching cannot see a single picture of what is already on the road.
Our approach. Put trip, fleet, and dispatch into shared context. That is the shape of Onyx Route.
Outcome. Dispatch decisions with clearer trip and fleet context. That is the outcome.
Example scenario
Problem. The digital journey is fragmented. Riders and drivers depend on messages outside the product, and the trip is hard to follow for the people in it.
Our approach. For regular routes with vetted private drivers and approved luxury vehicles, the product is StyleRide. Simpler digital journeys are also work the division does.
Outcome. A simpler digital journey for riders and service teams.
Example scenario
Problem. Travel is visible only as complaints and counts. The institution lacks movement data it can use when it plans.
Our approach. Treat movement data as an output of the operating network, which is part of Onyx Route.
Outcome. Movement data that can support better transport decisions. No coverage area or timetable is stated.
Movement operations
In development
A mobility operating system for fleets, riders, and service teams that need clearer movement data and reliable dispatch.
We are building Onyx Route. Route is in development. It treats movement as an operating network, not a booking screen. It connects trips, fleets, and dispatch into shared context so operators decide with a clearer picture and riders get more dependable journeys. The work starts from how movement actually runs.
Designed capabilities
Products and brands
In development
A mobility product in development, connecting riders with vetted private drivers and approved luxury vehicles on regular routes.
Explore brandQuestions
Digital mobility products for more connected journeys, fleets, and cities. OnyxNexus Mobility focuses on the systems that make movement services more dependable for riders, drivers, fleet operators, and cities. It treats mobility as an operating network, not just a booking interface. The work covers mobility platforms, fleet operations, rider experience, and movement intelligence.
Onyx Route is in development. A mobility operating system for fleets, riders, and service teams that need clearer movement data and reliable dispatch. The division builds dispatch decisions with live trip and fleet context, simpler digital journeys for riders and crews, movement data that can inform transport decisions, and a design built for real operating conditions.
StyleRide belongs to OnyxNexus Mobility. Its status is In development. A mobility product in development, connecting riders with vetted private drivers and approved luxury vehicles on regular routes. The brand page is /brands/styleride. StyleRide is in development. It is not a public service. StyleRide and Onyx Route are both named in this division. Neither name is the other.
The work is for three groups: riders and drivers, fleet operators, and cities and institutions. Riders and drivers need a journey they can both follow. Fleet operators need trip and fleet context for dispatch. Institutions need movement data that can support a transport decision.
They use generic archetypes, such as a fleet operator, a rider and driver service, or an institution planning how people move. Each card states a problem, an approach, and an outcome. They are illustrations of the domain. They are not customer stories, and they do not report ridership, fares, or places.
Use the contact form for Mobility, or write to support@onyxgroup.global. A conversation can cover a customer need, a partnership, a technology collaboration, or an investment opportunity connected to this division.
Connected logistics, delivery, and supply-chain operating systems.
Communications infrastructure, platforms, and customer engagement systems.
Events, concerts, production, and audience experiences shaped from strategy through delivery. OnyxNexus Media is an active division.
Work with Mobility
Talk to the Group about journeys, fleets, rider experience, dispatch, or a partnership connected to this division.
