Humanoid ComparisonsFigure vs Agility Digit

Manipulation Ambition Compared With Logistics Deployment Evidence

A task-level comparison of Figure and Agility Digit using current factory and warehouse evidence, with separate treatment of robot generations, deployment metrics and missing intervention data.

By TechniaHQRobot12 min read

Introduction

Figure and Agility publish different kinds of industrial evidence. Figure reports that Figure 02 accumulated more than 1,250 hours at BMW Plant Spartanburg, loaded more than 90,000 parts and contributed to more than 30,000 X3 vehicles before Figure 03 returned to the site for a logistics sequencing workflow. Agility reports more than 65,000 operating hours for Digit 4 across customer sites and a 100,000-tote milestone at GXO with about 98% on-task accuracy. Digit 5 was announced on September 15, 2026, with early access planned for the first half of 2027, so Digit 4 field history should not be presented as Digit 5 field history.

Key findings

  • Figure reports more than 1,250 hours of Figure 02 runtime at BMW Plant Spartanburg, more than 90,000 parts loaded and contribution to more than 30,000 X3 vehicles.
  • Agility reports more than 65,000 operating hours for Digit 4 and a 100,000-tote GXO milestone at about 98% on-task accuracy.
  • Digit 5 is a new generation announced in September 2026; its planned 2027 availability means Digit 4 operating history must remain labeled by generation.
  • The robots are evaluated on different tasks, so hand manipulation and warehouse tote throughput should remain separate metrics.
  • The public records are task-specific: Figure has documented automotive part handling and sequencing at BMW, while Digit has documented tote-handling deployments and commercial logistics agreements.

Manipulation Ambition Compared With Logistics Deployment Evidence - evidence comparison

The table uses source-backed fields and leaves non-comparable or undisclosed information visible.

System, category or questionVerified evidenceInterpretation or limitation
Figure at BMWFigure reports more than 1,250 hours of Figure 02 runtime, more than 90,000 parts loaded and contribution to more than 30,000 X3 vehicles; Figure 03 later returned for a logistics sequencing workflow.Company-reported factory evidence; public intervention and complete failure rates remain limited.
Agility Digit 4Agility reports more than 65,000 operating hours across customer sites and a 100,000-tote GXO milestone at about 98% on-task accuracy.Company-reported logistics evidence; keep Digit 4 operating history separate from the newer Digit 5 generation.
Digit 5 availabilityAgility announced Digit 5 on September 15, 2026, with early access expected in the first half of 2027 and general availability expected by the end of 2027.Planned availability is not field runtime.
Commercial accessBoth companies sell through enterprise relationships rather than public retail pricing for the industrial configurations discussed here.Contract terms, integration cost and service obligations are not publicly comparable.

The records cover different robot generations, tasks and sites. Compare only fields measured under compatible conditions, and keep company-reported operating metrics attributed to the publisher.

Evidence classification

  • Confirmed by official technical documentation specifications, architecture or access stated by the responsible organization.
  • Confirmed by a research paper result reported under a defined experiment, without implying deployment.
  • Demonstrated on a real system a physical robot or product performed the documented sequence.
  • Company claim without independent verification numerical or operational statement supplied by the company.
  • Public evidence insufficient version, control mode, duration, trial count or operating conditions are missing.

Definition and scope

Figure and Agility publish different types of industrial evidence. Figure reports automotive part handling and sequencing at BMW, while Agility reports tote-handling deployments and operating hours for Digit. The comparison keeps robot generation, task and site attached to every metric.

Figure 02 and Figure 03 are treated as separate generations, as are Digit 4 and Digit 5. A metric from an older generation is not assigned to the newer robot unless the company reports it for that version.

How the complete pipeline works

Figure combines humanoid mobility, hands and its Helix control stack for manipulation workflows. Digit combines bipedal mobility with purpose-built arms and grippers and is integrated into warehouse workflows through Agility’s fleet software.

For buyers, the useful comparison is the complete task loop: object presentation, robot motion, grasp or tote handling, recovery, resets, supervision and facility integration. Public sources do not expose all of those fields for both companies.

Key systems, products and technical evidence

Figure publishes Helix demonstrations and partner announcements. Agility publishes logistics deployments and commercial agreements, though site-level uptime and intervention data remain limited. The systems are not treated as interchangeable.

Figure’s BMW record and Agility’s Digit record are kept by robot generation and task. Figure 02 production data is not assigned to Figure 03, and Digit 4 operating hours are not assigned to Digit 5. Missing intervention, reset and full-shift failure data remain undisclosed.

Evidence from real systems

Figure reports more than 1,250 hours of Figure 02 operation at BMW and a later Figure 03 logistics sequencing workflow. Agility reports more than 65,000 operating hours for Digit 4, including a 100,000-tote milestone at GXO at about 98% on-task accuracy. These are company-reported records from different tasks and sites, so they should not be converted into a single performance score.

A stronger comparison would report the same task, shift length, throughput definition, intervention rate, reset policy and failure categories for both systems. Those common fields are not public, so this page limits conclusions to the documented BMW and logistics records.

Comparison method and engineering tradeoffs

The comparison uses only fields that can be traced to Figure or Agility records and keeps missing values visible. Company-reported hours, parts, tote counts and accuracy remain attributed to the publisher.

The two systems have been reported on different workflows, so cycle time, dexterity and throughput should only be compared after a shared task and measurement protocol are available.

Failure modes and misleading interpretations

The robots solve different tasks, so hand dexterity and tote throughput should not be converted into one performance score. Public intervention rates, reset policies and comparable full-shift failure data remain missing.

Generation labels also matter. Figure 02 BMW production totals do not establish Figure 03 reliability, and Digit 4 operating hours do not become Digit 5 field hours.

Practical applications and current maturity

Digit 4 has a longer public record for tote-handling logistics, while Figure has published automotive part handling and a Figure 03 sequencing workflow at BMW. Buyers should match the evidence to the intended task rather than treating either record as proof across all warehouse or factory work.

A procurement comparison should request the delivered robot generation, task definition, shift length, intervention rate, maintenance plan, charging strategy, integration scope and service terms.

Open problems and recommendations

Open questions include Figure 03 intervention and uptime data, Digit intervention rate over a full shift, and comparable integration and service costs. Those questions require matched task definitions and reporting that includes failed attempts and resets.

Future deployment reports would be more useful with robot generation, unit count, shift duration, throughput definition, interventions, reset rules and maintenance time published together.

Limitations and missing information

  • The robots solve different tasks, so hand dexterity and logistics throughput should not be scored as one metric. Public intervention rates and long-duration uptime are missing.
  • Benchmarks from different robots, versions, environments or control modes are not directly comparable.
  • Company-reported metrics are not independently audited unless a separate primary record establishes the same result.
  • Code, weights, prices, model versions, APIs and commercial availability can change after publication.
  • Long-duration reliability, intervention frequency and complete failure distributions are rarely published.

Conclusion

Figure and Agility publish substantial industrial activity, but their public records describe different robot generations and tasks. Figure reports automotive handling and sequencing work at BMW. Agility reports longer-running Digit 4 logistics deployments, including the GXO tote record, while Digit 5 is scheduled for 2027 access. Intervention rates, reset policies and comparable full-shift failure data remain missing, so the comparison stays task-specific.

Frequently asked questions

What is Figure vs Agility Digit?

Figure and Agility Robotics build bipedal humanoid systems for industrial work, but their public evidence covers different tasks. Figure has published automotive handling and sequencing records, while Agility has published tote-handling deployment data for Digit.

How does Figure vs Agility Digit work?

Figure pairs humanoid hardware with its Helix control stack and dexterous hands. Digit uses bipedal mobility, purpose-built arms and grippers, plus fleet and facility integration for logistics workflows. Their published systems should be compared on the same task before drawing performance conclusions.

What is the strongest real-world evidence?

Figure reports more than 1,250 hours of Figure 02 runtime at BMW, more than 90,000 parts loaded and contribution to more than 30,000 X3 vehicles. Agility reports more than 65,000 Digit 4 operating hours and a 100,000-tote GXO milestone at about 98% on-task accuracy. Both sets are company-reported and cover different tasks.

What information is still missing?

Comparable intervention rates, reset policies, full-shift failure distributions, integration cost and service terms are not public for both systems under one shared task. Figure 02, Figure 03, Digit 4 and Digit 5 should also remain separate generations in any comparison.

Sources and methodology

Sources for Figure vs Agility Digit were rechecked on September 26, 2026. The review prioritizes current official Figure and Agility deployment records and keeps metrics attached to the robot generation and task that produced them.

For Figure vs Agility Digit, evidence is sorted by test setting and control mode simulation is kept apart from physical trials, teleoperation from autonomous execution, and announced access from a system that can actually be obtained or deployed.

The review keeps robot generations and task definitions separate and leaves intervention, reset, cost and long-duration reliability fields undisclosed when neither company publishes a matched measure.

Source review notes

Review date recorded September 26, 2026

Supported by the cited sources

  • Figure reports more than 1,250 hours of Figure 02 operation at BMW, more than 90,000 parts loaded and contribution to more than 30,000 X3 vehicles.
  • Agility reports more than 65,000 hours of Digit 4 operation and a 100,000-tote GXO milestone at about 98% on-task accuracy; Digit 5 was announced separately in September 2026.

Not confirmed or incomplete

  • The robots solve different tasks, so hand dexterity and logistics throughput should not be scored as one metric. Public intervention rates and long-duration uptime are missing.
  • Company-reported metrics are not independently audited unless a separate primary record establishes the same result.
  • Long-duration reliability, intervention frequency and complete failure distributions are rarely published.

Likely to change quickly

  • Prices, model versions, APIs, software access and commercial availability.
  • Production, customer pilots, deployments and repository maintenance status.

Share this article

Share the current TechniaHQRobot article page.

Continue reading

Open the latest robotics reporting, Physical AI analysis and hardware notes.

Browse robotics news
Article by @techniahqrobot