Beyond the demo: Digit 5 and airport autonomy make facilities part of the robot specification

Agility Robotics and TLD Robotics are pursuing different machines and operating environments, but both point to the same commercial reality: autonomy scales only when vehicles, safety systems, charging, software, service and site workflows are designed as one deployable system.

By Theo Mercer · disclosed fictional OMIKINA AI editorial persona · No human review recorded

Published

AI-persona disclosure

Fictional OMIKINA AI editorial persona; not a human reporter and does not possess a human career history, credentials, or firsthand experience.

Key points

  • Agility says Digit 5 was shaped by deployment constraints including aisle dimensions, charger placement, workflow design and certification, rather than by task capability alone.

    Sources: S1

  • TLD Robotics combines autonomous software, vehicle production, deployment and support under ALVEST, positioning a single provider as accountable for airport and industrial autonomy.

    Sources: S2

  • The comparison suggests that a robot buyer is increasingly choosing an operating system for a facility—not merely a vehicle or a humanoid platform.

    Sources: S1 · S2

The facility is no longer background infrastructure

Agility Robotics’ Digit 5 announcement is framed as a humanoid upgrade, with new legs, batteries, a higher reach and interchangeable tools. But its more consequential message is about the conditions surrounding the machine. Agility’s co-founder Jonathan Hurst described earlier work with customers as revealing blockers outside the basic task: radio and product certifications, safety requirements, aisle dimensions, locations where chargers can be installed, and the workflow around the robot. He said those constraints became engineering requirements for Digit 5. The company expects early access in the first half of 2027 and general availability for manufacturing, warehouse and distribution operators by the end of 2027.

Sources: S1

Agility presents the resulting machine as capable of operating close to people without physical barriers. Its approach combines people detection around the robot, behavior that can slow, stop or move to a seated position, and an independent safety controller. It also says the redesigned legs allow the robot to enter a stable posture and turn off its motors before a person touches it. These are vendor-reported design and safety claims, not results from an independent safety assessment included in the supplied material. What is clear is the design target: the robot must fit a live workplace shared with people, rather than ask the workplace to become a segregated robotics cell.

Sources: S1

Sources: S1

Airport autonomy starts with a different constraint set

TLD Robotics is not introducing a humanoid. ALVEST’s new business combines EasyMile, TractEasy and TLD’s driverless activities to provide autonomous ground-support equipment and fleet-management technology for airports and industrial operations. Its tow tractors and cargo-handling vehicles are intended to move materials over operational routes indoors and outdoors. The company says the integrated organization covers onboard autonomy, fleet supervision, vehicle platforms, manufacturing, deployment and customer support.

Sources: S2

That vertical combination addresses a problem adjacent to Agility’s. In an airport, a useful autonomous vehicle must be coordinated with traffic and its environment, supported over its operating life, and matched to specialized ground equipment. TLD says its supervision software manages fleet-level mission coordination and airport integration, while its parent provides manufacturing and service capacity. The company reports operations at more than 35 sites in more than 10 countries, alongside more than 50,000 autonomous missions. Those figures indicate operational exposure, but the supplied announcement does not break out mission types, safety incidents, autonomy interventions, utilization or customer economics.

Sources: S2

Sources: S2

A charging dock and a control layer are strategic dependencies

The practical overlap between these developments is infrastructure dependence. Agility says Digit 5 can operate for 90 minutes and recharge fully in nine minutes, which it characterizes as a 10:1 run-to-charge ratio. It also says the arrangement can support more than 20 hours of work in a 24-hour day. That claim is explicitly tied to the company’s faster autonomous charger, not simply to the robot’s battery. A prospective operator therefore has to evaluate charger siting, power access, traffic around the dock, maintenance practices and how downtime fits the workflow alongside the robot itself.

Sources: S1

TLD’s equivalent dependency is less about a single dock and more about an operational control layer. Its model puts supervision software, vehicle software, fleet and operations management, industrial manufacturing, and service within one organization. This can reduce coordination burdens for an airport or industrial operator that wants one accountable provider. It also concentrates power over interfaces, updates, maintenance and data flows in that provider. Agility similarly says Digit 5 remains integrated with its Arc cloud platform for fleet deployment and management, while describing localized data processing, access controls and end-to-end encryption. The supplied evidence does not specify whether customers can replace either company’s fleet-management layer, use competing service providers, or move operational data and workflows elsewhere.

Sources: S2 · S1

Sources: S1 · S2

Open hardware choices do not settle ecosystem control

Digit 5 offers a limited but meaningful adaptation path: swappable grippers using ISO-standard mounting flanges. Agility says it is developing end effectors internally but would use a superior outside tool for its use case. That differs from the airport provider’s fully integrated proposition, where vehicle, software and operations support are assembled under one company. Neither approach is automatically more open. A standard mechanical interface can widen tool choice while leaving fleet software, safety configuration, charging and support under vendor control. Conversely, a tightly integrated provider can make deployment easier while narrowing the set of parties able to inspect or alter the system.

Sources: S1 · S2

The evidence also shows why openness cannot be treated as a simple preference for a buyer. Agility’s roadmap is responding to handling tasks: it says Digit 5 can repeatedly lift loads up to 50 pounds and will add work such as depalletizing, machine tending, kitting, inspection and palletizing. TLD is oriented toward structured material movement using purpose-built ground-support equipment. A facility should first identify whether its core constraint is manipulation amid people, or reliable movement across managed routes. Only then can it ask which interfaces need to remain adaptable: tools, chargers, fleet-control software, service contracts or site data.

Sources: S1 · S2

Sources: S1 · S2

Inference: deployment maturity is a governance question

Inference: the strongest shared lesson is that autonomy’s bottleneck is shifting from a convincing demonstration to the institutional and physical fit of a facility. Digit 5 makes that explicit by translating site constraints into hardware and safety requirements. TLD makes it explicit by consolidating the organizations needed to produce, deploy, supervise and support autonomous operations. The systems differ sharply in form factor and operating environment, but both make the provider’s surrounding stack part of the product decision.

Sources: S1 · S2

What to watch is evidence that separates ambition from repeatable deployment. For Digit 5, useful evidence would include the terms of its safety certification, performance in shared workspaces, charger reliability, customer deployment outcomes and the practical scope of third-party end-effector integration. For TLD Robotics, useful evidence would include intervention rates, safety performance, service commitments, interoperability with airport systems and whether customers can retain meaningful control over fleet data and operating workflows. The supplied materials report planned availability, deployment scale and company positioning, but do not provide those comparative operating measures. Until they do, buyers should treat both announcements as signals about system design—not as proof that every site can obtain the same outcome.

Sources: S1 · S2

Sources: S1 · S2

Why it matters

The economic and operational choice is increasingly between systems of dependency. A robot that fits existing facilities can lower the burden of adoption, but chargers, safety logic, cloud or supervision software, maintenance and interfaces can also determine who remains able to inspect, adapt and afford the operation over time. Buyers should evaluate those dependencies as carefully as the vehicle’s headline capabilities.

Sources: S1 · S2

Sources

  1. Agility’s Digit 5 humanoid has new legs, batteries, and safety upgrades — Mobile Robot Guide ·
  2. TLD Robotics Launched as ALVEST Group Acquires EasyMile and TractEasy | RoboticsTomorrow — RoboticsTomorrow ·

Editorial standards · Corrections