Concept in development

Onyx Mobility

Onyx Route

Mobility systems that make journeys, fleets, and dispatch more dependable for the people who use them.

A white car on a wet city road at dusk.

The division

What Mobility does, and why the network matters.

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.

Onyx 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 a concept in development. A mobility operating system for fleets, riders, and service teams that need clearer movement data and reliable dispatch. The concept 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 the capabilities being shaped. 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 described as a working product, not yet a public service. StyleRide is not Onyx Route.

How a journey is held

From a trip to a decision someone can defend.

This is how mobility operations are organised in general, and it is the path Onyx Route is being designed around. Route remains a concept in development. StyleRide stays a product in development.

  1. 01

    Treat movement as a network

    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.

  2. 02

    Give dispatch a shared context

    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 the design of Onyx Route.

  3. 03

    Make the rider journey simpler

    Rider experience is a digital journey a rider and a service team can both follow. Simpler digital journeys for riders and crews are an aim, not a claim that a public service is open.

  4. 04

    See the fleet and the trip

    Limited fleet and trip visibility is one of the problems the division takes on. Movement intelligence is the service meant to replace that gap with context an operator can use.

  5. 05

    Stay close to the real trip

    A mobility product fails when it ignores the trips people actually repeat. The problem is products that do not reflect how people actually travel, and Route is being designed around real operating conditions.

  6. 06

    Keep the two names apart

    Onyx Route is the concept for fleet, rider, and dispatch context. StyleRide is the mobility product for riders, vetted private drivers, and approved luxury vehicles on regular routes.

Mobility

Bring the journey that breaks between hands.

Talk to the Group about trips, fleets, rider experience, or dispatch context.

Who it serves

People who share a trip and not a picture.

Onyx 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.

Riders and drivers

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 described as a working product, not yet a public service. Simpler digital journeys are also part of the design of Onyx Route.

Fleet operators

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 is being designed so dispatch decisions sit on live trip and fleet context. That capability belongs to the concept.

Cities and institutions

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 the design of Onyx Route.

Outcomes

What the work is being designed to achieve.

These are the outcomes the division is working toward. Route's share of them belongs to a concept in development. StyleRide remains a product in development.

Clearer dispatch

Improve dispatch decisions with clearer trip and fleet context. Live trip and fleet context is part of the design of Onyx Route, not a system described as open.

Simpler journeys

Create simpler digital journeys for riders and service teams. StyleRide is the in-development product aimed at riders, vetted private drivers, and approved luxury vehicles on regular routes.

Data that can inform transport

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.

Illustrative scenarios

The kinds of movement this division is built for.

Each card is an illustrative scenario: a generic archetype, the problem they face, the approach, and the outcome we aim for. These are not case studies, and they do not report results. Onyx Route is a concept in development. StyleRide is a product in development, not a public service.

Illustrative scenario

A fleet operator

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.

The outcome we aim for. Dispatch decisions with clearer trip and fleet context. The outcome is the aim of the concept.

Illustrative scenario

A rider and driver service

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 an aim of the division.

The outcome we aim for. A simpler digital journey for riders and service teams.

Illustrative scenario

An institution planning how people move

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 the design of Onyx Route.

The outcome we aim for. Movement data that can support better transport decisions. No coverage area or timetable is stated.

Movement operations

Onyx Route

Concept in development

A mobility operating system for fleets, riders, and service teams that need clearer movement data and reliable dispatch.

Onyx Route approaches movement as an operating network, not a booking screen. The concept connects trips, fleets, and dispatch into shared context so operators decide better and riders get more dependable journeys - designed first around how movement actually works in the cities people travel through, then built to travel.

Designed capabilities

  • Dispatch decisions with live trip and fleet context
  • Simpler digital journeys for riders and crews
  • Movement data that informs local transport
  • Built for real-world network conditions

Products and brands

Part of the Mobility portfolio.

In development

StyleRide

A mobility product in development, connecting riders with vetted private drivers and approved luxury vehicles on regular routes.

Explore brand

Questions

Before you write to Mobility.

What does Onyx Mobility do?

Mobility systems that make journeys, fleets, and dispatch more dependable for the people who use them. Onyx 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.

What is Onyx Route?

Onyx Route is Concept in development. A mobility operating system for fleets, riders, and service teams that need clearer movement data and reliable dispatch. The capabilities being shaped are 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. Route is not a launched product.

What is StyleRide?

StyleRide belongs to Onyx 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. It is a working product, not yet a public service. StyleRide and Onyx Route are both named in this division. Neither name is the other.

Who is the work for?

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.

How should the illustrative scenarios be read?

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 the outcome the work aims for. They are illustrations of the domain. They are not customer stories, and they do not report ridership, fares, or places.

How do we start a conversation?

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.

Work with Mobility

Bring us the operating problem.

Talk to the Group about journeys, fleets, rider experience, dispatch, or a partnership connected to this division.