HashiCorp
HashiCorp provides infrastructure automation software tools for provisioning, securing, connecting, and running cloud infrastructure for teams.
About this data
Updated June 29, 2026
Overall Pulse Score
+9 over this period
A 0-100 index summarizing the tone of 301 relevant public mentions gathered from public online communities across 8 weeks in the selected period. It measures online sentiment, not a rating of the product's quality.
Weekly Sentiment Trend
Pulse Score by week over the selected period. Each point is one complete week of mentions.
This week in public discussion
Bugs and reliability problems dominated discussion of HashiCorp across the recent period, with complaints far outnumbering praise across 288 mentions. Commenters reported issues spanning multiple providers, including SSH provisioner slowdowns after an amazon-ebs update, Azure resource failures tied to 400 errors, and unexpected resource replacements in the Vault provider. Some discussion praised certain features and integrations, and several mentions highlighted a new AWS Lambda MicroVM-related release as a positive development.
Read the deeper analysisAI-generated summary of public online discussion during this period. It reflects the tone of that discussion, not facts about the product or our views.
Sentiment mix by week
How the tone of public discussion splits each week.
Most-discussed praise
Most-discussed complaints
Themes across the selected period, with mention counts.
How HashiCorp compares
Pulse Score over the selected period versus the top tracked competitors in Coding.
Where the mentions come from
Share of the 301 relevant public mentions in the selected period, by source.
Sample public mentions
Showing 5 of 301 analyzed public mentions in this period, with links to the original source. We do not reproduce full threads.
“amazon-ebs v1.8.1: SSH stdout relay ~50-70x slower than v1.8.0; verbose provisioners time out with "exit status: 123". #### Overview of the Issue After the amazon plugin auto-upgraded from **v1.8.0 → v1.8.1**, our amazon-ebs builds began failing with: The remote provisioner scrip...”
“azurerm_app_service_environment_v3: Read fails with 400/51019 when platform returns "not supported ... with kind ASEV3" for inboundNetworkDependenciesEndpoints. ### Is there an existing issue for this? - [x] I have searched the existing issues Community Note * Please vote on this...”
“Vault 2.0.0 Docker image fails to start: unable to set CAP_SETFCAP effective capability. **Describe the bug** After upgrading Docker image from 1.21.4 to 2.0.0, the container fails during startup with the following message: This happens because the container now runs as the vault...”
“azurerm_static_web_app - every update fails with 400 "The PrivateLinkServiceConnectionState field is required" once a private endpoint is attached. ### Is there an existing issue for this? - [X] I have searched the existing issues Community Note * Please vote on this issue by add...”
“[Bug]: version 5.10.0 changes to pki_secret_backend trigger resource replacement. ### Terraform Core Version 1.10.5 Terraform Vault Provider Version 5.10.0 Vault Server Version 1.16.2 Affected Resource(s) * vault_pki_secret_backend_root_cert * vault_pki_secret_backend_cert * vaul...”
1,459+ more analyzed mentions, full history, and theme breakdowns are part of Pro.
Get ProDeeper analysis
- Bug reports and reliability complaints overwhelmingly dominated discussion, outnumbering praise mentions by a substantial margin.
- Sentiment spiked briefly during a low-volume stretch in late May but fell back when discussion volume surged in early June and stayed subdued through late June.
- Opinion was divided on provider-specific integrations, with some commenters describing pipeline-blocking regressions while others appeared less affected by the same issues.
- Positive sentiment existed but remained a minority voice, concentrated around specific features and integrations rather than the product broadly.
| Praise theme | Mentions |
|---|---|
| Strong features | 24 |
| Good integrations | 21 |
| Feature requests | 9 |
| Security praise | 5 |
| New releases | 4 |
| Complaint theme | Mentions |
|---|---|
| Bugs | 185 |
| Reliability | 120 |
| Missing features | 66 |
| Feature requests | 46 |
| Lacking integrations | 9 |
Public discussion around HashiCorp over the four-week window was dominated by a heavy volume of bug reports and reliability complaints, which together dwarfed the praise signals by a wide margin. Commenters raised issues across multiple cloud provider integrations, with mentions pointing to regressions in specific plugin versions, unexpected resource replacement behavior, and state drift that went undetected during plan runs. The tone throughout was largely frustrated rather than hostile, suggesting users who rely on the tooling heavily and expect more stability than they perceived they were getting.
The score trajectory tells a telling story of a brief spike followed by a pull-back. Sentiment climbed noticeably around late May, reaching its highest point in the window, but volume at that moment was very low, so the lift likely reflected a small cluster of more favorable voices. When discussion volume surged sharply in early June, sentiment dropped back into the low-to-mid thirties and remained roughly flat through the final weeks. The pattern suggests the quieter periods leaned slightly positive while high-traffic weeks surfaced a proportionally larger share of complaints.
Praise did exist in the data. Feature-specific appreciation and integration highlights drew a modest but consistent thread of positive mentions, and a handful of commenters pointed to security-related strengths. New release activity generated some positive framing as well, though sample mentions suggested that at least one recent release introduced a regression that quickly became a complaint thread of its own.
Opinion divided most clearly around provider-specific behavior. Discussion suggested that some integrations, particularly on AWS and Azure resources, were seen as broken or brittle in ways that blocked pipelines and production workflows. Others in the same threads appeared to be working around issues without the same severity of impact, creating a split between users treating certain behaviors as critical blockers versus edge cases. Compatibility with adjacent tooling also surfaced as a point of tension, with some commenters noting gaps that others did not appear to encounter.
AI-generated summary of public online discussion during this period. It reflects the tone of that discussion, not facts about the product or our views.
Member perspectives
Individual opinions from Pro members, posted over time. These are personal member views, not aggregated sentiment data.
Overall Pulse Score
+9 over this period
A 0-100 index summarizing the tone of 301 relevant public mentions gathered from public online communities across 8 weeks in the selected period. It measures online sentiment, not a rating of the product's quality.
Data summary
Compare with another tool
HashiCorp
33
Trainual
88
Score-level preview from live weekly tracking.
Are you HashiCorp?
If you represent this product, you can share context about the data shown here. We read every submission.
Share feedbackAffiliate disclosure
Some links on this site may be affiliate links. If you click one and make a purchase, we may earn a commission at no extra cost to you. Learn more.
Compare with similar tools
Bubble
No-code platform that lets users design, build, and deploy full-stack web applications without writing code.
Free tier; paid plans available
View DetailsRevenueCat
A platform that manages in-app purchases, subscriptions, and revenue analytics for iOS and Android app developers.
Free tier; paid plans available
View Details