3 ms·

We moved off HashiCorp's Terraform Cloud when they tried to hike the price 100x on us, although that was technically pre-acquisition I think (it was their move

by rmccue 10mo ago

We moved off HashiCorp's Terraform Cloud when they tried to hike the price 100x on us, although that was technically pre-acquisition I think (it was their move to resource-based pricing). In talking with our account manager, they basically said they only really cared about enterprise accounts, and that migrating away would probably make sense for us. HashiCorp also changed their licenses to non-open-source licenses, but again I think this was technically pre-acquisition (I think as they were gearing up to be a more attractive target for an exit).

dangus 10mo ago
In addition to this, I’ve noticed that OpenTofu is gaining much more interesting features and are actually acting upon long-requested functionality that HashiCorp has refused to implement (example: provider for_each in 1.9.0)
- aryonoco 10mo ago
  Yeah I just implemented a new stack and noticed OpenTofu now supports client side encryption for the state files in with keys stored in Azure KeyVault (in the latest 1.11 release). AWS and GCP had been supported for a while. Client side state encryption was one of the things which HashiCorp always gatekeeped for HashiCorp Cloud and never implemented in the Open Souce / Sourece Available versions.
mitchellh 10mo ago
> (I think as they were gearing up to be a more attractive target for an exit). A common conspiracy theory, but not true.
- sethops1 10mo ago
  Source: the guy the company was named after
  - maxloh 10mo ago
    Where did you read that?
- ruraljuror 10mo ago
  Yeah how would you know? j/k Love ghostty!
- nextaccountic 10mo ago
  Then why move away from open source?
jen20 10mo ago
> were gearing up to be a more attractive target for an exit An "exit" from the public market?
- everfrustrated 10mo ago
  Yes. They were burning the cash they raised from IPO as weren't profitable and no real path to profitability. Needed to find a buyer to take private as the other option - raise debt or print shares - wasn't going to happen as the share price had massively tanked and wasn't going to go up any time soon. Hopefully mitchellh will write a book about Hashicorp some time. Would be fascinating to read the inside take.

by rmccue 10mo ago

dangus 10mo ago

In addition to this, I’ve noticed that OpenTofu is gaining much more interesting features and are actually acting upon long-requested functionality that HashiCorp has refused to implement (example: provider for_each in 1.9.0)

aryonoco 10mo ago
Yeah I just implemented a new stack and noticed OpenTofu now supports client side encryption for the state files in with keys stored in Azure KeyVault (in the latest 1.11 release). AWS and GCP had been supported for a while. Client side state encryption was one of the things which HashiCorp always gatekeeped for HashiCorp Cloud and never implemented in the Open Souce / Sourece Available versions.

mitchellh 10mo ago

> (I think as they were gearing up to be a more attractive target for an exit). A common conspiracy theory, but not true.

sethops1 10mo ago
Source: the guy the company was named after
- maxloh 10mo ago
  Where did you read that?
ruraljuror 10mo ago
Yeah how would you know? j/k Love ghostty!
nextaccountic 10mo ago
Then why move away from open source?

jen20 10mo ago

> were gearing up to be a more attractive target for an exit An "exit" from the public market?

everfrustrated 10mo ago
Yes. They were burning the cash they raised from IPO as weren't profitable and no real path to profitability. Needed to find a buyer to take private as the other option - raise debt or print shares - wasn't going to happen as the share price had massively tanked and wasn't going to go up any time soon. Hopefully mitchellh will write a book about Hashicorp some time. Would be fascinating to read the inside take.