Who Owns the Warehouse OS

The key divide here is who owns the operating system for the warehouse. In the Symbotic model, a retailer buys a large custom automation project and lets the integrator design the flow, hardware stack, and software logic around that site. In the Cytronic model, the brand buys a service, like renting compute from AWS, so the provider keeps improving one shared fulfillment engine and spreads those gains across many customers.

• Symbotic sits on the build your own side of the line. Its business is large scale warehouse systems for enterprises like Walmart, with 70 systems in deployment, 52 operational systems, and $22.7B backlog as of Q2 2026. That fits a high capex, customer specific rollout motion more than a simple usage based service.
  2 symbotic 4 symbotic
• A closer cloud style analog inside warehouse automation is Locus. Locus drops robots into existing warehouses in 4 to 6 weeks and rents them as robots as a service at about $2,000 per robot per month, turning a $5M to $10M warehouse retrofit into operating spend. That is much nearer to buying managed infrastructure than commissioning a custom facility.
  3 sacra
• Nimble shows what often happens when a robotics company sells tech into incumbents instead of owning the service end to end. FedEx announced a strategic alliance and investment with Nimble in September 2024 to scale FedEx Fulfillment using Nimble technology, which pushes Nimble toward being embedded inside a larger operator rather than becoming the operator itself.
  1 sacra 5 fedex

The next phase of physical AI in logistics will likely split cleanly in two. Integrators will keep winning giant bespoke projects for Walmart scale customers, while service operators that own fulfillment as a product will try to become the default utility for everyone else. The larger prize is the service layer, because every cost reduction in robots, software, or workflow can be rolled out across the whole network instead of one warehouse at a time.