The loop only closes if everything talks
Treadum sits on top of equipment, inspection machines, MES platforms and robots that other people build extremely well. Partnership is how integration depth gets built once instead of re-argued at every plant.
Ecosystem we integrate with
Four ways to partner
Equipment makers
Mixing, extrusion, calendering, building and curing equipment vendors who want their machines to be first-class citizens in an autonomy loop.
Inspection vendors
X-ray, shearography, vision and uniformity machine makers. Certified adapters mean your output becomes a control input, not a report.
System integrators
Automation and controls integrators who deliver Treadum deployments alongside their own line work, under joint delivery standards.
Silicon and platform
Accelerated-computing and robotics platforms underpinning edge inference, simulation, optimization and synthetic data generation.
Built on an NVIDIA physical-AI stack
Autonomy at the station needs compute at the station
Treadum fuses high-rate image and sensor streams while serving several models per tire. That workload does not fit on a CPU box in a cabinet, and it cannot wait for a round trip to a data centre.
- Isaac and Jetson for robotic building, press handling and material movement
- Metropolis, DeepStream, TensorRT and Holoscan for vision and sensor fusion
- Cosmos and Omniverse Replicator for rare-defect synthetic data
- cuOpt for mold allocation, cure sequencing and line balancing
- Omniverse for the as-built tire and line twin
- Triton and NIM for GPU serving; NeMo for tire-process reasoning models
What each partner class gets
| Partner class | We provide | You provide | Commercial |
|---|---|---|---|
| Equipment maker | Certified adapter, joint reference architecture | Protocol documentation and test access | Co-sell, no resale margin required |
| Inspection vendor | Fusion integration and joint validation data | Stream access and defect taxonomy alignment | Co-marketing and joint deployments |
| System integrator | Delivery training, deployment playbooks, support tier | Certified engineers and delivery quality standards | Delivery margin on integration scope |
| Silicon / platform | Reference workloads and benchmarks | Hardware access and engineering support | Joint go-to-market |
How a partnership starts
- Scope: Agree which machines, protocols or workloads are in scope and what a certified adapter must prove.
- Build: Joint engineering on the adapter or reference workload, with test data from the simulator or a partner site.
- Validate: Certification against the same golden-dataset and latency gates production deployments must pass.
- Deploy: First joint site, delivered together, with a shared runbook and a single escalation path.
- Scale: Adapter enters the standard catalogue and is reused across every subsequent deployment.
What we hold joint deployments to
One standard, regardless of who delivers
Integrator-delivered sites follow the same baselining, gating and envelope discipline as ours. A partner cannot shortcut shadow mode, and neither can we.
One escalation path
The customer never arbitrates between vendors. Joint deployments run a single escalation path with agreed response times.
Customer data stays customer data
Partners get no access to plant data beyond what the customer explicitly grants for the delivery scope.
Adapters are tested, not asserted
Every certified adapter has a test suite and a latency budget, and re-certifies on firmware changes.
We will say if it is not a fit
If an integration cannot meet the gates, we say so publicly rather than shipping something that will erode trust in autonomy.
What joint customers say
“We had three people watching X-ray images and still shipped uniformity rejects. Treadum flagged the cord shift at the building drum, not four hours later at final inspection.”
“The cure agent found 40 seconds of margin on a construction we had run the same way for eleven years. It proved it in shadow mode before it touched a press.”
“Genealogy is the part I did not expect to care about. Every tire now has a linked record from batch to grade, and audit prep went from weeks to an afternoon.”
[PLACEHOLDER] Design-partner quotes are illustrative until pilot references are published.
Partner program at a glance
Working with us
No. We specify and validate edge hardware and help size it, but procurement runs through you or your preferred supplier. We would rather be neutral on hardware.
After certification, yes for standard scopes. The first deployment is always joint, and envelope signing always involves us and the customer directly.
If a customer needs it, usually yes. If you provide protocol documentation and test access, it is faster, better and gets certified.
That is the customer’s call. We will integrate honestly and let the results decide, provided the envelope discipline is respected by everyone writing to the line.
Put one cell on autonomy in 90 days
Pick one wedge — splice inspection, X-ray defect detection, cure-state optimization or uniformity prediction. We baseline it, run shadow mode, then graduate to bounded autonomy under a signed control envelope.
Pilots start in shadow mode. No line changes until accuracy and safety gates pass.