White-label self-driving fleet ops — vehicle registry, Operational Design Domain, trip dispatch, safety-driver / teleop handoff, and a regulator-ready disengagement log.
White-label self-driving fleet ops — a vehicle registry, an Operational Design Domain as a first-class safety envelope, trip dispatch, safety-driver and teleop handoff, and a regulator-ready disengagement log. Autonomy is granted per shift and downward-safe.
What's included
Vehicle registry with SAE level, sensor suite, and drive-by-wire stack vendor
Operational Design Domain (ODD) as a first-class safety envelope — geofence, speed, weather, road class, localization floor
Trip dispatch (passenger / delivery / repositioning / validation) with per-trip ODD binding
Autonomy granted per shift and downward-safe — a vehicle can drop to teleop on its own but never self-promote
Teleoperation handoff with a live supervision ratio the program is staffed for
Disengagement log — every hand-back recorded with cause + narrated why (the log AV programs must keep)
Scenario library — promote any real disengagement into a replayable regression test against the current policy
About this module
Autonomy lives at /autonomy and is a control plane for running a self-driving fleet under real accountability. The vehicle registry records each unit's SAE level, sensor suite, and drive-by-wire stack vendor, and every trip — passenger, delivery, repositioning, or validation — dispatches with an Operational Design Domain bound to it. The ODD is a first-class safety envelope: geofence, speed, weather, road class, and a localization floor that define where a vehicle is actually allowed to drive itself.
Authority only ever moves in the safe direction. Autonomy is granted per shift and is downward-safe — a vehicle can drop itself to teleoperation, but it can never self-promote to a higher level of autonomy. Teleop handoff runs against a live supervision ratio the program is actually staffed for, so remote oversight is a real number, not an aspiration.
The record is built for regulators. A disengagement log captures every hand-back with its cause and a narrated why — the log AV programs must keep — and any real disengagement can be promoted into the scenario library as a replayable regression test against the current policy. It rides the shared actuation substrate, and the read plane works before the backing domain service is even deployed.
What you can do with it
Register vehicles by SAE level, sensor suite, and drive-by-wire vendor
Bind an Operational Design Domain to every dispatched trip
Hand a vehicle to teleop against a staffed supervision ratio
Keep a regulator-ready disengagement log with cause and narrative
Promote a real disengagement into a replayable regression scenario
Get this module
Free for all Turtini organizations.
Who it's for
- Autonomous-vehicle operators running passenger or delivery fleets
- Programs that need an auditable safety envelope and disengagement record
- Fleet-ops teams standing up teleoperation with real supervision ratios
Details
- Category
- Frontier
- Pricing
- Free
- Built by
- Badge
- Beta