Elasticsearch
One Node.js Brotli bug and a compromised CA bundle force ten patches across the Elastic Stack.
A side-by-side editorial comparison of HashiCorp and PgBouncer — release velocity, themes, recent moves, and the top alternatives to consider.
HashiCorp is rebuilding Terraform and Vault around AI agents as governed users
Late October was one coordinated launch: Terraform Developer Portal entered public preview as a governed self-service layer inside HCP Terraform, and Vault Arc and Secure Hub entered public preview for machine and agentic workloads and fleet-wide Vault governance. Boundary 1.1 added an MCP server, and Vault 2.2 focused on usability across hybrid estates. In November IBM began offering Vault Enterprise as a dedicated managed service on IBM Cloud.
PgBouncer patches a SCRAM flaw that let a known user log in as an admin
PgBouncer's 1.26 line pairs features with a heavy security load. 1.26.0 tracks search_path and default_transaction_read_only by default, so one client's SET no longer leaks to others in transaction pooling, adds pool_idle_timeout and per-user query_wait_timeout, and removes the old online-restart takeover in favour of rolling restarts. It also fixed three CVEs. Three weeks later, 1.26.1 fixed three more, including one where a user with a password in auth_file could log in as any other SCRAM user, admins included.
Late October was one coordinated launch: Terraform Developer Portal entered public preview as a governed self-service layer inside HCP Terraform, and Vault Arc and Secure Hub entered public preview for machine and agentic workloads and fleet-wide Vault governance. Boundary 1.1 added an MCP server, and Vault 2.2 focused on usability across hybrid estates. In November IBM began offering Vault Enterprise as a dedicated managed service on IBM Cloud.
Nearly every release now names agents as a first-class consumer of infrastructure, next to human developers. The pattern is consistent: approved patterns in Terraform, scoped identity in Vault and Boundary, and audit in Secure Hub. IBM integration is the second thread, with Cloudability cost data in Terraform runs and IBM Cloud now hosting Vault.
Expect the three public previews (Developer Portal, Vault Arc, Secure Hub) to move toward general availability, and more IBM products wired into HCP Terraform and Vault.
PgBouncer's 1.26 line pairs features with a heavy security load. 1.26.0 tracks search_path and default_transaction_read_only by default, so one client's SET no longer leaks to others in transaction pooling, adds pool_idle_timeout and per-user query_wait_timeout, and removes the old online-restart takeover in favour of rolling restarts. It also fixed three CVEs. Three weeks later, 1.26.1 fixed three more, including one where a user with a password in auth_file could log in as any other SCRAM user, admins included.
Since 1.25.1 every release has carried CVE fixes in the authentication and packet-handling paths, and 1.26.1 found a second instance of a bug class fixed weeks earlier. The project is auditing its pre-auth surface in public, while 1.26.0 shows it still cleaning up long-standing pooling surprises.
More security point releases are likely while the auth and buffer code is under review; the entries give no sign of the next feature release.
Other DevOps products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either HashiCorp or PgBouncer.
One Node.js Brotli bug and a compromised CA bundle force ten patches across the Elastic Stack.
QuestDB keeps proving its market-data case with reproducible benchmarks between releases.
Grav's 1.7 line keeps taking small patches after its security backport burst.
Z-Wave JS v15.32.0 ships the findings of two full-codebase security reviews.
Sanity moves agent settings onto the MCP endpoint, so every connected agent behaves alike.
Scalingo is back to routine runtime updates after its October router incident.
See all HashiCorp alternatives → · See all PgBouncer alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. HashiCorp is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. HashiCorp is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other DevOps products to evaluate alongside.
Top HashiCorp alternatives in DevOps are ranked by recent ship velocity. Browse the "HashiCorp alternatives" section above for the current picks, or visit /alternatives/hashicorp for the full list with editorial commentary on each.
Top PgBouncer alternatives in DevOps are ranked by recent ship velocity. Browse the "PgBouncer alternatives" section above for the current picks, or visit /alternatives/pgbouncer for the full list with editorial commentary on each.