HashiCorp Boundary is more than a secure access platform. Its licensing model decides what you can do, how you deploy, and what it costs. Understanding the Boundary licensing model is critical before you commit.
Boundary is offered under HashiCorp’s Business Source License (BSL). This license allows free use for non‑production, evaluation, and certain internal purposes. Once your usage meets the “production” threshold set in the license, you must switch to a commercial agreement. That agreement unlocks enterprise features, support, and compliance guarantees.
BSL is source‑available, not open source. You can read, modify, and build from the code, but redistribution is limited and commercial use triggers licensing fees. The goal is clear: give teams a path from testing to production without barriers, then monetize the features needed at scale.
Key parts of the Boundary licensing model:
- BSL Core Access – All core functionality for evaluation, development, and non‑commercial internal tools. Free under the BSL.
- Commercial License – Required for production workloads, customer‑facing services, or revenue‑generating uses. Includes enterprise modules, premium support, and governance tools.
- License Change Date – HashiCorp sets a future date when the BSL‑licensed version may convert to Mozilla Public License v2.0 (MPL 2.0), giving eventual open source rights to that version.
- Scope of Use – The license defines “use” in precise terms. Running for personal testing? Fine. Running as part of a product sold to customers? Commercial license required.
For teams evaluating Boundary, the model means you can start without paperwork, but you must track when your use crosses into production. The upgrade path is straightforward but must be budgeted.
HashiCorp enforces this model to align with its broader portfolio now under the BSL, including Vault, Nomad, and Consul. Legal compliance and clear auditing are essential to avoid disruption.
If your security and access workflows need speed, automation, and full enterprise capability, factor the Boundary licensing rules into your rollout plan.
Test Boundary’s capabilities and see how licensing fits your deployment. Try it live in minutes at hoop.dev.