Pricing Definitions

This topic provides definitions for HCP usage-based pricing that applies to the trial, PAYG, and Flex Multiyear billing models.

Usage-Based Pricing

Usage-based pricing applies to the trial, PAYG, and Flex Multiyear billing models.

On your HCP organization's billing model, every available HCP service has one or more billing metrics. These billing metrics are metered by incremental count or by time, with usage and costs accrued from the start of the month updated hourly in the billing page with up to a 30 minute delay. For example, by 10:30 am, the usage summary and balance will reflect charges for hours 9 am to 10 am.

The usage summary values are estimates until the statement is finalized at the end of the month. This allows for HCP to backfill any missing data.

Billable Metrics

Each HCP service has:

• One or more billable metrics
• One or more user-selected service attribes that affect the unit price per billable metric, such as edition (Standard, Plus, Premium) or cluster size

Each billable metric has:

• A name and definition
• A unit price per rating period

The unit price is exclusive of taxes unless otherwise specified. The rating period for the unit price is either:

• Hourly: Each unit during the rated hour accrues the stated hourly cost.
• Monthly: Each incremental unit during the rated hour accrues the stated monthly cost. The unit count resets to zero at the start of each month.

The sections below provide the billable metric definitions for HCP services.

HCP Terraform

Definitions

• HCP Terraform Organization (HCP Terraform Org): A unique, top-level entity of HCP Terraform that contains resources, users, and administrative policies. It serves as an access control boundary that isolates resources for security. One or multiple HCP Terraform Organization(s) can be associated with a single HCP Org and the associated HCP Org serves as a billing boundary for costs.
• HCP organization (HCP Org): A unique, top-level entity that contains resources, users, and administrative policies that serves as an access control boundary that isolates resources for security and a billing boundary for costs.
• Resource: A resource block in a HCP Terraform configuration and declares one or more infrastructure objects. Each infrastructure object, including but not limited to “Local Only” Resources, counts as a single Resource.
• Resource Under Management (RUM) or Managed Resource: A Resource in a HCP Terraform managed state file starting from the first time a Terraform plan or Terraform apply run is performed on the Resource, and/or the resource is provisioned, and where mode = managed in the state file. "Null Resources" are excluded from the Managed Resource.
• Null Resources: A specific type of Resource defined as null_resource or terraform_data resource in a HCP Terraform managed state file that are part of the standard resources under management lifecycle, but intentionally take no action.
• Hourly Peak Managed Resources: The sum of the maximum number of concurrent "Managed Resources" of each HCP Terraform Org that exist in an hourly billing period.

Pricing

Usage-based billing charges for HCP Terraform usage of Resources Under Management (RUM) based on the total number of Hourly Peak Managed Resources aggregated across all HCP Terraform Orgs linked to a single HCP org, within a billing hour. The rate of each RUM is determined by the product edition.

HCP Packer

Definitions

• HCP Packer Image Bucket: A unique HCP Packer configuration file that is being tracked by the HCP Packer Registry. The tracked configuration file can define one or multiple versions of an image.
• HCP Packer Registry: Tracks each artifact's metadata from configuration files. Such metadata is available in the user interface and via API, which makes the metadata accessible outside of the HCP Packer Registry. HCP Packer can track data from images across clouds but does not host any image templates or image artifacts themselves.
• HCP Packer User: Any individual with access to a customer’s HCP Packer Registry.
• HCP Packer Request: Any time a Customer queries the HCP Packer get channel API to fetch the assigned iteration, including but not limited to using the Terraform data source.
  • All other requests, including requests generated by the HCP Packer user interface, shall not apply for billing purposes.

Pricing

Usage-based billing charges for HCP Packer usage of:

• HCP Packer Image Buckets: An HCP Packer Image Bucket is charged on a per-hour basis, rounded up to the nearest hour, from the time its metadata is stored in the registry until the metadata is deleted. The hourly rate of each HCP Packer Image Bucket is determined by the product editions (i.e., Standard, Plus) and the total number of HCP Packer Image Buckets within a billing hour.
• HCP Packer Image Requests: An HCP Packer Request is charged per HCP Packer Request made. The rate of each HCP Packer Request is determined by the product edition.

HCP Vault Dedicated

Flex Multiyear Exclusions

HCP Vault Dedicated's Starter edition is not available on Flex Multiyear.

Definitions

• HCP Vault Dedicated Cluster(s): Agrouping of fully managed virtual machines used to run HCP Vault Dedicated.
  • HCP Vault Dedicated Clusters are charged on a per-hour basis, from the time a cluster is created until it is deleted. Partial hours are charged by the minute. The hourly rate is based on the product edition (i.e., Starter, Development, Standard, Plus) and the "Cluster Size" (i.e., Small, Medium, Large).
• HCP Vault Dedicated Client(s): Unique applications, services, and/or users that consume HCP Vault Dedicated.
  • For the purposes of billing and consumption, only unique and active HCP Vault Dedicated Clients during each monthly billing period are counted towards totals. Within a monthly billing period, each HCP Vault Dedicated Client is counted once, no matter how many times it has been active. Once an HCP Vault Dedicated Client has authenticated to a cluster, those HCP Vault Dedicated Clients have unlimited access to that cluster for the remainder of the month. A Secret with a configured Secret Sync Destination is counted as a unique and active Client. A Secret Sync Destination represents the external secrets management location where a Secret may be synchronized.
  • For the purposes of billing and consumption, a single HCP Vault Dedicated Client which authenticates to multiple HCP Vault Dedicated Clusters (excluding HCP Vault Dedicated Development and Starter edition Clusters) will be counted as multiple Clients.

Pricing

Usage-based billing charges for HCP Vault Dedicated usage of:

• HCP Vault Dedicated Clusters: Charged on a per-hour basis, from the time a cluster is created until it is deleted. Partial hours are charged by the minute. The HCP Vault Dedicated Cluster hourly rate is based on the product edition and the cluster size (i.e., Extra Small, Small, Medium, Large).
• HCP Vault Dedicated Clients: Charged when a unique HCP Vault Dedicated Client becomes active during the billing month. HCP Vault Dedicated Development edition allows a max 25 HCP Vault Dedicated Clients per month and is eligible for Silver Support but excluded from Sev-1.

HCP Vault Secrets

Definitions

• Secrets: Sensitive data and information for which access is controlled and managed by Customer's deployment of HashiCorp Products. Secrets may include, but are not limited to: tokens, API keys, passwords, encryption keys, or any type of credential. Secrets are unique name and value pairs enabling cloud native applications to connect with databases, SaaS services, and other third party systems.
• API Call(s): An action aligned to APIs that enable fetching static, auto-rotated or dynamic secret values (individual or bulk) through the various interfaces such as User Interface (UI), Command-Line-Interface (CLI) or directly with the API itself.

Pricing

Usage-based billing charges for HCP Vault Secrets usage of:

• Secrets: Each Secret is charged on a per-hour basis, from the time a Secret is created until it is destroyed. The hourly rate is based on the total number of Secrets within each edition, within a single HCP org, within a billing hour. Each partial hour is billed as a full hour.
• API Call(s): An HCP Vault Secrets API Call is charged per API Request made. The rate of each API Call is determined by the product edition.

HCP Boundary

Definitions

• HCP Boundary User: Any human or machine identity taking an authenticated action to HCP Boundary. Service or non-human accounts cannot be used to artificially reduce HCP Boundary Users.

Pricing

Usage-based billing charges for HCP Boundary usage of HCP Boundary Users. An HCP Boundary User is counted once for each month in which the User takes an authenticated action to HCP Boundary. The monthly rate of each HCP Boundary User is determined by the product edition.

HCP Vault Radar

Definitions

• Active Contributors: An HCP Vault Radar Monthly Active Contributor is a human or machine identity that contributed to a scanned Data Source within a measured month. HCP Vault Radar Monthly Active Contributor will be measured by counting the user contributions per Data Source. Service or non-human accounts cannot be used to artificially reduce HCP Vault Radar Monthly Active Contributors.
• Data Source: The application, database, file, storage location, or resources at a Host or Server level that will be scanned for secrets discovery by any variant of HCP Vault Radar.
• Resource Block: Up to 10,000 repositories, databases or component data locations that make up a data source.

Pricing

Usage-based billing charges for HCP Vault Radar usage of Active Contributors. Available only on Flex Multiyear.

HCP Consul Dedicated

Flex Multiyear Exclusions

HCP Consul Dedicated is not available on Flex Multiyear.

Definitions

• Consul Agent: The long running daemon on every member of the Consul Cluster and such Agent is able to run in either client or server mode.
• Consul Client: An agent that typically interfaces with the Consul Server and requires minimal infrastructure resources. Clients are hosted in the Customer's environment.
• Consul Cluster: Multiple Consul Servers that form a control group that has a single Consul Server Leader as well as a pool of Consul Clients that host and run a user's workloads.
• Consul Server Leader: A Consul Server within a Consul Cluster which is responsible for ingesting new log entries, replicating to other Consul Servers in the same Consul Cluster, and managing when an entry is considered committed. Only one Consul Server can act as the Consul Server Leader in a single Consul Cluster.
• Consul Server: A Consul Agent with an expanded set of technical responsibilities such as participating in a Raft quorum, maintaining cluster state, responding to RFC queries, exchanging WAN gossip with other Consul Clusters, and forwarding queries to Consul Server Leader or remote Consul Clusters. Consul Server is hosted in HashiCorp's environment.
• Consul Service: A logical representation of an application or microservice that is registered in Consul.
• Consul Service Instances: One or more running versions of a given Consul Service, each tracked as a distinct provider of the Consul Service by Consul's service registry.

Pricing

Usage-based billing charges for HCP Consul Dedicated usage of:

• Consul Clusters: Charged on a per-hour basis, from the time it is created until the time it is deleted. Partial hours are charged by the minute. The hourly rate is based on the product edition (i.e., Development, Standard, Plus & Premium), "Cluster Size" (i.e., Small, Medium, Large), cloud provider, and cloud region.
• Consul Service Instances: Charged by the minute. The minutely rate is based on the total number of "Service Instances" aggregated across all Consul Clusters, within an HCP Org, within a billing minute. For the purposes of billing and consumption, the Service Instance(s) which are registered with HCP Consul Dedicated Development edition Clusters are excluded from the aggregation.