@QuixiAI: https://x.com/QuixiAI/status/2073936537213915611
Summary
QuixiAI released QuixiCore, a family of native high-performance AI kernel libraries for modern accelerators, with standalone implementations for CUDA, Metal, ROCm, XPU, and Gaudi backends, all sharing a common contract but no shared code.
View Cached Full Text
Cached at: 07/06/26, 01:59 AM
QuixiAI/QuixiCore
Source: https://github.com/QuixiAI/QuixiCore
QuixiCore
QuixiCore is a family of native high-performance AI kernel libraries for modern accelerators.
QuixiCore is one kernel library contract with five standalone native implementations: CUDA, Metal, ROCm, XPU, and Gaudi.
Each backend is a standalone implementation written directly for its target platform. The repositories share no implementation code. They share a common kernel contract: the same operations, quant formats, correctness expectations, benchmark methodology, and public library identity.
Backends
| Backend | Platform | Repository |
|---|---|---|
| QuixiCore CUDA | NVIDIA CUDA, Ampere+ | QuixiAI/QuixiCore-CUDA |
| QuixiCore Metal | Apple Silicon / Metal | QuixiAI/QuixiCore-Metal |
| QuixiCore ROCm | AMD ROCm / CDNA2-4 | QuixiAI/QuixiCore-ROCm |
| QuixiCore XPU | Intel GPU / oneAPI / SYCL | QuixiAI/QuixiCore-XPU |
| QuixiCore Gaudi | Intel Gaudi2-3 / HPU | QuixiAI/QuixiCore-Gaudi |
Design Philosophy
QuixiCore is built around one principle:
Native implementations. Shared contract. No shared code.
CUDA kernels should be written like CUDA kernels. Metal kernels should be written like Metal kernels. ROCm kernels should be written like ROCm kernels. XPU kernels should be written for Intel GPU tooling. Gaudi kernels should be written for the Gaudi HPU/TPC stack.
The shared layer is not source code. The shared layer is the definition of what each backend must implement.
Backend Relationship
The umbrella repository links to backend repositories but does not vendor them.
QuixiCore does not use git submodules. Each backend declares the QuixiCore contract version it implements using backend metadata, and implementation work happens in that backend repository.
Repository Role
This repository is the umbrella contract repository for the QuixiCore family. It contains:
- Backend registry metadata
- Kernel and quant format registries
- Correctness and benchmarking specifications
- Coverage and architecture support matrices
- Release and naming policy
- Test-vector organization
It intentionally does not contain backend implementation code, shared kernel code, platform bindings, or build systems.
Contract Version
The initial contract target is v0.1. See roadmap/v0.1-checklist.md for the checklist that turns the current scaffold into a usable compatibility target.
Similar Articles
@QuixiAI: QuixiAI/ThunderKittens and QuixiAI/ThunderMittens are now rebranded to QuixiCore-CUDA and QuixiCore-Metal Announcing Qu…
QuixiAI rebrands ThunderKittens and ThunderMittens into QuixiCore-CUDA and QuixiCore-Metal, creating a unified family of cross-platform kernels for AI workloads.
@QuixiAI: https://x.com/QuixiAI/status/2068776183102067086
DwarfStar is a self-contained native inference engine optimized for DeepSeek V4 Flash and PRO models, supporting Metal, CUDA, and ROCm backends, with a focus on high-end personal machines and Mac Studios.
Qualcomm wants to grow in the AI space (multiple acquisition's underway)
Qualcomm is aggressively expanding in AI through multiple acquisitions, including Modular (creator of Mojo and MAX inference framework) and potentially Tenstorrent, signaling a significant push against Nvidia's CUDA ecosystem.
@QuixiAI: QuixiAI/ThunderMittens (fork from @HazyResearch) Porting ThunderKittens (and literally everything else) to Metal. Now w…
QuixiAI ported ThunderKittens to Metal, enabling kernel support on MPS and MLX for training models on Mac.
@akshay_pachaar: Apple finally did it. Its new framework, Core AI, runs models entirely on Apple silicon, so inference happens on the us…
Apple released Core AI, a new framework that runs AI models entirely on Apple silicon devices (iPhone, iPad, Mac, Vision Pro) with zero server calls. It includes a memory-safe Swift API, model export recipes for PyTorch, an optimizer, and debugging tools, supporting models like Qwen, Mistral, and SAM3.