Zapdev-labs
Building faster LLMs on real hardware
Zapdev-labs builds quantization, inference runtimes, and benchmarks — C and Python tooling that cuts memory, raises tokens-per-second, and ships local /v1 chat HTTP APIs you can run on your hardware.
Current Focus
LLM Compression
Weight and KV-cache quantization — PolarQuant, FastVQ, and oxidize-quantize for edge deployment.
Local Inference
C and Python runtimes with local /v1 chat endpoints — oxidize, turboforge, and miniforge.
Open Source
Benchmarks, agent tooling, and inference stacks built in public for developers worldwide.
- 12+
- Open-source projects
- 3-bit
- KV cache compression
- 6×
- KV memory reduction
Open Source Work
Tools and libraries built in public.
Selected Capabilities
We take on complex inference problems at the edge of what's possible and make them boringly reliable.
AI / INFERENCE
LLM infrastructure, quantization pipelines, and local serving stacks.
DEV TOOLS
Open-source libraries, hardware probes, and cross-backend benchmark harnesses.
PRODUCT / SYSTEMS
Interfaces and APIs that match the depth of the underlying inference system.
Built With
C rewrite
Oxidize is moving closer to the metal
The next Oxidize runtime is a C11 application: a dependency-light core, a native CLI, and explicit CPU and GPU backends. The rewrite is active in the public repository while releases and installers catch up.
$ git clone https://github.com/Zapdev-labs/oxidize.git && make -C oxidize/oxidize-cVerify
Run the C test suite
make -C oxidize/oxidize-c testCUDA
Build the GPU backend
make -C oxidize/oxidize-c cudaThe C rewrite is under active development. Inspect the source and current build targets: oxidize-c
How we work
Issue in, fix out
Most work starts on oxidize — open a GitHub issue, research the root cause, then use AI tooling to land a tested patch.
- 01
Open an issue
File a repro on oxidize — crash, wrong output, or slow inference
- 02
Research
Read the stack trace · profile on real hardware · trace root cause
- 03
AI-assisted fix
Cursor on the oxidize codebase · patch, test, open PR
Proof, not promises
Benchmarks you can rerun
ollama-performance-benchmark runs each backend sequentially on the same GGUF and prompt. On our hardware, oxidize and miniforge beat stock llama.cpp tokens-per-second.
View benchmark repoBack-to-back run on one prompt · Ryzen 7 PRO · Qwen3.5-4B Q4
Reference
Common questions
Stay Updated
Reach out for collaboration on quantization, local inference, or benchmark work.