Statement descriptor reference

What is the HASHICORP* HCP charge?

Evidence review pending
08/01 HASHICORP* HCP $85.00

Illustrative statement row. The date and amount are examples, not proof of this transaction or a standard price.

The short answer

The registry records HashiCorp Cloud Platform Managed Cluster Hosting as a possible interpretation of HASHICORP* HCP. This descriptor-to-company association has not passed claim-level evidence review. Compare the exact line, amount and posted status with your own receipt or account activity; the name alone cannot confirm the merchant or whether you authorized the payment.

What do the parts of HASHICORP* HCP mean?

HASHICORP * HCP
Before the asterisk, "HASHICORP" usually names the platform or parent company. After it, "HCP" usually names the product, store or order. How descriptors work →

The notes below are unreviewed registry explanations, not confirmation of merchant identity, authorization or current policy. Claim-level source review is pending for this entry.

Evidence review pending pending confidence 2 listed sources How we verify

Why it shows up like this

Unreviewed registry note: A line item listed as HASHICORP* HCP indicates metered infrastructure charges from HashiCorp, Inc. for services hosted on the HashiCorp Cloud Platform. This billing entry covers HashiCorp Cloud Platform Managed Cluster Hosting, such as fully managed clusters for HCP Vault secret management or HCP Consul service mesh. Like public cloud environments managed through AWS or repositories on GitHub, HCP allows software teams to deploy dedicated automation tools without maintaining the underlying virtual machines themselves.

Unreviewed registry note: This charge appears because an organization administrator or software engineer configured active cloud resources linked to your payment card. HashiCorp calculates billing on an hourly consumption model determined by cluster tier and active running time. Invoices generate at the close of each billing cycle, typically charging your card on the first calendar day of the month. Even if a development cluster sits idle, HashiCorp continues billing hourly until the resource is explicitly terminated through the cloud portal.

Don’t recognize it? Common scenarios

Unreviewed registry note: Engineering accounts often accrue cloud charges when test clusters or evaluation instances are left active after initial deployment.

  • Unreviewed registry note: An engineering team provisioned a managed HCP Vault cluster on AWS or Azure for application secret rotation.
  • Unreviewed registry note: An ongoing development cluster remained running continuously throughout the billing month.
  • Unreviewed registry note: HCP Packer or HCP Waypoint usage exceeded free tier starter thresholds.

Frequently Asked Questions

How does HashiCorp bill for HCP clusters?

Unreviewed registry note: HCP clusters are billed on an hourly consumption model based on tier (Development, Standard, Plus) and running duration. Terminating the cluster halts billing immediately.

Independent reference — not affiliated with HashiCorp, Inc.. Billing names and policies change; verify with the merchant or your bank before acting.

Sources and evidence

Sources may support different parts of this page. A company homepage does not establish a statement descriptor, refund policy or contact detail. Check the claim notes and your own receipt before acting.

Evidence review pending · pending · About UnknownCharges