We built Botpylon because warehouse robots don't talk to each other.
After watching 12 warehouse automation deployments stall at the same coordination failure, Maria Vasquez and Jonah Reyes decided the dispatch brain had to be an independent product, not a vendor add-on. Botpylon was founded in Phoenix, AZ in 2024.
The problem that built the company
Maria Vasquez spent six years in warehouse automation at a logistics integration firm, deploying robot systems across 12 fulfillment centers in the Southwest and Southeast US. Each deployment had the same arc: the robots worked. The coordination did not.
The pattern repeated at every site. A 3PL would run two or three robot vendors because no single vendor's hardware covered the full floor configuration: AMRs for free-path picking, AGVs for heavy tote transport, fixed conveyor induction at the dock. Each vendor's fleet management software ran in isolation, dispatching only to its own robots. Within six months of go-live, the operations team was watching cross-vendor congestion pile up at the same four intersections, shift after shift, with no system able to see across the vendor boundary.
The missing piece was always identical: a dispatch brain that was vendor-neutral by design, that ingested state from every fleet controller and coordinated the whole floor as one system. No robot vendor offered it because their software was built to sell their own hardware, not coordinate with a competitor's fleet. No WMS offered it because WMS systems generate pick sequences, not real-time robot routing decisions.
Maria and Jonah Reyes, who had spent years building AMR control systems and real-time fleet scheduling software, co-founded Botpylon in Phoenix in 2024 to build that layer as an independent product. The Phoenix area placed them close to the Southwest logistics corridor and the 3PL operations teams they were building for.
warehouse deployments watched fail at the same coordination point
year Botpylon was founded in Phoenix, AZ
person team across engineering, product, and customer success
proprietary hardware required. Software-only dispatch layer
Every fulfillment center deserves a dispatch brain, not a dispatch vendor.
Fleet agnosticism, not hardware bias
Botpylon does not sell robots. We do not have preferred hardware partners. We coordinate every AMR and AGV on your floor regardless of which vendor built it. The dispatch brain works for the operations team, not for the robot manufacturer's sales quota.
Dispatch brain, not WMS replacement
We are not a Warehouse Management System and we do not try to be. Your WMS knows what needs to be picked. Botpylon handles the physical coordination problem: how to move a large robot fleet through a congested floor without stop-and-wait cascades. These are different problems that need different software.
Transparent pricing as a position
We publish prices because 3PL buyers spend weeks in vendor RFP fog just to find out a system costs too much. A mid-market fulfillment operator should be able to evaluate warehouse orchestration software in an afternoon, not a quarter.
