Get ClikaRT
Pick the platform you are deploying to and copy the commands. Each platform has its own archive on the release page, named ClikaRT_<os>_<arch>-<version>.tar.xz (.zip on Windows) with a .sha256 checksum beside it; the tree inside is that platform's complete bundle. Access to the release page comes with your evaluation; your delivery contact arranges it.
wget https://github.com/Clika/runtime_internal/releases/download/0.4.6/ClikaRT_linux_x86_64-0.4.6.tar.xz
wget https://github.com/Clika/runtime_internal/releases/download/0.4.6/ClikaRT_linux_x86_64-0.4.6.tar.xz.sha256
sha256sum -c ClikaRT_linux_x86_64-0.4.6.tar.xz.sha256
tar -xf ClikaRT_linux_x86_64-0.4.6.tar.xz
export CLIKART_BUNDLE_DIR="$PWD/ClikaRT_linux_x86_64-0.4.6"
# Verify:
"$CLIKART_BUNDLE_DIR"/examples/bin/version_00_hello_worldNo driver needed.
Then continue with Quick install, which picks up at the extracted bundle. Complete installation has per-platform depth.
All combinations
The fetch pattern is the same for every platform; only the archive name changes. Every archive is one file:
wget https://github.com/Clika/runtime_internal/releases/download/0.4.6/ClikaRT_linux_x86_64-0.4.6.tar.xz
wget https://github.com/Clika/runtime_internal/releases/download/0.4.6/ClikaRT_linux_x86_64-0.4.6.tar.xz.sha256
sha256sum -c ClikaRT_linux_x86_64-0.4.6.tar.xz.sha256
tar -xf ClikaRT_linux_x86_64-0.4.6.tar.xz
export CLIKART_BUNDLE_DIR="$PWD/ClikaRT_linux_x86_64-0.4.6"
(Windows, in PowerShell: curl.exe -LO <url> for the archive and its .sha256, compare (Get-FileHash <archive>).Hash against the sidecar, tar -xf <archive>, $env:CLIKART_BUNDLE_DIR = "$PWD\<extracted dir>".)
Per platform, the archive and the driver requirements:
| OS | Architecture | Archive | Accelerators and drivers |
|---|---|---|---|
| Linux | x86_64 | ClikaRT_linux_x86_64-<version>.tar.xz | CPU (no driver) · CUDA (NVIDIA driver only) · Vulkan (Vulkan 1.2 or newer) |
| Linux | arm64 | ClikaRT_linux_arm64-<version>.tar.xz | CPU · CUDA · Vulkan, as above |
| Windows | x86_64 | ClikaRT_windows_x86_64-<version>.zip | CPU · Vulkan · CUDA on request |
| Windows | arm64 | ClikaRT_windows_arm64-<version>.zip | CPU · Vulkan |
| macOS | Apple silicon | ClikaRT_macos_arm64-<version>.tar.xz | CPU · Metal (ships with macOS) |
| Android | arm64-v8a | ClikaRT_android_arm64-<version>.tar.xz, then Deploy to mobile | CPU · Vulkan |
The two Linux archives carry both CUDA images, lib/libClikaRT_cuda13x.so and lib/libClikaRT_cuda12x.so, and each image is self-contained: the CUDA runtime and cuBLASLt are inside it. A CUDA machine needs its NVIDIA driver and nothing else, no CUDA toolkit install and no LD_LIBRARY_PATH; the runtime loads the image the driver serves (a driver of major version 580 or newer serves the CUDA 13 image, an older driver the CUDA 12 image).
Every desktop archive verifies the same way after extraction: run examples/bin/version_00_hello_world (.exe on Windows) from the extracted root; it prints the ClikaRT version.
Python wheels
The clika-runtime wheel is a release asset beside the archives, one per CPython version (3.10 to 3.14) and platform. It carries the runtime and its backends inside the package, so the Python path needs no archive and no environment setup. On Linux (x86_64 and aarch64) the wheel comes in three flavors, told apart by the local version tag; the NVIDIA driver picks the flavor (nvidia-smi prints the driver version in its header):
| Version | Contents | Pick it when |
|---|---|---|
0.4.6 | every non-CUDA backend, no CUDA image | the machine has no NVIDIA GPU |
0.4.6+cu13x | the non-CUDA backends plus the CUDA 13 image | the NVIDIA driver is major version 580 or newer |
0.4.6+cu12x | the non-CUDA backends plus the CUDA 12 image | the NVIDIA driver is older than 580 |
A CUDA flavor's image is self-contained, as in the archives: the driver is the one requirement, no CUDA toolkit and no LD_LIBRARY_PATH. macOS (Apple silicon) and Windows x64 carry no CUDA and ship one unsuffixed wheel each for CPython 3.10 to 3.14; Windows arm64 ships one for CPython 3.11 to 3.14. No wheel declares a pip requirement. Download the wheel whose CPython tag, platform tag and flavor match the machine, verify it against its .sha256 sidecar, and install it from the file; numpy is the array bridge the tutorial uses, installed separately. (The release page writes the + of a flavor tag as %2B in the download URL; the file lands with the + in its name.)
wget https://github.com/Clika/runtime_internal/releases/download/0.4.6/clika_runtime-0.4.6%2Bcu13x-cp313-cp313-manylinux_2_28_x86_64.whl
wget https://github.com/Clika/runtime_internal/releases/download/0.4.6/clika_runtime-0.4.6%2Bcu13x-cp313-cp313-manylinux_2_28_x86_64.whl.sha256
sha256sum -c clika_runtime-0.4.6+cu13x-cp313-cp313-manylinux_2_28_x86_64.whl.sha256
pip install ./clika_runtime-0.4.6+cu13x-cp313-cp313-manylinux_2_28_x86_64.whl
pip install numpy
python -c "import clika_runtime as crt; print(crt.version())"
The last line prints 0.4.6. Use ClikaRT from Python is the guide to the wheel's surface.
System requirements is the authority on platforms, drivers and hardware.