A new platform for documentation and tutorials is launching soon.
We are migrating HCP documentation into HashiCorp Developer, our new developer experience.
»HashiCorp Flex Billing
»What is HashiCorp Flex?
HashiCorp FlexTM is a pricing program that allows customers to commit to a specific amount of spend upfront and draw down that committed balance through consumption of cloud services on the HashiCorp Cloud Platform. The program gives customers access to tiered usage pricing, deep discount options, and the flexibility to use the commitment across the HashiCorp Cloud Platform, including Terraform Cloud Business Tier, HCP Vault, HCP Consul, HCP Packer, and Cloud Support.
The support level specified for each product in your contract determined the SLAs. Services with Development Edition defaults to Bronze level support.
For additional information on HashiCorp Flex, contact Sales.
»HashiCorp Flex Metric Definitions
HashiCorp Flex customers can access the complete Flex consumption pricing table on the HCP portal billing page. Below is a summary of the pricing metrics for eligible cloud services included in Flex. Some of these metrics are billed slightly differently from HCP pay-as-you-go pricing.
| Eligible Cloud Service | Pricing Metric | Billing Unit (Frequency) | Metric Definition |
|---|---|---|---|
| Terraform Cloud Business Tier | Apply | Rate Per Apply (Monthly) | An "Apply" means a completed TFCB Run where the apply phase successfully completes. |
| Admin User | Hourly Rate per Admin User | An "Admin User" is a user with adminstrative access to manage policies, policy overrides, workspaces, or VCS settings. | |
| Concurrent Run | Hourly Rate per Concurrent Run Setting | Concurrency refers to a group of runs from a global queue processed by multiple concurrent workers. This allows you to execute multiple runs at the same time. | |
| HCP Vault (Development, Standard, Plus) | Vault Cluster | Hourly Rate per Cluster | A Vault Cluster is a group of Vault servers with a single primary active Vault Server node with several directly connected passive standby Vault Server nodes, used for high availability and fail-over. |
| Vault Client | Rate per Client (Monthly) | Vault Clients are considered unique applications, services, and/or users that consume Vault. Only active clients count towards totals for the billing and consumption during the billing period. For more information visit our client webpage. | |
| HCP Consul (Development, Standard, Plus) | Consul Cluster | Hourly Rate per Cluster | A Consult Cluster is a group of Consul servers that form a data center. |
| Consul Service Instance | Minutely Rate per Service instance | A “Service” is a logical representation of an application or microservice that is registered in Consul. “Service Instances” refer to one or more running versions of a given service, each tracked as a distinct provider of the service by Consul's service registry. | |
| HCP Packer (Standard, Plus) | Image | Hourly Rate per Image | An image is a unique HashiCorp Packer configuration file. It can define one or multiple builds of an image. |
| Request | Rate per Request (Monthly) | A Packer “request” occurs whenever a customer queries either the channel API or the iterations API to fetch an iteration. |
»Usage Metering and Cost Calculation
Billing metrics are metered by incremental count or by time, with usage and costs accrued so far in the month displayed and updated in the billing page every hour. Usage and costs are finalized and deducted from your Flex balance and an invoice is sent at the end of every month.
A few of the metrics above like Vault clients, Terraform applies, and Packer requests are incrementally counted for each month. Each subsequent unit is priced based on the pricing tier, and the count resets at the beginning of the following month.
Other metrics like clusters and service instances are metered over time. At the end of every hour, HCP will look at the billing unit count for the last hour, apply tiered pricing, support uplift, and discount to calculate the total charge and add it to the running balance. The billing usage summary will update every hour, though calculations may be delayed up to 30 minutes. For example, by 10:30am, the usage summary and balance will be updated for hours 9am to 10am.
In the usage summary, the ‘quantity’ shows the total sum of the units (hours for metrics metered over time, raw count for incremental metrics), and ‘amount’ shows the total cost associated with that metric with tiered pricing and discount applied. The rate shown is an estimated blended rate calculated by dividing the ‘amount’ by the ‘quantity.’ The blended rate can change within the month as usage reaches higher usage tiers. Multiplying quantity and rate may result in slight discrepancies due to rounding in the UI.
- Vault clients and Consul service instances are aggregated across the entire organization for pricing purposes. For example, increasing client count on one Vault cluster will decrease the marginal price of each additional client for all Vault clusters in the organization as higher pricing tiers are reached.
- Terraform metrics are aggregated across all TFC Business organizations linked to Flex.
The usage summary will still display the number of clients and service instance hours attributed to each cluster separately, but will show the same blended rate for each cluster. For example, if Vault cluster A has one client and Vault cluster B has three clients, a quarter of the total Vault client charge to the organization will be attributed to cluster A, and three-quarters to cluster B, with the same blended rate for both.
The usage summary values are estimates until the statement is finalized at the end of the month. This allows for HCP to finalize price tiers and backfill any missing data.
»Terraform Cloud Business Tier
Applies, Admin Users, and Concurrent Runs determine Terraform Cloud for Business Tier consumption. Metering these metrics occurs across all workspaces and TFC Business orgs linked to Flex, meaning usage in one organization puts you in a higher tier discount and lower the prices for usage in other orgs too.
| Metric | Quantity | Estimate Rate |
|---|---|---|
| Apply | Total number of Applies per month | The Apply pricing is tiered. The rate of each Apply is based on the total sum of Applies across all TFC Business Flex orgs for the month. |
| Admin User | Each Admin User is metered from the time the Admin User’s administrative access is granted until revoked. One Admin User in one organization counts as one "admin hour". The total billable quantity is based on how many admins are added, and for how long in all your TFC Business Flex organizations for the month. | The Admin User pricing is tiered. The hourly rate of each “Admin User” varies depending on how many admins are present across your TFCB orgs. |
| Concurrent Runs | Concurrent Runs are charged based on the max allowed concurrency set on your orgs (shown as “Run Concurrency Limit” in TFC UI), and not the concurrency used. A concurrency limit of 1 in your first org is free and not billed. Enabling a higher setting or linking additional TFC orgs to Flex will result in charges. For example, a concurrency limit of 2 in your org will be charged one “Concurrency hour” for every hour of the month. Note that the default setting for your Concurrency Limit is 1 for each TFC Business org. Please contact support to change this value. | The Concurrent Runs pricing is tiered. The hourly rate is based on the sum of your Concurrency Limit values across your TFCB orgs each hour. The estimated rate is a blended rate, calculated by dividing the total cost of “Concurrent Runs” by the total “Concurrency hours” for the month. |
»HCP Vault
Vault clusters and Vault clients determine HCP Vault consumption. These metrics are metered across clusters in your HCP organization, meaning more usage in one cluster can lower the rate of others. ‘Starter’ edition Flex clusters are not available in Flex billing.
| Metric | Quantity | Estimate Rate |
|---|---|---|
| Vault Cluster | The cost and usage information for each Vault cluster is displayed separately. The quantity shows the time duration of each cluster that has been actively running for the month. | The hourly rate is based on the Service “Edition” (i.e., Development, Standard, Plus) and the Vault Cluster size (i.e., Small, Medium, Large). This is a flat hourly rate per cluster. |
| Vault Client | The quantity displayed in each cluster is the number of Vault clients authenticated with that cluster within the month. Note that each Vault client is counted once within a billing month, no matter how many times it has been active. A single Vault Client, which authenticates to multiple Vault Clusters (excluding Vault Development Clusters), are counted as multiple billable Vault Clients. | The Vault Client rate is tiered. The monthly rate of each client is based on the total number of Vault Clients aggregated across all Vault Clusters (excluding Development Clusters) within the billing month. The estimated rate is a blended rate and will be the same across all clusters. This is calculated by dividing the total client cost by the total number of clients across all clusters within the month. |
»HCP Consul
Consul clusters and Consul service instances determine HCP Consul consumption. These metrics are metered across clusters in your HCP organization, meaning more usage in one cluster can lower the rate of others.
| Metric | Quantity | Estimate Rate |
|---|---|---|
| Consul Cluster | The cost and usage information for each Consul cluster is displayed separately. The quantity shows the time duration of each cluster that has been actively running for the month. | The hourly rate is based on the Service “Edition” (i.e., Development, Standard, Plus) and the Consul Cluster size (i.e., Small, Medium, Large). This is a flat hourly rate per cluster. |
| Consul Service Instance | Each service instance is metered from when it is registered until it is deregistered. One service instance registered for one hour is a single “Service Instance Hour.” The total quantity for each cluster is calculated by summing all service instance hours for the month (excluding Development Clusters). | Consul Service Instance rates are presented hourly, but metered on a per-minute basis for higher accuracy. The Consul Service Instance pricing is tiered. The per-minute rate of each service instance is based on the total number of registered service instances aggregated across all Consul Clusters (excluding Development Clusters) within a billing minute. The estimated rate is a blended rate and will be the same across all clusters. This is calculated by dividing the total service instance hours cost by the total quantity across all clusters within the month. |
»HCP Packer
Images and Requests determine HCP Packer consumption. These metrics are tiered based on usage across your HCP organization, meaning the more usage you have, the less per unit price you pay.
| Metric | Quantity | Estimate Rate |
|---|---|---|
| Images | Each image is metered from the time its metadata is stored in the registry until the metadata is deleted. One image stored for one hour is a single "Image hour.” The total quantity is calculated by summing all image hours for the month. | The image pricing is tiered. The hourly rate of each “Image” is determined by the Service Editions (i.e., Standard, Plus) and the total number of “Images” within a billing hour. The estimated rate for each service edition is a blended rate, calculated by dividing the total cost of images by the total image hours within the current billing month. |
| Request | Total number of requests for the month | The Request pricing is tiered. The rate of each “Request” is determined by the Service Editions (i.e., Standard, Plus) and the total number of “Requests” within a billing month. The estimated rate is the blended rate, calculated by dividing the total cost of requests by the total number of requests within the current billing month. |