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

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.1.3
File Size Uploaded
epure_runtime-0.1.3.tar.gz 27.5 kB Details

Built distributions (wheels)

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

Download URL epure_runtime-0.1.3.tar.gz
Size 27.5 kB
Tags Source
SHA-256 checksum
How to use checksums
38d309dc9bb152b8b12e93e77ff4b3536bdc8bb90ea850a0cb8316a0c649ff56
BLAKE2b-256 checksum
How to use checksums
cd8fcc741bd759cc3e8c0d5785a88b2b0182ae1a1987556b3abc793d85362771
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.1.3-cp39-abi3-win_amd64.whl

Download URL epure_runtime-0.1.3-cp39-abi3-win_amd64.whl
Size 186.1 kB
Tags CPython 3.9 Windows x86-64 abi3
SHA-256 checksum
How to use checksums
daf9edb716df0dbe0f151f20de6dea3e8905b7e9a421facd34d3813a648fff18
BLAKE2b-256 checksum
How to use checksums
8fc772c9392f2de8f2a7ba94a7660a5273a29d0a8eba483749c01b7fb39bc837
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.1.3-cp39-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl

Download URL epure_runtime-0.1.3-cp39-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
Size 309.1 kB
Tags CPython 3.9 Linux glibc 2.17+ x86-64 abi3
SHA-256 checksum
How to use checksums
5ae57bdaa97ac5843d593af1fbf60aeaad1a07c78d7f0f4598c7816a9c0515a7
BLAKE2b-256 checksum
How to use checksums
62d7979b6a37d275f13c27c53eeaa7588a4a675418662114ea437eaf9fe99583
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.1.3-cp39-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl

Download URL epure_runtime-0.1.3-cp39-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
Size 306.3 kB
Tags CPython 3.9 Linux glibc 2.17+ ARM64 abi3
SHA-256 checksum
How to use checksums
5d7619ffad416f20e37cf5a4b73fc8573df22333b0b1de82c09ca673210ca28c
BLAKE2b-256 checksum
How to use checksums
a3ce1585bd71bedd792429a027917bd4a37de646d86d90c5f517ab492382155b
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.1.3-cp39-abi3-macosx_11_0_arm64.whl

Download URL epure_runtime-0.1.3-cp39-abi3-macosx_11_0_arm64.whl
Size 277.8 kB
Tags CPython 3.9 abi3 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
5f775befc6fd589a90429197e9ec129a16fe8edfcf2579dd2bdf0f71ab3f240d
BLAKE2b-256 checksum
How to use checksums
bc26ed74c5d64c2688a2977f4dd47c00afdda275aababb9c8ba11278e5563719
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.1.3-cp39-abi3-macosx_10_12_x86_64.whl

Download URL epure_runtime-0.1.3-cp39-abi3-macosx_10_12_x86_64.whl
Size 285.1 kB
Tags CPython 3.9 abi3 macOS 10.12+ x86-64
SHA-256 checksum
How to use checksums
28385aec74c3754d1af548d65f8d0bc62d1586b4c058c707fa5cf2550c06e4b2
BLAKE2b-256 checksum
How to use checksums
8583934b873f8d60f14b48c802adf32c5f9ee837f2c9416b2671144e6ea616b1
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

0.2.2

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

This release

0.1.3 This release

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