Jetson-aware inventory
The agent reports architecture, platform details and accelerator context used for operator visibility and release constraints.
NVIDIA Jetson
OTA delivery for NVIDIA Jetson fleets
Jetson fleets often combine device software, accelerated containers and model files. Meshanics keeps those payload identities separate while allowing them to travel in one signed release transaction.
Good fit
When to evaluate it
- +Vision and robotics products on Jetson
- +Fleets spanning Orin and Xavier hardware
- +Deployments where raw inference data must remain on the device
Product boundary
What the current product does
Model compatibility
Model manifests can constrain hardware profile and framework so an incompatible candidate is refused before activation.
Local evaluation
A model-evaluation adapter can decide candidate health on the device; aggregate quality windows contain counts and metrics, not samples.
Remote and isolated sites
The same signed release model works through the hosted control plane or an air-gap gateway.
Explicit limit
Meshanics does not replace JetPack, BSP flashing, NVIDIA container tooling, or a training platform. Base-OS delivery requires a product-qualified RAUC A/B image and bootloader policy.
Questions
Does Meshanics require changes to application code?
No. The static Linux agent installs on the device and activates signed payloads through typed adapters. Health behavior and recovery limits are configured for the artifact, not embedded in customer application code.
Does Meshanics certify CRA compliance?
No. Meshanics records and exports evidence for the manufacturer's compliance work. The manufacturer remains responsible for product scope, risk decisions, conformity assessment, reporting, and declarations.