Riders

On-demand that knows who's where, right now.

Sub-second rider-to-driver matching across cost, ETA, service tier, vehicle type. Dynamic zone pricing. Multi-network orchestration.

Operators in riders come to Mycelium when their spreadsheets stop scaling — when every morning starts with an exception, when three branches or three airports have three different rule books, when a 45-minute customer window needs to become 30.

Dynamic pricing · zone × time

Per-zone fare multipliers decided by current demand, supply position, and configured rate floors. Rules travel per-request.

08:42 · FRI · PEAK 5 RULES ACTIVE
1.0x A1
1.0x A2
1.1x A3
1.2x A4
1.4x A5
1.6x A6
1.3x A7
1.1x A8
1.0x B1
1.1x B2
1.3x B3
1.5x B4
1.8x B5
1.7x B6
1.2x B7
1.0x B8
1.1x C1
1.2x C2
1.5x C3
1.9x C4
2.2x C5
2.0x C6
1.4x C7
1.1x C8
1.0x D1
1.1x D2
1.2x D3
1.4x D4
1.6x D5
1.5x D6
1.2x D7
1.0x D8
1.0x E1
1.0x E2
1.0x E3
1.1x E4
1.2x E5
1.1x E6
1.0x E7
1.0x E8
1.0x 2.5x COST RULE · ZONE A4 HIT +1.2x — AIRPORT SURCHARGE
01

Dynamic pricing you can actually inspect.

Per-zone, per-time, per-demand pricing. Not a black-box multiplier — a rule surface you can tune and audit. Supply positioning runs against predicted demand before the spike.

  • Sub-second rider-to-driver matching across cost, ETA, tier, vehicle
  • Live ETAs against real-time and historical traffic
  • Driver supply positioning against predicted demand
9:41
ACME · Rides
CONFIRMED · 3 MIN AWAY
D
Daniel · Sedan
White · 45-123-89
★ 4.8
FARE · DYNAMIC
$ 38.50
Zone A to D · 5.4 km
Off-peak multiplier
Rider · Booking confirmed
02

Three supply sources, one dispatch loop.

Owned fleet, contracted drivers, partner ride-hailing networks — decided per ride against cost, ETA, and service tier. One cost model, one operational view, one set of white-label apps for riders and drivers.

  • Multi-network orchestration in a single dispatch loop
  • Branded rider and driver apps
  • Operator-owned, not consumer brand — you run it under your own banner
Observed

What the numbers look like in production.

Sub-sec
Rider-to-driver match latency
Zone
Dynamic pricing by time and demand
3 sources
Owned, contracted, partner — one dispatch loop
Owned · contracted · on-demand
One dispatch loop across three carrier shapes

Send your zone map and historical demand. We'll model the supply positioning.

A real demand surface beats any demo. Thirty-minute call, honest deltas.