HashiCorp Exploring Potential Sale

License change, founder exit, and sale context

• Commenters see the sale exploration, prior license change, and a founder’s departure as part of the same arc: shifting from community-first OSS to maximizing enterprise value.
• Some think the sale is timed “before it turns into a fire sale” as users migrate to open forks.

Financial health and sustainability

• One view: financials “don’t look terrible” and the sale is mainly for holders to cash out.
• Counterview: revenue growth slowed sharply after the license change; operating losses and returns on capital are deeply negative, making the business “value destroying” without major restructuring.
• Several argue the huge sales & marketing spend suggests the products might fare better inside a larger company that can share those functions.

Licensing backlash and forks (Terraform / OpenTofu)

• Many teams are sticking to pre-license-change Terraform versions or migrating to OpenTofu.
• OpenTofu maintainers report strong uptake and contributions; some users are cautious, worried about provider compatibility and migration friction.
• Guidance in-thread: usually just replace terraform with tofu and keep using HashiCorp providers via the new registry; a migration guide exists.

Vault, OpenBao, and storage trade-offs

• Users anticipate being “forced to migrate off Vault” and mention OpenBao as the main fork.
• OpenBao maintainers explain why most storage backends were removed (maintainability, ability to add features like pagination/transactions, limited maintainer capacity).
• Some operators are unhappy that only Raft (plus in-memory/file) is supported, arguing it makes OpenBao “a different product” and hinders drop‑in migration.
• Others counter that upstream already effectively only supports Raft and that storage migration is a one‑time operator burden; alpha and GA timelines for OpenBao are still emerging.

Pricing, business model, and alternatives

• Multiple accounts describe HashiCorp’s enterprise pricing, especially for Vault, as “exorbitant” or effectively “we don’t want your business.”
• Former sales-side experience in the thread confirms Vault’s identity-based pricing model was a major blocker, especially for smaller or less-centralized orgs.
• Some see this as evidence that “open source + generous free tier” is hard to monetize post‑ZIRP. Ideas floated: keep core SDK OSS, close-source plugins, and charge per resource.
• Alternatives mentioned include Crossplane (with Terraform-based providers), Pulumi, cloud-native secrets managers, and various orchestration stacks; Nomad is seen as lacking a clear OSS successor.

Potential buyers and user impact

• Speculation centers on big incumbents that “missed the cloud wars” or do multi‑cloud management: IBM, Cisco, Broadcom, possibly Microsoft or a cloud provider.
• Fears: acquisition by Oracle/Broadcom-type buyers leading to lock‑in, price hikes, or product stagnation.
• Hoped-for outcomes: a buyer like Microsoft or Cloudflare that keeps tools open and stabilizes the roadmap.
• For Terraform specifically, many believe users are relatively safe due to OpenTofu and other drop‑in alternatives; Vault and other products are seen as higher risk.