Robot Orchestration Layer
One AI layer for every robot on your floor
Sancho connects FANUC, KUKA, ABB, UR, Siemens, and more into a single AI-driven orchestration plane. No manual hand-coding between incompatible controllers. No week-long re-integrations when you add a new arm.
The Problem
Four vendors, four protocols, four integration projects
Every time a manufacturer adds a robot arm from a different vendor, the engineering team faces weeks of integration work. FANUC speaks one dialect, KUKA another, ABB a third. The controllers were never designed to talk to each other, let alone to the MES, the vision system, and the quality cameras above the line.
The result: a disproportionate share of every automation project budget disappears into protocol translation, and production agility is capped at the slowest integration cycle.
Sancho eliminates that ceiling. A single connector layer translates across all vendor protocols in real time, exposing a unified API your AI agents and MES can actually use.
From fragmented controllers to a unified cell
Three steps from install to autonomous operation.
01
Deploy the Connector
Install a single Sancho edge agent on your cell network. It auto-discovers every robot controller, PLC, and vision system on the subnet within minutes, no manual endpoint configuration.
02
Translate Protocols
Sancho normalizes FANUC Karel, KUKA KRL, ABB RAPID, UR Script, OPC-UA, and EtherNet/IP into a single event-driven API. Your orchestration logic reads one schema regardless of vendor.
03
Orchestrate with AI
Connect the Sancho API to your AI agents or use our built-in scheduling engine. Route jobs to the next available arm, respond to real-time alarms, and surface cell-wide telemetry to your MES.
The vendors on your floor, on day one
Stable connectors ship tested against real hardware. Beta connectors are in production pilots.
Robot Arms
Field Protocols
MES / Upstream
What pilot customers found
"Cell commissioning time dropped from three weeks to four days on our first pilot workcell with Sancho. The unified API was the piece we had been building around instead of having."
3 wk
to 4 days, first pilot cell commissioning time (early-access data)
14
integration types covered across stable and beta connectors
<8ms
median command round-trip across vendor connectors (measured in pilot cells)
Built on a factory floor, not in a conference room
Sancho started in 2025 after our founders ran into the same integration wall across multiple automation projects. ABB on one side, FANUC on the other, a Siemens S7 in the middle, and nothing talking to anything. Each project, the same 14-week integration slog.
The first protocol bridge was written to solve a specific problem on a real cell. The first production deployment ran on a 12-arm EV battery assembly cell. We have been building from that production reality ever since.
Meet the team
Chao Cao
CEO and Co-founder
Rafael Moreno
CTO and Co-founder
Ingrid Svensson
Head of Customer Engineering
Ready to connect your cell?
Request access to the pilot program. We work with 3 to 5 new facilities per quarter.