FareedKhan-dev/kimi-k3-in-c
A 2.78-trillion-parameter Kimi K3 running inference on a single CPU in 8.24 GB of RAM. Portable C99: no BLAS, no framework, no GPU.
Build with Backblaze B2
SDKs, agent skills, IDE extensions, and reference pipelines from Backblaze Labs. All open source.
Loading star history...
Where it stands
Rank, growth pace and release cadence relative to everything GStars tracks.
2 releases in the last 90 days, the latest 33 days ago, with 9 contributors on GitHub.
Use Cases & Benefits
- Runs inference of a 2.78-trillion-parameter transformer model entirely on a single CPU using portable C99 without GPU or external frameworks.
- Enables memory-efficient, byte-identical model output across machines with RAM from 8 GB to over 128 GB by streaming model layers from disk and caching selectively.
- Use for deploying large language model inference on resource-constrained devices or ordinary laptops without GPUs or specialized hardware.
- Use for research and development environments requiring reproducible, framework-free transformer inference in pure C with minimal dependencies.
- Use for building chat-capable AI assistants that run locally with configurable memory presets and incremental token generation on commodity hardware.
Should you depend on it?
License terms, project hygiene and risks, from GitHub metadata and GStars' snapshots.
License
Apache 2.0
Permissive: commercial use, modification and redistribution are allowed with attribution; includes an explicit patent grant from contributors.
Community files
- README: present
- Contributing guide: present
Watch-outs
No watch-outs from GStars' checks.
General guidance from repository metadata, not legal advice. How we score
From the README
A 2.78-trillion-parameter model. One CPU. 8 GB of RAM.
Kimi K3 inference in portable C99. No BLAS. No framework. No GPU.
The same 2.78-trillion-parameter model, the same answer, on whatever machine you own. More memory only buys speed:
Same short prompt at every size, and the output is byte-identical from the smallest machine to the largest; only the clock changes. One machine, 124 cores, fast NVMe drive: the first three rows still read the model from disk each step, so a slower drive is slower there, while the 128 GB+ row keeps everything in memory and no longer waits on the disk. On that same machine v1.0.0 made the math per token about 8× lighter, a follow-up question in a chat 3.9× faster, and long prompts about half as costly. (A token is roughly a short word-piece; the two runnable demos below are the original captures on a slower drive, so their clock reads a little higher.) Full data in docs/data/.
I am open to AI research roles and PhD positions. CV.
The macOS, Windows and NEON ports, chat mode, the ultra preset, the faster MXFP4 kernels and a long list of parser fixes came from the people below. Who did what.
Compared with peers in Deep Learning
Fastest-growing repositories GStars tracks in this cohort for the week of Nov 8, by 7-day star growth
| Repository | Stars | +7d | Health | Last release |
|---|---|---|---|---|
| rohitg00/ai-engineering-from-scratch | 78.3K | +1.6K | 75 | 1 day ago |
| SYSTRAN/faster-whisper | 26.5K | — | 40 | 368 days ago |
| GeeeekExplorer/nano-vllm | 16.3K | — | 12 | — |
| Lightning-AI/litgpt | 13.8K | — | 58 | 129 days ago |
| data-privacy-stack/presidio | 11.8K | — | 64 | 10 days ago |
| FareedKhan-dev/kimi-k3-in-c | 10.3K | — | 34 | 33 days ago |
| Category median | 16.3K | — | 58 | — |
Also by FareedKhan-dev
Other repositories from this maintainer that GStars tracks
Discover Repositories
Search across tracked repositories by name or description