System requirements
ClikaRT ships one distribution per platform. Every distribution includes the CPU backend; accelerator backends are included where the platform has them and load on demand at run time.
Platforms
| Platform | Architecture | Backends |
|---|---|---|
| Linux | x86_64 | CPU, CUDA, Vulkan |
| Linux | arm64 | CPU, CUDA, Vulkan |
| Android | arm64-v8a | CPU, Vulkan |
| Windows | x86_64 | CPU, Vulkan (CUDA on request) |
| Windows | arm64 | CPU, Vulkan |
| macOS | Apple silicon | CPU, Metal |
Host software
| Requirement | Detail |
|---|---|
| C++ toolchain | A C++17 compiler for your own code; the library itself has no compiler requirement |
| CMake | 3.20 or newer |
| Linux glibc | 2.28 or newer (manylinux_2_28 compatible) |
| NVIDIA driver | The driver alone: the runtime's CUDA images carry the CUDA runtime and cuBLASLt inside them, so no CUDA toolkit install and no LD_LIBRARY_PATH. A driver of major version 580 or newer serves the CUDA 13 image, an older driver the CUDA 12 image; the Linux archives carry both, and the Python wheel comes in one flavor per image |
| Vulkan | A driver supporting Vulkan 1.2 or newer |
| Python | CPython 3.10 to 3.14 for the clika-runtime wheel on Linux, macOS and Windows x64; CPython 3.11 to 3.14 on Windows arm64 |
Accelerators
| Backend | Hardware |
|---|---|
| CUDA | NVIDIA GPUs from compute capability 7.0 (Volta) upward, Jetson included |
| Vulkan | Desktop and mobile GPUs with a conformant Vulkan driver (NVIDIA, AMD, Intel, Qualcomm Adreno) |
| Metal | Apple silicon |
info
Memory and disk requirements depend on the model you run: a model needs its weights resident on the device that runs it, plus working memory for activations and the KV cache. The Modelverse pages list per-model figures.