Skip to main content

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

huggingface.co/Exeaon

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.2.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for epure-runtime 0.2.2
File Size Uploaded
epure_runtime-0.2.2.tar.gz 31.7 kB Details

Built distributions (wheels)

Table of built distributions (wheels) for epure-runtime 0.2.2
File
epure_runtime-0.2.2-cp39-abi3-win_amd64.whl CPython 3.9 abi3 Windows x86-64 Details
epure_runtime-0.2.2-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.2.2-cp39-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl CPython 3.9 abi3 Linux glibc 2.17+ ARM64 Details
epure_runtime-0.2.2-cp39-abi3-macosx_11_0_arm64.whl CPython 3.9 abi3 macOS 11.0+ ARM64 Details
epure_runtime-0.2.2-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.2.2.tar.gz

Download URL epure_runtime-0.2.2.tar.gz
Size 31.7 kB
Tags Source
SHA-256 checksum
How to use checksums
c409683f98c0fac510f20d0cfdc73d917027c47727e49d55a0d6e25027faa1aa
BLAKE2b-256 checksum
How to use checksums
9e1fd6c59c6287e6a3ee78a0c9f9d3b21c2db191da61e7ed4f5b489aaca136eb
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

Release files / epure_runtime-0.2.2-cp39-abi3-win_amd64.whl

Download URL epure_runtime-0.2.2-cp39-abi3-win_amd64.whl
Size 190.8 kB
Tags CPython 3.9 Windows x86-64 abi3
SHA-256 checksum
How to use checksums
2760fb9599dcc77277f5a59fdc6110aecc0667cfd832c90d6ad4a22822d02548
BLAKE2b-256 checksum
How to use checksums
9a46c935ee8ca44f6a062c04cb72c1a94f5723d4244c099658004dbae60e5103
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

Release files / epure_runtime-0.2.2-cp39-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl

Download URL epure_runtime-0.2.2-cp39-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
Size 313.7 kB
Tags CPython 3.9 Linux glibc 2.17+ x86-64 abi3
SHA-256 checksum
How to use checksums
8f561026ef3d80b41bafc44b8ffb006210d0c65b76d0c6d4089311591284b24e
BLAKE2b-256 checksum
How to use checksums
5d2a8766b6acfe4a259f955dcac612fdc65e241117e564641a6a7411eca1b2d7
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

Release files / epure_runtime-0.2.2-cp39-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl

Download URL epure_runtime-0.2.2-cp39-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
Size 311.0 kB
Tags CPython 3.9 Linux glibc 2.17+ ARM64 abi3
SHA-256 checksum
How to use checksums
3b76d0b3adaa561192cb1bdf62198d2f91052e8fa93ca2011c280cee0c0e9c91
BLAKE2b-256 checksum
How to use checksums
92974c2d9d1ed841818aabeb1e0675ac11465ebd0e90580affa480e5873b5a94
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

Release files / epure_runtime-0.2.2-cp39-abi3-macosx_11_0_arm64.whl

Download URL epure_runtime-0.2.2-cp39-abi3-macosx_11_0_arm64.whl
Size 282.4 kB
Tags CPython 3.9 abi3 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
5888dc9731e4ae5feba50197d71f653e41c4d32b9d6595a589d8e42b0f00d108
BLAKE2b-256 checksum
How to use checksums
1fabf6d7700acc3d9344934528ad353dbf6b478691cab1a0799879a0cc839477
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

Release files / epure_runtime-0.2.2-cp39-abi3-macosx_10_12_x86_64.whl

Download URL epure_runtime-0.2.2-cp39-abi3-macosx_10_12_x86_64.whl
Size 289.8 kB
Tags CPython 3.9 abi3 macOS 10.12+ x86-64
SHA-256 checksum
How to use checksums
3911a1550df66aaf75720ac9051369ead1e92d1bed3dd649e51dbabfb2a6efdc
BLAKE2b-256 checksum
How to use checksums
0b6f8a3baa1a12ae551a0fa5464ef81f8013267ee51fbc053086af2564c25d51
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

Release history Release notifications | RSS feed

0.2.5

6 release files

0.2.4

6 release files

0.2.3

6 release files

This release

0.2.2 This release

6 release files

0.2.1

6 release files

0.2.0

6 release files

0.1.5

6 release files

0.1.4

6 release files

0.1.3

6 release files

0.1.2

6 release files

0.1.1

6 release files

0.1.0

6 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page