ModuleX vs Locus Robotics

ModuleX is software. Its AI Composer takes a plain-English process description, asks clarifying questions, then produces a typed-node graph on a visual canvas you can edit node by node, with a changelog of every change it applied. The Assistant can search connected tools, request access to a service it lacks, and pause for human approval before any write or delete. Knowledge nodes pull from uploaded documents, Files is a built-in workspace workflows read and write, and published workflows can be exposed as an MCP server for Claude Code, Cursor, Codex, Hermes or OpenClaw. BYOK applies per integration. Recent changelog items (Files, MCP publishing, access requests, approval pauses) all extend the same theme: inspectable, human-gated automation over Slack, GitHub, Notion, Gmail, Stripe, Linear and HubSpot. Locus Robotics is hardware-plus-orchestration. Locus Origin handles person-to-goods picking, Locus Vector moves heavy or oversized inventory, and Locus Array has robots pick and consolidate orders in the aisle; LocusONE assigns tasks across robots, people and workflows in real time, with LocusIntelligence behind routing. Workflows span picking, putaway, replenishment, slotting, sortation, returns and pick-and-pass, scaling from 10 to 1,000+ robots per site and connecting to 65+ WMS/ERP systems including SAP EWM, Manhattan and Blue Yonder. The feature sets share vocabulary (workflows, orchestration, integrations) but zero functional overlap.

ModuleX is freemium with run-based credits — the vendor's own not-for list flags roughly 1-cent credits per run as a poor fit for high-volume, low-cost pipelines. Integrations use BYOK billed at no ModuleX markup, so model and API spend stays with your provider; self-hosted deployment is gated behind an Enterprise agreement. Locus Robotics publishes no list price; it sells Robots-as-a-Service as a subscription bundling deployment, optimization, field services and 24/7 global support. That structure converts a capital project into recurring spend, but the payback depends entirely on daily pick volume — the vendor itself names low-volume warehouses as a bad fit. A buyer cannot meaningfully cost these against each other: one is per-run software credits on a card, the other is a multi-year site-level subscription with robots installed on a warehouse floor. Budget cycle, approval path and spend category all differ.