Hirschbach Orders 500 Aurora Autonomous Trucks Under DaaS Model

Hirschbach Motor Lines has committed to deploy 500 Aurora autonomous trucks under a Driver as a Service (DaaS) subscription model, marking one of the largest publicly announced autonomous-truck orders to date.

How does Aurora's Driver as a Service model work?

Under the DaaS structure, Hirschbach owns the tractors outright while subscribing to Aurora's autonomous driving system. The carrier retains control over the asset — depreciation schedule, trade-in timing, spec choices — while Aurora operates the self-driving software and hardware stack as a recurring service.

Aurora CEO Chris Urmson said early adopters like Hirschbach are demonstrating how quickly fleets move from testing to scaling autonomous operations. "The industry is primed for this product, and our momentum toward meaningful commercial revenue is hitting a new gear," Urmson said.

The approach is designed to give fleets control over total cost of ownership while enabling Aurora to operate a capital-efficient, high-margin business model. Aurora avoids the balance-sheet weight of owning 500 tractors; Hirschbach avoids vendor lock-in on the asset itself.

What the 500-truck commitment signals

The 500-truck deployment represents one of the largest publicly announced commitments to autonomous trucking to date and signals growing confidence in the technology's near-term viability. Most autonomous pilots to date have involved single-digit or low-double-digit unit counts.

No timeline for the rollout was disclosed in the announcement. Aurora has been testing autonomous Class 8 tractors on public highways in Texas and has stated commercial revenue operations are underway, but the company has not published per-mile or per-load pricing for the DaaS subscription.

What remains unknown for fleet TCO

Several cost variables remain unquantified. The DaaS subscription fee structure — whether it is per truck per month, per mile, or per load — was not disclosed. Maintenance responsibility for the autonomous hardware stack — lidar units, compute modules, sensor arrays — was not specified. Whether Hirschbach's existing shop technicians will be trained to service Aurora hardware or whether Aurora will dispatch field service is unclear.

Warranty terms for the autonomous system were not published. If a lidar unit fails at 300,000 miles, who pays for replacement — Aurora under the subscription, or Hirschbach as the truck owner? The announcement did not address that split.

Insurance cost delta versus a human-driven truck was not disclosed. Some autonomous developers have stated they will self-insure or backstop liability; others expect the carrier to carry the policy. Hirschbach's approach was not detailed.

What this means for small fleets

The Hirschbach order does not open a path for owner-operators or sub-50-truck fleets in the near term. Aurora's DaaS model presumes scale — 500 trucks suggests a subscription price point that only makes sense when spread across a large dedicated lane with high utilization. A three-truck operation running regional dry van will not see a DaaS offer in 2026.

The order does confirm that autonomous hardware is moving from prototype to production-intent spec. If Hirschbach is committing to 500 units, Aurora's sensor and compute stack has reached a design freeze stable enough to support a multi-year service contract. That matters for the broader market: parts availability, technician training curricula, and service bulletins will follow once a platform is locked.

For fleets evaluating autonomous in the next 24 months, the DaaS structure offers a lower-risk entry than buying autonomous-capable tractors outright. If the technology underperforms or regulatory headwinds emerge, the carrier can walk away at subscription renewal rather than sitting on stranded assets. That optionality may accelerate adoption among large fleets running high-volume dedicated lanes where driver recruitment has been chronically tight.