Platform

The architecture behind unified robot orchestration

A four-layer stack: real-time connector, protocol normalizer, AI scheduling engine, and telemetry pipeline. Each layer is independently deployable.

11

Robot vendors supported

<8ms

Median command latency

99.7%

Uptime in pilot cells

1

Unified API schema

Four layers, one coherent stack

Sancho is not a monolithic middleware. Each layer handles a discrete concern: the connector layer speaks the vendor protocols; the translation engine normalizes them into a single event schema; the AI orchestrator schedules jobs and propagates alarms across vendors; the telemetry pipeline surfaces cell-wide state to your MES or analytics stack. Your team can adopt a single layer or deploy all four from day one.

Connector Layer Vendor protocol drivers
Translation Engine Unified event schema
AI Orchestrator Job routing and scheduling
Telemetry Pipeline MES and analytics export
Sancho platform architecture diagram showing four layers
Connector Reference

Every controller we speak

Connectors are versioned, regression-tested against real hardware, and carry a stability label. Beta connectors are in active production pilots with early customers.

Robot Arms

FANUC R-30iB / R-30iB+

Karel + FOCAS2 over Ethernet

stable

KUKA KR C4 / KR C5

KUKA RSI + KRL remote

stable

ABB IRC5 / OmniCore

RWS 2.0 + EGM

stable

Universal Robots e-Series

RTDE + URScript socket

stable

Yaskawa Motoman YRC1000

MotoPlus + ROS-I

beta

Doosan M0609 / M1013

DRL SDK over TCP

beta

Field Protocols

OPC-UA

Server + subscription model

stable

EtherNet/IP

CIP explicit + implicit

stable

Siemens S7 PLC (TIA Portal)

S7comm via libnodave

stable

MQTT 3.1.1 / 5.0

Edge broker passthrough

stable

PROFINET IO

RT class 2 + 3

beta

Modbus TCP

Coil + register mapping

beta

MES Uplink

REST webhooks

Cell events to any HTTP endpoint

stable

gRPC streaming

Low-latency telemetry export

stable

SAP DMC

Plant order integration

beta

Plex AMS

Production tracking sync

beta
Cell Configuration

Declare your cell in one YAML file

No GUI wizard required. Define robots, protocols, and routing rules as code. Version-control your cell configuration alongside your application code.

cell-config.yaml 
# Sancho cell configuration
cell_id: "assembly-b3"
site: "san-jose-plant"

robots:
  - id: "arm-fanuc-01"
    vendor: "FANUC"
    model: "LR-Mate 200iD"
    connector: "fanuc-karel-v2"
    ip: "192.168.10.11"
  - id: "arm-ur-02"
    vendor: "UR"
    model: "UR10e"
    connector: "ur-rtde-v3"
    ip: "192.168.10.12"

orchestration:
  mode: "ai-scheduled"
  latency_target_ms: 5
  failover: "next-available"

telemetry:
  export: "grpc"
  endpoint: "mes.internal:50051"
Get Started

See the platform against your cell layout

We run a 45-minute technical walkthrough scoped to your exact vendor mix. No slides, all live demo on hardware we've already integrated.

Request a walkthrough Solutions by vertical