IBM completes acquisition of HashiCorp

Original Article ↗ Hacker News Discussion ↗

HashiCorp’s Trajectory, IPO, and Culture Shift

  • Many retail investors report heavy losses: IPO around $80, sale to IBM around $35, with insiders and pre‑IPO holders seen as the main winners.
  • Employees describe paying taxes on high IPO valuations only to see prices fall, with capital-loss deductions offering limited consolation.
  • Several threads describe a pivot from “practitioner‑first” to “enterprise‑first” after IPO, layoffs focused on non‑enterprise features, and a decline in the earlier engineering‑driven culture.
  • HashiCorp is widely perceived as never having achieved sustainable profitability; some argue layoffs were therefore not “arbitrary” but inevitable under the growth‑without‑profit model.

Pricing, RUM Model, and Customers

  • The Terraform Cloud “Resources Under Management” (RUM) model is heavily criticized as opaque, expensive, and incentive‑misaligned (discouraging clean separation of projects and accounts).
  • Some defend RUM as better aligned to infrastructure scale than per‑run or per‑workspace pricing and kinder to fast‑changing early‑stage setups.
  • Debate over “filtering out price‑sensitive customers”: one camp says chasing only high‑paying enterprises is rational; another argues huge, neglected price‑sensitive segments can be profitable too.
  • Several teams report either refusing to evaluate Pulumi or abandoning HashiCorp cloud offerings entirely over RUM quotes in the high six or seven figures.

Product Quality, Design, and Operational Risk

  • Terraform Cloud is called “absurdly simple” to re‑implement, with many teams preferring self‑hosted OSS automation (Atlantis, Terrateam).
  • Terraform itself draws mixed reviews: powerful but “hacky,” poor debuggability, sharp edges around destructive changes, and complex provider interactions (especially with Kubernetes).
  • Long subthread on whether accidental resource deletion is a design flaw vs an “operational maturity” issue; suggestions include stronger defaults, policy‑as‑code, and cloud‑side deletion protection.
  • Vault and Nomad inspire both strong praise and strong criticism:
    • Some love Nomad as a simpler Kubernetes alternative, especially on bare metal; others report large clusters (tens of thousands of nodes) as unreliable and hard to operate.
    • Vault is seen by some as heavyweight and over‑engineered compared to cloud key‑management services; others value its portability across environments.

IBM Acquisition Reactions and Red Hat Precedent

  • Many view IBM as “where good companies go to die,” citing Lotus, Rational, and previous startup acquisitions that were eventually gutted or enshittified.
  • Counterexamples center on Red Hat: multiple Red Hat engineers say day‑to‑day engineering is largely unchanged years after acquisition, with separate tooling, culture, and promotions intact, though sales and some product lines did see more IBM influence and layoffs.
  • Some ex‑Red Hat and ex‑IBM voices describe compensation erosion, culture drift, and eventual “bluewashing”; others report promotions, global travel, and more reasonable workloads under IBM.
  • HashiCorp insiders express mixed emotions: nostalgia for the small‑company days, concern about full integration into “the IBM mothership,” and cautious hope for more resources and reach.

Open Source, Forks, and Alternatives

  • Terraform’s shift away from an OSS license is repeatedly condemned and linked to HashiCorp’s decline; OpenTofu is widely recommended as the community fork, with relatively painless migration reported.
  • Vendors like Spacelift are advertising migration kits from Terraform Cloud/Enterprise to OpenTofu‑based platforms.
  • Alternatives mentioned: Pulumi, Crossplane (though seen as more complex), managed Kubernetes/ECS, and cloud‑native secrets managers. For Vault, OpenBao is noted but seen as currently low‑momentum.

AI / Analyst Hype and IBM Strategy

  • IBM’s claim that generative AI will create “1 billion cloud‑native applications by 2028” is widely mocked as analyst‑driven hype.
  • IDC‑style reports at $2,500+ per PDF are derided as “management consultant fodder,” yet others note they remain influential for executives and enterprise sales decks.

Practical Impact for Practitioners

  • Terraform, Vault, Consul, Nomad, Vagrant, and Packer are expected to keep working in the near term; the main concern is longer‑term stewardship, pricing, and product direction under IBM.
  • Many commenters see the acquisition as the final push to:
    • Migrate Terraform code and workflows to OpenTofu and independent clouds,
    • Re‑evaluate Nomad vs Kubernetes or ECS,
    • Prefer cloud‑native or OSS alternatives over IBM‑controlled offerings.
  • Overall sentiment: sadness at “end of an era,” skepticism about IBM’s product track record, and a belief that community forks and competitors will increasingly carry the HashiCorp ideas forward.