What does Figure's BMW Spartanburg humanoid deployment actually look like?

What is verified about the BMW Spartanburg deployment

Figure AI's Figure 02 humanoid robot has operated commercially at BMW Group's Spartanburg, South Carolina plant since August 2024 as a pilot, scaling to full live-production deployment with verified output. Per Figure AI's November 19, 2025 announcement, the deployment produced:

• More than 30,000 BMW X3 vehicles built with Figure 02 robots contributing to chassis assembly
• 11-month live-production deployment from August 2024 through July 2025 (the formal pilot-to-production phase)
• 1,250 hours of runtime accumulated across the deployment period
• More than 90,000 parts handled in chassis-assembly tasks
• 10-hour shifts Monday through Friday

BMW Group simultaneously confirmed the Spartanburg deployment's success and announced expansion to its Plant Leipzig facility as the second humanoid production site. The dual-plant trajectory makes Figure-and-BMW the most operationally-developed humanoid manufacturing partnership in the cohort.

Why end-product OEM acceptance verification matters

Per DEPLOY's verified-vs-claimed framework on capability claims, the BMW Spartanburg deployment occupies a structurally distinct verification position from peer humanoid pilots. Most humanoid enterprise pilots verify against cycle-counting metrics (how many times the robot performed a task). BMW Spartanburg verifies against end-product OEM acceptance: the 30,000 vehicles built with Figure 02 robots passed BMW's normal quality-control process and shipped to dealers for retail sale.

The verification bar is structurally higher than logistics cycle-counting for several reasons:

• Customer warranty chain: the vehicles Figure 02 helped build carry BMW's brand warranty. If a robot-assembled component fails in the field, BMW's warranty obligations and brand reputation are exposed.
• Engineering acceptance: BMW's quality assurance team, manufacturing engineering team, and procurement organization all accepted Figure 02's chassis-assembly work as production-grade across an 11-month operational envelope.
• Seasonal and operational variation: 11 months spans seasonal product mix, line-rate variation, engineering change orders, and customer-relationship maturation. The deployment ran across the full operating envelope BMW puts its production line through.
• Compared to internal-facility pilots: per DEPLOY's maker-facility rule, deployments inside the maker's or parent corporation's own facility classify as research rather than customer commercial deployment. BMW is an independent customer of Figure; the Spartanburg deployment is verified third-party commercial deployment, not internal research.

Where Figure 02 ends and Figure 03 begins

A factual disambiguation worth surfacing because consumer queries and trade-press summaries frequently conflate the two generations:

• Figure 02 is the BMW Spartanburg deployment. The 30,000-vehicle anchor is Figure 02's verification record, not Figure 03's.
• Figure 03 is the current-generation Figure platform. Per the registry, Figure 03's confirmed customer deployment as of mid-2026 is the Catalyst Brands Reno distribution center, not BMW. See what is Figure 03 for the full Figure 03 institutional and deployment context.

Whether Figure 03 eventually deploys at BMW Spartanburg (or Plant Leipzig) is a forward question. As of the current corpus state, Figure 02 remains the BMW anchor and Figure 03 anchors at Catalyst Brands. DEPLOY surfaces this distinction explicitly because the forward question and the current state are editorially distinct artifacts.

Where this deployment sits in the cohort

Applying DEPLOY's four-tier capability framework and five-tier availability framework:

• Capability tier: verified enterprise-deployed. The BMW Spartanburg deployment is the canonical exemplar of this tier across the humanoid cohort, with end-product OEM acceptance distinguishing it from logistics-throughput deployments.
• Availability tier: not applicable. Figure 02 is enterprise-deployed; no consumer commerce surface exists; per-unit pricing is enterprise-contract-bound and not publicly disclosed.

Comparing across the cohort's enterprise-deployed automotive manufacturing pilots:

• Figure 02 at BMW Spartanburg (this piece): 30,000 vehicles, 11-month operational record, end-product OEM acceptance. Plant Leipzig expansion announced.
• Apptronik Apollo at Mercedes-Benz: Berlin Marienfelde Digital Factory and a Hungarian assembly plant; structural pilot operating across two European facilities.
• Boston Dynamics Atlas at Hyundai Metaplant America: Savannah, Georgia EV manufacturing facility; pilot context. Hyundai is Boston Dynamics' parent company; per the maker-facility rule this is research-tier rather than independent commercial deployment.

Three automotive humanoid pilots, three structurally distinct positions: Figure 02 at BMW operates with the strongest verification anchor (end-product OEM acceptance at 30K-vehicle scale); Apollo at Mercedes operates dual-facility European pilots with disclosure depth still developing; Atlas at Hyundai Metaplant operates parent-corporation-facility pilots with the editorial qualification the maker-facility rule introduces.

What the framework cap-flags at BMW Spartanburg

Per DEPLOY's discipline, the BMW Spartanburg deployment is editorially clean on its core verification surface but several adjacent claim layers sit at cap-flag tier:

• Economic productivity figures: Figure's claims about productivity gains, hours saved, or per-unit cost impact at BMW Spartanburg are not publicly disclosed at the depth that the 30,000-vehicle production figure is verified.
• Plant Leipzig deployment scope: the expansion announcement is verified; specific deployment timeline, scale, and task scope are not yet at the disclosure depth of Spartanburg.
• Figure 02 vs Figure 03 future at BMW: whether Spartanburg upgrades to Figure 03 or remains on Figure 02 is a forward question. No commitment has been disclosed at the depth that would justify framework reading.

Where to go for context

For canonical institutional depth on Figure AI as the maker, see Figure AI's registry record. For the BMW Group customer context including the broader Plant Leipzig expansion, see BMW Group's registry record. For the foundational signal anchoring this deployment, see Figure 02 BMW Spartanburg 30,000 vehicles signal.

For the broader Figure 03 generation context, see what is Figure 03. For Figure 03's distinct Reno deployment, see Figure at Catalyst Brands Reno deployment deep-dive.

For the framework DEPLOY applies to deployment status across humanoid makers, see how DEPLOY verifies deployment status. For the broader humanoid capability and availability frameworks, see what can humanoid robots actually do today and can I buy a humanoid robot in 2026. For consumer-evaluation context on Figure 03 specifically, see Figure 03 pricing. For methodology canonical references applicable to BMW Spartanburg deployment: the 4-way autonomy-boundary taxonomy (enterprise-deployed tier; end-product OEM acceptance verification) + verified-vs-claimed at within-entity granularity (Figure 02 vs Figure 03 generation distinction) + the 9-tier source-quality rubric.