Other · archived
HashiCorp
HashiCorp has deprecated Boundary Community Edition, the free self-hosted edition of its zero-trust secure-access / PAM tool, and archived its GitHub repository effective immediately; R&D now goes only to Boundary Enterprise and HCP Boundary
left 9 Oct 2026
Quick answers
- Is it true that HashiCorp deprecates Boundary Community Edition on 9 October 2026 — repository archived, move to Boundary Enterprise or HCP Boundary?
- Yes — and the date has already passed (9 Oct 2026). If you run the free, self-hosted Boundary Community Edition for zero-trust access to your infrastructure — as a replacement for bastion hosts and jump servers, or as a privileged-access (PAM) layer — it is now a deprecated product with no further HashiCorp development.
- When did it take effect?
- 9 Oct 2026 (already passed). Verified against the vendor's own announcement.
- What should I use instead?
- HashiCorp directs users to its commercial editions: Boundary Enterprise (self-managed) or HCP Boundary (HashiCorp-managed cloud), both of which continue to receive development as the company focuses Boundary on "market-leading human and agentic privileged access." If a commercial license is not an option, the archived code base remains available in read-only mode and may be forked and self-maintained — HashiCorp notes the community can continue development independently, but advises weighing the license terms and any outstanding security issues first.
What this means for you
If you run the free, self-hosted Boundary Community Edition for zero-trust access to your infrastructure — as a replacement for bastion hosts and jump servers, or as a privileged-access (PAM) layer — it is now a deprecated product with no further HashiCorp development. The `hashicorp/boundary` GitHub repository has been archived effective immediately (9 October 2026) and is read-only: no new releases, no bug fixes, and no security patches will ship from HashiCorp. Existing deployments keep running, but HashiCorp explicitly warns you to review the license and any open bugs or security vulnerabilities before continuing to rely on it. This affects only the Community Edition — HCP Boundary and Boundary Enterprise are unaffected and are where all future work goes.
Where to go
HashiCorp directs users to its commercial editions: Boundary Enterprise (self-managed) or HCP Boundary (HashiCorp-managed cloud), both of which continue to receive development as the company focuses Boundary on "market-leading human and agentic privileged access." If a commercial license is not an option, the archived code base remains available in read-only mode and may be forked and self-maintained — HashiCorp notes the community can continue development independently, but advises weighing the license terms and any outstanding security issues first. Alternatives in the same space include Teleport and self-run bastion/SSH-CA setups.
- HCP Boundary — HashiCorp-managed cloud edition, actively developed
- Boundary Enterprise — self-managed commercial edition, actively developed
- Fork the archived open-source repository and self-maintain (read-only upstream)
- Teleport — third-party zero-trust access / bastion alternative
HashiCorp has deprecated Boundary Community Edition, the free, self-hosted edition of its zero-trust secure-access and privileged-access-management (PAM) tool. In an official announcement on HashiCorp Discuss dated 9 October 2026, the company said it is “shifting focus towards developing enterprise capabilities” and has archived the Boundary Community Edition GitHub repository effective immediately.
The deprecation applies only to the Community Edition. HashiCorp was explicit that it “does not reflect HCP Boundary, Boundary Enterprise, or any other HashiCorp products.”
What changes
- The
hashicorp/boundaryGitHub repository is archived as of 9 October 2026 and is read-only. The README has been updated to reflect this. - No further HashiCorp development on the Community Edition — no new releases, bug fixes, or security patches from the vendor.
- The code stays available in read-only mode. The community “will still be able to fork the code and continue development on their own.”
- HashiCorp’s own caution: “review the license file and take into consideration any bugs or open security vulnerabilities prior to continued use.”
Boundary Community Edition launched in 2020 (with a commercial launch at HashiConf in October 2022). HashiCorp says it is concentrating R&D on Boundary’s commercial editions to build “a market-leading human and agentic privileged access solution.”
What to do
- Already on a commercial edition? Nothing to do — HCP Boundary and Boundary Enterprise are unaffected and keep getting development.
- Running Community Edition in production? Plan a move to Boundary Enterprise (self-managed) or HCP Boundary (managed), or evaluate a third-party zero-trust access tool such as Teleport.
- Want to stay on the open source? You can fork the archived repository and self-maintain it — but you inherit all future maintenance, and HashiCorp specifically flags reviewing the license and any open security issues before relying on it further.
Entry changelog
- — last reviewed.
- — Entry created from HashiCorp's official deprecation announcement on HashiCorp Discuss (post by HashiCorp staff, 9 October 2026), surfaced via Layer-2 discovery (Hacker News). The forum JSON was fetched and read directly. The repository was archived effective immediately, so this is a past-dated (status: passed) deprecation; sunsetDate set to the 9 October 2026 announcement/archive date. No detect: fingerprint — the announcement names no package or container-image artifact, and Boundary CE is typically installed as a binary, so a fingerprint would be a guess (Constitution §3.2).
Put this countdown in your README
Building on HashiCorp? Drop this badge into a project’s README or docs — it shows the days left and
refreshes on its own every night from this page. 
[](https://lastcall.dev/entries/hashicorp-boundary-community-edition-deprecated)Spot an error or a changed date? Tell us and it’s corrected the same night.