Altinity Stable Builds for ClickHouse®
Run Business-Critical ClickHouse Applications Confidently with Altinity Stable® Builds
Vetted for production use, maintained for 3 years. Join hundreds of organizations who enjoy the peace of mind from running Altinity Stable Builds.
We have nodes that are running on Altinity Stable Release 21.8. Some processes have been up for 800 days. They have processed many, many petabytes of data in that time.
Altinity Financial Services Customer
What are Altinity Stable Builds?
Altinity Stable Builds are production-certified ClickHouse binaries based on ClickHouse Long Term Support (LTS) releases. We build them for organizations who value stable operation without major upgrade for long periods of time. Altinity offers Enterprise support for Stable Builds as part of all Altinity.Cloud and Altinity Enterprise support subscriptions.
Why You Will Love Altinity Stable Builds
Ready for Production Use
Altinity Stable Builds are extensively tested and vetted with real workloads. We also collect early adopter feedback on upgrade and operation to ensure things go smoothly. Deploy once, with confidence.
Long Term Support
Major version upgrades are expensive. Altinity maintains Altinity Stable Build versions for up to three years. We even backport features by customer request. That’s three years of secure, convenient operation for each release.
Go the Extra Mile on Security
Altinity QA suites have extensive tests for in-flight and at-rest data protection. Need to deploy into FedRAMP or PCI-DSS environments? FIPS-compatible Altinity Stable Builds are the answer.
100% Open Source
Leave worries about lock-in and relicensing behind. Altinity Stable Builds are Apache 2.0 licensed. No hold-backs or closed source components.
Documentation
Installation docs, description of builds, and awesome release notes. The information you need to deploy Altinity Stables is at your fingertips.
Up-to-Date and Ready for Use
Altinity Stable Builds have the latest LTS branch fixes and are completely compatible with official ClickHouse binaries. Pick from rpm, apt, tarball in our code repo or pull Docker images from Docker Hub.
Read More About Our Builds
The Altinity Build System for ClickHouse®: Why, What, and How
Altinity Stable Builds deliver open source ClickHouse LTS with 3 years of support, CVE scanning, transparent CI/CD pipeline, upgrade guidance, and real-time data lake builds.
Altinity Stable Build for ClickHouse® 25.8
Altinity Stable® Build for ClickHouse 25.8 is now available! Altinity Stable Builds are based on ClickHouse Long-Term Support releases and are maintained for 3 years.
Altinity Stable® Build for ClickHouse® 24.8
The newly released Altinity Stable Build® for ClickHouse® 24.8 gives users the power of ClickHouse 24.8 with three years of support.
Frequently Asked Questions
Altinity Stable Builds start from upstream ClickHouse LTS releases, then go through additional Altinity build, test, security, and release validation before they are certified for production use. Compared with upstream LTS, Altinity Stable Builds ship later, include carefully selected fixes and backports, and are maintained by Altinity for up to 3 years. They are 100% open source, compatible with official ClickHouse binaries, and designed for teams that want a stable ClickHouse release lifecycle without chasing every upstream release.
Altinity Stable Builds typically ship 3 to 4 months after the upstream LTS release because Altinity waits for the branch to stabilize before certifying it. During that period, regressions surface, backports land, early adopters test upgrades, and Altinity runs additional CI, regression, security, and compatibility checks. The goal is not to be first. The goal is to give teams a ClickHouse build they can trust in production.
Yes. Altinity Stable Builds are API-compatible with official upstream ClickHouse builds and are designed to work with the same open source ClickHouse ecosystem. If you are moving between upstream and Altinity Stable Builds, review the release notes, confirm the target version, and test the upgrade or downgrade path before changing production clusters.
Altinity Stable Builds are available as Deb or Apt packages, RPM packages, and tarballs from builds.altinity.cloud, or as Docker images from Docker Hub. Full installation and upgrade instructions are in the Stable Build quickstart guide. Before installing or upgrading, review the release notes for the version you plan to use so you understand any version-specific requirements or upgrade steps.
Altinity offers additional build tracks for teams with these requirements. For data lake workloads, Altinity Antalya builds extend ClickHouse with real-time query on Apache Iceberg tables, Compute Swarms, and Hybrid Tables for querying MergeTree and Iceberg data together. For regulated environments, FIPS-compatible Altinity Stable Builds use BoringSSL cryptography libraries for encryption of most application and inter-server traffic. FIPS-compatible builds enable ClickHouse to operate in a manner compatible with FIPS 140-2, but they do not by themselves make an environment FedRAMP or PCI-DSS compliant.
Start with the Altinity Stable Builds release notes for the ClickHouse version you want to run. The release notes show available versions, upgrade guidance, known issues, and whether a FIPS-compatible build is available. For production systems, install a specific version instead of relying on an unpinned package install or assuming a Docker latest tag exists. After installation, run SELECT version() to confirm that the cluster is using the intended Altinity Stable Build.
