Separate commercial, limited, prototype and development stages.
Robot product dossier · 09
Proteus, Vulcan and STARK
Amazon Robotics · Amazon operations / United States and Europe · AMR · tactile manipulation · tote handling
Limited deployment / pilotOperational systems with staged expansion reported by AmazonLast reviewed: 11 August 2026
Decision questionWhat can a vertically integrated operator's robot fleet teach other warehouses—and what cannot be transferred?
09
FUURAA thesis
Proteus, Vulcan and STARK show how mobile transport, manipulation and human workflow can be designed as an operating system. Their results depend on Amazon-specific facilities, software, volume and process control.
Reading method
Do not ask only what the robot can do; ask how the whole system works, fails and recovers.
Inventory software, payloads, facilities and people beyond the robot.
Move from demos to repeated tests, field data and auditable records.
State what first-party reporting still cannot prove.
System and workflow map
Four interdependent layers turn a product name into real operating conditions.
Each layer explains its role and what procurement, research or deployment teams should watch.
Mobile flow
Proteus moves goods through shared operational spaces.
Manipulation
Vulcan and STARK target handling steps with different physical demands.
Facility software
Dispatch and inventory systems connect robots to order flow.
Human work design
Automation changes station layout, task allocation and ergonomics.
Decision checklist
Five checks turn product interest into verifiable procurement, research or pilot questions.
Define the task, interfaces, safety and operations before requesting evidence that supports a decision.
- 01
Task fit
Map each robot to a specific material-flow constraint and human task.
- 02
Integration load
Assess warehouse software, inventory, stations, conveyors and data dependencies.
- 03
Safety case
Review shared-space traffic, manipulation hazards and ergonomic outcomes.
- 04
Operating model
Define maintenance, central control, local recovery and process-change ownership.
- 05
Evidence to request
Request sustained network throughput, item coverage, intervention and worker-outcome data.
Scope boundaries
Product availability, a video demonstration or a commercial agreement each supports only bounded conclusions.
- 01
Amazon's internal operating results may not transfer to facilities with different volume or software.
- 02
A family of specialised robots is not one general-purpose robot.
- 03
Company reporting should be complemented by site-level safety and workforce evidence.
Sources and evidence status
Primary product material and independent evaluation context are kept distinct.
Dates, source identity, supported conclusions and reading boundaries remain reviewable.
01
Amazon Robotics · 2026-06-04
↗02Proteus, Vulcan and STARK — official product or programme source
A family of logistics systems including autonomous mobile transport, touch-enabled handling and collaborative tote movement.
OSHA · Accessed 2026-08-11
↗Warehousing — Hazards and solutions
Supporting material used to calibrate evaluation method and scope boundaries.