HashiCorp Vault
Management of secrets, encryption keys and privileged access.
BUSL-1.1Source-available (not OSI)
Building on it: what may you do?
Short answers based on the licence, for the version in the catalog.
- B1 Change the code for internal use in your company Yes, with conditions Usually, for internal use. Check the terms.
- B2 Build your own product or service on top and offer it to customers as SaaS No Usually no for a service that competes with the vendor, without an agreement.
- B3 Make a closed-source derivative and sell or distribute it No No, not without an agreement with the vendor.
- B4 Use the project's name and trademark No No, not without permission. The licence covers the code, not the name or logo.
Keep in mind
- Contributing back to the project requires signing a Contributor License Agreement (CLA).
- Dual licensing: the vendor also sells a commercial licence if the terms above don't suit you.
This is guidance, not legal advice. Check with a lawyer before deciding.
The licence in brief
Business Source License 1.1 (BUSL-1.1)
Source-available, not OSI open source. The project's Additional Use Grant decides; a competing or hosted service is often forbidden. Becomes open on a Change Date.
This is guidance, not legal advice (inte juridisk rådgivning). Check with a lawyer before deciding.
Facts
- Licence
- BUSL-1.1
- Licence type
- Source-available (not OSI)
- Open core
- No
- GitHub stars
- 36.3k
- Latest activity
- Deployment
- Docker
- Login/SSO
- OIDC, LDAP
- API
- Unknown
- Multi-tenant
- Unknown
- EU vendor
- Unknown
- Source code
- github.com/hashicorp/vault
- Source
- GitHub API, fetched 2026-10-03
Licence analysis per use case
Sign in to see what the licence means for eight use cases – from internal self-hosting to offering the tool as a service.
Sign in