May Mobility's Fixed-Route Shuttle Strategy

Not every automated-mobility company is trying to replace the trip you'd otherwise take in your own car. May Mobility runs shuttles on fixed or semi-fixed routes, closer in spirit to a transit line than to a robotaxi you'd hail to an arbitrary address.

That constraint is the whole point. A vehicle that only has to handle a defined loop, at defined stops, on streets that have already been mapped and driven thousands of times, faces a dramatically narrower engineering problem than one that has to handle an arbitrary point-to-point trip anywhere inside a large geofence. The operating design domain, engineering shorthand for the conditions a system is built and validated to handle, shrinks considerably when the route is fixed in advance.

Permitting tends to follow the same logic. A transit authority or a state regulator evaluating a fixed shuttle route can reason about a known, bounded set of conditions. Evaluating a robotaxi that might turn down any residential street in a multi-square-mile zone is a different, harder problem, and permit timelines for the two categories have often reflected that difference.

The business model behind a fixed-route shuttle also tends to differ from a point-to-point robotaxi's. A robotaxi service is built to charge each rider a fare set by the operator, competing directly against a taxi, a rideshare trip, or driving oneself. A shuttle running a university loop or a downtown circulator is more often funded, in whole or in part, through a contract with the university, a transit agency, or a municipal government, with individual riders paying a reduced fare or nothing at all. That difference matters for how each business scales: a robotaxi operator needs enough ride volume and fare revenue to cover its own fleet costs, while a shuttle operator can build a sustainable program around a smaller number of institutional contracts even without consumer fare revenue covering the full cost.

Speed is a related design choice rather than an incidental one. Many fixed-route shuttle deployments run at lower speeds than a robotaxi navigating mixed city traffic would, which is both a safety margin appropriate to a route that often shares space with pedestrians and cyclists, and a reflection of the fact that a shuttle's value proposition is filling a transit gap rather than competing with a robotaxi or a personal car on trip time.

Low speed doesn't eliminate the case for a human presence on board, either. A number of fixed-route shuttle deployments retain an attendant or safety monitor even where the vehicle is capable of driving the route on its own, partly because the vehicle regularly shares space with pedestrians and cyclists at close range and partly because transit agencies and municipal partners have their own comfort thresholds independent of what a state permit technically allows. That's a similar dynamic to the safety-driver question point-to-point robotaxi operators face, just applied to a narrower and slower operating environment.

This makes May Mobility's bet structurally different from Waymo's or Zoox's, rather than simply a smaller version of the same idea. It's aimed at filling gaps in existing transit networks, a university campus loop, a downtown circulator, a last-mile connection to a rail stop, rather than displacing the personal car trip a point-to-point robotaxi is ultimately competing against.

Other operators have taken similar fixed-route approaches with their own variations on the model, and this site's autonomous shuttle pilots briefing covers several of them. May Mobility's current deployments, alongside every point-to-point robotaxi program, are tracked together on the robotaxi deployment tracker, since the two categories increasingly compete for the same permitting attention even if they're solving different problems.