TYPE 01
COMPOUNDING OEMs
Vacuum emulsifier and homogeniser manufacturers whose equipment becomes measurably better when a learned controller drives it.
- Co-sell into installed base
- Reference integration per vessel class
PARTNERS
The plant
is already
full of vendors.
Serumon does not replace your mixer OEM, your spectrophotometer or your filling line. It makes them act together. That makes equipment vendors, colour specialists and integrators natural channel partners rather than competitors.
5PARTNER TYPES
CHANNELGTM MOTION
OPENINTEGRATION
CO-SELLMODEL
Five agents, one runtime, one audit trail.
COMPOUNDING OEMsFILLING OEMsCOLOUR / SPECTROSYSTEM INTEGRATORSGPU / HARDWARECDMO NETWORKS
PARTNER TYPES
Five ways to work together
TYPE 02
FILLING + PACKAGING OEMs
Filler, capper and packaging line builders who want giveaway performance as a differentiator rather than a customer complaint.
- Giveaway as a spec claim
- Robot cell integration
TYPE 03
COLOUR + SPECTRO VENDORS
Spectrophotometry and colour-formulation specialists whose instruments gain a closed loop back into compounding.
- Instrument + prescription bundle
- Shared shade-standard workflows
TYPE 04
SYSTEM INTEGRATORS
Automation and OT integrators who deliver the survey, connectors, network segmentation and go-live work at scale.
- Certified delivery partner
- Adapter SDK access
TYPE 05
CDMO NETWORKS
Contract-manufacturer groups standardising autonomy across sites and selling it as a capability to brand customers.
- Multi-site enterprise terms
- Brand-scoped isolation
WHY PARTNER
What each side brings
YOU BRING
Installed base, plant relationships, mechanical and process expertise, and delivery capacity we cannot build alone at speed.
WE BRING
The autonomy layer: perception, world models, control policies, the twin, and the audit surface that makes it acceptable to quality.
CUSTOMER GETS
Equipment that hits spec more often, with one accountable loop rather than five vendors pointing at each other.
PARTNER PROGRAMME
How a partnership starts
-
01
TECHNICAL FIT
We validate integration against your equipment or instruments in the sandbox and on one real installation.
-
02
JOINT ACCOUNT
One shared customer, one wedge, one metric. Partnerships that start with a press release rather than a plant do not work.
-
03
ENABLEMENT
Your engineers get the adapter SDK, documentation and training; ours learn your equipment properly.
-
04
SCALE
Repeatable delivery playbook per equipment class, with commercial terms that reflect who does the work.
COMMERCIAL MODELS
How partners get paid
| MODEL | FIT | SHAPE |
|---|---|---|
| Referral | Vendors with plant relationships | Introduction fee on closed subscription |
| Co-sell | OEMs and instrument vendors | Joint pursuit, shared account plan, revenue share |
| Delivery partner | System integrators | Integrator bills survey, connectors and go-live work |
| Embedded | Equipment builders | Serumon capability offered with new equipment [ASPIRATIONAL] |
| Network | CDMO groups | Enterprise agreement across member sites |
INTEGRATION
What partnering technically involves
ADAPTER
An edge SDK adapter for your equipment: read, write, health, with a declarative tag schema including units and limits.
VALIDATION
Joint validation of control behaviour on a real installation before anything is offered commercially.
DOCUMENTATION
A reference integration document per equipment class so every subsequent deployment is faster.
SUPPORT PATH
A clear escalation boundary so a customer never has to arbitrate between us and you at 3am.
CHANNEL LOGIC
Why channel matters here
1000sPLANTS IN SAM
FEWDIRECT SELLERS
HIGHINTEGRATION EFFORT
DEEPOEM RELATIONSHIPS
CHANNEL SCALE IS A ROADMAP OBJECTIVE FOR THE 1–3 YEAR WINDOW [ASPIRATIONAL].
HARDWARE
GPU and edge hardware partners
Every Serumon deployment ships edge GPU compute into a plant, and every deployment drives training capacity behind it. That makes hardware partnership structural rather than incidental.
The five products span Jetson and IGX at the edge, DGX and HGX for training, and OVX for Omniverse simulation, using Isaac, Metropolis, Holoscan, Modulus, cuOpt, TensorRT, Triton and NeMo across the stack.
- Edge: Jetson Orin, Jetson Thor, IGX.
- Training: DGX and HGX class.
- Simulation: OVX for the Omniverse twin.
- SDKs: Isaac, Metropolis, Holoscan, Modulus, cuOpt, TensorRT, Triton, NeMo.
- Deployment path: NVIDIA AI Enterprise for regulated sites [ASPIRATIONAL].
HARDWARE FOOTPRINT / PLANT
- EDGE NODES
- PER VESSEL CLUSTER
- VISION NODES
- PER LINE
- ROBOT CELL
- PER CELL
- TRAINING
- CENTRAL DGX
- SIMULATION
- OVX
- REFRESH CYCLE
- PLANNED
Incumbents sell a vessel, or an instrument, or a filler. The customer still has to make them agree. That agreement is the product.
PARTNER FAQ
Partnership questions
No. We do not build vessels, homogenisers, fillers, robots or spectrophotometers, and we have no intention of starting. We make the equipment you already sold perform better.
Usually yes, through the edge SDK. Integration effort depends on how open the control interface is and what write access is available; we assess that jointly before promising anything.
Embedded arrangements are possible in principle for equipment builders, but the audit trail must remain attributable and inspectable. Anything that obscures which system moved a setpoint is not acceptable in a GMP plant.
One shared customer, one wedge workflow, one metric, with clear ownership of survey, integration and support. Everything else follows from whether that works.
PARTNER
Bring us a shared customer
The best first conversation is not about the programme structure. It is about a specific plant where your equipment and our autonomy would obviously be better together.