Secret Manager Cost Calculator
Price Secret Manager from active versions, replica locations and access operations, and see what version pruning saves.
Inputs
Billing counts active versions, so disabling or destroying old ones stops the charge.
Automatic replication and each user-managed location are billed as separate replicas.
Caching a fetched secret in memory is the main way to cut access operations.
Monthly Cost
$86.61
Billable Active Version Replicas
1,194replicas
Version Storage Charge
$71.64
Access Operation Charge
$14.97
Access Operations with Caching
1,578thousands
Saved by Client Caching
$10.27
Saved by Keeping One Version
$48.00
Cost per Secret
$0.4331
Step by step
Values used
Secrets stored = 200 secrets; Active versions kept per secret = 3 versions; Replica locations per secret = 2 locations; Price per active version replica = 0.0600 USD/month; Access operations = 5,000 thousands/month; Price per 10,000 access operations = 0.0300 USD; Free active versions = 6 versions; Free access operations = 10 thousands/month; Rotations per month across all secrets = 200 rotations; Client cache lifetime = 5 minutes; Workloads fetching secrets = 60 workloads; Secrets each workload reads = 3 secrets
Secret Manager Cost
cost = (secrets × active versions × replica locations − free versions) × version price + (access operations − free) ÷ 10,000 × access price.
Monthly Cost
= 86.61
Billable Active Version Replicas
= 1,194 replicas
Version Storage Charge
= 71.64
Access Operation Charge
= 14.97
Access Operations with Caching
= 1,578 thousands
Saved by Client Caching
= 10.27
How it works
Secret Manager multiplies three numbers you control independently: how many secrets you keep, how many versions of each remain active, and how many locations replicate them. Access operations are the second meter, and because a workload that reads a secret on every request generates one operation each time, caching the fetched value in memory is the difference between thousands and millions of operations. Secret sprawl is usually version sprawl — rotation scripts that add a version and never destroy the old one bill forever across every replica location. Confirm the per-version and per-operation prices in the Google Cloud pricing calculator, and check whether automatic replication or a pinned location list suits your residency rules.
Formula
Secret Manager Cost
cost = (secrets × active versions × replica locations − free versions) × version price + (access operations − free) ÷ 10,000 × access price.
- active versions
- Enabled or disabled versions; only destroyed versions stop billing
- replica locations
- Each location holding a copy is billed as its own version replica
- access operations
- Every accessSecretVersion call, which is why clients should cache
Frequently Asked Questions
How is Secret Manager Cost calculated?
cost = (secrets × active versions × replica locations − free versions) × version price + (access operations − free) ÷ 10,000 × access price. Secret Manager multiplies three numbers you control independently: how many secrets you keep, how many versions of each remain active, and how many locations replicate them. Access operations are the second meter, and because a workload that reads a secret on every request generates one operation each time, caching the fetched value in memory is the difference between thousands and millions of operations.
Why does Secret Manager Cost matter?
Secret sprawl is usually version sprawl — rotation scripts that add a version and never destroy the old one bill forever across every replica location. Confirm the per-version and per-operation prices in the Google Cloud pricing calculator, and check whether automatic replication or a pinned location list suits your residency rules.
What values do I need to enter?
This calculator takes 12 inputs: Secrets stored, Active versions kept per secret, Replica locations per secret, Price per active version replica, Access operations, Price per 10,000 access operations, Free active versions, Free access operations, Rotations per month across all secrets, Client cache lifetime, Workloads fetching secrets, Secrets each workload reads. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.
Does disabling a secret version stop the charge?
No. Billing counts active versions, and a disabled version is still stored and still billed. You must destroy the version to stop paying for it, which is why rotation automation should include a destroy step for versions past your rollback window.