epure-runtime
Run compressed models. Small footprint, same answers.
pip install epure-runtime
from epure import load
model, tok = load("Exeaon/Exeaon-Dzo-1.7B")
ids = tok("Explain the memory wall.", return_tensors="pt").input_ids
print(tok.decode(model.generate(ids, max_new_tokens=128)[0]))
Or from the shell:
epure run Exeaon/Exeaon-Dzo-1.7B --prompt "Explain the memory wall."
epure info Exeaon/Exeaon-Dzo-1.7B
epure eval Exeaon/Exeaon-Dzo-1.7B --tasks arc_easy,piqa --limit 200
Why this exists
At batch one, a language model reads every weight from memory to produce one token and uses each weight exactly once. Arithmetic intensity is about 0.5 FLOP per byte, so decode speed is:
tokens/second ≤ memory bandwidth ÷ model bytes
The accelerator's FLOP rating never enters it. A 7B model in bf16 is 14 GB — on 1 TB/s that is a ceiling near 71 tok/s regardless of the spec sheet. The only lever is how many bytes the model is.
So .ebin models are stored compressed, and stay compressed in memory. The
packed indices go straight into the matmul, where the kernel decodes them in the
operand path. The dense weight is never assembled — not on disk, not in RAM, not
as a temporary.
That is the difference between this and a loader that decompresses at startup. A loader gives you a smaller download. This gives you a smaller process.
What it does
Loads .ebin containers, local or straight from the Hugging Face Hub |
|
| Serves them on CPU (fused Rust kernel) and CUDA (fused Triton kernel) | |
| Fine-tunes them in the compressed state — indices frozen, codebook and scales learn | |
Evaluates them through lm-eval, on the in-memory model rather than a reloaded copy |
What it does not do
It cannot compress anything. There is no encoder here and there will not be
one — no epure compress, no writer, no bulk dense export. This package reads
the format and runs it. The compressor is ℰ-PURE and it stays with us.
You do not need it. Everything required to run, fine-tune, benchmark, serve and ship a published model is in this repository, under Apache-2.0.
Fine-tuning without decompressing
The quantization indices stay fixed. The codebook and the per-group scales train — roughly 1% of the weight values — so adaptation happens in the compressed state and memory tracks activations rather than parameter count.
from epure import load, make_trainable, snapshot_indices, verify_frozen
model, tok = load("Exeaon/Exeaon-Dzo-1.7B")
params, n = make_trainable(model, mode="both") # "scale" | "cb" | "both"
before = snapshot_indices(model)
... # your training loop, over `params`
verify_frozen(model, before) # raises if any index moved
verify_frozen is not decoration. A fine-tune that silently rewrites indices
has stopped being a fine-tune of a compressed model, and the loss curve looks
identical either way.
Installation
pip install epure-runtime # runtime only
pip install 'epure-runtime[eval]' # + lm-eval harness
pip install 'epure-runtime[audio]' # + speech models
Python ≥ 3.9. CPU works out of the box; CUDA support activates automatically when a GPU and Triton are present.
You do not need Rust. The fused CPU kernel is written in Rust and ships
compiled inside the wheel, so pip install gets the fast path with no cargo,
no compiler and no toolchain. Wheels are abi3, one per platform, covering every
Python from 3.9 up.
Check which backend you got:
from epure.kernels import cpu, cuda
print(cpu.available(), cpu.threads()) # True 8
print(cuda.available())
If cpu.available() is False there is no wheel for your platform and the
runtime is falling back to pure PyTorch — correct, but slower. Open an issue
with your platform and we will add it to the build matrix.
Building the kernel yourself (contributors only)
pip install maturin
maturin develop --release
Documentation
| Inference | running models, choosing a backend, what to expect |
| Fine-tuning | training in the compressed state, and proving it stayed compressed |
| Benchmarks | the measurement harness, and published results |
API
load(path, device=None) |
.ebin path or HF repo id → (model, tokenizer) |
apply_to(model, path, ...) |
swap an existing module tree's weights for packed stores |
describe(path) |
container summary, as used by epure info |
make_trainable(model, mode) |
"scale" · "cb" · "both" → (params, count) |
snapshot_indices(model) / verify_frozen(model, snap) |
prove indices never moved |
resolve(path) |
repo id → local file, downloading if needed |
Models
| class | runs on |
|---|---|
| Dzo | laptop, CPU, edge |
| Nunya | a single GPU |
| Kese | server, multi-GPU, MoE |
Licence
Apache-2.0. See LICENSE.
Models published by Exeaon are derived from openly licensed base models; each model card names its base model and ships the upstream licence unmodified.
Built by Zenux Plimver Technologies LTD, Ghana.
Metadata
Release files for epure-runtime 0.1.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| epure_runtime-0.1.4.tar.gz | 27.7 kB | Details |
Built distributions (wheels)
| File | Reset | |||
|---|---|---|---|---|
| epure_runtime-0.1.4-cp39-abi3-win_amd64.whl | CPython 3.9 | abi3 | Windows x86-64 | Details |
| epure_runtime-0.1.4-cp39-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl | CPython 3.9 | abi3 | Linux glibc 2.17+ x86-64 | Details |
| epure_runtime-0.1.4-cp39-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl | CPython 3.9 | abi3 | Linux glibc 2.17+ ARM64 | Details |
| epure_runtime-0.1.4-cp39-abi3-macosx_11_0_arm64.whl | CPython 3.9 | abi3 | macOS 11.0+ ARM64 | Details |
| epure_runtime-0.1.4-cp39-abi3-macosx_10_12_x86_64.whl | CPython 3.9 | abi3 | macOS 10.12+ x86-64 | Details |
Total release size: 1.4 MB
Release files / epure_runtime-0.1.4.tar.gz
| Download URL | epure_runtime-0.1.4.tar.gz |
|---|---|
| Size | 27.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
68c7682d008a3b7de1110e2b3a837ac4fcf265292eba082c1093008c1c5597a7
|
|
BLAKE2b-256 checksum How to use checksums |
ef96bd2814b41a8483c8295d2956efeb8e5617ae18abcc4cf475ca0849e2747f
|
| 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 Aug 8, 2026.
Transparency logRelease files / epure_runtime-0.1.4-cp39-abi3-win_amd64.whl
| Download URL | epure_runtime-0.1.4-cp39-abi3-win_amd64.whl |
|---|---|
| Size | 186.3 kB |
| Tags | CPython 3.9 Windows x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
f085ec99d304b3614511a45e01f51f49b93743388b1b50ce4559a8d913600548
|
|
BLAKE2b-256 checksum How to use checksums |
4c0ee04d885184d392a98bb3823228118920ea971a7cacd40553dee68ac04fe3
|
| 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 Aug 8, 2026.
Transparency logRelease files / epure_runtime-0.1.4-cp39-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | epure_runtime-0.1.4-cp39-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 309.3 kB |
| Tags | CPython 3.9 Linux glibc 2.17+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
62383bb5cc2383249b6b29415459edda123ae84657d2fdab3cb0c92819466b09
|
|
BLAKE2b-256 checksum How to use checksums |
e6d9f9443139ca638fee1da49097ef5ef191f144b544d331d26d1c47e64278aa
|
| 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 Aug 8, 2026.
Transparency logRelease files / epure_runtime-0.1.4-cp39-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | epure_runtime-0.1.4-cp39-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 306.6 kB |
| Tags | CPython 3.9 Linux glibc 2.17+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
d305d6a4554794e02ebff8083d2bf83110e73c5164a0a3822bcb6b3828ceda9a
|
|
BLAKE2b-256 checksum How to use checksums |
cdce0376438425e9e0193b69de31ace4c2f76b99ac6c36746d5ae951ba60aeb6
|
| 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 Aug 8, 2026.
Transparency logRelease files / epure_runtime-0.1.4-cp39-abi3-macosx_11_0_arm64.whl
| Download URL | epure_runtime-0.1.4-cp39-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 278.0 kB |
| Tags | CPython 3.9 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
d8e02c6d872f8857075ecd111ff389f92b140b21fe1e9fdd09fd92737082e724
|
|
BLAKE2b-256 checksum How to use checksums |
f5fb5761417e37b15500d4871b8c99d8c68b8e0f81917d55f3f95740b741bf5e
|
| 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 Aug 8, 2026.
Transparency logRelease files / epure_runtime-0.1.4-cp39-abi3-macosx_10_12_x86_64.whl
| Download URL | epure_runtime-0.1.4-cp39-abi3-macosx_10_12_x86_64.whl |
|---|---|
| Size | 285.4 kB |
| Tags | CPython 3.9 abi3 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
be8f4b6d131cdf8154d3e5f29cdfdc796bea52ddd57158d922339c615f644ddd
|
|
BLAKE2b-256 checksum How to use checksums |
2702745544a5db29c8479b5edebdb01c3d38a88cbd7452c880310630f5986d5b
|
| 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 Aug 8, 2026.
Transparency log