We regretfully announce that we are deprecating Boundary Community Edition and have shifted our focus towards developing enterprise capabilities. We are sincerely grateful to everyone who has used Boundary Community Edition, shared feedback, opened issues, participated in discussions, and contributed to the project over the years. Your involvement has helped shape Boundary and informed how the product has evolved. This deprecation is only for Boundary Community Edition. It does not reflect HCP Boundary, Boundary Enterprise, or any other HashiCorp products.
Background
Boundary Community Edition was first introduced in 2020 with a subsequent commercial launch in October of 2022 at HashiConf. It was initially introduced as a zero-trust based secure access tool to replace home grown access tools, bastion hosts and jump servers but it quickly matured into a PAM solution, allowing large enterprise organizations to meet their governance and compliance needs.
With Boundary’s product maturation and its eventual product market fit within the enterprise PAM space, our focus turned towards developing enterprise capabilities which would cater to large, complex environments at scale.
This led us to making the unfortunate decision to completely deprecate this community edition of Boundary and instead focus all our R&D efforts towards Boundary’s commercial editions (Enterprise and HCP) in order to turn it into a market leading human and agentic privileged access solution.
Details
-
The Boundary Community Edition Github repository has been archived effective immediately. The README file has been updated to reflect this.
-
The code base will be available in read-only mode and the community will still be able to fork the code and continue development on their own.
-
Please review the license file and take into consideration any bugs or open security vulnerabilities prior to continued use of the product in the future.