Zaro vs Locus Robotics

Locus Robotics is hardware-plus-orchestration: Locus Origin for person-to-goods picking, Locus Vector for heavy payloads and transport, and Locus Array where robots pick and consolidate directly in the aisle. LocusONE assigns tasks across robots, people and workflows in real time, LocusIntelligence drives routing decisions, and the platform supports picking, putaway, replenishment, slotting, sortation, returns and material transport, including mezzanine and multi-level sites without fixed infrastructure. Connectivity extends to 65+ WMS/ERP systems via API, with dashboards in LocusONE. Zaro is a software context layer: company knowledge lives as files (pipeline-q3.md, customer-tiers.yaml, objection-playbook.md) that the work writes back to, so versioning is inherent and updates land in seconds. Every answer cites the file and version, opens to show who last changed it, and sits behind scoped read/call/change permissions plus an audit trail. Applied modules cover retail store intelligence, go-to-market intelligence, and distributed manufacturing. The two feature sets share no capability — one moves atoms, the other governs context.

Locus Robotics does not publish pricing; it is a sales-led subscription. The RaaS model bundles deployment, optimization, field services and 24/7 global support into a recurring fee, which the vendor positions as an alternative to large upfront CapEx. Payback depends on pick volume, so low-volume sites are explicitly a poor fit. Zaro is freemium with credit-based usage drawn from a shared pool and no per-seat fees; credit top-ups roll over for 12 months. There is no hardware, no site survey, and no deployment project fee visible in the data — but there is an upfront cost in effort: seeding context requires a find-clean-agree-govern project, and the files must be maintained or answers go stale. Comparing the two price lines is meaningless: one is a per-site automation contract measured in robot fleets, the other is a usage-metered software layer. A buyer's decision should be driven by whether the spend removes labor travel or removes AI answer ambiguity.