Availability, access, and licensing.

Availability

ZJX 1.29 REDLINE is the current release line. It adds the ultrafast objective beside compact and fast, with four workers by default; every REDLINE product gate passed on the frozen candidate and ZJX 1.29.0 was released on 2026-09-08. Published as tag v1.29.0 with the Linux x86-64 package and checksums; the public release record lists the exact artifacts. ZJX 1.28.0 LOCKWIRE, released 2026-09-06, was the previous release with published assets; 1.29 changes none of its workflow, fidelity, or boundaries.

Platform

x86-64 Linux with glibc, unprivileged user operation. Runtime dependencies: glibc, liblzma.so.5, libzstd.so.1.

Not claimed

Windows, macOS, ARM, musl, other distributions, network filesystems. The local desktop wrapper is laboratory tooling, not a supported GUI download.

Interfaces

Two command-line executables with JSON results, a progress record stream, and bounded cancellation, for people and pipelines.

Objectives

Compact (default), fast, and the new ultrafast, chosen per archive; ultrafast runs four workers by default and up to eight.

Release details

Release ZJX 1.29.0 REDLINE, tag v1.29.0, published 2026-09-08, source revision 0115105b, build mode ReleaseSafe on a portable baseline x86-64 target. The package and its executables are the qualified third release candidate promoted unchanged, so they report the version literal 1.29.0-rc3; nothing was rebuilt or repackaged for publication. All four artifacts were retrieved through two authenticated paths and revalidated: the package hashed to the frozen candidate identity byte for byte, verified its own checksum list, installed rootless into a clean userspace, and packed, tested, listed, and restored a tree containing a symbolic link with the exact link target.

The package contains bin/zjx (SHA-256 636af810b567098a1ee65201a9e408284585f2abcaf0dac1abacb43abe69796d), bin/zjx-archive, a rootless installer, checksums, build provenance, and the user documentation including the objectives guide and the support matrix. The checksum files are the provenance mechanism of the release; they are not signatures.

Public release record: artifacts, checksums, qualification summary, and documented limitations · Previous release record (1.28.0 LOCKWIRE)

Package access

The release artifacts are held in the operator-controlled release and are not served for anonymous download from this site. To obtain the package, write to Greyforge Labs with a short description of your intended use; access for noncommercial use and the terms for commercial use are handled in the reply. Verify what you receive against the checksums above before installing.

Request the packageRelease details

License

ZJX is licensed under the PolyForm Noncommercial License 1.0.0. Commercial evaluation, deployment, embedding, resale, hosted use, managed archival services, and internal business use require a separate written commercial license from Greyforge Labs. Public qualification does not establish a service-level agreement or production-support commitment on its own; the supported compatibility window, decoder retention, and support duration are agreed in the commercial license. Source availability under the noncommercial license is not a support commitment.

Commercial evaluation

One representative slice of your retention lane, one report you can act on. Send a description of what you retain and what you pay to keep it. Scope, data handling, and where the run happens are agreed before any file moves.

1. Sample. A representative slice of the real retention lane, sanitized if needed, plus the compressor and settings you use today.
2. Run. ZJX compact, fast, and ultrafast against your current method and the same 14-configuration comparator set, in your environment or on a controlled Greyforge host, as agreed.
3. Report. Complete archive bytes, creation and verification time, exact-restore evidence, memory and processing cost, and the limitations, in the same form as the published campaigns.

Evaluations are scoped, paid engagements; fee, licensing, packaging, and support terms are agreed in writing first. Nothing here promises an NDA, zero telemetry, or a fixed retention period; those are terms of the written agreement.

Contact