Piper Kernels
Quantized attention, linear, and convolution operators for PyTorch inference. Piper Kernels combines compact weight formats and GPU kernels with optional compiler fusions that avoid intermediate tensors and repeated preparation. Portable PyTorch references define the corresponding numerical operations.
Use the operators directly or install quantized weights in PyTorch modules. Applications own model loading, checkpoint naming, and device placement; Piper Offload uses these weight formats for its model runtime.
Installation
Requires Python 3.13 or newer and PyTorch 2.14 or newer.
pip install piper-kernels
The base package requires only PyTorch. Optional extras provide weight-format and accelerator dependencies:
| Extra | Use |
|---|---|
convrot |
ConvRot INT8 weights |
nvfp4 |
Ordinary and ConvRot NVFP4 weights |
triton |
Optimized GPU backends |
For example, install "piper-kernels[convrot,triton]" for ConvRot INT8 GPU
execution. On Linux, install the CUDA or ROCm PyTorch build and its matching
Triton first; the extra does not install Linux Triton.
On 64-bit Windows, the triton extra selects Triton 3.8 through
triton-windows. Optimized
execution needs Windows 10 or 11, a supported GPU with a current driver, and
the Visual C++ Redistributable for Visual Studio 2015–2022. For NVIDIA,
triton-windows bundles the CUDA toolchain and TinyCC; no separate CUDA toolkit
or Visual Studio installation is needed. For AMD, use
TheRock's ROCm PyTorch build
and its matching GPU device packages; see
AMD validation coverage.
Quick start
This runs dense Piper Attention on CUDA when available and on CPU otherwise.
Inputs use [batch, heads, sequence, head_dim] layout:
import torch
from piper_kernels import piper_attention
device = "cuda" if torch.cuda.is_available() else "cpu"
query, key, value = (
torch.randn(1, 2, 128, 64, device=device, dtype=torch.bfloat16) for _ in range(3)
)
with torch.inference_mode():
output = piper_attention(query, key, value, is_causal=False)
print(output.shape) # torch.Size([1, 2, 128, 64])
Supported GPUs with the required backend installed use an optimized path; other configurations use the slower reference for the same quantized algorithm. Both approximate floating-point attention, and compiler fusions can change rounding. Measure numerical quality and full-operator latency on your workload; see attention for input and backend support.
Guides
| Task | Read |
|---|---|
| Choose and use dense, sparse, or SageAttention2++ attention | Attention |
| Construct, load, run, update, or shard quantized weights; enable compiler fusions | Weights and quantized operators |
| Understand implementation boundaries, extend kernels, or run checks | Development |
| Measure performance and quality, tune, or inspect generated kernels | Benchmarks |
These docs describe the checked-out revision. Use the matching Git tag for an installed release. AGENTS.md gives repository instructions for coding agents; VERSIONING.md covers compatibility and releases, and CHANGELOG.md records changes between releases.
Licensed under the Apache License, Version 2.0.
Metadata
Release files for piper-kernels 0.7.6
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 | |
|---|---|---|---|---|
| piper_kernels-0.7.6.tar.gz | 369.3 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| piper_kernels-0.7.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 889.2 kB
Release files / piper_kernels-0.7.6.tar.gz
| Download URL | piper_kernels-0.7.6.tar.gz |
|---|---|
| Size | 369.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0a7142915d5693a163d0341c8037dfd3ef1084b00cf6e251769bf8c01dba8559
|
|
BLAKE2b-256 checksum How to use checksums |
34133ee096c432e775f102ca0b09d404e9bbc100d210096642f710d145adcb33
|
| 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 22, 2026.
Transparency logRelease files / piper_kernels-0.7.6-py3-none-any.whl
| Download URL | piper_kernels-0.7.6-py3-none-any.whl |
|---|---|
| Size | 519.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c4d082885e9c137f5c54d7f0b84dc03f9d6bb054c84056adedb47f80333e66c0
|
|
BLAKE2b-256 checksum How to use checksums |
a69aafaf0a63c939057a16e0c8f98688a6ef0a2ca44af627e35783cef4ef41ad
|
| 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 22, 2026.
Transparency logSecurity for piper-kernels 0.7.6
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 piper_kernels-0.7.6.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 22, 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.