Composable ML pipelines for reproducible experiments.
NexuML is a modular PyTorch framework for building machine-learning systems from reusable, typed components connected through explicit TensorDict keys. A ScenarioSpec describes data, model pipelines, training, evaluation, logging, export, and execution in one place and can be persisted as validated YAML.
Why NexuML?
ML projects often start as a clean notebook and gradually collect project-specific dataset code, model wiring, training loops, evaluation scripts, and export logic. Copying a project template improves the folder structure, but it still duplicates implementations and makes experiments harder to reproduce or extend.
NexuML separates reusable implementations from experiment composition. Datasets, model blocks, evaluation algorithms, and loader backends can live in libraries; scenarios assemble those pieces into explicit pipelines without reimplementing the training lifecycle for every project.
Core ideas
- Typed component definitions — Python scenarios construct concrete Pydantic definitions directly; stable registry identities are used for discovery and persisted YAML.
- TensorDict pipelines — named tensors flow through ordered stages using explicit
keys_inandkeys_outcontracts. - Declarative scenarios —
ScenarioSpeccomposes data, pipeline, training, evaluation, logging, checkpoint, export, and execution configuration. - One Lightning lifecycle — PyTorch Lightning owns the training loop; local and Ray execution reuse the same NexuML session semantics.
- Pluggable data paths — PyTorch, NVIDIA DALI, and tensor-shard loaders plus dataset export to NumPy, mmap, Torch, TensorDict memmap, WebDataset, and tensor shards.
- Post-training evaluation — typed evaluation definitions materialize stateful algorithms while fitted pipeline layers can perform post-train processing before test.
- Portable model artifacts — export a compiled pipeline with weights, resolved configuration, metadata, and dependency information.
- CLI workflow — inspect registries and backends, resolve scenarios, build pipelines, train, tune, export datasets, and package models.
Install
NexuML is currently published on TestPyPI. PyPI remains the fallback for dependencies.
For most users, install the framework together with the reusable base library:
uv pip install --index https://test.pypi.org/simple --default-index https://pypi.org/simple "nexuml[library]"
Install only the framework and CLI when you want to provide all components yourself:
uv pip install --index https://test.pypi.org/simple --default-index https://pypi.org/simple nexuml
NVIDIA DALI, Ray, tracking, tuning, S3, and export integrations are optional. See the installation guide before adding platform-specific extras.
Container image
The complete Linux AMD64 development and training environment is also published with an explicit NexuML and CUDA version:
docker pull ghcr.io/nexufed/nexuml:0.2.0-cuda12.8.1
docker run --rm -it --gpus all ghcr.io/nexufed/nexuml:0.2.0-cuda12.8.1
The image contains both NexuML packages and all optional extras. See the installation guide for host requirements and other tags.
First look
With the base library installed, inspect a real scenario without starting a training job:
nexuml registry list scenarios
nexuml resolve cifar-resnet
nexuml build configs/cifar-resnet.yaml
This shows the central NexuML flow: a Python scenario is resolved to a reproducible configuration and then materialized into a validated TensorDict pipeline. Continue with Get started for training requirements.
Learn by building
The NexuML Tutorial repository is the home for complete hands-on projects. It builds an external NexuML library from scratch rather than hiding the framework behind finished built-in components.
The learning path starts with MNIST library basics, then adds file-backed Speech Commands audio with native DALI loading and demonstrates pipeline composition by swapping a CNN encoder for a Transformer while reusing the rest of the system.
Version note: the tutorial repository evolves independently from NexuML. NexuML 0.2 uses typed component definitions and rejects the legacy selector/parameter-bag syntax, so use a tutorial revision compatible with the NexuML version you install.
Documentation
- Get started — install NexuML and inspect your first scenario.
- Tutorials — complete hands-on projects and the tutorial compatibility note.
- Guides — accomplish a specific task such as training, tuning, exporting, or adding a component.
- Concepts — understand the architecture, TensorDict data flow, definitions, discovery, and scenarios.
- Reference — exact CLI, configuration, backend, decorator, and Python API information.
Extending NexuML
External libraries can provide their own typed layers, data sources, evaluation algorithms, loader backends, and scenarios through the nexuml.libraries entry-point group or a local library root. See Build a custom library for the package structure and component contracts.
Metadata
Release files for nexuml 0.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| nexuml-0.2.1.tar.gz | 129.3 kB | With provenance | Details for nexuml-0.2.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| nexuml-0.2.1-py3-none-any.whl | Python 3 | none | any | Details for nexuml-0.2.1-py3-none-any.whl |
Total release size: 291.8 kB
Release files / nexuml-0.2.1.tar.gz
| Download URL | nexuml-0.2.1.tar.gz |
|---|---|
| Size | 129.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9f53186ea5750c42c40861057371bc85754eaaf8a9520bffa751ece09a3c2695
|
|
BLAKE2b-256 checksum How to use checksums |
804a6c20a56d737835518450a5ba5726beb92af74ed6059fd9784f4e445df744
|
| 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 Sep 3, 2026.
Transparency logRelease files / nexuml-0.2.1-py3-none-any.whl
| Download URL | nexuml-0.2.1-py3-none-any.whl |
|---|---|
| Size | 162.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6d3f7dbe152e94682735211d0c23aa5a91b4ae5ffc4d7a513f96e981afe77aac
|
|
BLAKE2b-256 checksum How to use checksums |
a690233882641db19a5c842bf98f75b5b41239aa002d0556c73a322b0a0edae9
|
| 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 Sep 3, 2026.
Transparency logSecurity for nexuml 0.2.1
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 2 files in this release have been uploaded with provenance metadata.
Attestation for nexuml-0.2.1.tar.gz
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 Sep 3, 2026.
Transparency logA 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.