HashiCorp Licensing FAQ
The FAQs play an important role in providing interpretive guidance to our users. We view the guidance in these FAQs as binding, so users of our software should feel assured in relying on them as our official positions now and in the future.
Change history
Apr. 15, 2024
| Added examples to question 14. |
Apr. 12, 2024 | Added final MPLv2 release versions for specific products to question 7.
|
Feb. 26, 2024 | Added question 13.
|
Oct. 17, 2023
| Non-substantive updates to FAQ Nos. 8, 12, 14, and 26 to conform to the language in the October 16, 2023 clarifications to the BSL license.
|
Aug. 2023 | Added additional FAQ items in response to questions.
|
Aug. 10, 2023
| Posted original FAQ
|
Overview of the license change
What did HashiCorp announce today (Aug 10)?
Why is HashiCorp making this change?
What are the implications of this change for end users of HashiCorp’s open source products?
What are the implications of this change for integration partners of HashiCorp?
What are the implications of this change for commercial customers of HashiCorp?
Who is impacted by this change?
What products will be covered by BSL 1.1 in their next release?
What are the usage limitations for HashiCorp’s products under BSL?
How does this impact the licensing of Terraform providers?
Can I continue to use versions of the products that were provided under the original MPL 2.0 license?
Will HashiCorp backport security patches to previous releases under the MPL 2.0 license?
Defining competitive offerings
What is a “competitive offering” under the HashiCorp BSL license?
What is considered a "paid support arrangement"?
What does the term “embedded” mean under the HashiCorp BSL license?
I’m building (or have built) a product that embeds one or more HashiCorp products, and I’m concerned you may view it as competitive. How can I get clarity as to whether my product will violate the new BSL license?
I am the author of an open-source project that uses HashiCorp technology in a non-competitive way (e.g. uses Terraform but not in a production environment). If someone else uses my project to produce a competitive product or hosted service (e.g. starts using my project in their SaaS solution), am I at risk of being considered competitive and violating the BSL license? Do I need to track all users of my project and report suspected infringing use?
If I want to build a product that is competitive with HashiCorp, does that mean I’m now prevented from using any HashiCorp tools under the BSL license?
What if HashiCorp releases a new product or feature in the future that makes my project competitive?
The BSL license and open source
What is the Business Source License (BSL, or BUSL)?
Why did HashiCorp select the BSL license?
What’s the difference between the BSL and others such as AGPL, SSPL or the addition of Common Clause to agreements that HashiCorp could have chosen?
If I modify the source code of software licensed under the BSL, can I redistribute my modified version under another license?
Does HashiCorp still believe in open source?
How does HashiCorp now refer to the freely available versions of products that were formerly known as open source (or OSS)?
Can I mix BSL licensed code with code provided under a different license (i.e., Apache, MPL, etc.) in my project?
Internal use of HashiCorp products
Can I host the HashiCorp products as a service internal to my organization?
Consulting and professional services
Can I continue to provide professional services around HashiCorp products?
I’m a consultant who helps my customers run their infrastructure using HashiCorp tooling. Does HashiCorp consider me a competitor?
More information
Where can I learn more about this announcement or ask further questions?