This release is a pre-release and may not be stable for production use.
Built on Kubernetes. Konduktor uses existing open source tools to build a platform that makes it easy for ML Researchers to submit batch jobs and for administrative/infra teams to easily manage GPU clusters.
How it works
Konduktor uses a combination of open source projects. Where tools exist with MIT, Apache, or another compatible open license, we want to use and even contribute to that tool. Where we see gaps in tooling, we build it.
Architecture
Konduktor can be self-hosted and run on any certified Kubernetes distribution or managed by us. Contact us at founders@trainy.ai if you are just interested in the managed version. We're focused on tooling for clusters with NVIDIA cards for now but in the future we may expand to our scope to support other accelerators.
For ML researchers
- Konduktor CLI & SDK - user friendly batch job framework, where users only need to specify the resource requirements of their job and a script to launch that makes simple to scale work across multiple nodes. Works with most ML application frameworks out of the box.
num_nodes: 100
resources:
accelerators: H100:8
cloud: kubernetes
labels:
kueue.x-k8s.io/queue-name: user-queue
kueue.x-k8s.io/priority-class: low-priority
run: |
torchrun \
--nproc_per_node 8 \
--rdzv_id=1 --rdzv_endpoint=$master_addr:1234 \
--rdzv_backend=c10d --nnodes $num_nodes \
torch_ddp_benchmark.py --distributed-backend nccl
For cluster administrators
- DCGM Exporter, GPU operator, Network Operator - For installing NVIDIA driver, container runtime, and exporting node health metrics.
- Kueue - centralized creation of job queues, gang-scheduling, and resource quotas and sharing across projects.
- Prometheus - For publishing metrics about node health and workload queues.
- OpenTelemetry - For pushing logs from each node
- Grafana, Loki - Visualizations for metrics/logging solution.
Community & Support
Development Setup
Prerequisites
- Python 3.10+
- Poetry for dependency management (installation guide)
- kubectl and access to a Kubernetes cluster (for integration/smoke tests)
Quick Start
# Clone the repository
git clone https://github.com/Trainy-ai/konduktor.git
cd konduktor
# Install dependencies (including dev tools)
poetry install --with dev
# Verify installation
poetry run konduktor --help
Running Tests
# Run unit tests
poetry run pytest tests/unit_tests/ -v
# Run smoke tests (requires Kubernetes cluster)
poetry run pytest tests/smoke_tests/ -v
Code Formatting
All code must pass linting before being merged. Run the format script to auto-fix issues:
bash format.sh
This runs:
- ruff - Python linter and formatter
- mypy - Static type checking
Local Kubernetes Cluster (Optional)
For running smoke tests locally, you can set up a kind cluster:
# Install kind and set up a local cluster with JobSet and Kueue
bash tests/kind_install.sh
1 maintainer
Metadata
1 maintainer
Release files for konduktor-nightly 0.1.0.dev20261019104514
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 | |
|---|---|---|---|---|
| konduktor_nightly-0.1.0.dev20261019104514.tar.gz | 386.1 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| konduktor_nightly-0.1.0.dev20261019104514-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 830.2 kB
Release files / konduktor_nightly-0.1.0.dev20261019104514.tar.gz
| Download URL | konduktor_nightly-0.1.0.dev20261019104514.tar.gz |
|---|---|
| Size | 386.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
02201562dce708ff2eaf1f4ef734cc408357fa719250e5d1b81b1747b565d096
|
|
BLAKE2b-256 checksum How to use checksums |
79cc558e749f61f1803334e0b862814582121b6a9e1b759416f2c995d11f7720
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 logRelease files / konduktor_nightly-0.1.0.dev20261019104514-py3-none-any.whl
| Download URL | konduktor_nightly-0.1.0.dev20261019104514-py3-none-any.whl |
|---|---|
| Size | 444.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0a12fc014bc41443c5be8e71cd4ae3101e767a25007c913929f26412a47b9896
|
|
BLAKE2b-256 checksum How to use checksums |
8026560b0e033f358df08af393781e673292ecec699d2c370f498f66676c959b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 logSecurity for konduktor-nightly 0.1.0.dev20261019104514
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 konduktor_nightly-0.1.0.dev20261019104514.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 Oct 19, 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.
