# OEM Expansion Figures
OEM-04
OEM Deployment Spectrum
OEM delivery can progress from hosted API access through local workers and embedded sidecars to controlled private deployment.
Four OEM deployment models ordered from hosted API through local worker and embedded sidecar to private deployment.
OEM-05
OEM Pilot to Production
A representative-object pilot should prove contract fit, output value, return-path fidelity, and operational ownership before production expansion.
Governed OEM lifecycle from representative input through contract validation, result review, return-path testing, production decision, and expansion.
Pilot lifecycle
- 1Select representative inputUse a sanitized object that reflects the partner workflow and data contract.
- 2Validate the contractConfirm identity, schema, versioning, failure handling, and provenance.
- 3Run the capabilityProcess the representative input through the agreed SecEng module.
- 4Review output valueAssess usefulness, evidence quality, workflow fit, and partner differentiation.
- 5Validate the return pathReturn a partner-usable object without losing state or provenance.
- 6Define production ownershipAssign support, deployment, monitoring, versioning, and escalation.
Retest loop returns to Validate the contract
What does the pilot justify?
- Stop
- Refine the pilot
- Production planning
- Expand capability