1

Today we are deprecating Boundary Community Edition and shifting our focus toward developing enterprise capabilities, effective immediately. 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 and does not reflect HCP Boundary, Boundary Enterprise, or any other HashiCorp products. With Boundary’s product maturation and its product market fit within the enterprise PAM space, our focus is now turning toward developing enterprise capabilities which would cater to large, complex environments at scale.

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.

It would’ve been nice to MPL this repo before archiving if the plan was for folks to fork it and continue their own development.

3

damn, and I had plans to set this up in my homelab nomad/consul/vault cluster and try it out…

5

I live in fear of this happening to nomad and vault

Thanks for the update and for all the work put into Boundary Community Edition. It’s sad to see the community edition deprecated, but I understand the focus on enterprise capabilities. Hopefully, the community can continue contributing through forks.

7

I feel like it would really require one managed fork that somebody (likely an organization, or at least preferably) manages it…but I guess we all could do it too just would be hard to stay organized