←back to thread

IBM to acquire Confluent

(www.confluent.io)
443 points abd12 | 10 comments | 08 Dec 25 13:43 UTC | HN request time: 0.001s | source | bottom
Show context
hadrien01 ◴[08 Dec 25 14:48 UTC] No.46192816[source]▶
Genuine question: how did the IBM acquisitions of Red Hat and HashiCorp turn out?

For Red Hat, there's no longer an official "public" distribution of RHEL, but apart from that they seemingly have been left alone and able to continue to develop their own products. But that's only my POV as a user of OSS Red Hat products at home and of RHEL and OpenShift at work.

replies(8): >>46192864 #>>46192912 #>>46193004 #>>46193010 #>>46193433 #>>46198058 #>>46201336 #>>46202389 #
1. rmccue ◴[08 Dec 25 15:03 UTC] No.46193010[source]▶
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).

replies(3): >>46193245 #>>46193416 #>>46193841 #
2. dangus ◴[08 Dec 25 15:22 UTC] No.46193245[source]▶
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)
replies(1): >>46201421 #
3. mitchellh ◴[08 Dec 25 15:33 UTC] No.46193416[source]▶
> (I think as they were gearing up to be a more attractive target for an exit).

A common conspiracy theory, but not true.

replies(3): >>46194984 #>>46200280 #>>46202156 #
4. jen20 ◴[08 Dec 25 16:00 UTC] No.46193841[source]▶
> were gearing up to be a more attractive target for an exit

An "exit" from the public market?

replies(1): >>46195063 #
5. sethops1 ◴[08 Dec 25 17:24 UTC] No.46194984[source]▶
Source: the guy the company was named after
replies(1): >>46228692 #
6. everfrustrated ◴[08 Dec 25 17:29 UTC] No.46195063[source]▶
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.

7. ruraljuror ◴[09 Dec 25 01:36 UTC] No.46200280[source]▶
Yeah how would you know?

j/k Love ghostty!

8. aryonoco ◴[09 Dec 25 05:02 UTC] No.46201421[source]▶
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.

9. nextaccountic ◴[09 Dec 25 07:17 UTC] No.46202156[source]▶
Then why move away from open source?
10. maxloh ◴[11 Dec 25 07:39 UTC] No.46228692{3}[source]▶
Where did you read that?