Skip to main content

Motrix Deploy

motrix-deploy runs exported policies without a training framework. It provides deployment artifacts, robot/task contracts, shared control execution, runtime plugin discovery, and the implementation behind mxlab deploy. Install motrixlab for the sole mxlab CLI; this component retains its Python APIs and internal callable deployment adapter. Use mxlab --version to query the version. Install the task and runtime plugins needed for your target. motrix-deploy does not depend on motrix-rl: training-run export belongs to motrix-rl, which depends on this package, while deployment runs independently. Create artifacts with mxlab export-deploy run_dir=<run-dir> output=artifacts/policy.deploy; see the deployment tutorial for export. Environment packages provide profile compilers through package registration callbacks in motrix_deploy.profiles; see adding a profile compiler for the provider recipe and discovery requirements.

With the Go2 task and a simulation backend installed:

mxlab deploy task=go2-walk-flat/sim artifact=artifacts/go2-walk-flat.deploy

Hardware API

Hardware backends return a fully constructed HardwareRuntime, independent of the robot model or transport:

from motrix_deploy.runtime.hardware import HardwareRuntime

runtime = HardwareRuntime(robot)  # An already constructed RobotInterface.

Construction does not open the robot connection. Bind a ControlSession before running; robot startup, enable, safe stop, and transport cleanup remain owned by the interface. The runtime uses the robot's optional gamepad device unless one is explicitly supplied.

For CLI recipes, hardware backend entry points in motrix_deploy.backends implement factory(config, context) -> HardwareRuntime. The context supplies the artifact's robot and control specifications. create_hardware_runtime validates and returns the plugin-created runtime; hardware plugins own runtime construction and may configure its scheduler or gamepad. Simulation entry points continue to return a SimulationRuntime.

See the deployment tutorial for export, simulation, and hardware workflows, or the Python example for programmatic control.

Metadata

Release files for motrix-deploy 0.4.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distribution (wheel)

Table of built distributions (wheels) for motrix-deploy 0.4.0
File Interpreter ABI Platform Actions
motrix_deploy-0.4.0-py3-none-any.whl Python 3 none any Details for motrix_deploy-0.4.0-py3-none-any.whl

Release files / motrix_deploy-0.4.0-py3-none-any.whl

Download URL motrix_deploy-0.4.0-py3-none-any.whl
Size 43.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
e5ea13bd1d54b989926c290eed1a3b9a095d1d95bb3dc3d33b38060e07d6b2f7
BLAKE2b-256 checksum
How to use checksums
04b3d742f20661307323cabfb3ade1334facbafb52d2b2cf3f60d7ff5b4820bc
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 19, 2026.

Transparency log

Security for motrix-deploy 0.4.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 1 file in this release has been uploaded with provenance metadata.

Attestation for motrix_deploy-0.4.0-py3-none-any.whl

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 19, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page