OpenBao the fork of HashiCorp Vault

[sakib60]

In the DevOps field, the need to efficiently manage sensitive information such as passwords, access tokens, and certificates has become more important than ever. It is in this context that the OpenBao project emerges as an open source fork to HashiCorp Vault, the reference tool in secrets management .

History and Origins
OpenBao , like OpenTOFU , was born following HashiCorp's decision to adopt india car owner data the Business Source License ↗ (BSL) for several of its products, including Terraform, Vault , Vagrant… This decision, motivated by the desire to limit competition, particularly from cloud service providers, has raised concerns within the open source community. Indeed, the BSL, although it allows the use, modification and distribution of the code, imposes significant restrictions, particularly in terms of commercialization of the software.

In response to these restrictions, the Linux Foundation , supported by IBM , took the initiative to fork Vault , thus giving birth to OpenBao . This project is intended as a direct response to the open source community's concerns about BSL. By opting for the MPLv2 license, OpenBao is committed to maintaining a high level of freedom and openness, allowing the community to contribute, modify, and distribute the software without the limitations imposed by BSL.

OpenBao was launched from the latest open source version of Vault, 1.14, which was under the stewardship of HashiCorp prior to the adoption of BSL. This choice symbolizes not only technical continuity with previous versions of Vault , but also a commitment to open source principles and a desire to preserve accessibility and flexibility for users and contributors.