> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tensor9.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Secret Manager costs

> Compare Secret Manager backend choices using explicit service-adapter planning assumptions.

Tensor9 BYOC planning comparisons for `google::1.0.0::secret-manager`, with backend choices shown together. Read [how Tensor9 estimates service-adapter costs](/byoc/costs/overview.md) for price scope and capacity qualification, or return to [additional services](/byoc/costs/additional-services.md).

## Google Secret Manager → Key Vault

Origin API: `google::1.0.0::secret-manager`. Target backend: `azure::1.0.0::keyvault`.

**Designed mapping.** This cost model describes an intended adapter. Its estimated price does not establish a delivered or selectable backend.

### Google Secret Manager · Secret-version accesses

Estimated monthly service charges by Secret-version accesses. Adapter hosting and Tensor9 fees are excluded. Source: us-central1; target: eastus; currency: USD.

![Google Secret Manager · Secret-version accesses: monthly service charges by Secret-version accesses. Exact values are in the following table.](/images/diagrams/service-cost/2c6d212c713a20a37cb3e2d6fb7be209f87987711a29fbec9d1ab8974d9336fc-light.svg)

![Google Secret Manager · Secret-version accesses: monthly service charges by Secret-version accesses. Exact values are in the following table.](/images/diagrams/service-cost/0e8155084706630f75c6038aad47db95bf1b5355f696ef538faf9a5f0d1cb442-dark.svg)

Comparison pills describe all sampled scale points; card amounts show the named workload. Costs The Same means within 20% at every point. Costs Depend includes mixed results and unpriced samples.

Exact sampled model outputs in USD/month. Difference means target minus origin; a positive difference means the target costs more.
Estimated allocation from planning assumptions; not benchmark calibrated. Lines connect evaluated samples; intermediate capacity and prices are not inferred. Unpriced means no target quote or cost difference is available within the sizing policy.

| Secret-version accesses (operations/s) | Secret Manager | Target scenario | Key Vault | Difference |
| -: | -: | - | -: | -: |
| 0 | 12 | Key Vault (one staging copy) | 118.2539 | 106.2539 |
| 0 | 12 | Key Vault (two staging copies) | 236.4319 | 224.4319 |
| 1 | 19.884 | Key Vault (one staging copy) | 118.2539 | 98.3699 |
| 1 | 19.884 | Key Vault (two staging copies) | 236.4319 | 216.5479 |
| 10 | 90.84 | Key Vault (one staging copy) | 118.2539 | 27.4139 |
| 10 | 90.84 | Key Vault (two staging copies) | 236.4319 | 145.5919 |
| 100 | 800.4 | Key Vault (one staging copy) | 118.2539 | -682.1461 |
| 100 | 800.4 | Key Vault (two staging copies) | 236.4319 | -563.9681 |
| 1000 | 7896 | Key Vault (one staging copy) | 118.2539 | -7777.7461 |
| 1000 | 7896 | Key Vault (two staging copies) | 236.4319 | -7659.5681 |
| 10000 | 78852 | Key Vault (one staging copy) | 1635.9239 | -77216.0761 |
| 10000 | 78852 | Key Vault (two staging copies) | 3271.7719 | -75580.2281 |

**Estimated allocation from planning assumptions; not benchmark calibrated.**

The sizing policy grows compute with translated work and peak headroom, memory with compute and working set, and disk with resident working state and reserve. Monthly usage is distinct from resident data; each workload's assumptions define the translation. HA changes pricing, not this policy's throughput estimate. Unpriced workloads exceed the policy's configuration range; no silent vertical cap or automatic sharding is assumed.

| Sample / scenario | Basis | Mean / peak work/s | Required vCPU | Allocated vCPU | Memory GiB | SSD GiB | Resident GiB | Policy | Constraints |
| - | - | -: | -: | -: | -: | -: | -: | - | - |
| 0 operations/s / Key Vault (one staging copy) | PlanningAssumption | 0.003805175038051750380517503805175038 / 0.007610350076103500761035007610350076 | 0.000007247952453431905486700007247952453 | 2 | 8 | 100 | 0.001430511474609375 | `service-adapter-planning-2026-10-22.1` | None reported |
| 0 operations/s / Key Vault (two staging copies) | PlanningAssumption | 0.003805175038051750380517503805175038 / 0.007610350076103500761035007610350076 | 0.000007247952453431905486700007247952453 | 2 | 8 | 100 | 0.001430511474609375 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1 operations/s / Key Vault (one staging copy) | PlanningAssumption | 1.003805175038051750380517503805175 / 2.00761035007610350076103500761035 | 0.001912009857215336667391461912009857 | 2 | 8 | 100 | 0.001430511474609375 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1 operations/s / Key Vault (two staging copies) | PlanningAssumption | 1.003805175038051750380517503805175 / 2.00761035007610350076103500761035 | 0.001912009857215336667391461912009857 | 2 | 8 | 100 | 0.001430511474609375 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10 operations/s / Key Vault (one staging copy) | PlanningAssumption | 10.00380517503805175038051750380518 / 20.00761035007610350076103500761036 | 0.01905486700007247952453431905486701 | 2 | 8 | 100 | 0.001430511474609375 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10 operations/s / Key Vault (two staging copies) | PlanningAssumption | 10.00380517503805175038051750380518 / 20.00761035007610350076103500761036 | 0.01905486700007247952453431905486701 | 2 | 8 | 100 | 0.001430511474609375 | `service-adapter-planning-2026-10-22.1` | None reported |
| 100 operations/s / Key Vault (one staging copy) | PlanningAssumption | 100.0038051750380517503805175038052 / 200.0076103500761035007610350076104 | 0.1904834384286439080959628904834385 | 2 | 8 | 100 | 0.001430511474609375 | `service-adapter-planning-2026-10-22.1` | None reported |
| 100 operations/s / Key Vault (two staging copies) | PlanningAssumption | 100.0038051750380517503805175038052 / 200.0076103500761035007610350076104 | 0.1904834384286439080959628904834385 | 2 | 8 | 100 | 0.001430511474609375 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1000 operations/s / Key Vault (one staging copy) | PlanningAssumption | 1000.003805175038051750380517503805 / 2000.00761035007610350076103500761 | 1.904769152714358193810248604769152 | 2 | 8 | 100 | 0.001430511474609375 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1000 operations/s / Key Vault (two staging copies) | PlanningAssumption | 1000.003805175038051750380517503805 / 2000.00761035007610350076103500761 | 1.904769152714358193810248604769152 | 2 | 8 | 100 | 0.001430511474609375 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10000 operations/s / Key Vault (one staging copy) | PlanningAssumption | 10000.00380517503805175038051750381 / 20000.00761035007610350076103500762 | 19.0476262955715010509531057476263 | 32 | 128 | 100 | 0.001430511474609375 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10000 operations/s / Key Vault (two staging copies) | PlanningAssumption | 10000.00380517503805175038051750381 / 20000.00761035007610350076103500762 | 19.0476262955715010509531057476263 | 32 | 128 | 100 | 0.001430511474609375 | `service-adapter-planning-2026-10-22.1` | None reported |

* Row-store throughput (capacityOpsPerVcpuSecond, default 1500) is measured-by-tensor9 as a lower bound: the DynamoDB adapter on Cloud SQL db-custom-2-7680 (2 vCPU, PostgreSQL 16, us-west1) served 2,974 ops/s of YCSB-A at 16 threads without recorded saturation (src/main/kotlin/t9/prime/equiv/generated/eval/CloudsqlPostgresqlYcsbAT16GoYcsbV1\_0\_0.kt). Published CPU-bound pgbench reaches 3,101 read-write transactions and 20,289 point reads per vCPU-second (AWS z1d.2xlarge, PostgreSQL 14.5), so actual capacity is likely higher. Reads and writes share one coefficient: at the same adapter version, read-only YCSB-C was not faster than 50%-update YCSB-A.
* Log-broker throughput (capacityStreamMiBPerVcpuSecond 20 at 0.5 utilization, 4 GiB RAM per vCPU) is provider-documented by Google Managed Service for Apache Kafka sizing ([https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size](https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size)): write-equivalent bytes are replicated writes plus a quarter of reads. Producer batches below 10 KB lower per-CPU throughput; that penalty is not modeled.
* Disk utilization 0.8 is provider-documented headroom below Cloud SQL automatic storage increase, which triggers near 91-95% full ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)). The 20 GiB reserve exceeds PostgreSQL's 1 GB default max\_wal\_size; the remainder of that reserve is unmeasured.
* CPU tiers, 4 GiB per vCPU, at most 6.5 GiB per vCPU, 96 vCPU and 65,536 GiB disk follow Cloud SQL Enterprise custom machine limits (provider-documented, same page); 624 GiB is 96 × 6.5. Targets billed per node, unit or throughput unit are sized by their backend instead.
* No public evidence: peak/mean work (2) and the RAM working-set fraction (0.1). Proposed measurements: the p99 one-minute rate over the monthly mean from customer CloudWatch metrics; the buffer hit ratio while stepping RAM under a fixed YCSB-B load.
* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.
* The operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Key Vault (one staging copy) | Origin list price · Active source secret versions | 0.06 | USD/version-month |
| Key Vault (one staging copy) | Origin list price · Source version accesses | 0.000003 | USD/requests |
| Key Vault (one staging copy) | Origin list price · Source version and metadata mutations | 0 | USD/requests |
| Key Vault (one staging copy) | Representative value size | 1024 | bytes |
| Key Vault (one staging copy) | Versions retained in adapter state | 10 | versions/object |
| Key Vault (one staging copy) | Provider revisions retained per logical object | 2 | versions/object |
| Key Vault (one staging copy) | Physical record / payload storage | 1.5 | multiplier |
| Key Vault (one staging copy) | Provider reconciliation checks | 30 | checks/object-month |
| Key Vault (one staging copy) | Provider calls per current-value mutation | 2 | operations/mutation |
| Key Vault (one staging copy) | Provider reconciliation retry multiplier | 1.1 | multiplier |
| Key Vault (one staging copy) | Active source versions per logical secret | 2 | versions/secret |
| Key Vault (one staging copy) | Target price guess · read | 0 | USD/read |
| Key Vault (one staging copy) | Target price guess · write | 0 | USD/write |
| Key Vault (one staging copy) | Target list price · provider operation | 0.000003 | USD/provider operation |
| Key Vault (one staging copy) | Target price guess · GiB-month | 0 | USD/GiB-month |
| Key Vault (one staging copy) | Target price guess · published GiB | 0 | USD/published GiB |
| Key Vault (one staging copy) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Key Vault (one staging copy) | Target price guess · network GiB | 0 | USD/network GiB |
| Key Vault (one staging copy) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Key Vault (one staging copy) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Key Vault (one staging copy) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Key Vault (one staging copy) | Target price guess · resource-hour | 0 | USD/resource-hour |
| Key Vault (one staging copy) | Target price guess · resource-month | 0 | USD/resource-month |
| Key Vault (one staging copy) | Target price guess · input token | 0 | USD/input token |
| Key Vault (one staging copy) | Target price guess · output token | 0 | USD/output token |
| Key Vault (one staging copy) | Target monthly base charge | 0 | USD/month |
| Key Vault (one staging copy) | Approximate target service minimum | 0 | USD/month |
| Key Vault (one staging copy) | Minimum primary CPU | 2 | vCPU |
| Key Vault (one staging copy) | Minimum primary RAM | 8 | GiB |
| Key Vault (one staging copy) | Minimum primary disk | 100 | GiB |
| Key Vault (one staging copy) | Additional full-price standby copy | 0 | 0 or 1 |
| Key Vault (one staging copy) | Allocated share of provisioned cost | 1 | fraction |
| Key Vault (one staging copy) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Key Vault (one staging copy) | Planning peak / mean work | 2 | multiplier |
| Key Vault (one staging copy) | Planning primary CPU utilization | 0.7 | fraction |
| Key Vault (one staging copy) | Resident state reserved in RAM | 0.1 | fraction |
| Key Vault (one staging copy) | Planning disk utilization | 0.8 | fraction |
| Key Vault (one staging copy) | Maintenance and log disk reserve | 20 | GiB |
| Key Vault (one staging copy) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Key Vault (one staging copy) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Key Vault (one staging copy) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Key Vault (one staging copy) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Key Vault (one staging copy) | Dependent object sink write price guess | 0.000005 | USD/write |
| Key Vault (two staging copies) | Origin list price · Active source secret versions | 0.06 | USD/version-month |
| Key Vault (two staging copies) | Origin list price · Source version accesses | 0.000003 | USD/requests |
| Key Vault (two staging copies) | Origin list price · Source version and metadata mutations | 0 | USD/requests |
| Key Vault (two staging copies) | Representative value size | 1024 | bytes |
| Key Vault (two staging copies) | Versions retained in adapter state | 10 | versions/object |
| Key Vault (two staging copies) | Provider revisions retained per logical object | 2 | versions/object |
| Key Vault (two staging copies) | Physical record / payload storage | 1.5 | multiplier |
| Key Vault (two staging copies) | Provider reconciliation checks | 30 | checks/object-month |
| Key Vault (two staging copies) | Provider calls per current-value mutation | 2 | operations/mutation |
| Key Vault (two staging copies) | Provider reconciliation retry multiplier | 1.1 | multiplier |
| Key Vault (two staging copies) | Active source versions per logical secret | 2 | versions/secret |
| Key Vault (two staging copies) | Target price guess · read | 0 | USD/read |
| Key Vault (two staging copies) | Target price guess · write | 0 | USD/write |
| Key Vault (two staging copies) | Target list price · provider operation | 0.000003 | USD/provider operation |
| Key Vault (two staging copies) | Target price guess · GiB-month | 0 | USD/GiB-month |
| Key Vault (two staging copies) | Target price guess · published GiB | 0 | USD/published GiB |
| Key Vault (two staging copies) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Key Vault (two staging copies) | Target price guess · network GiB | 0 | USD/network GiB |
| Key Vault (two staging copies) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Key Vault (two staging copies) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Key Vault (two staging copies) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Key Vault (two staging copies) | Target price guess · resource-hour | 0 | USD/resource-hour |
| Key Vault (two staging copies) | Target price guess · resource-month | 0 | USD/resource-month |
| Key Vault (two staging copies) | Target price guess · input token | 0 | USD/input token |
| Key Vault (two staging copies) | Target price guess · output token | 0 | USD/output token |
| Key Vault (two staging copies) | Target monthly base charge | 0 | USD/month |
| Key Vault (two staging copies) | Approximate target service minimum | 0 | USD/month |
| Key Vault (two staging copies) | Minimum primary CPU | 2 | vCPU |
| Key Vault (two staging copies) | Minimum primary RAM | 8 | GiB |
| Key Vault (two staging copies) | Minimum primary disk | 100 | GiB |
| Key Vault (two staging copies) | Additional full-price standby copy | 1 | 0 or 1 |
| Key Vault (two staging copies) | Allocated share of provisioned cost | 1 | fraction |
| Key Vault (two staging copies) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Key Vault (two staging copies) | Planning peak / mean work | 2 | multiplier |
| Key Vault (two staging copies) | Planning primary CPU utilization | 0.7 | fraction |
| Key Vault (two staging copies) | Resident state reserved in RAM | 0.1 | fraction |
| Key Vault (two staging copies) | Planning disk utilization | 0.8 | fraction |
| Key Vault (two staging copies) | Maintenance and log disk reserve | 20 | GiB |
| Key Vault (two staging copies) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Key Vault (two staging copies) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Key Vault (two staging copies) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Key Vault (two staging copies) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Key Vault (two staging copies) | Dependent object sink write price guess | 0.000005 | USD/write |

* Monthly operation quantity varies with this steady average rate; stored inventory and other meters retain their defaults. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
* Planning estimate · editable authored rates and sizing assumptions dated 2026-10-22; not verified provider prices. us-central1 → eastus, USD/month.
* Source prices are reference charges, not an invoice. Target lines cover selected service usage/configuration only; adapter hosting and Tensor9 fees are excluded.
* Explicit tariff samples are not performance measurements or capacity qualification. No interpolation or break-even guarantee is implied.
* Variant assumptions show the first axis sample; any axis-dependent configuration is described by this curve's workload note.
* Rates are cited provider list prices, editable for discounts, commitments or another region. Workload translation and capacity coefficients remain editable planning assumptions, not benchmark measurements or a commercial quote.
* Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free.
* Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified.
* Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity.
* A declared adapter mapping and cost model do not establish implementation availability or service equivalence.
* This exact directed mapping has a design profile. Cost modeling does not establish an implemented or deployable adapter.
* Origin unit prices are cited provider list prices. Retention, amplification, and capacity coefficients are authored planning guesses; they are editable, not measured capacity.
* Reverse-cloud Secret Manager adapters are declared designs. This planning scenario assumes a durable record plus reconciled provider copy; it does not certify a delivered implementation or promote availability.
* Application reads use durable adapter records. Managed operations estimate independent backend reconciliation, not a provider secret-access charge on every application read.
* Provider reconciliation operations use the vault-operation tariff; Standard secrets have no storage meter.
* Row-store throughput (capacityOpsPerVcpuSecond, default 1500) is measured-by-tensor9 as a lower bound: the DynamoDB adapter on Cloud SQL db-custom-2-7680 (2 vCPU, PostgreSQL 16, us-west1) served 2,974 ops/s of YCSB-A at 16 threads without recorded saturation (src/main/kotlin/t9/prime/equiv/generated/eval/CloudsqlPostgresqlYcsbAT16GoYcsbV1\_0\_0.kt). Published CPU-bound pgbench reaches 3,101 read-write transactions and 20,289 point reads per vCPU-second (AWS z1d.2xlarge, PostgreSQL 14.5), so actual capacity is likely higher. Reads and writes share one coefficient: at the same adapter version, read-only YCSB-C was not faster than 50%-update YCSB-A.
* Log-broker throughput (capacityStreamMiBPerVcpuSecond 20 at 0.5 utilization, 4 GiB RAM per vCPU) is provider-documented by Google Managed Service for Apache Kafka sizing ([https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size](https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size)): write-equivalent bytes are replicated writes plus a quarter of reads. Producer batches below 10 KB lower per-CPU throughput; that penalty is not modeled.
* Disk utilization 0.8 is provider-documented headroom below Cloud SQL automatic storage increase, which triggers near 91-95% full ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)). The 20 GiB reserve exceeds PostgreSQL's 1 GB default max\_wal\_size; the remainder of that reserve is unmeasured.
* CPU tiers, 4 GiB per vCPU, at most 6.5 GiB per vCPU, 96 vCPU and 65,536 GiB disk follow Cloud SQL Enterprise custom machine limits (provider-documented, same page); 624 GiB is 96 × 6.5. Targets billed per node, unit or throughput unit are sized by their backend instead.
* No public evidence: peak/mean work (2) and the RAM working-set fraction (0.1). Proposed measurements: the p99 one-minute rate over the monthly mean from customer CloudWatch metrics; the buffer hit ratio while stepping RAM under a fixed YCSB-B load.
* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.
* The operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
* Secret Manager pricing: [https://cloud.google.com/secret-manager/pricing](https://cloud.google.com/secret-manager/pricing)
* Azure Retail Prices API: [https://prices.azure.com/api/retail/prices](https://prices.azure.com/api/retail/prices)

Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied.

Excluded costs and workload features:

* Free allowances, committed discounts, credits, taxes and negotiated rates.
* Commercial Tensor9 fees and operations labor unless entered separately.
* Regional replication, customer-managed KMS, source free allowances and rotation functions.
* Taxes, discounts, credits and free-tier allowances unless explicitly reflected in edited rates.
* Unmodeled dependent services, task execution and operations outside the selected workload family.

List prices read: 2026-10-22. Model: `plan-cd9e6893763424e3abd6c10da1b4b23b43d7de09` / `2026-10-22.planning.2`. Curve: `workload-1`.

Sources: [Secret Manager pricing](https://cloud.google.com/secret-manager/pricing), [Azure Retail Prices API](https://prices.azure.com/api/retail/prices).

### Google Secret Manager · Active source versions

Estimated monthly service charges by Active source versions. Adapter hosting and Tensor9 fees are excluded. Source: us-central1; target: eastus; currency: USD.

![Google Secret Manager · Active source versions: monthly service charges by Active source versions. Exact values are in the following table.](/images/diagrams/service-cost/f24d08131a4c3253a88f8c14b1ab5820f22bfc67af084d7623b076c35b319d69-light.svg)

![Google Secret Manager · Active source versions: monthly service charges by Active source versions. Exact values are in the following table.](/images/diagrams/service-cost/393d00549341ba68c3e1f0ed775d06afb91fa97fe61b829bd297ff104a5c2098-dark.svg)

Comparison pills describe all sampled scale points; card amounts show the named workload. Costs The Same means within 20% at every point. Costs Depend includes mixed results and unpriced samples.

Exact sampled model outputs in USD/month. Difference means target minus origin; a positive difference means the target costs more.
Estimated allocation from planning assumptions; not benchmark calibrated. Lines connect evaluated samples; intermediate capacity and prices are not inferred. Unpriced means no target quote or cost difference is available within the sizing policy.

| Active source versions (versions) | Secret Manager | Target scenario | Key Vault | Difference |
| -: | -: | - | -: | -: |
| 0 | 3 | Key Vault (one staging copy) | 118.244 | 115.244 |
| 0 | 3 | Key Vault (two staging copies) | 236.422 | 233.422 |
| 10 | 3.6 | Key Vault (one staging copy) | 118.244495 | 114.644495 |
| 10 | 3.6 | Key Vault (two staging copies) | 236.422495 | 232.822495 |
| 100 | 9 | Key Vault (one staging copy) | 118.24895 | 109.24895 |
| 100 | 9 | Key Vault (two staging copies) | 236.42695 | 227.42695 |
| 1000 | 63 | Key Vault (one staging copy) | 118.2935 | 55.2935 |
| 1000 | 63 | Key Vault (two staging copies) | 236.4715 | 173.4715 |
| 10000 | 603 | Key Vault (one staging copy) | 118.739 | -484.261 |
| 10000 | 603 | Key Vault (two staging copies) | 236.917 | -366.083 |
| 100000 | 6003 | Key Vault (one staging copy) | 123.194 | -5879.806 |
| 100000 | 6003 | Key Vault (two staging copies) | 241.372 | -5761.628 |

**Estimated allocation from planning assumptions; not benchmark calibrated.**

The sizing policy grows compute with translated work and peak headroom, memory with compute and working set, and disk with resident working state and reserve. Monthly usage is distinct from resident data; each workload's assumptions define the translation. HA changes pricing, not this policy's throughput estimate. Unpriced workloads exceed the policy's configuration range; no silent vertical cap or automatic sharding is assumed.

| Sample / scenario | Basis | Mean / peak work/s | Required vCPU | Allocated vCPU | Memory GiB | SSD GiB | Resident GiB | Policy | Constraints |
| - | - | -: | -: | -: | -: | -: | -: | - | - |
| 0 versions / Key Vault (one staging copy) | PlanningAssumption | 0.3843226788432267884322678843226788 / 0.7686453576864535768645357686453576 | 0.0007320431977966224541567007320431977 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 0 versions / Key Vault (two staging copies) | PlanningAssumption | 0.3843226788432267884322678843226788 / 0.7686453576864535768645357686453576 | 0.0007320431977966224541567007320431977 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10 versions / Key Vault (one staging copy) | PlanningAssumption | 0.3843226788432267884322678843226788 / 0.7686453576864535768645357686453576 | 0.0007320431977966224541567007320431977 | 2 | 8 | 100 | 0.00007152557373046875 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10 versions / Key Vault (two staging copies) | PlanningAssumption | 0.3843226788432267884322678843226788 / 0.7686453576864535768645357686453576 | 0.0007320431977966224541567007320431977 | 2 | 8 | 100 | 0.00007152557373046875 | `service-adapter-planning-2026-10-22.1` | None reported |
| 100 versions / Key Vault (one staging copy) | PlanningAssumption | 0.3843226788432267884322678843226788 / 0.7686453576864535768645357686453576 | 0.0007320431977966224541567007320431977 | 2 | 8 | 100 | 0.0007152557373046875 | `service-adapter-planning-2026-10-22.1` | None reported |
| 100 versions / Key Vault (two staging copies) | PlanningAssumption | 0.3843226788432267884322678843226788 / 0.7686453576864535768645357686453576 | 0.0007320431977966224541567007320431977 | 2 | 8 | 100 | 0.0007152557373046875 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1000 versions / Key Vault (one staging copy) | PlanningAssumption | 0.3843226788432267884322678843226788 / 0.7686453576864535768645357686453576 | 0.0007320431977966224541567007320431977 | 2 | 8 | 100 | 0.007152557373046875 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1000 versions / Key Vault (two staging copies) | PlanningAssumption | 0.3843226788432267884322678843226788 / 0.7686453576864535768645357686453576 | 0.0007320431977966224541567007320431977 | 2 | 8 | 100 | 0.007152557373046875 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10000 versions / Key Vault (one staging copy) | PlanningAssumption | 0.3843226788432267884322678843226788 / 0.7686453576864535768645357686453576 | 0.0007320431977966224541567007320431977 | 2 | 8 | 100 | 0.07152557373046875 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10000 versions / Key Vault (two staging copies) | PlanningAssumption | 0.3843226788432267884322678843226788 / 0.7686453576864535768645357686453576 | 0.0007320431977966224541567007320431977 | 2 | 8 | 100 | 0.07152557373046875 | `service-adapter-planning-2026-10-22.1` | None reported |
| 100000 versions / Key Vault (one staging copy) | PlanningAssumption | 0.3843226788432267884322678843226788 / 0.7686453576864535768645357686453576 | 0.0007320431977966224541567007320431977 | 2 | 8 | 100 | 0.7152557373046875 | `service-adapter-planning-2026-10-22.1` | None reported |
| 100000 versions / Key Vault (two staging copies) | PlanningAssumption | 0.3843226788432267884322678843226788 / 0.7686453576864535768645357686453576 | 0.0007320431977966224541567007320431977 | 2 | 8 | 100 | 0.7152557373046875 | `service-adapter-planning-2026-10-22.1` | None reported |

* Row-store throughput (capacityOpsPerVcpuSecond, default 1500) is measured-by-tensor9 as a lower bound: the DynamoDB adapter on Cloud SQL db-custom-2-7680 (2 vCPU, PostgreSQL 16, us-west1) served 2,974 ops/s of YCSB-A at 16 threads without recorded saturation (src/main/kotlin/t9/prime/equiv/generated/eval/CloudsqlPostgresqlYcsbAT16GoYcsbV1\_0\_0.kt). Published CPU-bound pgbench reaches 3,101 read-write transactions and 20,289 point reads per vCPU-second (AWS z1d.2xlarge, PostgreSQL 14.5), so actual capacity is likely higher. Reads and writes share one coefficient: at the same adapter version, read-only YCSB-C was not faster than 50%-update YCSB-A.
* Log-broker throughput (capacityStreamMiBPerVcpuSecond 20 at 0.5 utilization, 4 GiB RAM per vCPU) is provider-documented by Google Managed Service for Apache Kafka sizing ([https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size](https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size)): write-equivalent bytes are replicated writes plus a quarter of reads. Producer batches below 10 KB lower per-CPU throughput; that penalty is not modeled.
* Disk utilization 0.8 is provider-documented headroom below Cloud SQL automatic storage increase, which triggers near 91-95% full ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)). The 20 GiB reserve exceeds PostgreSQL's 1 GB default max\_wal\_size; the remainder of that reserve is unmeasured.
* CPU tiers, 4 GiB per vCPU, at most 6.5 GiB per vCPU, 96 vCPU and 65,536 GiB disk follow Cloud SQL Enterprise custom machine limits (provider-documented, same page); 624 GiB is 96 × 6.5. Targets billed per node, unit or throughput unit are sized by their backend instead.
* No public evidence: peak/mean work (2) and the RAM working-set fraction (0.1). Proposed measurements: the p99 one-minute rate over the monthly mean from customer CloudWatch metrics; the buffer hit ratio while stepping RAM under a fixed YCSB-B load.
* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.
* The operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Key Vault (one staging copy) | Origin list price · Active source secret versions | 0.06 | USD/version-month |
| Key Vault (one staging copy) | Origin list price · Source version accesses | 0.000003 | USD/requests |
| Key Vault (one staging copy) | Origin list price · Source version and metadata mutations | 0 | USD/requests |
| Key Vault (one staging copy) | Representative value size | 1024 | bytes |
| Key Vault (one staging copy) | Versions retained in adapter state | 10 | versions/object |
| Key Vault (one staging copy) | Provider revisions retained per logical object | 2 | versions/object |
| Key Vault (one staging copy) | Physical record / payload storage | 1.5 | multiplier |
| Key Vault (one staging copy) | Provider reconciliation checks | 30 | checks/object-month |
| Key Vault (one staging copy) | Provider calls per current-value mutation | 2 | operations/mutation |
| Key Vault (one staging copy) | Provider reconciliation retry multiplier | 1.1 | multiplier |
| Key Vault (one staging copy) | Active source versions per logical secret | 2 | versions/secret |
| Key Vault (one staging copy) | Target price guess · read | 0 | USD/read |
| Key Vault (one staging copy) | Target price guess · write | 0 | USD/write |
| Key Vault (one staging copy) | Target list price · provider operation | 0.000003 | USD/provider operation |
| Key Vault (one staging copy) | Target price guess · GiB-month | 0 | USD/GiB-month |
| Key Vault (one staging copy) | Target price guess · published GiB | 0 | USD/published GiB |
| Key Vault (one staging copy) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Key Vault (one staging copy) | Target price guess · network GiB | 0 | USD/network GiB |
| Key Vault (one staging copy) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Key Vault (one staging copy) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Key Vault (one staging copy) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Key Vault (one staging copy) | Target price guess · resource-hour | 0 | USD/resource-hour |
| Key Vault (one staging copy) | Target price guess · resource-month | 0 | USD/resource-month |
| Key Vault (one staging copy) | Target price guess · input token | 0 | USD/input token |
| Key Vault (one staging copy) | Target price guess · output token | 0 | USD/output token |
| Key Vault (one staging copy) | Target monthly base charge | 0 | USD/month |
| Key Vault (one staging copy) | Approximate target service minimum | 0 | USD/month |
| Key Vault (one staging copy) | Minimum primary CPU | 2 | vCPU |
| Key Vault (one staging copy) | Minimum primary RAM | 8 | GiB |
| Key Vault (one staging copy) | Minimum primary disk | 100 | GiB |
| Key Vault (one staging copy) | Additional full-price standby copy | 0 | 0 or 1 |
| Key Vault (one staging copy) | Allocated share of provisioned cost | 1 | fraction |
| Key Vault (one staging copy) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Key Vault (one staging copy) | Planning peak / mean work | 2 | multiplier |
| Key Vault (one staging copy) | Planning primary CPU utilization | 0.7 | fraction |
| Key Vault (one staging copy) | Resident state reserved in RAM | 0.1 | fraction |
| Key Vault (one staging copy) | Planning disk utilization | 0.8 | fraction |
| Key Vault (one staging copy) | Maintenance and log disk reserve | 20 | GiB |
| Key Vault (one staging copy) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Key Vault (one staging copy) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Key Vault (one staging copy) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Key Vault (one staging copy) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Key Vault (one staging copy) | Dependent object sink write price guess | 0.000005 | USD/write |
| Key Vault (two staging copies) | Origin list price · Active source secret versions | 0.06 | USD/version-month |
| Key Vault (two staging copies) | Origin list price · Source version accesses | 0.000003 | USD/requests |
| Key Vault (two staging copies) | Origin list price · Source version and metadata mutations | 0 | USD/requests |
| Key Vault (two staging copies) | Representative value size | 1024 | bytes |
| Key Vault (two staging copies) | Versions retained in adapter state | 10 | versions/object |
| Key Vault (two staging copies) | Provider revisions retained per logical object | 2 | versions/object |
| Key Vault (two staging copies) | Physical record / payload storage | 1.5 | multiplier |
| Key Vault (two staging copies) | Provider reconciliation checks | 30 | checks/object-month |
| Key Vault (two staging copies) | Provider calls per current-value mutation | 2 | operations/mutation |
| Key Vault (two staging copies) | Provider reconciliation retry multiplier | 1.1 | multiplier |
| Key Vault (two staging copies) | Active source versions per logical secret | 2 | versions/secret |
| Key Vault (two staging copies) | Target price guess · read | 0 | USD/read |
| Key Vault (two staging copies) | Target price guess · write | 0 | USD/write |
| Key Vault (two staging copies) | Target list price · provider operation | 0.000003 | USD/provider operation |
| Key Vault (two staging copies) | Target price guess · GiB-month | 0 | USD/GiB-month |
| Key Vault (two staging copies) | Target price guess · published GiB | 0 | USD/published GiB |
| Key Vault (two staging copies) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Key Vault (two staging copies) | Target price guess · network GiB | 0 | USD/network GiB |
| Key Vault (two staging copies) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Key Vault (two staging copies) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Key Vault (two staging copies) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Key Vault (two staging copies) | Target price guess · resource-hour | 0 | USD/resource-hour |
| Key Vault (two staging copies) | Target price guess · resource-month | 0 | USD/resource-month |
| Key Vault (two staging copies) | Target price guess · input token | 0 | USD/input token |
| Key Vault (two staging copies) | Target price guess · output token | 0 | USD/output token |
| Key Vault (two staging copies) | Target monthly base charge | 0 | USD/month |
| Key Vault (two staging copies) | Approximate target service minimum | 0 | USD/month |
| Key Vault (two staging copies) | Minimum primary CPU | 2 | vCPU |
| Key Vault (two staging copies) | Minimum primary RAM | 8 | GiB |
| Key Vault (two staging copies) | Minimum primary disk | 100 | GiB |
| Key Vault (two staging copies) | Additional full-price standby copy | 1 | 0 or 1 |
| Key Vault (two staging copies) | Allocated share of provisioned cost | 1 | fraction |
| Key Vault (two staging copies) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Key Vault (two staging copies) | Planning peak / mean work | 2 | multiplier |
| Key Vault (two staging copies) | Planning primary CPU utilization | 0.7 | fraction |
| Key Vault (two staging copies) | Resident state reserved in RAM | 0.1 | fraction |
| Key Vault (two staging copies) | Planning disk utilization | 0.8 | fraction |
| Key Vault (two staging copies) | Maintenance and log disk reserve | 20 | GiB |
| Key Vault (two staging copies) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Key Vault (two staging copies) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Key Vault (two staging copies) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Key Vault (two staging copies) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Key Vault (two staging copies) | Dependent object sink write price guess | 0.000005 | USD/write |

* Inventory varies independently of monthly reads and mutations. Retention remains an explicit planning assumption. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
* Planning estimate · editable authored rates and sizing assumptions dated 2026-10-22; not verified provider prices. us-central1 → eastus, USD/month.
* Source prices are reference charges, not an invoice. Target lines cover selected service usage/configuration only; adapter hosting and Tensor9 fees are excluded.
* Explicit tariff samples are not performance measurements or capacity qualification. No interpolation or break-even guarantee is implied.
* Variant assumptions show the first axis sample; any axis-dependent configuration is described by this curve's workload note.
* Rates are cited provider list prices, editable for discounts, commitments or another region. Workload translation and capacity coefficients remain editable planning assumptions, not benchmark measurements or a commercial quote.
* Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free.
* Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified.
* Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity.
* A declared adapter mapping and cost model do not establish implementation availability or service equivalence.
* This exact directed mapping has a design profile. Cost modeling does not establish an implemented or deployable adapter.
* Origin unit prices are cited provider list prices. Retention, amplification, and capacity coefficients are authored planning guesses; they are editable, not measured capacity.
* Reverse-cloud Secret Manager adapters are declared designs. This planning scenario assumes a durable record plus reconciled provider copy; it does not certify a delivered implementation or promote availability.
* Application reads use durable adapter records. Managed operations estimate independent backend reconciliation, not a provider secret-access charge on every application read.
* Provider reconciliation operations use the vault-operation tariff; Standard secrets have no storage meter.
* Row-store throughput (capacityOpsPerVcpuSecond, default 1500) is measured-by-tensor9 as a lower bound: the DynamoDB adapter on Cloud SQL db-custom-2-7680 (2 vCPU, PostgreSQL 16, us-west1) served 2,974 ops/s of YCSB-A at 16 threads without recorded saturation (src/main/kotlin/t9/prime/equiv/generated/eval/CloudsqlPostgresqlYcsbAT16GoYcsbV1\_0\_0.kt). Published CPU-bound pgbench reaches 3,101 read-write transactions and 20,289 point reads per vCPU-second (AWS z1d.2xlarge, PostgreSQL 14.5), so actual capacity is likely higher. Reads and writes share one coefficient: at the same adapter version, read-only YCSB-C was not faster than 50%-update YCSB-A.
* Log-broker throughput (capacityStreamMiBPerVcpuSecond 20 at 0.5 utilization, 4 GiB RAM per vCPU) is provider-documented by Google Managed Service for Apache Kafka sizing ([https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size](https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size)): write-equivalent bytes are replicated writes plus a quarter of reads. Producer batches below 10 KB lower per-CPU throughput; that penalty is not modeled.
* Disk utilization 0.8 is provider-documented headroom below Cloud SQL automatic storage increase, which triggers near 91-95% full ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)). The 20 GiB reserve exceeds PostgreSQL's 1 GB default max\_wal\_size; the remainder of that reserve is unmeasured.
* CPU tiers, 4 GiB per vCPU, at most 6.5 GiB per vCPU, 96 vCPU and 65,536 GiB disk follow Cloud SQL Enterprise custom machine limits (provider-documented, same page); 624 GiB is 96 × 6.5. Targets billed per node, unit or throughput unit are sized by their backend instead.
* No public evidence: peak/mean work (2) and the RAM working-set fraction (0.1). Proposed measurements: the p99 one-minute rate over the monthly mean from customer CloudWatch metrics; the buffer hit ratio while stepping RAM under a fixed YCSB-B load.
* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.
* The operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
* Secret Manager pricing: [https://cloud.google.com/secret-manager/pricing](https://cloud.google.com/secret-manager/pricing)
* Azure Retail Prices API: [https://prices.azure.com/api/retail/prices](https://prices.azure.com/api/retail/prices)

Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied.

Excluded costs and workload features:

* Free allowances, committed discounts, credits, taxes and negotiated rates.
* Commercial Tensor9 fees and operations labor unless entered separately.
* Regional replication, customer-managed KMS, source free allowances and rotation functions.
* Taxes, discounts, credits and free-tier allowances unless explicitly reflected in edited rates.
* Unmodeled dependent services, task execution and operations outside the selected workload family.

List prices read: 2026-10-22. Model: `plan-cd9e6893763424e3abd6c10da1b4b23b43d7de09` / `2026-10-22.planning.2`. Curve: `workload-2`.

Sources: [Secret Manager pricing](https://cloud.google.com/secret-manager/pricing), [Azure Retail Prices API](https://prices.azure.com/api/retail/prices).

## Google Secret Manager → Secrets Manager

Origin API: `google::1.0.0::secret-manager`. Target backend: `aws::1.0.0::secretsmanager`.

**Designed mapping.** This cost model describes an intended adapter. Its estimated price does not establish a delivered or selectable backend.

### Google Secret Manager · Secret-version accesses

Estimated monthly service charges by Secret-version accesses. Adapter hosting and Tensor9 fees are excluded. Source: us-central1; target: us-east-1; currency: USD.

![Google Secret Manager · Secret-version accesses: monthly service charges by Secret-version accesses. Exact values are in the following table.](/images/diagrams/service-cost/999187db5b2ab6ef15772836ce80eccc28108ec7947b8aab4c57e035f46c678c-light.svg)

![Google Secret Manager · Secret-version accesses: monthly service charges by Secret-version accesses. Exact values are in the following table.](/images/diagrams/service-cost/83c688ffb092bc51829266cab6228708c174bf4d7793ade2707c502133c285cb-dark.svg)

Comparison pills describe all sampled scale points; card amounts show the named workload. Costs The Same means within 20% at every point. Costs Depend includes mixed results and unpriced samples.

Exact sampled model outputs in USD/month. Difference means target minus origin; a positive difference means the target costs more.
Estimated allocation from planning assumptions; not benchmark calibrated. Lines connect evaluated samples; intermediate capacity and prices are not inferred. Unpriced means no target quote or cost difference is available within the sizing policy.

| Secret-version accesses (operations/s) | Secret Manager | Target scenario | Secrets Manager | Difference |
| -: | -: | - | -: | -: |
| 0 | 12 | Secrets Manager (one staging copy) | 158.3045 | 146.3045 |
| 0 | 12 | Secrets Manager (two staging copies) | 276.4825 | 264.4825 |
| 1 | 19.884 | Secrets Manager (one staging copy) | 158.3045 | 138.4205 |
| 1 | 19.884 | Secrets Manager (two staging copies) | 276.4825 | 256.5985 |
| 10 | 90.84 | Secrets Manager (one staging copy) | 158.3045 | 67.4645 |
| 10 | 90.84 | Secrets Manager (two staging copies) | 276.4825 | 185.6425 |
| 100 | 800.4 | Secrets Manager (one staging copy) | 158.3045 | -642.0955 |
| 100 | 800.4 | Secrets Manager (two staging copies) | 276.4825 | -523.9175 |
| 1000 | 7896 | Secrets Manager (one staging copy) | 158.3045 | -7737.6955 |
| 1000 | 7896 | Secrets Manager (two staging copies) | 276.4825 | -7619.5175 |
| 10000 | 78852 | Secrets Manager (one staging copy) | 1675.9745 | -77176.0255 |
| 10000 | 78852 | Secrets Manager (two staging copies) | 3311.8225 | -75540.1775 |

**Estimated allocation from planning assumptions; not benchmark calibrated.**

The sizing policy grows compute with translated work and peak headroom, memory with compute and working set, and disk with resident working state and reserve. Monthly usage is distinct from resident data; each workload's assumptions define the translation. HA changes pricing, not this policy's throughput estimate. Unpriced workloads exceed the policy's configuration range; no silent vertical cap or automatic sharding is assumed.

| Sample / scenario | Basis | Mean / peak work/s | Required vCPU | Allocated vCPU | Memory GiB | SSD GiB | Resident GiB | Policy | Constraints |
| - | - | -: | -: | -: | -: | -: | -: | - | - |
| 0 operations/s / Secrets Manager (one staging copy) | PlanningAssumption | 0.003805175038051750380517503805175038 / 0.007610350076103500761035007610350076 | 0.000007247952453431905486700007247952453 | 2 | 8 | 100 | 0.001430511474609375 | `service-adapter-planning-2026-10-22.1` | None reported |
| 0 operations/s / Secrets Manager (two staging copies) | PlanningAssumption | 0.003805175038051750380517503805175038 / 0.007610350076103500761035007610350076 | 0.000007247952453431905486700007247952453 | 2 | 8 | 100 | 0.001430511474609375 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1 operations/s / Secrets Manager (one staging copy) | PlanningAssumption | 1.003805175038051750380517503805175 / 2.00761035007610350076103500761035 | 0.001912009857215336667391461912009857 | 2 | 8 | 100 | 0.001430511474609375 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1 operations/s / Secrets Manager (two staging copies) | PlanningAssumption | 1.003805175038051750380517503805175 / 2.00761035007610350076103500761035 | 0.001912009857215336667391461912009857 | 2 | 8 | 100 | 0.001430511474609375 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10 operations/s / Secrets Manager (one staging copy) | PlanningAssumption | 10.00380517503805175038051750380518 / 20.00761035007610350076103500761036 | 0.01905486700007247952453431905486701 | 2 | 8 | 100 | 0.001430511474609375 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10 operations/s / Secrets Manager (two staging copies) | PlanningAssumption | 10.00380517503805175038051750380518 / 20.00761035007610350076103500761036 | 0.01905486700007247952453431905486701 | 2 | 8 | 100 | 0.001430511474609375 | `service-adapter-planning-2026-10-22.1` | None reported |
| 100 operations/s / Secrets Manager (one staging copy) | PlanningAssumption | 100.0038051750380517503805175038052 / 200.0076103500761035007610350076104 | 0.1904834384286439080959628904834385 | 2 | 8 | 100 | 0.001430511474609375 | `service-adapter-planning-2026-10-22.1` | None reported |
| 100 operations/s / Secrets Manager (two staging copies) | PlanningAssumption | 100.0038051750380517503805175038052 / 200.0076103500761035007610350076104 | 0.1904834384286439080959628904834385 | 2 | 8 | 100 | 0.001430511474609375 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1000 operations/s / Secrets Manager (one staging copy) | PlanningAssumption | 1000.003805175038051750380517503805 / 2000.00761035007610350076103500761 | 1.904769152714358193810248604769152 | 2 | 8 | 100 | 0.001430511474609375 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1000 operations/s / Secrets Manager (two staging copies) | PlanningAssumption | 1000.003805175038051750380517503805 / 2000.00761035007610350076103500761 | 1.904769152714358193810248604769152 | 2 | 8 | 100 | 0.001430511474609375 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10000 operations/s / Secrets Manager (one staging copy) | PlanningAssumption | 10000.00380517503805175038051750381 / 20000.00761035007610350076103500762 | 19.0476262955715010509531057476263 | 32 | 128 | 100 | 0.001430511474609375 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10000 operations/s / Secrets Manager (two staging copies) | PlanningAssumption | 10000.00380517503805175038051750381 / 20000.00761035007610350076103500762 | 19.0476262955715010509531057476263 | 32 | 128 | 100 | 0.001430511474609375 | `service-adapter-planning-2026-10-22.1` | None reported |

* Row-store throughput (capacityOpsPerVcpuSecond, default 1500) is measured-by-tensor9 as a lower bound: the DynamoDB adapter on Cloud SQL db-custom-2-7680 (2 vCPU, PostgreSQL 16, us-west1) served 2,974 ops/s of YCSB-A at 16 threads without recorded saturation (src/main/kotlin/t9/prime/equiv/generated/eval/CloudsqlPostgresqlYcsbAT16GoYcsbV1\_0\_0.kt). Published CPU-bound pgbench reaches 3,101 read-write transactions and 20,289 point reads per vCPU-second (AWS z1d.2xlarge, PostgreSQL 14.5), so actual capacity is likely higher. Reads and writes share one coefficient: at the same adapter version, read-only YCSB-C was not faster than 50%-update YCSB-A.
* Log-broker throughput (capacityStreamMiBPerVcpuSecond 20 at 0.5 utilization, 4 GiB RAM per vCPU) is provider-documented by Google Managed Service for Apache Kafka sizing ([https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size](https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size)): write-equivalent bytes are replicated writes plus a quarter of reads. Producer batches below 10 KB lower per-CPU throughput; that penalty is not modeled.
* Disk utilization 0.8 is provider-documented headroom below Cloud SQL automatic storage increase, which triggers near 91-95% full ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)). The 20 GiB reserve exceeds PostgreSQL's 1 GB default max\_wal\_size; the remainder of that reserve is unmeasured.
* CPU tiers, 4 GiB per vCPU, at most 6.5 GiB per vCPU, 96 vCPU and 65,536 GiB disk follow Cloud SQL Enterprise custom machine limits (provider-documented, same page); 624 GiB is 96 × 6.5. Targets billed per node, unit or throughput unit are sized by their backend instead.
* No public evidence: peak/mean work (2) and the RAM working-set fraction (0.1). Proposed measurements: the p99 one-minute rate over the monthly mean from customer CloudWatch metrics; the buffer hit ratio while stepping RAM under a fixed YCSB-B load.
* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.
* The operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Secrets Manager (one staging copy) | Origin list price · Active source secret versions | 0.06 | USD/version-month |
| Secrets Manager (one staging copy) | Origin list price · Source version accesses | 0.000003 | USD/requests |
| Secrets Manager (one staging copy) | Origin list price · Source version and metadata mutations | 0 | USD/requests |
| Secrets Manager (one staging copy) | Representative value size | 1024 | bytes |
| Secrets Manager (one staging copy) | Versions retained in adapter state | 10 | versions/object |
| Secrets Manager (one staging copy) | Provider revisions retained per logical object | 2 | versions/object |
| Secrets Manager (one staging copy) | Physical record / payload storage | 1.5 | multiplier |
| Secrets Manager (one staging copy) | Provider reconciliation checks | 30 | checks/object-month |
| Secrets Manager (one staging copy) | Provider calls per current-value mutation | 2 | operations/mutation |
| Secrets Manager (one staging copy) | Provider reconciliation retry multiplier | 1.1 | multiplier |
| Secrets Manager (one staging copy) | Active source versions per logical secret | 2 | versions/secret |
| Secrets Manager (one staging copy) | Target price guess · read | 0 | USD/read |
| Secrets Manager (one staging copy) | Target price guess · write | 0 | USD/write |
| Secrets Manager (one staging copy) | Target list price · provider operation | 0.000005 | USD/provider operation |
| Secrets Manager (one staging copy) | Target price guess · GiB-month | 0 | USD/GiB-month |
| Secrets Manager (one staging copy) | Target price guess · published GiB | 0 | USD/published GiB |
| Secrets Manager (one staging copy) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Secrets Manager (one staging copy) | Target price guess · network GiB | 0 | USD/network GiB |
| Secrets Manager (one staging copy) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Secrets Manager (one staging copy) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Secrets Manager (one staging copy) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Secrets Manager (one staging copy) | Target price guess · resource-hour | 0 | USD/resource-hour |
| Secrets Manager (one staging copy) | Target list price · resource-month | 0.4 | USD/resource-month |
| Secrets Manager (one staging copy) | Target price guess · input token | 0 | USD/input token |
| Secrets Manager (one staging copy) | Target price guess · output token | 0 | USD/output token |
| Secrets Manager (one staging copy) | Target monthly base charge | 0 | USD/month |
| Secrets Manager (one staging copy) | Approximate target service minimum | 0 | USD/month |
| Secrets Manager (one staging copy) | Minimum primary CPU | 2 | vCPU |
| Secrets Manager (one staging copy) | Minimum primary RAM | 8 | GiB |
| Secrets Manager (one staging copy) | Minimum primary disk | 100 | GiB |
| Secrets Manager (one staging copy) | Additional full-price standby copy | 0 | 0 or 1 |
| Secrets Manager (one staging copy) | Allocated share of provisioned cost | 1 | fraction |
| Secrets Manager (one staging copy) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Secrets Manager (one staging copy) | Planning peak / mean work | 2 | multiplier |
| Secrets Manager (one staging copy) | Planning primary CPU utilization | 0.7 | fraction |
| Secrets Manager (one staging copy) | Resident state reserved in RAM | 0.1 | fraction |
| Secrets Manager (one staging copy) | Planning disk utilization | 0.8 | fraction |
| Secrets Manager (one staging copy) | Maintenance and log disk reserve | 20 | GiB |
| Secrets Manager (one staging copy) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Secrets Manager (one staging copy) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Secrets Manager (one staging copy) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Secrets Manager (one staging copy) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Secrets Manager (one staging copy) | Dependent object sink write price guess | 0.000005 | USD/write |
| Secrets Manager (two staging copies) | Origin list price · Active source secret versions | 0.06 | USD/version-month |
| Secrets Manager (two staging copies) | Origin list price · Source version accesses | 0.000003 | USD/requests |
| Secrets Manager (two staging copies) | Origin list price · Source version and metadata mutations | 0 | USD/requests |
| Secrets Manager (two staging copies) | Representative value size | 1024 | bytes |
| Secrets Manager (two staging copies) | Versions retained in adapter state | 10 | versions/object |
| Secrets Manager (two staging copies) | Provider revisions retained per logical object | 2 | versions/object |
| Secrets Manager (two staging copies) | Physical record / payload storage | 1.5 | multiplier |
| Secrets Manager (two staging copies) | Provider reconciliation checks | 30 | checks/object-month |
| Secrets Manager (two staging copies) | Provider calls per current-value mutation | 2 | operations/mutation |
| Secrets Manager (two staging copies) | Provider reconciliation retry multiplier | 1.1 | multiplier |
| Secrets Manager (two staging copies) | Active source versions per logical secret | 2 | versions/secret |
| Secrets Manager (two staging copies) | Target price guess · read | 0 | USD/read |
| Secrets Manager (two staging copies) | Target price guess · write | 0 | USD/write |
| Secrets Manager (two staging copies) | Target list price · provider operation | 0.000005 | USD/provider operation |
| Secrets Manager (two staging copies) | Target price guess · GiB-month | 0 | USD/GiB-month |
| Secrets Manager (two staging copies) | Target price guess · published GiB | 0 | USD/published GiB |
| Secrets Manager (two staging copies) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Secrets Manager (two staging copies) | Target price guess · network GiB | 0 | USD/network GiB |
| Secrets Manager (two staging copies) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Secrets Manager (two staging copies) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Secrets Manager (two staging copies) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Secrets Manager (two staging copies) | Target price guess · resource-hour | 0 | USD/resource-hour |
| Secrets Manager (two staging copies) | Target list price · resource-month | 0.4 | USD/resource-month |
| Secrets Manager (two staging copies) | Target price guess · input token | 0 | USD/input token |
| Secrets Manager (two staging copies) | Target price guess · output token | 0 | USD/output token |
| Secrets Manager (two staging copies) | Target monthly base charge | 0 | USD/month |
| Secrets Manager (two staging copies) | Approximate target service minimum | 0 | USD/month |
| Secrets Manager (two staging copies) | Minimum primary CPU | 2 | vCPU |
| Secrets Manager (two staging copies) | Minimum primary RAM | 8 | GiB |
| Secrets Manager (two staging copies) | Minimum primary disk | 100 | GiB |
| Secrets Manager (two staging copies) | Additional full-price standby copy | 1 | 0 or 1 |
| Secrets Manager (two staging copies) | Allocated share of provisioned cost | 1 | fraction |
| Secrets Manager (two staging copies) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Secrets Manager (two staging copies) | Planning peak / mean work | 2 | multiplier |
| Secrets Manager (two staging copies) | Planning primary CPU utilization | 0.7 | fraction |
| Secrets Manager (two staging copies) | Resident state reserved in RAM | 0.1 | fraction |
| Secrets Manager (two staging copies) | Planning disk utilization | 0.8 | fraction |
| Secrets Manager (two staging copies) | Maintenance and log disk reserve | 20 | GiB |
| Secrets Manager (two staging copies) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Secrets Manager (two staging copies) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Secrets Manager (two staging copies) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Secrets Manager (two staging copies) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Secrets Manager (two staging copies) | Dependent object sink write price guess | 0.000005 | USD/write |

* Monthly operation quantity varies with this steady average rate; stored inventory and other meters retain their defaults. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
* Planning estimate · editable authored rates and sizing assumptions dated 2026-10-22; not verified provider prices. us-central1 → us-east-1, USD/month.
* Source prices are reference charges, not an invoice. Target lines cover selected service usage/configuration only; adapter hosting and Tensor9 fees are excluded.
* Explicit tariff samples are not performance measurements or capacity qualification. No interpolation or break-even guarantee is implied.
* Variant assumptions show the first axis sample; any axis-dependent configuration is described by this curve's workload note.
* Rates are cited provider list prices, editable for discounts, commitments or another region. Workload translation and capacity coefficients remain editable planning assumptions, not benchmark measurements or a commercial quote.
* Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free.
* Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified.
* Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity.
* A declared adapter mapping and cost model do not establish implementation availability or service equivalence.
* This exact directed mapping has a design profile. Cost modeling does not establish an implemented or deployable adapter.
* Origin unit prices are cited provider list prices. Retention, amplification, and capacity coefficients are authored planning guesses; they are editable, not measured capacity.
* Reverse-cloud Secret Manager adapters are declared designs. This planning scenario assumes a durable record plus reconciled provider copy; it does not certify a delivered implementation or promote availability.
* Application reads use durable adapter records. Managed operations estimate independent backend reconciliation, not a provider secret-access charge on every application read.
* The monthly tariff is per logical secret, prorated hourly; replica secrets bill as separate secrets. Normalize provider-version inventory by the selected providerVersions before applying it; application reads use adapter state. The 30-day trial is not applied.
* Row-store throughput (capacityOpsPerVcpuSecond, default 1500) is measured-by-tensor9 as a lower bound: the DynamoDB adapter on Cloud SQL db-custom-2-7680 (2 vCPU, PostgreSQL 16, us-west1) served 2,974 ops/s of YCSB-A at 16 threads without recorded saturation (src/main/kotlin/t9/prime/equiv/generated/eval/CloudsqlPostgresqlYcsbAT16GoYcsbV1\_0\_0.kt). Published CPU-bound pgbench reaches 3,101 read-write transactions and 20,289 point reads per vCPU-second (AWS z1d.2xlarge, PostgreSQL 14.5), so actual capacity is likely higher. Reads and writes share one coefficient: at the same adapter version, read-only YCSB-C was not faster than 50%-update YCSB-A.
* Log-broker throughput (capacityStreamMiBPerVcpuSecond 20 at 0.5 utilization, 4 GiB RAM per vCPU) is provider-documented by Google Managed Service for Apache Kafka sizing ([https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size](https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size)): write-equivalent bytes are replicated writes plus a quarter of reads. Producer batches below 10 KB lower per-CPU throughput; that penalty is not modeled.
* Disk utilization 0.8 is provider-documented headroom below Cloud SQL automatic storage increase, which triggers near 91-95% full ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)). The 20 GiB reserve exceeds PostgreSQL's 1 GB default max\_wal\_size; the remainder of that reserve is unmeasured.
* CPU tiers, 4 GiB per vCPU, at most 6.5 GiB per vCPU, 96 vCPU and 65,536 GiB disk follow Cloud SQL Enterprise custom machine limits (provider-documented, same page); 624 GiB is 96 × 6.5. Targets billed per node, unit or throughput unit are sized by their backend instead.
* No public evidence: peak/mean work (2) and the RAM working-set fraction (0.1). Proposed measurements: the p99 one-minute rate over the monthly mean from customer CloudWatch metrics; the buffer hit ratio while stepping RAM under a fixed YCSB-B load.
* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.
* The operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
* Secret Manager pricing: [https://cloud.google.com/secret-manager/pricing](https://cloud.google.com/secret-manager/pricing)
* AWS Secrets Manager price list (AWS Price List API): [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSSecretsManager/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSSecretsManager/current/us-east-1/index.json)

Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied.

Excluded costs and workload features:

* Free allowances, committed discounts, credits, taxes and negotiated rates.
* Commercial Tensor9 fees and operations labor unless entered separately.
* Regional replication, customer-managed KMS, source free allowances and rotation functions.
* Taxes, discounts, credits and free-tier allowances unless explicitly reflected in edited rates.
* Unmodeled dependent services, task execution and operations outside the selected workload family.

List prices read: 2026-10-22. Model: `plan-96b1d4e954b801d96ec02f26bbb527e1c9945239` / `2026-10-22.planning.2`. Curve: `workload-1`.

Sources: [Secret Manager pricing](https://cloud.google.com/secret-manager/pricing), [AWS Secrets Manager price list (AWS Price List API)](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSSecretsManager/current/us-east-1/index.json).

### Google Secret Manager · Active source versions

Estimated monthly service charges by Active source versions. Adapter hosting and Tensor9 fees are excluded. Source: us-central1; target: us-east-1; currency: USD.

![Google Secret Manager · Active source versions: monthly service charges by Active source versions. Exact values are in the following table.](/images/diagrams/service-cost/4108a10651659dd466137b7f1fd52c725081c11e0346aa6858475e3828fd9d5b-light.svg)

![Google Secret Manager · Active source versions: monthly service charges by Active source versions. Exact values are in the following table.](/images/diagrams/service-cost/d7a16e3c83ed70a8b54984e2459fa2914bfab6ba27d48293ebc8de89fc2c9ba0-dark.svg)

Comparison pills describe all sampled scale points; card amounts show the named workload. Costs The Same means within 20% at every point. Costs Depend includes mixed results and unpriced samples.

Exact sampled model outputs in USD/month. Difference means target minus origin; a positive difference means the target costs more.
Estimated allocation from planning assumptions; not benchmark calibrated. Lines connect evaluated samples; intermediate capacity and prices are not inferred. Unpriced means no target quote or cost difference is available within the sizing policy.

| Active source versions (versions) | Secret Manager | Target scenario | Secrets Manager | Difference |
| -: | -: | - | -: | -: |
| 0 | 3 | Secrets Manager (one staging copy) | 118.288 | 115.288 |
| 0 | 3 | Secrets Manager (two staging copies) | 236.466 | 233.466 |
| 10 | 3.6 | Secrets Manager (one staging copy) | 120.288825 | 116.688825 |
| 10 | 3.6 | Secrets Manager (two staging copies) | 238.466825 | 234.866825 |
| 100 | 9 | Secrets Manager (one staging copy) | 138.29625 | 129.29625 |
| 100 | 9 | Secrets Manager (two staging copies) | 256.47425 | 247.47425 |
| 1000 | 63 | Secrets Manager (one staging copy) | 318.3705 | 255.3705 |
| 1000 | 63 | Secrets Manager (two staging copies) | 436.5485 | 373.5485 |
| 10000 | 603 | Secrets Manager (one staging copy) | 2119.113 | 1516.113 |
| 10000 | 603 | Secrets Manager (two staging copies) | 2237.291 | 1634.291 |
| 100000 | 6003 | Secrets Manager (one staging copy) | 20126.538 | 14123.538 |
| 100000 | 6003 | Secrets Manager (two staging copies) | 20244.716 | 14241.716 |

**Estimated allocation from planning assumptions; not benchmark calibrated.**

The sizing policy grows compute with translated work and peak headroom, memory with compute and working set, and disk with resident working state and reserve. Monthly usage is distinct from resident data; each workload's assumptions define the translation. HA changes pricing, not this policy's throughput estimate. Unpriced workloads exceed the policy's configuration range; no silent vertical cap or automatic sharding is assumed.

| Sample / scenario | Basis | Mean / peak work/s | Required vCPU | Allocated vCPU | Memory GiB | SSD GiB | Resident GiB | Policy | Constraints |
| - | - | -: | -: | -: | -: | -: | -: | - | - |
| 0 versions / Secrets Manager (one staging copy) | PlanningAssumption | 0.3843226788432267884322678843226788 / 0.7686453576864535768645357686453576 | 0.0007320431977966224541567007320431977 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 0 versions / Secrets Manager (two staging copies) | PlanningAssumption | 0.3843226788432267884322678843226788 / 0.7686453576864535768645357686453576 | 0.0007320431977966224541567007320431977 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10 versions / Secrets Manager (one staging copy) | PlanningAssumption | 0.3843226788432267884322678843226788 / 0.7686453576864535768645357686453576 | 0.0007320431977966224541567007320431977 | 2 | 8 | 100 | 0.00007152557373046875 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10 versions / Secrets Manager (two staging copies) | PlanningAssumption | 0.3843226788432267884322678843226788 / 0.7686453576864535768645357686453576 | 0.0007320431977966224541567007320431977 | 2 | 8 | 100 | 0.00007152557373046875 | `service-adapter-planning-2026-10-22.1` | None reported |
| 100 versions / Secrets Manager (one staging copy) | PlanningAssumption | 0.3843226788432267884322678843226788 / 0.7686453576864535768645357686453576 | 0.0007320431977966224541567007320431977 | 2 | 8 | 100 | 0.0007152557373046875 | `service-adapter-planning-2026-10-22.1` | None reported |
| 100 versions / Secrets Manager (two staging copies) | PlanningAssumption | 0.3843226788432267884322678843226788 / 0.7686453576864535768645357686453576 | 0.0007320431977966224541567007320431977 | 2 | 8 | 100 | 0.0007152557373046875 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1000 versions / Secrets Manager (one staging copy) | PlanningAssumption | 0.3843226788432267884322678843226788 / 0.7686453576864535768645357686453576 | 0.0007320431977966224541567007320431977 | 2 | 8 | 100 | 0.007152557373046875 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1000 versions / Secrets Manager (two staging copies) | PlanningAssumption | 0.3843226788432267884322678843226788 / 0.7686453576864535768645357686453576 | 0.0007320431977966224541567007320431977 | 2 | 8 | 100 | 0.007152557373046875 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10000 versions / Secrets Manager (one staging copy) | PlanningAssumption | 0.3843226788432267884322678843226788 / 0.7686453576864535768645357686453576 | 0.0007320431977966224541567007320431977 | 2 | 8 | 100 | 0.07152557373046875 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10000 versions / Secrets Manager (two staging copies) | PlanningAssumption | 0.3843226788432267884322678843226788 / 0.7686453576864535768645357686453576 | 0.0007320431977966224541567007320431977 | 2 | 8 | 100 | 0.07152557373046875 | `service-adapter-planning-2026-10-22.1` | None reported |
| 100000 versions / Secrets Manager (one staging copy) | PlanningAssumption | 0.3843226788432267884322678843226788 / 0.7686453576864535768645357686453576 | 0.0007320431977966224541567007320431977 | 2 | 8 | 100 | 0.7152557373046875 | `service-adapter-planning-2026-10-22.1` | None reported |
| 100000 versions / Secrets Manager (two staging copies) | PlanningAssumption | 0.3843226788432267884322678843226788 / 0.7686453576864535768645357686453576 | 0.0007320431977966224541567007320431977 | 2 | 8 | 100 | 0.7152557373046875 | `service-adapter-planning-2026-10-22.1` | None reported |

* Row-store throughput (capacityOpsPerVcpuSecond, default 1500) is measured-by-tensor9 as a lower bound: the DynamoDB adapter on Cloud SQL db-custom-2-7680 (2 vCPU, PostgreSQL 16, us-west1) served 2,974 ops/s of YCSB-A at 16 threads without recorded saturation (src/main/kotlin/t9/prime/equiv/generated/eval/CloudsqlPostgresqlYcsbAT16GoYcsbV1\_0\_0.kt). Published CPU-bound pgbench reaches 3,101 read-write transactions and 20,289 point reads per vCPU-second (AWS z1d.2xlarge, PostgreSQL 14.5), so actual capacity is likely higher. Reads and writes share one coefficient: at the same adapter version, read-only YCSB-C was not faster than 50%-update YCSB-A.
* Log-broker throughput (capacityStreamMiBPerVcpuSecond 20 at 0.5 utilization, 4 GiB RAM per vCPU) is provider-documented by Google Managed Service for Apache Kafka sizing ([https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size](https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size)): write-equivalent bytes are replicated writes plus a quarter of reads. Producer batches below 10 KB lower per-CPU throughput; that penalty is not modeled.
* Disk utilization 0.8 is provider-documented headroom below Cloud SQL automatic storage increase, which triggers near 91-95% full ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)). The 20 GiB reserve exceeds PostgreSQL's 1 GB default max\_wal\_size; the remainder of that reserve is unmeasured.
* CPU tiers, 4 GiB per vCPU, at most 6.5 GiB per vCPU, 96 vCPU and 65,536 GiB disk follow Cloud SQL Enterprise custom machine limits (provider-documented, same page); 624 GiB is 96 × 6.5. Targets billed per node, unit or throughput unit are sized by their backend instead.
* No public evidence: peak/mean work (2) and the RAM working-set fraction (0.1). Proposed measurements: the p99 one-minute rate over the monthly mean from customer CloudWatch metrics; the buffer hit ratio while stepping RAM under a fixed YCSB-B load.
* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.
* The operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Secrets Manager (one staging copy) | Origin list price · Active source secret versions | 0.06 | USD/version-month |
| Secrets Manager (one staging copy) | Origin list price · Source version accesses | 0.000003 | USD/requests |
| Secrets Manager (one staging copy) | Origin list price · Source version and metadata mutations | 0 | USD/requests |
| Secrets Manager (one staging copy) | Representative value size | 1024 | bytes |
| Secrets Manager (one staging copy) | Versions retained in adapter state | 10 | versions/object |
| Secrets Manager (one staging copy) | Provider revisions retained per logical object | 2 | versions/object |
| Secrets Manager (one staging copy) | Physical record / payload storage | 1.5 | multiplier |
| Secrets Manager (one staging copy) | Provider reconciliation checks | 30 | checks/object-month |
| Secrets Manager (one staging copy) | Provider calls per current-value mutation | 2 | operations/mutation |
| Secrets Manager (one staging copy) | Provider reconciliation retry multiplier | 1.1 | multiplier |
| Secrets Manager (one staging copy) | Active source versions per logical secret | 2 | versions/secret |
| Secrets Manager (one staging copy) | Target price guess · read | 0 | USD/read |
| Secrets Manager (one staging copy) | Target price guess · write | 0 | USD/write |
| Secrets Manager (one staging copy) | Target list price · provider operation | 0.000005 | USD/provider operation |
| Secrets Manager (one staging copy) | Target price guess · GiB-month | 0 | USD/GiB-month |
| Secrets Manager (one staging copy) | Target price guess · published GiB | 0 | USD/published GiB |
| Secrets Manager (one staging copy) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Secrets Manager (one staging copy) | Target price guess · network GiB | 0 | USD/network GiB |
| Secrets Manager (one staging copy) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Secrets Manager (one staging copy) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Secrets Manager (one staging copy) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Secrets Manager (one staging copy) | Target price guess · resource-hour | 0 | USD/resource-hour |
| Secrets Manager (one staging copy) | Target list price · resource-month | 0.4 | USD/resource-month |
| Secrets Manager (one staging copy) | Target price guess · input token | 0 | USD/input token |
| Secrets Manager (one staging copy) | Target price guess · output token | 0 | USD/output token |
| Secrets Manager (one staging copy) | Target monthly base charge | 0 | USD/month |
| Secrets Manager (one staging copy) | Approximate target service minimum | 0 | USD/month |
| Secrets Manager (one staging copy) | Minimum primary CPU | 2 | vCPU |
| Secrets Manager (one staging copy) | Minimum primary RAM | 8 | GiB |
| Secrets Manager (one staging copy) | Minimum primary disk | 100 | GiB |
| Secrets Manager (one staging copy) | Additional full-price standby copy | 0 | 0 or 1 |
| Secrets Manager (one staging copy) | Allocated share of provisioned cost | 1 | fraction |
| Secrets Manager (one staging copy) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Secrets Manager (one staging copy) | Planning peak / mean work | 2 | multiplier |
| Secrets Manager (one staging copy) | Planning primary CPU utilization | 0.7 | fraction |
| Secrets Manager (one staging copy) | Resident state reserved in RAM | 0.1 | fraction |
| Secrets Manager (one staging copy) | Planning disk utilization | 0.8 | fraction |
| Secrets Manager (one staging copy) | Maintenance and log disk reserve | 20 | GiB |
| Secrets Manager (one staging copy) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Secrets Manager (one staging copy) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Secrets Manager (one staging copy) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Secrets Manager (one staging copy) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Secrets Manager (one staging copy) | Dependent object sink write price guess | 0.000005 | USD/write |
| Secrets Manager (two staging copies) | Origin list price · Active source secret versions | 0.06 | USD/version-month |
| Secrets Manager (two staging copies) | Origin list price · Source version accesses | 0.000003 | USD/requests |
| Secrets Manager (two staging copies) | Origin list price · Source version and metadata mutations | 0 | USD/requests |
| Secrets Manager (two staging copies) | Representative value size | 1024 | bytes |
| Secrets Manager (two staging copies) | Versions retained in adapter state | 10 | versions/object |
| Secrets Manager (two staging copies) | Provider revisions retained per logical object | 2 | versions/object |
| Secrets Manager (two staging copies) | Physical record / payload storage | 1.5 | multiplier |
| Secrets Manager (two staging copies) | Provider reconciliation checks | 30 | checks/object-month |
| Secrets Manager (two staging copies) | Provider calls per current-value mutation | 2 | operations/mutation |
| Secrets Manager (two staging copies) | Provider reconciliation retry multiplier | 1.1 | multiplier |
| Secrets Manager (two staging copies) | Active source versions per logical secret | 2 | versions/secret |
| Secrets Manager (two staging copies) | Target price guess · read | 0 | USD/read |
| Secrets Manager (two staging copies) | Target price guess · write | 0 | USD/write |
| Secrets Manager (two staging copies) | Target list price · provider operation | 0.000005 | USD/provider operation |
| Secrets Manager (two staging copies) | Target price guess · GiB-month | 0 | USD/GiB-month |
| Secrets Manager (two staging copies) | Target price guess · published GiB | 0 | USD/published GiB |
| Secrets Manager (two staging copies) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Secrets Manager (two staging copies) | Target price guess · network GiB | 0 | USD/network GiB |
| Secrets Manager (two staging copies) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Secrets Manager (two staging copies) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Secrets Manager (two staging copies) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Secrets Manager (two staging copies) | Target price guess · resource-hour | 0 | USD/resource-hour |
| Secrets Manager (two staging copies) | Target list price · resource-month | 0.4 | USD/resource-month |
| Secrets Manager (two staging copies) | Target price guess · input token | 0 | USD/input token |
| Secrets Manager (two staging copies) | Target price guess · output token | 0 | USD/output token |
| Secrets Manager (two staging copies) | Target monthly base charge | 0 | USD/month |
| Secrets Manager (two staging copies) | Approximate target service minimum | 0 | USD/month |
| Secrets Manager (two staging copies) | Minimum primary CPU | 2 | vCPU |
| Secrets Manager (two staging copies) | Minimum primary RAM | 8 | GiB |
| Secrets Manager (two staging copies) | Minimum primary disk | 100 | GiB |
| Secrets Manager (two staging copies) | Additional full-price standby copy | 1 | 0 or 1 |
| Secrets Manager (two staging copies) | Allocated share of provisioned cost | 1 | fraction |
| Secrets Manager (two staging copies) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Secrets Manager (two staging copies) | Planning peak / mean work | 2 | multiplier |
| Secrets Manager (two staging copies) | Planning primary CPU utilization | 0.7 | fraction |
| Secrets Manager (two staging copies) | Resident state reserved in RAM | 0.1 | fraction |
| Secrets Manager (two staging copies) | Planning disk utilization | 0.8 | fraction |
| Secrets Manager (two staging copies) | Maintenance and log disk reserve | 20 | GiB |
| Secrets Manager (two staging copies) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Secrets Manager (two staging copies) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Secrets Manager (two staging copies) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Secrets Manager (two staging copies) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Secrets Manager (two staging copies) | Dependent object sink write price guess | 0.000005 | USD/write |

* Inventory varies independently of monthly reads and mutations. Retention remains an explicit planning assumption. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
* Planning estimate · editable authored rates and sizing assumptions dated 2026-10-22; not verified provider prices. us-central1 → us-east-1, USD/month.
* Source prices are reference charges, not an invoice. Target lines cover selected service usage/configuration only; adapter hosting and Tensor9 fees are excluded.
* Explicit tariff samples are not performance measurements or capacity qualification. No interpolation or break-even guarantee is implied.
* Variant assumptions show the first axis sample; any axis-dependent configuration is described by this curve's workload note.
* Rates are cited provider list prices, editable for discounts, commitments or another region. Workload translation and capacity coefficients remain editable planning assumptions, not benchmark measurements or a commercial quote.
* Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free.
* Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified.
* Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity.
* A declared adapter mapping and cost model do not establish implementation availability or service equivalence.
* This exact directed mapping has a design profile. Cost modeling does not establish an implemented or deployable adapter.
* Origin unit prices are cited provider list prices. Retention, amplification, and capacity coefficients are authored planning guesses; they are editable, not measured capacity.
* Reverse-cloud Secret Manager adapters are declared designs. This planning scenario assumes a durable record plus reconciled provider copy; it does not certify a delivered implementation or promote availability.
* Application reads use durable adapter records. Managed operations estimate independent backend reconciliation, not a provider secret-access charge on every application read.
* The monthly tariff is per logical secret, prorated hourly; replica secrets bill as separate secrets. Normalize provider-version inventory by the selected providerVersions before applying it; application reads use adapter state. The 30-day trial is not applied.
* Row-store throughput (capacityOpsPerVcpuSecond, default 1500) is measured-by-tensor9 as a lower bound: the DynamoDB adapter on Cloud SQL db-custom-2-7680 (2 vCPU, PostgreSQL 16, us-west1) served 2,974 ops/s of YCSB-A at 16 threads without recorded saturation (src/main/kotlin/t9/prime/equiv/generated/eval/CloudsqlPostgresqlYcsbAT16GoYcsbV1\_0\_0.kt). Published CPU-bound pgbench reaches 3,101 read-write transactions and 20,289 point reads per vCPU-second (AWS z1d.2xlarge, PostgreSQL 14.5), so actual capacity is likely higher. Reads and writes share one coefficient: at the same adapter version, read-only YCSB-C was not faster than 50%-update YCSB-A.
* Log-broker throughput (capacityStreamMiBPerVcpuSecond 20 at 0.5 utilization, 4 GiB RAM per vCPU) is provider-documented by Google Managed Service for Apache Kafka sizing ([https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size](https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size)): write-equivalent bytes are replicated writes plus a quarter of reads. Producer batches below 10 KB lower per-CPU throughput; that penalty is not modeled.
* Disk utilization 0.8 is provider-documented headroom below Cloud SQL automatic storage increase, which triggers near 91-95% full ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)). The 20 GiB reserve exceeds PostgreSQL's 1 GB default max\_wal\_size; the remainder of that reserve is unmeasured.
* CPU tiers, 4 GiB per vCPU, at most 6.5 GiB per vCPU, 96 vCPU and 65,536 GiB disk follow Cloud SQL Enterprise custom machine limits (provider-documented, same page); 624 GiB is 96 × 6.5. Targets billed per node, unit or throughput unit are sized by their backend instead.
* No public evidence: peak/mean work (2) and the RAM working-set fraction (0.1). Proposed measurements: the p99 one-minute rate over the monthly mean from customer CloudWatch metrics; the buffer hit ratio while stepping RAM under a fixed YCSB-B load.
* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.
* The operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
* Secret Manager pricing: [https://cloud.google.com/secret-manager/pricing](https://cloud.google.com/secret-manager/pricing)
* AWS Secrets Manager price list (AWS Price List API): [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSSecretsManager/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSSecretsManager/current/us-east-1/index.json)

Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied.

Excluded costs and workload features:

* Free allowances, committed discounts, credits, taxes and negotiated rates.
* Commercial Tensor9 fees and operations labor unless entered separately.
* Regional replication, customer-managed KMS, source free allowances and rotation functions.
* Taxes, discounts, credits and free-tier allowances unless explicitly reflected in edited rates.
* Unmodeled dependent services, task execution and operations outside the selected workload family.

List prices read: 2026-10-22. Model: `plan-96b1d4e954b801d96ec02f26bbb527e1c9945239` / `2026-10-22.planning.2`. Curve: `workload-2`.

Sources: [Secret Manager pricing](https://cloud.google.com/secret-manager/pricing), [AWS Secrets Manager price list (AWS Price List API)](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSSecretsManager/current/us-east-1/index.json).

See the [service catalog](/byoc/service-adapters/catalog.md) for operation coverage, supported directions and backend limitations.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.