ParetoStackpareto-stackdocshpc-labs

Install

ParetoStack 0.3.13 runs on Windows 10 and 11 (x86_64 and ARM64), Linux (x86_64 and aarch64) and NVIDIA DGX-class Arm servers. Download the package for your system from your account page (a purchase is needed; the license file is on the same page: paretostack license install license.json) and verify it before you install.

Verify your download

Every release is signed, so you can be sure a package is the one we built before you run anything from it. The release lists the SHA-256 of every package in SHA256SUMS; that list carries a digital signature (SHA256SUMS.sig) made with a key held in AWS KMS, which cannot be exported. Download SHA256SUMS, SHA256SUMS.sig and release-signing-key.pem from your account page next to the package, then:

  • Linux and macOS (needs openssl): ./verify-download.sh paretostack-linux-0.3.13.tar.gz
  • Windows (PowerShell 5.1 or 7, nothing to install): powershell -ExecutionPolicy Bypass -File .\verify-download.ps1 .\paretostack-windows-0.3.13.zip
  • By hand: openssl dgst -sha256 -verify release-signing-key.pem -signature SHA256SUMS.sig SHA256SUMS, then compare the package's SHA-256 with its line in SHA256SUMS.
  • After the first install: paretostack check-download PACKAGE checks a later download with the key that came inside the package, so it does not depend on this website. The scripts are at verify-download.sh and verify-download.ps1, the key at release-signing-key.pem. Compare the key fingerprint the script prints with this one, which is the only thing a computer cannot check for you:

13:EC:3E:15:66:7F:50:C2:F6:0C:A3:C1:FE:41:4D:F0:C6:E0:2C:42:5E:1E:0E:03:20:3D:DB:C3:9C:CA:59:08

The same fingerprint is in release-signing-key.txt. If the two ever differ, do not install and write to support@hpc-labs.ai.

Windows

You need Windows 10 or 11 and PowerShell. Python 3.11 or newer (64-bit) is required; the installer can set up Python, Git and CMake for you.

  1. Unzip paretostack-windows-0.3.13.zip to a local folder (not a network drive).
  2. Run install.cmd in that folder (double-click it, or run it from a Command Prompt). It bypasses the script policy for that one run only; your system settings are not changed.
  3. install.cmd -Everything also installs Python 3.12, Git and CMake through winget, asking before each step.
  4. -WithModels also installs Ollama and a local code model sized for your memory (a download of several GB).
  5. -Yes skips the questions; -NoCompiler skips the compiler offer.
  6. When the machine has no C compiler, the installer offers a portable one (llvm-mingw: gcc, clang, make; about 190 MB; no administrator rights; the download is checked against a recorded SHA-256). It is kept in %LOCALAPPDATA%\ParetoStack\toolchain, is not put on your PATH, and ParetoStack finds it itself. It is what the Python-to-C port, the build search and C / C++ projects need. Run install.cmd again later to add it.
  7. Open a new PowerShell window (so the PATH is read again) and try it:
paretostack arch                  which machine this is (OS, CPU, instruction set, compilers)
paretostack doctor                what is installed and what is missing
paretostack examples              the example projects that come with this version
paretostack examples run word_filter --yes

The command is a plain text file, %LOCALAPPDATA%\ParetoStack\bin\paretostack.cmd, that runs the private environment's python.exe -m paretostack: the installer creates no new unsigned program, so antivirus tools have nothing new to stop. Nothing in the installer disables or changes your antivirus. If a prompt names a file under %LOCALAPPDATA%\ParetoStack, allow it or exclude that folder.

If something does not work: "python is not recognized" means a new window is needed after the install; "running scripts is disabled" means use install.cmd instead of typing .\install.ps1. Send the output of paretostack doctor together with the error message when you ask for help.

Linux

  1. Unpack paretostack-linux-0.3.13.tar.gz (the Python code is the same on x86_64 and aarch64).
  2. Run ./install.sh in the unpacked folder. It installs into a private virtual environment and copies the sample projects to ~/ParetoStack/sample.
  3. ./install.sh --everything also installs the missing system packages (it lists them first; add --yes to run them).
  4. ./install.sh --with-models also installs Ollama and a local code model.
  5. Open a new shell, or export PATH="$HOME/.local/bin:$PATH".
paretostack doctor
paretostack examples
paretostack examples run word_filter --yes

NVIDIA DGX (Arm)

Use paretostack-dgx-0.3.13.tar.gz on an aarch64 DGX such as the DGX Spark (GB10). ./install.sh installs the command and starts the web console as a local user service on http://127.0.0.1:8196/; ./install.sh --no-console installs the command only. The DGX profile checks the hardware and adds GPU checks to paretostack doctor. The same --everything and --with-models options apply.

Update

Download the newer package from your account page (bug-fix releases of the version line you bought are included), unpack it, and run update.cmd (Windows) or ./update.sh (Linux and DGX). It replaces only the ParetoStack files: no prerequisites, no PATH change. On a DGX with the console service, systemctl --user restart paretostack-console makes it pick the update up. Versions you already installed keep working. A later version line (for example 0.4) is a separate purchase.

The example scripts

Each package also contains example.cmd (Windows) and example.sh (Linux and DGX). They run the example projects one after the other, print a summary with a speed-up plot that tags each example bit-exact or contract, and write one log file. example all --parallel 4 runs the single-core examples four at a time, each on its own core, and labels those numbers [in a lane]. Ctrl+C at any time prints a summary of what was measured so far.

AI models (optional)

Models are optional. A local model (Ollama) is used automatically when there is one: nothing leaves the machine. Claude or OpenAI are used only when you ask for them (/model claude, /model openai in the pareto chat), and only after you have seen exactly what would be sent (a short summary: the machine, the project's name, the plan's item list; never source code) and answered yes. pareto --model none never uses a model.