Toolspublished

NVIDIA’s TensorRT Model Connect Skips ONNX, but x86_64 Users Must Build From Source

The open-source preview turns model conversion into a versioned deployment artifact, separating engine construction from native inference while imposing an ARM-first installation path.

By 3 min read
NVIDIA’s TensorRT Model Connect Skips ONNX, but x86_64 Users Must Build From Source

Listen to this story

The audio brief

About 1:43
0:001:43
Read transcript
NVIDIA has released TensorRT Model Connect in public preview, and its key move is to skip ONNX entirely: a supported Hugging Face checkpoint can become a versioned .bundle artifact that a native C++ application loads directly. The goal is to separate engine construction from inference, so production systems do not need to carry PyTorch through the runtime path. The workflow accepts a model ID or local checkpoint, builds TensorRT engines and related assets, and exposes task-level APIs for text, images, and audio. There is also a lower-level module API for more control. NVIDIA’s quick start builds Qwen3-0.6B in bf16, with a cache length of 16,384 tokens, then runs the resulting bundle from the command line. That command is primarily a build-and-package step; the same artifact can move into C++ software. There is an important exception. Native profiles avoid PyTorch at inference, while hybrid profiles still launch a Python helper, with that dependency recorded in their manifests. Custom GPU kernels can also be added through TVM FFI. The immediate constraint is installation. Published wheels require Linux aarch64, Python 3.10 or 3.12, glibc 2.39 or newer, and TensorRT 11.1.0.106. x86_64 users must build from source through Docker. NVIDIA reports that 102 of 105 tested profiles beat declared references by more than five percent, but that is a company-reported snapshot—not a universal guarantee. The open question is whether this clean bundle boundary can broaden beyond its current ARM-first path.

Story brief

3 key points

NVIDIA’s public-preview TensorRT Model Connect defines a packaging and serving boundary around TensorRT: supported Hugging Face or local checkpoints become versioned .bundle artifacts that native C++ applications can load. The workflow may reduce deployment dependencies, but it is currently practical mainly for Linux aarch64 users. NVIDIA publishes no x86_64 wheels, requiring a Docker-based source build, and some...

  1. 01

    TRTMC’s quick start builds Qwen3-0.6B at bf16 and supports a 16,384-token cache length.

  2. 02

    Native profiles remove PyTorch from the inference runtime; hybrid profiles explicitly retain a Python helper dependency.

  3. 03

    Current wheels require Linux aarch64, Python 3.10 or 3.12, glibc 2.39+, and TensorRT 11.1.0.106.

NVIDIA has released TensorRT Model Connect, or TRTMC, in public preview: an Apache-2.0 tool that takes supported Hugging Face or local model checkpoints to TensorRT inference in two commands, without an intermediate ONNX export. Its central promise is operational: teams can move the resulting artifact into a native C++ application without carrying PyTorch through the runtime path.

The bundle becomes the handoff

TRTMC accepts a model ID or local checkpoint and creates a deployment bundle containing TensorRT engines and runtime-specific assets. The resulting versioned .bundle file loads through native C++ task APIs, creating a defined boundary between model building and the software that serves inference.

NVIDIA frames the conventional route as PyTorch through ONNX or TorchScript to TensorRT, followed by model-specific C++ integration. TRTMC instead exposes task-level inputs and outputs for text, images and audio, with a semantic API for more managed deployment and a module-level API for finer control.

A command-line build, then a native target

The documented quick start builds Qwen3-0.6B at bf16 precision and runs the bundle from the command line. The same bundle can be loaded from C++, making the command-line step a build and packaging path rather than the required production-serving environment.

trtmc build Qwen/Qwen3-0.6B --precision bf16 --max-cache-length 16384 --output qwen3-0.6b.bundle
trtmc run ./qwen3-0.6b.bundle --prompt "What is the capital of France? Answer in one word." --chat-template --no-thinking

PyTorch-free has an exception

For native profiles, inference can run in C++ without PyTorch in the runtime path. The design is not universal: a small number of hybrid profiles invoke a helper Python executable, and their manifests explicitly declare that dependency.

TRTMC also supports custom GPU kernels through TVM FFI, offering a route to extend specialized deployments beyond the provided task APIs.

The installation constraint is immediate

Current release wheels target Linux aarch64 only, with Python 3.10 or 3.12, glibc 2.39 or newer, and TensorRT 11.1.0.106. No x86_64 wheels are published, so users on that architecture must build from source through Docker.

NVIDIA’s July 29 GB300 snapshot covered 105 profiles across 76 model families; 102 beat their declared reference by more than 5%. That company-reported result is a snapshot rather than a guarantee for every checkpoint, hardware configuration or workload.

NVIDIA says it uses nightly releases and automated validation to support new models and architectures. It also says Codex agents built the project’s implementations, tuning, tests, integrations and documentation under human direction and review.

Sources

  1. marktechpost.comNVIDIA Releases TensorRT Model Connect in Public Preview: Hugging Face Checkpoint to Native C++ Inference in Two Commands
  2. blockchain.newsNVIDIA TensorRT Model Connect Simplifies AI Deployment