# OpenFHE v1.4.2+ with HEXL: supported branch/tag? **URL:** \ **Category:** OpenFHE Hardware Acceleration\ **Tags:** hexl, development-release, questions\ **Created:** [March 2, 2026, 3:33pm UTC](https://openfhe.discourse.group/t/openfhe-v1-4-2-with-hexl-supported-branch-tag/2288 "2026-03-02T15:33:13Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Gabba](https://avatars.discourse-cdn.com/v4/letter/g/bc8723/32.png) [@Gabba](https://openfhe.discourse.group/u/Gabba)\ **Post date:** [March 2, 2026, 3:33pm UTC](https://openfhe.discourse.group/t/openfhe-v1-4-2-with-hexl-supported-branch-tag/2288/1 "2026-03-02T15:33:13Z")
Hi all, I’m benchmarking CKKS workloads on an AVX-512 capable AWS Intel Xeon (Ice Lake). I’d like to use [OpenFHE](https://github.com/openfheorg/openfhe-development) **v1.4.2 (stable)** or **newer** **(e.g., v1.5.0 dev)**. However, the official openfhe-hexl README states it “can be staged into OpenFHE v1.4.0”, and the documented openfhe-configurator workflow checks out openfhe-development v1.4.0 + openfhe-hexl v1.4.0.0. [GitHub - openfheorg/openfhe-hexl](https://github.com/openfheorg/openfhe-hexl), [GitHub - openfheorg/openfhe-configurator](https://github.com/openfheorg/openfhe-configurator) 1. Is HEXL supported on OpenFHE v1.4.2+? If yes, which branch/tag or procedure is recommended? 2. If not, is the recommended approach to stay on OpenFHE v1.4.0 when HEXL acceleration is required? 3. Is there a plan to update openfhe-hexl to track newer OpenFHE releases (1.4.2+)? Any feedback is greatly appreciated! ---
**Author:** ![pascoe](https://avatars.discourse-cdn.com/v4/letter/p/90ced4/32.png) [@pascoe](https://openfhe.discourse.group/u/pascoe)\ **Post date:** [March 2, 2026, 7:03pm UTC](https://openfhe.discourse.group/t/openfhe-v1-4-2-with-hexl-supported-branch-tag/2288/2 "2026-03-02T19:03:59Z")
There is a PR for v1.5.0 available now. It should be merged to main after review. >