/ quick start / installation

How to install post-quantum cryptography with NEXUS-Q.

The quickest route depends on your programming language and platform. NEXUS-Q is Rust-first; its language bindings may require the native library. Use the steps below to select a supported path instead of assuming every SDK is a pure-language package.

/ guide / technical overview

How to Install Post-Quantum Cryptography

1. Choose your integration

For a Rust application, start with the published Rust crate. For Python, Node.js, Java, Kotlin, .NET or another language, open the matching SDK instructions and confirm native runtime requirements.

2. Rust quick start

Install Rust and Cargo, then add the top-level crate to your application. Current main build requirements in the v4.1.2 documentation specify Rust 1.88 or newer; check the exact release notes for your chosen version.

Rust command

cargo add nexusq

3. Python package

The project lists nexusq on PyPI. The reviewed 4.1.2 release is source-distribution-only, without a wheel listed. A local build environment and native libnexusq may be required.

Python command

python -m pip install nexusq==4.1.2

4. Check native dependencies

Several language SDKs are thin bindings over libnexusq. Read the binding-specific README for platform support, runtime installation and version matching. Do not mix SDK and native-library versions without checking compatibility.

5. Verify and test

Pin a release, verify package provenance and checksums where provided, run the documented tests, and test interoperability and error handling. Review the threat model before handling real secrets. NEXUS-Q does not claim independent third-party audit or FIPS 140-3 certification.

/ next steps

Explore NEXUS-Q

If you need another language, start at the SDK catalogue. For algorithm details, read the PQC overview.

Project identity: NEXUS-Q is an independent open-source post-quantum cryptography project. It is not affiliated with Google and is unrelated to the discontinued Google Nexus Q media player.

Technical details and package availability can change between releases. Always consult the tagged source, package registry and release notes for the version you install.