HashiCorp archives Boundary Community Edition, no new releases planned
The Boundary Community Edition (CE) repository on GitHub, under the HashiCorp organisation, now carries a notice that CE is no longer under active development and that the repository has been archived as of October 8, 2026.
The notice says future Boundary development will focus on HCP Boundary and Boundary Enterprise, where the company says it can provide enterprise grade human and agentic access capabilities.
The repository is now read-only. It no longer accepts new issues, pull requests or community contributions. Existing source code and previously released binaries remain available for reference and for existing self-managed use.
On the maintenance side, the notice is blunt: no new Boundary CE releases, maintenance updates, bug fixes or security patches are currently planned.
The closing paragraph speaks to current users. Teams that keep using Boundary CE should evaluate whether it meets their operational, security and compliance requirements. For supported capabilities, including production-scale governance, compliance, session recording, enterprise support and future Boundary development, the notice asks readers to evaluate HCP Boundary or Boundary Enterprise.
Key facts
- The Boundary Community Edition repository was archived as of October 8, 2026 and is no longer under active development.
- The repository is read-only: no new issues, pull requests or community contributions are accepted.
- No new CE releases, maintenance updates, bug fixes or security patches are currently planned.
- Existing source code and previously released binaries stay available for reference and existing self-managed use.
- Future Boundary development will focus on HCP Boundary and Boundary Enterprise.
Why it matters
Boundary is an access tool, and the open source edition has now stopped moving. The notice puts the whole future of the product into HCP Boundary and Boundary Enterprise, and frames those offerings around enterprise grade human and agentic access. For anyone who treated the free edition as a long-term foundation, the roadmap is now entirely on the commercial side.
Who it affects
Teams that run Boundary CE in their own environments are the most exposed, since they will not get new releases, fixes or security patches. Anyone who wanted to file issues or send pull requests can no longer do so. Teams that need production-scale governance, compliance, session recording or enterprise support are the ones the notice points toward HCP Boundary or Boundary Enterprise.
How to use it
Nothing changes on the technical side for an existing deployment: the source code and previously released binaries remain available for reference and existing self-managed use. The notice asks teams that continue with CE to evaluate whether it meets their operational, security and compliance requirements. Those who need supported capabilities are directed to evaluate HCP Boundary or Boundary Enterprise.
How solid is it
The statement comes from the repository's own archive notice, dated October 8, 2026, so it is a primary source. The notice text does not name HashiCorp; the owner is known only from the story title and URL. The notice gives no reason for ending Community Edition development beyond the stated focus on HCP Boundary and Boundary Enterprise.
Risks and caveats
The main risk is security: no security patches are currently planned for CE, so teams staying on it carry that exposure themselves. The wording is "currently planned", not a permanent ban. The notice mentions no fork, community maintainer or successor project, and describes no migration path or tooling from CE to HCP Boundary or Boundary Enterprise. It gives no end-of-life date or support window for previously released CE binaries, and mentions no pricing or licensing.
“No new Boundary CE releases, maintenance updates, bug fixes, or security patches are currently planned.”
— Boundary repository notice