HashiCorp Vault · FinOps Profile

Hvault Finops

FOCUS-aligned FinOps for HashiCorp Vault: open-source self-managed (no vendor cost), Enterprise self-managed (annual contract priced by client count), HCP Vault Dedicated (cluster-hour), and HCP Vault Secrets (per-secret-per-month). IBM acquired HashiCorp in 2025 - billing for HCP flows through the IBM HashiCorp Cloud Platform.

Hvault Finops is the FinOps profile for HashiCorp Vault on the APIs.io network, aligned with the FinOps Foundation Framework.

It defines 5 billable meters, billed in USD, on a annual (enterprise) / hourly (hcp) cycle, and pricing category subscription + pay-as-you-go.

The profile maps 7 FOCUS columns for cost-allocation reporting.

Tagged areas include FinOps, FOCUS, Secrets Management, and Security.

Category: Security & Identity Pricing: Subscription + Pay-As-You-Go Billing: Annual (Enterprise) / Hourly (HCP) FOCUS v1.3
FinOpsFOCUSSecrets ManagementSecurity

Framework Alignment

Framework
Data Spec

Charge Categories

PurchaseUsageCreditTaxAdjustment

FOCUS Columns

BillingCurrency
USD
ChargeCategory
Usage
InvoiceIssuerName
IBM HashiCorp Cloud Platform
ProviderName
HashiCorp
PublisherName
HashiCorp, Inc.
ServiceCategory
Security & Identity
ServiceName
HashiCorp Vault

Meters

enterprise_clients
Unit: client
Distinct clients (services or humans) authenticating against Vault Enterprise; the primary pricing dimension for self-managed Enterprise contracts.
hcp_cluster_hours
Unit: cluster-hour
Cluster-hours for HCP Vault Dedicated, billed by cluster size and tier (Development, Standard, Plus).
hcp_secrets
Unit: secret-month
Active secrets stored in HCP Vault Secrets, billed per-secret-per-month.
hcp_secrets_syncs
Unit: sync
Native syncs from HCP Vault Secrets to integration targets (AWS, Azure, GCP, Vercel, GitHub Actions).
api_requests
Unit: request
Internal Vault API request volume, useful for capacity planning even when not directly billed.

Sources