Skip to main content

Get Modelverse

Modelverse ships inside the ClikaRT release archives: one archive per platform, carrying the ClikaRT runtime and Modelverse together (the clika-modelverse executable, the library, the public headers, and the CMake packages for both products). Installing ClikaRT installs Modelverse; there is no separate Modelverse download and no second install step. Each platform's archive lives on the release page; access comes with your evaluation, arranged by your delivery contact.

Fetch the archive matching your platform and the checksum beside it, verify, and extract. 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 MODELVERSE_INSTALL_DIR="$PWD/ClikaRT_linux_x86_64-0.4.6"

MODELVERSE_INSTALL_DIR is the extracted directory, the same one the ClikaRT documentation calls CLIKART_BUNDLE_DIR; one directory carries both products. (Windows, in PowerShell: curl.exe -LO <url> per file, then tar -xf <archive>; CertUtil -hashfile <archive> SHA256 prints the checksum to compare.)

Per platform, the archive to pick and the check that it runs on your machine:

OSArchitectureArchiveVerify withNotes
Linuxx86_64ClikaRT_linux_x86_64-<version>.tar.xzbin/clika-modelverse devicesCPU always; CUDA with the NVIDIA driver alone, Vulkan with a Vulkan 1.2 driver
Linuxarm64ClikaRT_linux_arm64-<version>.tar.xzbin/clika-modelverse devicesCPU · CUDA · Vulkan, as above
Windowsx86_64ClikaRT_windows_x86_64-<version>.zipbin\clika-modelverse.exe devicesCPU · Vulkan · CUDA on request
Windowsarm64ClikaRT_windows_arm64-<version>.zipbin\clika-modelverse.exe devicesCPU · Vulkan
macOSApple siliconClikaRT_macos_arm64-<version>.tar.xzbin/clika-modelverse devicesCPU · Metal (ships with macOS)
Androidarm64-v8aClikaRT_android_arm64-<version>.tar.xzpush the directory to the device, run over adb shellCPU · Vulkan

The Linux archives carry both CUDA images, and each image is self-contained: the CUDA runtime and cuBLASLt are inside it, so 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).

The Python wheels on the release page are the ClikaRT runtime's (clika-runtime, three flavors on Linux, picked by the NVIDIA driver); Get ClikaRT covers them. Modelverse has no Python package in this release: the clika-modelverse executable and the C++ library are its shipped surface.

Every archive carries modelverse.json at its top level, the manifest that pins the exact ClikaRT identity this Modelverse build linked against (version plus content hashes) and the minimum glibc it runs on; a mismatched runtime/Modelverse pair is refused with a readable error, never undefined behavior. dist.json beside it describes the platform build itself (backends compiled in, library layout).

Accelerators, drivers and hardware are the runtime's: the ClikaRT system requirements are the authority.

Then continue with Quick install, which picks up at the extracted directory.