INFERENCE COMPRESSION PLATFORM

Serve 9 users at 128K where fp16 serves 2.

Same GPU · Same weights · No retraining

Task-aware KV-cache compression for long-context LLMs. Measured in real vLLM serving on one A100, retrieval-verified.

● Proven
Mistral-7B 128K KV receipt
● Public
Qwen 35B compressed artifact
● Measured
vLLM runtime: 2× fp16 throughput at 4.5× its users

LATEST · AUG 14 — 9 users × 128K on one A100, retrieval-gated  ship log ↓

Request Pilot

Bring your model; we benchmark the right compression layer against your stack.
Free technical pilot for the first 5 design partners · Prefer email? contact@fraqtl.ai

THE PROBLEM

KV cache and VRAM are the bottleneck.

At long context, KV cache size determines how many users you can serve concurrently and what models fit on your hardware. Most teams are forced to choose: shorter context, smaller model, or more GPUs. fraQtl removes that choice.

QWEN 3.6 35B-A3B · 1× A100-80GB
VRAM at increasing context length

FP16 hits the GPU ceiling at 64K. fraQtl runs 128K with 28 GB headroom.

A100-80GB CEILING
71 GB
25.6 GB
16K
BOTH FIT
OOM
82.9 GB
36.8 GB
64K
FP16 NEEDS 2 GPUS
OOM
85+ GB
51.7 GB
128K
FRAQTL: 28 GB FREE
FP16 BASELINE
FRAQTL COMPRESSED

FP16 64K = 82.86 GB measured (OOM on 80 GB ceiling). 16K and 128K FP16 figures are conservative model + KV-cache extrapolations. fraQtl numbers measured on a single A100-80GB with the public artifact.

WHY IT MATTERS

Fewer GPUs. Longer context. Lower cost.

At long context, KV cache is what caps users-per-GPU and context length. fraQtl compresses it while keeping retrieval intact — longer context, more concurrent users, fewer GPUs, on the hardware you already have. The receipts below are the argument.

BENCHMARKS

The numbers behind the pilot.

All numbers traceable to the public Hugging Face sidecar repos and the benchmark receipts — and reproducible on your own hardware.

Reproduce these numbers on your hardware → python fraqtl_repro_receipts.py  # ships with the runtime repo · rented A100 is enough

Receipts available per lane — maturity varies by lane. The vLLM speed receipt, D1 KV receipt, and Qwen artifact are public today.

LEAD RECEIPT NEW · JULY 2026

Compressed KV at full speed — and it compounds under load.

The fraQtl runtime reads its packed KV pages straight into the tensor cores — no reconstruction step. In real vLLM serving on one A100-80GB (CUDA graphs on), single-user decode runs at 95–99% of fp16 speed at 8K–32K — and 1.32× faster than fp16 at 128K; under concurrent load the memory advantage becomes a throughput advantage: 2.1× fp16 aggregate tokens/sec at 128K context per user. Two models, one kernel, zero per-model changes. Every number retrieval-verified — never “lossless.”

95–99%
of fp16 decode speed, single user
Mistral-7B · 95% @8K · 98.5% @32K · 1.32× fp16 @128K
9 users
at 128K each, on one A100 — fp16 holds 2
134.1 agg tok/s · 2× fp16 at 4.5× its users · 9/9 needles
2.42×
more KV tokens per GPU
997,200 vs 412,544 pool tokens · Mistral-7B
405/405
needle cells retrieved, exact match
3 models · multi-depth × multi-key grids · all arms
fraQtl
receipt · 2026-08-14

One GPU, three crowds

One 80 GB A100. Every block is a user held at ≈128K context, needle-tested at their own depth.

fp16 KVholds 2
u1
u2
OUT OF MEMORY
66.6tok/s
fp8 KVpeak, at 4 users
u1
u2
u3
u4
u5
PREEMPT
117.6tok/s
fraQtl9/9 needles
u1
u2
u3
u4
u5
u6
u7
u8
u9
134.1tok/s
$ Qwen3-4B-Instruct-2507 · vLLM · 9/9 passkeys recovered exactly, placements spanning 0–100%receipts, not hype
MODEL MATRIX 3 ARCHITECTURES · ONE KERNEL

One kernel, every model — zero per-model changes.

Each model gets a sidecar from the factory (<1h, weights untouched) and runs on the identical membrane kernel. Same command, same recipe — three architectures, one pattern: ~2.4× fp16 capacity, weight-floor parity at short context, and the win grows where context grows.

MODEL KV CAPACITY VS FP16 VS FP8 8K DECODE 32K DECODE 128K DECODE NEEDLE CELLS
Qwen3-4B-Instruct-2507
2025 · native 256K
2.39× 1.21× 92% fp16 97% fp16 1.34× fp16 · 95% fp8 189/189
Llama-3.1-8B-Instruct
native 128K
2.35× 1.20× 96% fp16 97% fp16 1.23× fp16 · 1.00× fp8 90/90
Mistral-7B-v0.3
native 32K
2.42× 1.21× 95% fp16 99% fp16 n/a — collapses at 128K in all arms incl. fp16 126/126
Needle cells = exact-match passkey grids, 7 depths × 3 keys per context (Llama 5 × 3), all three arms. Capacity = measured KV pool tokens, 8K config. Cells are receipts; blanks are runs not done, not failures.
REAL VLLM SERVING · ONE A100-80GB
CUDA GRAPHS ON · TEMPERATURE 0 · FP8 ALWAYS SHOWN

Alone, fraQtl matches fp16 — and beats it at 128K. Under load, the advantage grows.

At one user, weights dominate and everyone is within a few percent. Add users and fp16 runs out of KV memory first, fp8 second — fraQtl keeps serving: parity with fp8 at 1 user grows to 1.4× fp8 at 6 users.

CELL FRAQTL FP16 FP8 KV NEEDLES
Mistral-7B · 8K · batch 1 · decode tok/s 85.7 90.39 90.05
Mistral-7B · 32K · batch 1 · decode tok/s 76.84 77.98 82.81
Qwen3-4B-2507 · 128K · batch 1 · decode tok/s 69.5 52.59 72.7
Mistral-7B · KV pool tokens · one A100 997,200 412,544 825,104
Qwen3-4B-2507 · users @128K each · bit-plane V2 (Aug 14) 9 2 5 ✓ 9/9
Qwen3-4B-2507 · aggregate tok/s · bit-plane V2 at 9 users 134.1 66.6 117.6 (peak, at 4)
Qwen3-4B-2507 · users @128K ctx each · V1 layout (Jul 05) 6 2 5 ✓ every user
Qwen3-4B-2507 · aggregate tok/s @128K · V1 clean max (Jul 05) 140.9 66.6 105.0
Qwen3-4B-2507 · 32K · 24 concurrent users · aggregate tok/s 429.7 246.0 432.3 ✓ 24/24
JULY V1 LADDER · 128K/USER · EACH CONFIG AT ITS CLEAN MAX · THE PER-LAYOUT BANDWIDTH ROOF
fraQtl
140.9 tok/s · 6 users
fp8 KV
105.0 tok/s · 5 users
fp16
66.6 tok/s · 2 users

Prefill at 128K: ~3,950 tok/s — at parity with fp16, faster than fp8. Every user needle-tested at their own depth, every rung of the ladder.

RETRIEVAL VERIFICATION · THE HONESTY LAYER

We never say “lossless.” We say retrieval-verified: needle-in-a-haystack passkey grids — 7 depths × 3 keys per context, exact-match gated — run on every arm of every receipt. Qwen3-4B-2507: 189/189 cells across 8K/32K/128K. Mistral-7B-v0.3: 126/126 cells across 8K/32K. Llama-3.1-8B: 90/90 cells across 8K/32K — 405/405 total — plus the Aug 14 nine-user run: 9/9 per-user passkeys at depths spanning 0–100%. Same kernel for all three models, zero per-model kernel changes — a new model's sidecar builds in under an hour.

Framing: BF16/FP16 is the quality reference; public Q4 is the practical size baseline teams already deploy. Matched Q4_K_M bakeoff in progress — results published when locked. Method: vLLM (real paged serving), CUDA graphs on, prefix caching off, two-pass subtractive decode timing, temperature 0, exact-match passkey retrieval per arm; concurrency cells give every user a full 128K context (130,048-token prompt + 1,024-token decode) with an independent passkey at a distinct depth. fp8 = fp16 weights + fp8-E4M3 KV (FlashInfer) — the strong baseline; weights identical across all arms. fraQtl = rank-protected eigenbasis KV read fragment-native into the tensor cores, zero reconstruction. 128K receipts run with chunked prefill disabled (known perf bug under chunking, fix in progress; stock arms unaffected). A batch-routing bug that dropped needles at batch ≥2 was found 07-03, root-caused, fixed, and fully re-receipted — pre-fix numbers were never published. No 256K claims yet: capacity verified, quality gate open. Qwen3-4B KV pool: 845,136 tokens vs fp16 361,776 (fp8 709,488) — 2.3× capacity. Aug 14 nine-user cells use bit-plane V2 KV tiering (+45% KV pool vs V1); the July V1-layout receipt (6 users, 140.9 aggregate) remains the per-layout bandwidth roof — V2 trades ~5% aggregate for 3 more users. Per-user decode at 9 users is 14.9 tok/s (fp16: ~33, for its 2 users). All cells reproducible from the public Hugging Face sidecar repos (huggingface.co/fraQtl) with fraqtl_repro_receipts.py; run IDs available on request.
RECEIPT · LLAMA.CPP 128K MISTRAL-7B

Standard low-bit KV loses retrieval at long context. fraQtl doesn't.

Mistral-7B at 128K context in llama.cpp. Same model, same prompts — only the KV-cache representation changes. Q8 and Q4 reduce memory but give up needle retrieval; fraQtl D1 reaches memory below Q8 with retrieval intact.

KV CONFIG @ 128K LIVE VRAM NIAH VS FP16
fp16 KV (baseline) 22,657 MiB 5 / 5
Q8 KV 15,437 MiB 1 / 5 −31.9%
Q4 KV 11,287 MiB 0 / 5 −50.2%
fraQtl D1 13,261 MiB 5 / 5 −41.5%
Mistral-7B-Instruct · 128K context · llama.cpp · NIAH = 5-needle retrieval. Live VRAM is measured resident KV-cache footprint.
fraQtl D1 uses 14.1% less live VRAM than Q8 KV (13,261 vs 15,437 MiB) and keeps 5/5 vs Q8's 1/5 — lower memory and intact retrieval at the same time.
Retrieval gating has since been strengthened: the vLLM runtime receipts below use 7-depth × 3-key exact-match passkey grids — 189/189 cells on Qwen3-4B-2507, 126/126 on Mistral-7B. See the lead receipt ↑
RESEARCH BACKING — partial-stack bake-off vs published methods (NIAH, PPL Δ, KIVI / TOVA / SnapKV) expand ▾

Four numbers vs the nearest published method.

Partial-stack research bake-off (Mistral / Llama, sub-4-bit, C44). The headline customer claim is the D1 llama.cpp receipt above; these are a separate research comparison, reproducible on the benchmark page.

METRIC FRAQTL NEAREST PUBLISHED DIFFERENCE
NIAH retention (1080 trials) 98.5% 97.8% · TOVA +0.7 pp
PPL Δ at 3.5× compression +0.012 +0.214 · SnapKV ~18× tighter
NIAH at 128K (Llama 3.1 8B) 100% 0% · KIVI-2 +100 pp
GPUs needed at 128K (35B MoE) 1× A100-80GB 2× A100-80GB · FP16 1× vs 2×
Sources: Mistral-7B-Instruct C44 bake-off (1080 NIAH trials, 8K–31K, 3 needle types). Llama 3.1 8B C44d/e (128K, 3 needles × 5 trials per depth). Qwen 3.6 35B-A3B VRAM measured on a single A100-80GB.
Honest note: at matched 4-bit, fraQtl ties KIVI-4 / KVQuant-4 within sampling noise. The wins above are at sub-4-bit, at 128K, vs eviction methods, and on hardware footprint.
Show full method breakdown · 7 baselines, 7 axes +
METHOD MEMORY QUALITY CALIBRATION OVERHEAD NIAH
1080 TRIALS
PPL Δ
V-ONLY
fraQtl (V-only) 3.5× ✓ ✓ within noise ✓ 0.3s no measured (C44) 98.5% +0.012
fraQtl (V+K) ~3× ✓ ✓ within noise ✓ 0.3s benchmark-dependent 97.8%
FP16 baseline 97.0% 0
TOVA ⚠ degrades ✓ none per-token 97.8% +0.259
SnapKV ⚠ degrades ✓ none per-token 94.1% +0.214
StreamingLLM ✗ poor ✓ none per-token 37.8% +0.548
H2O ✗ OOM ✓ none eager attn 0.0%
KVQuant-2 ✓ 2-bit ⚠ moderate ✗ 5–15 min custom kernels +0.27
KIVI-2 ✓ 2-bit ✗ collapses at 128K ✓ none per-token 37.8% → 0%@128K +1.00
NIAH: needle-in-a-haystack retrieval. C44 bake-off, Mistral-7B-Instruct, 8K–31K context, 3 needle types × 360 trials per method.
† H2O: OOM at 16K+ context (eager attention required).
RECEIPT 2

Quality matches FP16 within sampling noise.

Qwen 3.6 35B-A3B compressed (single-seed) · vs FP16 baseline
BENCHMARK FP16 FRAQTL Δ
MMLU 0-shot 82.40% 82.24% −0.16 pp
∞Bench Passkey @ 125,315 tokens 30 / 30 30 / 30 parity
HumanEval pass@1 reference 100% retention within sampling noise
Wikitext-2 PPL Δ +0.033 tight
Single-seed numbers from the public Qwen 3.6 artifact. 3-seed bit-identical verification on PPL: σ = 0 across seeds 7 / 123 / 2024. Architecture-level 3-seed validation (V/K theorem) on Mistral 7B GQA-4 + Qwen 2.5 3B GQA-2 + Llama 3.2 3B + Phi-3.
RECEIPT 3

Memory savings break the multi-GPU requirement.

VRAM · Single A100-80GB
QWEN 3.6 35B-A3B

FP16 OOMs at 64K. fraQtl runs 128K with 28 GB headroom.

Same model. Same hardware. 8× the context. The difference between needing 1 GPU and needing 2.

CONTEXT FP16 BASELINE FRAQTL HARDWARE
16K ~71 GB 25.6 GB Both fit on 1× A100-80GB
64K 82.9 GB → OOM 36.8 GB FP16 needs 2 GPUs; fraQtl 1
128K 85+ GB 51.7 GB FP16 needs 2 GPUs; fraQtl 1 · 28 GB free
FP16 64K = 82.86 GB measured (OOMs on 80 GB ceiling). 16K and 128K FP16 figures are model + KV-cache extrapolations — conservative lower bounds.
fraQtl numbers measured on a single A100-80GB with the public artifact at huggingface.co/fraQtl/Qwen3.6-35B-A3B-compressed.
30-DAY PILOT

Bring your model. Keep the savings.

Send us your model and a workload sample. We calibrate, deliver a compressed artifact + benchmark report + integration path for your deployment stack. If the numbers don't move, no commitment.

1
You send
Model (HF org/name), a small workload sample, target context length, current GPU setup. The Tally form takes ~2 min.
2
We calibrate + benchmark
Per-model calibration on your workload. Compressed artifact + benchmark report against your FP16 baseline. Pilot turnaround: 1–2 weeks.
3
You deploy
A compressed artifact that loads through standard Transformers, or runtime KV integration on your stack (vLLM runtime measured — see the lead receipt). Integration support included.
DELIVERY 1 · ARTIFACT
Compressed model on HuggingFace
Loads through standard Transformers; integration support included.
DELIVERY 2 · RUNTIME KV
One-line cache compression
Composes with the artifact for additional savings at long context. Early-access integration.
Request Pilot

Free technical pilot for the first 5 qualified design partners.

RELEASES SHIP LOG · LATEST FIRST

Compressed models, ready to load.

Everything shipped, dated, latest first — runtime integrations, receipts, and public artifacts on HuggingFace. Reproducible numbers throughout.

2026 · AUG 14 RECEIPT
Nine 128K users on one A100 (bit-plane V2 KV) — 134.1 aggregate tok/s, 2× fp16 throughput at 4.5× its users, 9/9 per-user needles, +45% KV pool Lead receipt ↓
2026 · JUL 22 HI-FI GGUF
Gemma-4 Hi-Fi GGUFs: E2B-it + 26B-A4B-it — calibrated GGUFs with KLD receipts, in the Hi-Fi Quants collection HuggingFace →
2026 · JUL 10 RECEIPT
Third architecture receipted: Llama-3.1-8B — 2.35× fp16 KV capacity, 1.23× fp16 decode @128K, 90/90 needle grids — model matrix complete, three architectures on one unchanged kernel See the matrix ↓
2026 · JUL 07 REPRO KIT
KV sidecar repro kit public — Mistral-7B + Qwen3-4B sidecar repos + SM80 runtime wheel; fraqtl_repro_receipts.py reproduces every cell on a rented A100 HuggingFace →
2026 · JUL 05 RECEIPT
128K concurrency receipt lands (vLLM) — 6 users at 128K context each on one A100 — 140.9 vs fp16’s 66.6 aggregate tok/s (2.1×), every user’s needle retrieved Lead receipt ↓
2026 · JUL 02 RUNTIME
Membrane kernel lands in vLLM (warptile_v32) — fragment-native compressed-KV reader — packed page straight into the tensor cores, zero reconstruction; 95–99% of fp16 decode single-user
2026 · MAY RUNTIME
llama.cpp 128K KV integration (D1) — Mistral-7B at 128K below Q8’s live VRAM with 5/5 retrieval where Q8 drops to 1/5 — the original moat receipt D1 receipt ↓
PUBLIC ARTIFACT 2026 · APR 27

Qwen 3.6 35B-A3B compressed

MoE · 35B params (3B active) · weight-compressed artifact · 23.8 GB on disk
HuggingFace →
MMLU
82.24%
FP16: 82.40% · −0.16pp
∞Bench Passkey
30 / 30
at 125,315 tokens
VRAM @ 128K
51.7 GB
FP16 OOMs · 1× A100
Next: derotated-K kernel (8 users/A100 target) · 256K quality gate · chunked-prefill fix · subscribe to release updates →
MECHANISM

Why deletion fails where noise succeeds.

Each cell is a KV-cache dimension. Watch what happens to attention routing under each compression strategy.

Rank throws away signal.
Quantization preserves it.

Rank Reduction — dimensions deleted
PPL: 9.19 (FP16)
Quantization — precision reduced
PPL: 9.19 (FP16)
Full mechanism on /research →
RESEARCH ROADMAP

What's shipping vs what's in the lab.

Two lanes. Public means measured, reproducible, and safe to deploy today. Research means active work we're not making customer claims on yet — listed so you can see where the substrate is heading.

● Public · website-ready
Measured
D1 long-context KV
Mistral-7B 128K in llama.cpp: below Q8 live VRAM, 5/5 retrieval. The llama.cpp lane receipt above.
Measured · new
vLLM full-speed KV
95–99% of fp16 decode at 2.42× KV capacity, needle intact. the lead receipt above.
Public artifact
Qwen 3.6 35B-A3B
Compressed weight artifact on Hugging Face. 128K on 1× A100, MMLU 82.24% vs 82.40% FP16.
Quality anchor
Hi-Fi calibration
FP16-reference calibration recipe behind the public artifact — quality and size, no speed claim.
◐ Research · in progress · no customer claims yet
MoE expert compression Task-aware sidecars Derotated-K kernel · 8 users/A100 target 256K quality gate · chunked-prefill fix

Active research, not part of the pilot deliverable and carrying no performance or accuracy claim until published with receipts. See the research →

PILOT INTAKE

Send us your model. We'll tell you if fraQtl can help.

A 30-day technical pilot. We calibrate on your workload, benchmark against your FP16 baseline, and hand you a deployable artifact. Free for the first 5 qualified design partners.

Direct contact: contact@fraqtl.ai
Replies within 1 business day.