Shep vs Locus Robotics

Locus Robotics automates physical warehouse work. Its AMRs handle picking, putaway, and transport, while the LocusONE platform rebalances tasks across associates and robots in real time as volume and SKU mix shift. Locus Array, launched as a new class of Physical AI for Robots-to-Goods fulfillment, extends this to autonomous picking, putaway, induction, drop-off, slotting, and replenishment — the vendor claims up to 90% labor reduction with it. Deployment is designed to be rapid inside existing facilities, with multi-level and mezzanine support and point-to-point transport that needs no fixed paths or permanent infrastructure. It plugs into major WMS stacks. Shep orchestrates software, not hardware: you describe a feature in a sentence and it creates an isolated git worktree and branch, optionally drafts a YAML spec with approval gates, and runs an agent session (Claude Code, Cursor CLI, Gemini CLI, or any terminal agent) in that worktree. When the agent finishes, Shep commits, pushes, opens a draft PR, watches CI, and pushes fixes — up to three retries, configurable. Parallelism is the point: 3, 5, or 10+ features at once, with a local dashboard graph at localhost:4050 and SQLite state in ~/.shep/. It only auto-merges with --allow-merge, and it is agent-agnostic. One is a fleet of robots plus orchestration software; the other is a git-worktree scheduler for terminal agents.

There is no overlap to compare. Locus Robotics is priced as contact sales under a Robots-as-a-Service subscription — an ongoing RaaS cost that the vendor's own not-for list says won't pay back for small warehouses with low daily order volumes, so the decision is a capacity and labor-math exercise, not a sticker comparison. Expect a procurement cycle involving your WMS vendor and a facility pilot; the not-for list also flags sites with extremely narrow aisles and businesses unwilling to commit to ongoing subscription costs. Shep costs nothing. It is free and MIT-licensed, runs locally, and the feature list explicitly states no account, no usage meter, and no Shep servers. You pay only in your existing agent subscriptions and your own CI minutes. So the honest answer to 'which is cheaper' is Shep, trivially — but that comparison is meaningless because you cannot buy warehouse throughput with a free CLI. Budget on the Locus side goes to robots, deployment, and a recurring RaaS line; budget on the Shep side is essentially zero software cost. The two never appear in the same line item, which is exactly why this pairing is not a purchasing decision.