Hashicorp Boundary End of Life (EOL) Dates and End of Support (EOS) Dates
Hashicorp Boundary end of life (EOL) and end of support (EOS) dates: 3 Hashicorp Boundary versions have reached EOL, including Hashicorp Boundary 0.18 (EOL date: Dec 11, 2025) — no longer receiving security updates or patches. Hashicorp Boundary 0.21.3 is the current supported release — 3 versions in active support. Also see Hashicorp Terraform end of support life for related end-of-life information.
Currently Supported Hashicorp Boundary Releases - Active EOS/EOSL Support (3)
Hashicorp Boundary End of Life (EOL) Releases - No Longer Supported (3)
| Release | Released | Security Support | Latest |
|---|---|---|---|
| 0.18 | (2 years and 1 month ago) | (11 months ago) | 0.18.2 (1 year and 11 months ago) |
| 0.17 | (2 years and 3 months ago) | (1 year and 1 month ago) | 0.17.2 (2 years and 1 month ago) |
| 0.16 | (2 years and 6 months ago) | (1 year and 9 months ago) | 0.16.3 (2 years and 3 months ago) |
If you run HashiCorp Boundary end of life planning for your team, the short answer is that Boundary Community Edition was archived on October 8, 2026, while the Boundary Enterprise and HCP Boundary editions carry on. HashiCorp, now part of IBM, has not published a single end date for the whole product, so you need to know which edition you run.
Hashicorp Boundary End of Life: What Is Deprecated
The Boundary Community Edition is the source-available build of the identity-based access proxy that gave teams least-privileged access to cloud infrastructure, a form of infrastructure access control. On October 9, HashiCorp announced its deprecation on the forum: the GitHub repository is archived and read-only, so it takes no new issues or pull requests. No new releases, bug fixes or security patches are planned, which means any vulnerabilities found later stay unpatched in the open source code.
Existing binaries and source code stay available for self-managed use. Boundary is privileged access and access management infrastructure, so an unpatched build deserves a close security review. This is a deprecation of the open-source edition, not a formal EOL date for Boundary itself.
Boundary EOL Dates by Release
Each release of Boundary is a major release when its first or second digit changes, and generally available builds get a support period of up to two years. The table below follows endoflife.date's May 1, 2026 data, the latest version listed being 0.21.3.
| Release | Released | Security support |
|---|---|---|
| 0.21 | Dec 11, 2025 | Supported (0.21.3) |
| 0.20 | Sep 25, 2025 | Supported (0.20.3) |
| 0.19 | Feb 10, 2025 | Supported (0.19.5) |
| 0.18 | Oct 14, 2024 | Ended Dec 11, 2025 |
| 0.17 | Jul 31, 2024 | Ended Sep 25, 2025 |
| 0.16 | Apr 30, 2024 | Ended Feb 10, 2025 |
Those dates predate the archive, so treat the supported rows as true only for the commercial editions. On Boundary Enterprise, support for a PostgreSQL version also ends one year before PostgreSQL's own EOL.
Security Support and the HashiCorp Support Policy
The HashiCorp support policy is shared across Terraform, Vault, Consul, Nomad and Boundary. Code-fixes and hot-fixes arrive as a new minor release on the latest major release branch, covering up to two releases back, and you should stay current within two releases to get the best security support. Boundary follows that same two-release window and release cadence, unlike Terraform, which has no long term support (LTS) designation according to versio.io, or Vault, Consul and Nomad, which ship LTS builds.
IBM Self-Managed Boundary EOL Dates
IBM now sells Boundary as a self-managed product under the Vault product ID 5900-BJF. Its lifecycle addendum lists the end of mod/fix support per version, and newer IBM releases move to Support Cycle 2 from April 2026.
| Product | Version | End of mod/fix support |
|---|---|---|
| IBM Boundary Self-Managed | 0.19.x | July 31, 2027 |
| IBM Boundary Self-Managed | 0.20.x | September 30, 2027 |
| IBM Boundary Self-Managed | 0.21.x | December 31, 2027 |
| IBM Vault Self-Managed | 1.19 (LTS) | April 30, 2027 |
If your Boundary license comes through an enterprise license with IBM, these are the dates your support contract follows.
Boundary Community Edition Migration and Alternative Options
The Boundary Community Edition end of life follows the IBM acquisition in February 2025, which also brought price increases and a tighter Terraform free plan that pushed Terraform users to resource-based pricing. HashiCorp says it will focus research and development on the commercial editions of Boundary. Your choices are to pay for Enterprise, to maintain the archived code yourself, or to run an unplanned migration, so it pays to evaluate early and set a budget.
Commercial Editions or an Open Source Alternative
Boundary Enterprise and HCP Boundary add session recording and compliance features that the community build never had. With the community build at end of life, Enterprise, HCP Boundary or an alternative such as Infisical, an open-source tool for secrets management and privileged access, is the replacement path. Teams that want to leave the HashiCorp stack, Vault and Terraform included, would pick the alternative.