Equipment OEMs, integrators, brand sourcing teams and materials suppliers all touch the same shoe. Partnering means the plant gets one autonomy layer instead of five disconnected ones.
Each has a defined technical path and a defined commercial one.
Cutting tables, stitchers, presses, lasting machines and ovens. Ship your machine Footeon-ready with a certified connector and a joint reference line.
Deploy and support Footeon inside plants you already serve, with training, sandbox access and deployment playbooks.
Standardise quality evidence across your contract manufacturers with one audit format and one set of quality agreements.
Leather, textile, EVA, PU, rubber and adhesive suppliers whose lots drive process windows. Feed datasheets in, get outcome data back.
A certified connector turns a machine into a node the agents can actually control.
| # | Node | Agent | Depends on | Status |
|---|---|---|---|---|
| 01 | Twin simulate | Yield-and-Energy | — | SUCCEEDED |
| 02 | Cut and nest | Cut-and-Nest | Twin simulate | SUCCEEDED |
| 03 | Stitch upper | Stitch-and-Upper | Cut and nest | SUCCEEDED |
| 04 | Mould sole | Mold-and-Sole | Stitch upper | SUCCEEDED |
| 05 | Last upper | Last-and-Bond | Mould sole | SUCCEEDED |
| 06 | Bond sole | Last-and-Bond | Last upper | APPROVAL |
| 07 | Inspect pair | Quality-and-Fit | Bond sole | SUCCEEDED |
| 08 | Finish and pack | Robot-and-Assembly | Inspect pair | SUCCEEDED |
Roughly eight weeks from first call to a listed connector.
Agree which parameters are readable, which are writable, and which are validated.
week 1
Implement against the connector SDK in Python, Go or Rust with our engineers on call.
weeks 2–5
Conformance suite, latency benchmark and fail-closed behaviour verified on real hardware.
weeks 6–7
Published in the connector catalogue and available to every Footeon plant.
week 8
Shipped adapters across the plant. Certified partner connectors are added here.
Connectors ship as versioned adapters. Anything not listed is reachable through OPC UA, MQTT, Modbus TCP or the Footeon REST/gRPC API.
The trade is straightforward.
Early stage and deliberately small.
A connector maps machine capabilities to Footeon tools with enforced ranges.
from footeon.connector import Connector, Capability
press = Connector(vendor="acme-press", protocol="opcua")
press.capability(Capability(
tool="press.set_recipe",
writable=["temp_c", "pressure_bar", "dwell_s"],
readable=["temp_actual", "pressure_actual", "cycle_state", "alarms"],
ranges={"temp_c": (140, 190), "pressure_bar": (2.0, 5.0)},
validated=True,
fail_closed="hold_last_known_good",
))
press.certify() # runs conformance, latency and fail-closed suitesIllustrative outcomes from joint reference lines.
“The nesting agent found yield our best pattern cutter could not — and then explained the layout hide by hide. We stopped arguing about scrap and started managing it.”
Leather yield 79.1% → 87.4%
“Bonding is where our warranty costs live. Having an agent watch humidity, primer flash-off and press pressure on every pair — and stop for a human when it wants to move a validated parameter — is the first thing that has actually moved delamination.”
Delamination returns −71%
“We run 40 model changeovers a month. Simulating the nest, the mould recipe and the bond window in the twin before the line starts took hours out of every launch.”
Changeover time −46%
Design-partner scenarios are illustrative and modelled on public footwear-manufacturing benchmarks — named references are [PLACEHOLDER] pending customer approval.
Connectors run inside the sandboxed edge runtime and inherit its controls.
No. Footeon is a software and factory-edge autonomy layer that sits on top of the machines you already run. We connect over OPC UA, MQTT, Modbus TCP and vendor SDKs, read sensors and vision, and write setpoints back through the controls you already trust — with approval gates on any validated parameter.
Only if you choose. Inference runs on factory-edge servers, and Enterprise deployments can run fully on-premises or in your VPC with no telemetry egress. Brand IP — patterns, lasts, construction specs — is tenant-isolated and never used to train models for another customer.
Line at $8,000 per line per month for one workflow, Factory at $55,000 per month for the whole loop, and Enterprise from $350k to $4M ACV for multi-site networks with custom material, last and bond models. Outcome-based components are available on leather waste, rework and returns.
A typical wedge deployment on one line runs six to ten weeks: two weeks of sensing and baseline capture, three to five weeks of shadow-mode model tuning against your material lots, then graduated autonomy. Whole-factory rollouts follow line by line.
Tell us what you build and which plants you serve. We will scope a connector and a reference line.