Instructions to use Exeaon/Exeaon1-Dzo-4B with libraries, inference providers, notebooks, and local apps. Follow these links to get started.
- Notebooks
- Google Colab
- Kaggle
- Local Apps Settings
- llama.cpp
How to use Exeaon/Exeaon1-Dzo-4B with llama.cpp:
Install (macOS, Linux)
curl -LsSf https://llama.app/install.sh | sh # Start a local OpenAI-compatible server with a web UI: llama serve -hf Exeaon/Exeaon1-Dzo-4B # Run inference directly in the terminal: llama cli -hf Exeaon/Exeaon1-Dzo-4B
Install from WinGet (Windows)
winget install llama.cpp # Start a local OpenAI-compatible server with a web UI: llama serve -hf Exeaon/Exeaon1-Dzo-4B # Run inference directly in the terminal: llama cli -hf Exeaon/Exeaon1-Dzo-4B
Use pre-built binary
# Download pre-built binary from: # https://github.com/ggerganov/llama.cpp/releases # Start a local OpenAI-compatible server with a web UI: ./llama-server -hf Exeaon/Exeaon1-Dzo-4B # Run inference directly in the terminal: ./llama-cli -hf Exeaon/Exeaon1-Dzo-4B
Build from source code
git clone https://github.com/ggerganov/llama.cpp.git cd llama.cpp cmake -B build cmake --build build -j --target llama-server llama-cli # Start a local OpenAI-compatible server with a web UI: ./build/bin/llama-server -hf Exeaon/Exeaon1-Dzo-4B # Run inference directly in the terminal: ./build/bin/llama-cli -hf Exeaon/Exeaon1-Dzo-4B
Use Docker
docker model run hf.co/Exeaon/Exeaon1-Dzo-4B
- LM Studio
- Jan
- vLLM
How to use Exeaon/Exeaon1-Dzo-4B with vLLM:
Install from pip and serve model
# Install vLLM from pip: pip install vllm # Start the vLLM server: vllm serve "Exeaon/Exeaon1-Dzo-4B" # Call the server using curl (OpenAI-compatible API): curl -X POST "http://localhost:8000/v1/chat/completions" \ -H "Content-Type: application/json" \ --data '{ "model": "Exeaon/Exeaon1-Dzo-4B", "messages": [ { "role": "user", "content": "What is the capital of France?" } ] }'Use Docker
docker model run hf.co/Exeaon/Exeaon1-Dzo-4B
- Ollama
How to use Exeaon/Exeaon1-Dzo-4B with Ollama:
ollama run hf.co/Exeaon/Exeaon1-Dzo-4B
- Unsloth Desktop
- Pi
How to use Exeaon/Exeaon1-Dzo-4B with Pi:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf Exeaon/Exeaon1-Dzo-4B
Configure the model in Pi
# Install Pi: npm install -g @earendil-works/pi-coding-agent # Add to ~/.pi/agent/models.json: { "providers": { "llama-cpp": { "baseUrl": "http://localhost:8080/v1", "api": "openai-completions", "apiKey": "none", "models": [ { "id": "Exeaon/Exeaon1-Dzo-4B" } ] } } }Run Pi
# Start Pi in your project directory: pi
- Docker Model Runner
How to use Exeaon/Exeaon1-Dzo-4B with Docker Model Runner:
docker model run hf.co/Exeaon/Exeaon1-Dzo-4B
- Lemonade
How to use Exeaon/Exeaon1-Dzo-4B with Lemonade:
Pull the model
# Download Lemonade from https://lemonade-server.ai/ lemonade pull Exeaon/Exeaon1-Dzo-4B
Run and chat with the model
lemonade run user.Exeaon1-Dzo-4B-{{QUANT_TAG}}List all available models
lemonade list
- Hermes Agent
How to use Exeaon/Exeaon1-Dzo-4B with Hermes Agent:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf Exeaon/Exeaon1-Dzo-4B
Configure Hermes
# Install Hermes: curl -fsSL https://hermes-agent.nousresearch.com/install.sh | bash hermes setup # Point Hermes at the local server: hermes config set model.provider custom hermes config set model.base_url http://127.0.0.1:8080/v1 hermes config set model.default Exeaon/Exeaon1-Dzo-4B
Run Hermes
hermes
- Atomic Chat
- OpenClaw
How to use Exeaon/Exeaon1-Dzo-4B with OpenClaw:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf Exeaon/Exeaon1-Dzo-4B
Configure OpenClaw
# Install OpenClaw: npm install -g openclaw@latest # Register the local server and set it as the default model: openclaw onboard --non-interactive --mode local \ --auth-choice custom-api-key \ --custom-base-url http://127.0.0.1:8080/v1 \ --custom-model-id "Exeaon/Exeaon1-Dzo-4B" \ --custom-provider-id llama-cpp \ --custom-compatibility openai \ --custom-text-input \ --accept-risk \ --skip-health
Run OpenClaw
openclaw agent --local --agent main --message "Hello from Hugging Face"
Exeaon-Dzo-4B
Compressed with E-PURE. Runs with the free
epure-runtime, and stays
compressed in memory โ the dense weight is never assembled.
| Base model | Qwen/Qwen3-4B |
| Size on disk | 2.040 GB |
| Compression | 3.67x |
| Bits per weight | 4.33 (measured index entropy) |
| Format | .ebin |
Quality
Measured against the base model on the same hardware, same harness version,
same limit. Not copied from anyone's README.
| benchmark | Qwen3-4B | Exeaon-Dzo-4B | delta |
|---|---|---|---|
| ARC-Challenge | 51.67 | 49.33 | -2.34 |
| ARC-Easy | 78.33 | 76.00 | -2.33 |
| HellaSwag | 57.67 | 57.67 | +0.00 |
| PIQA | 74.67 | 74.33 | -0.34 |
| mean | 65.59 | 64.33 | -1.25 |
Retention: 98.1% of base mean accuracy.
Note where the loss sits rather than reading only the mean: reasoning-heavy tasks degrade first, and a model chosen for retrieval or classification is affected differently from one chosen for reasoning.
Speed and footprint
| Qwen3-4B | Exeaon-Dzo-4B | |
|---|---|---|
| decode, batch 1 | 11.9 tok/s | 8.5 tok/s |
| decode, batch 8 | 89.0 tok/s | 30.1 tok/s |
| peak VRAM | 8.65 GB | 5.02 GB |
Read this honestly: on GPU we are slower than dense fp16. A vendor tensor-core GEMM is extremely well tuned and a large GPU has bandwidth to spare, so dequantization costs more cycles than compression buys back. The win on GPU is footprint โ whether the model fits, and what is left for the KV cache. On CPU, where bandwidth is the binding constraint, the fused kernel wins on both footprint and speed.
Measured on Tesla T4, torch 2.5.1+cu121,
lm-eval 0.4.12, limit 300, kernel rust+triton.
Usage
pip install epure-runtime
from epure import load
model, tok = load("Exeaon/Exeaon-Dzo-4B")
ids = tok("Explain the memory wall.", return_tensors="pt").input_ids
print(tok.decode(model.generate(ids, max_new_tokens=128)[0]))
epure run Exeaon/Exeaon-Dzo-4B --prompt "Explain the memory wall."
No Rust toolchain needed: the fused CPU kernel ships compiled inside the wheel.
Fine-tuning without decompressing
Quantization indices stay frozen; the codebook and per-group scales train โ about 1% of the weight values. The dense weight is never materialized, so memory tracks activations rather than parameter count.
from epure import load, make_trainable, snapshot_indices, verify_frozen
model, tok = load("Exeaon/Exeaon-Dzo-4B")
params, n = make_trainable(model, mode="both")
before = snapshot_indices(model)
... # an ordinary PyTorch loop over `params`
verify_frozen(model, before) # raises if any index moved
Limitations
- Compression is lossy; the measured gap is in the table above.
- The KV cache is not compressed by default and can exceed the weights at long context.
- GPU decode is slower than dense fp16 (see above).
- Inherits every limitation, bias and knowledge cutoff of the base model.
- Not evaluated for safety-critical, medical, legal or financial use.
Licence and attribution
Derived from Qwen/Qwen3-4B, released under Apache-2.0, which
permits redistribution of modified versions. The original LICENSE and
NOTICE files are included in this repository unmodified, as it requires.
Ours: the compression method, calibration, packaging, runtime. Not ours: the pretrained knowledge, which comes from the base model authors. This model is not endorsed by or affiliated with them.
Citation
@misc{exeaon2026,
title = {Exeaon: compressed language models that run, and train, without
decompressing},
author = {Akpalu, Elliot Elikplim},
year = {2026},
publisher = {Zenux Plimver Technologies LTD},
url = {https://huggingface.co/Exeaon}
}
Zenux Plimver Technologies LTD, Ghana
- Downloads last month
- 132
We're not able to determine the quantization variants.