Price Secret Manager from active versions, replica locations and access operations, and see what version pruning saves.
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.
Secret Manager Cost
cost = (secrets × active versions × replica locations − free versions) × version price + (access operations − free) ÷ 10,000 × access price.
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.
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.
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.
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.