> ## 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.

# PostgreSQL Flexible Server costs

> Compare PostgreSQL Flexible Server backend choices using explicit service-adapter planning assumptions.

Tensor9 BYOC planning comparisons for `azure::1.0.0::postgresql::flexible`, 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).

## Azure PostgreSQL Flexible Server → Cloud SQL for PostgreSQL

Origin API: `azure::1.0.0::postgresql::flexible`. Target backend: `google::1.0.0::cloudsql::postgresql`.

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

### Azure PostgreSQL Flexible Server · Primary allocated compute

Estimated monthly service charges by Primary allocated compute. Adapter hosting and Tensor9 fees are excluded. Source: eastus; target: us-central1; currency: USD.

![Azure PostgreSQL Flexible Server · Primary allocated compute: monthly service charges by Primary allocated compute. Exact values are in the following table.](/images/diagrams/service-cost/e5bd66792a6c14f1e3ff232660c37c9ddebbdb84df2fe0e57bbd9a3175018d7b-light.svg)

![Azure PostgreSQL Flexible Server · Primary allocated compute: monthly service charges by Primary allocated compute. Exact values are in the following table.](/images/diagrams/service-cost/ea8e5887f6cff588075b9b52b2037a5b14805a1bbd22c0a68bb4cf67a695cc71-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.

| Primary allocated compute (vCPU-hours/month) | PostgreSQL Flexible Server | Target scenario | Cloud SQL for PostgreSQL | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | Cloud SQL for PostgreSQL (one copy) | 118.178 | 118.178 |
| 0 | 0 | Cloud SQL for PostgreSQL (two copies) | 236.356 | 236.356 |
| 1460 | 129.94 | Cloud SQL for PostgreSQL (one copy) | 118.178 | -11.762 |
| 1460 | 129.94 | Cloud SQL for PostgreSQL (two copies) | 236.356 | 106.416 |
| 2920 | 259.88 | Cloud SQL for PostgreSQL (one copy) | 219.356 | -40.524 |
| 2920 | 259.88 | Cloud SQL for PostgreSQL (two copies) | 438.712 | 178.832 |
| 5840 | 519.76 | Cloud SQL for PostgreSQL (one copy) | 421.712 | -98.048 |
| 5840 | 519.76 | Cloud SQL for PostgreSQL (two copies) | 843.424 | 323.664 |
| 11680 | 1039.52 | Cloud SQL for PostgreSQL (one copy) | 826.424 | -213.096 |
| 11680 | 1039.52 | Cloud SQL for PostgreSQL (two copies) | 1652.848 | 613.328 |
| 23360 | 2079.04 | Cloud SQL for PostgreSQL (one copy) | 1635.848 | -443.192 |
| 23360 | 2079.04 | Cloud SQL for PostgreSQL (two copies) | 3271.696 | 1192.656 |
| 46720 | 4158.08 | Cloud SQL for PostgreSQL (one copy) | 3254.696 | -903.384 |
| 46720 | 4158.08 | Cloud SQL for PostgreSQL (two copies) | 6509.392 | 2351.312 |

**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 vCPU-hours/month / Cloud SQL for PostgreSQL (one copy) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 0 vCPU-hours/month / Cloud SQL for PostgreSQL (two copies) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1460 vCPU-hours/month / Cloud SQL for PostgreSQL (one copy) | PlanningAssumption | 0 / 0 | 2 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1460 vCPU-hours/month / Cloud SQL for PostgreSQL (two copies) | PlanningAssumption | 0 / 0 | 2 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 2920 vCPU-hours/month / Cloud SQL for PostgreSQL (one copy) | PlanningAssumption | 0 / 0 | 4 | 4 | 16 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 2920 vCPU-hours/month / Cloud SQL for PostgreSQL (two copies) | PlanningAssumption | 0 / 0 | 4 | 4 | 16 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 5840 vCPU-hours/month / Cloud SQL for PostgreSQL (one copy) | PlanningAssumption | 0 / 0 | 8 | 8 | 32 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 5840 vCPU-hours/month / Cloud SQL for PostgreSQL (two copies) | PlanningAssumption | 0 / 0 | 8 | 8 | 32 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 11680 vCPU-hours/month / Cloud SQL for PostgreSQL (one copy) | PlanningAssumption | 0 / 0 | 16 | 16 | 64 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 11680 vCPU-hours/month / Cloud SQL for PostgreSQL (two copies) | PlanningAssumption | 0 / 0 | 16 | 16 | 64 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 23360 vCPU-hours/month / Cloud SQL for PostgreSQL (one copy) | PlanningAssumption | 0 / 0 | 32 | 32 | 128 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 23360 vCPU-hours/month / Cloud SQL for PostgreSQL (two copies) | PlanningAssumption | 0 / 0 | 32 | 32 | 128 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 46720 vCPU-hours/month / Cloud SQL for PostgreSQL (one copy) | PlanningAssumption | 0 / 0 | 64 | 64 | 256 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 46720 vCPU-hours/month / Cloud SQL for PostgreSQL (two copies) | PlanningAssumption | 0 / 0 | 64 | 64 | 256 | 100 | 0 | `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 workload family already selected resource-hours; the throughput coefficient is not applied again.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Cloud SQL for PostgreSQL (one copy) | Origin list price · Primary compute | 0.089 | USD/vCPU-hours |
| Cloud SQL for PostgreSQL (one copy) | Origin list price · Primary memory | 0 | USD/GiB-hours |
| Cloud SQL for PostgreSQL (one copy) | Origin list price · Primary provisioned storage | 0.115 | USD/GiB-month |
| Cloud SQL for PostgreSQL (one copy) | Origin list price · Database reads | 0 | USD/operations |
| Cloud SQL for PostgreSQL (one copy) | Origin list price · Database writes | 0 | USD/operations |
| Cloud SQL for PostgreSQL (one copy) | Target CPU / source CPU | 1 | multiplier |
| Cloud SQL for PostgreSQL (one copy) | Target RAM / source RAM | 1 | multiplier |
| Cloud SQL for PostgreSQL (one copy) | Target disk / source disk | 1 | multiplier |
| Cloud SQL for PostgreSQL (one copy) | Target price guess · read | 0 | USD/read |
| Cloud SQL for PostgreSQL (one copy) | Target price guess · write | 0 | USD/write |
| Cloud SQL for PostgreSQL (one copy) | Target price guess · provider operation | 0 | USD/provider operation |
| Cloud SQL for PostgreSQL (one copy) | Target list price · GiB-month | 0.17 | USD/GiB-month |
| Cloud SQL for PostgreSQL (one copy) | Target price guess · published GiB | 0 | USD/published GiB |
| Cloud SQL for PostgreSQL (one copy) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Cloud SQL for PostgreSQL (one copy) | Target list price · network GiB | 0.19 | USD/network GiB |
| Cloud SQL for PostgreSQL (one copy) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Cloud SQL for PostgreSQL (one copy) | Target list price · vCPU-hour | 0.0413 | USD/vCPU-hour |
| Cloud SQL for PostgreSQL (one copy) | Target list price · GiB-hour | 0.007 | USD/GiB-hour |
| Cloud SQL for PostgreSQL (one copy) | Target price guess · resource-hour | 0 | USD/resource-hour |
| Cloud SQL for PostgreSQL (one copy) | Target price guess · resource-month | 0 | USD/resource-month |
| Cloud SQL for PostgreSQL (one copy) | Target price guess · input token | 0 | USD/input token |
| Cloud SQL for PostgreSQL (one copy) | Target price guess · output token | 0 | USD/output token |
| Cloud SQL for PostgreSQL (one copy) | Target monthly base charge | 0 | USD/month |
| Cloud SQL for PostgreSQL (one copy) | Target service minimum | 9.365 | USD/month |
| Cloud SQL for PostgreSQL (one copy) | Minimum primary CPU | 2 | vCPU |
| Cloud SQL for PostgreSQL (one copy) | Minimum primary RAM | 8 | GiB |
| Cloud SQL for PostgreSQL (one copy) | Minimum primary disk | 100 | GiB |
| Cloud SQL for PostgreSQL (one copy) | Additional full-price standby copy | 0 | 0 or 1 |
| Cloud SQL for PostgreSQL (one copy) | Allocated share of provisioned cost | 1 | fraction |
| Cloud SQL for PostgreSQL (one copy) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Cloud SQL for PostgreSQL (one copy) | Planning peak / mean work | 2 | multiplier |
| Cloud SQL for PostgreSQL (one copy) | Planning primary CPU utilization | 0.7 | fraction |
| Cloud SQL for PostgreSQL (one copy) | Resident state reserved in RAM | 0.1 | fraction |
| Cloud SQL for PostgreSQL (one copy) | Planning disk utilization | 0.8 | fraction |
| Cloud SQL for PostgreSQL (one copy) | Maintenance and log disk reserve | 20 | GiB |
| Cloud SQL for PostgreSQL (one copy) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Cloud SQL for PostgreSQL (one copy) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Cloud SQL for PostgreSQL (one copy) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Cloud SQL for PostgreSQL (one copy) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Cloud SQL for PostgreSQL (one copy) | Dependent object sink write price guess | 0.000005 | USD/write |
| Cloud SQL for PostgreSQL (two copies) | Origin list price · Primary compute | 0.089 | USD/vCPU-hours |
| Cloud SQL for PostgreSQL (two copies) | Origin list price · Primary memory | 0 | USD/GiB-hours |
| Cloud SQL for PostgreSQL (two copies) | Origin list price · Primary provisioned storage | 0.115 | USD/GiB-month |
| Cloud SQL for PostgreSQL (two copies) | Origin list price · Database reads | 0 | USD/operations |
| Cloud SQL for PostgreSQL (two copies) | Origin list price · Database writes | 0 | USD/operations |
| Cloud SQL for PostgreSQL (two copies) | Target CPU / source CPU | 1 | multiplier |
| Cloud SQL for PostgreSQL (two copies) | Target RAM / source RAM | 1 | multiplier |
| Cloud SQL for PostgreSQL (two copies) | Target disk / source disk | 1 | multiplier |
| Cloud SQL for PostgreSQL (two copies) | Target price guess · read | 0 | USD/read |
| Cloud SQL for PostgreSQL (two copies) | Target price guess · write | 0 | USD/write |
| Cloud SQL for PostgreSQL (two copies) | Target price guess · provider operation | 0 | USD/provider operation |
| Cloud SQL for PostgreSQL (two copies) | Target list price · GiB-month | 0.17 | USD/GiB-month |
| Cloud SQL for PostgreSQL (two copies) | Target price guess · published GiB | 0 | USD/published GiB |
| Cloud SQL for PostgreSQL (two copies) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Cloud SQL for PostgreSQL (two copies) | Target list price · network GiB | 0.19 | USD/network GiB |
| Cloud SQL for PostgreSQL (two copies) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Cloud SQL for PostgreSQL (two copies) | Target list price · vCPU-hour | 0.0413 | USD/vCPU-hour |
| Cloud SQL for PostgreSQL (two copies) | Target list price · GiB-hour | 0.007 | USD/GiB-hour |
| Cloud SQL for PostgreSQL (two copies) | Target price guess · resource-hour | 0 | USD/resource-hour |
| Cloud SQL for PostgreSQL (two copies) | Target price guess · resource-month | 0 | USD/resource-month |
| Cloud SQL for PostgreSQL (two copies) | Target price guess · input token | 0 | USD/input token |
| Cloud SQL for PostgreSQL (two copies) | Target price guess · output token | 0 | USD/output token |
| Cloud SQL for PostgreSQL (two copies) | Target monthly base charge | 0 | USD/month |
| Cloud SQL for PostgreSQL (two copies) | Target service minimum | 9.365 | USD/month |
| Cloud SQL for PostgreSQL (two copies) | Minimum primary CPU | 2 | vCPU |
| Cloud SQL for PostgreSQL (two copies) | Minimum primary RAM | 8 | GiB |
| Cloud SQL for PostgreSQL (two copies) | Minimum primary disk | 100 | GiB |
| Cloud SQL for PostgreSQL (two copies) | Additional full-price standby copy | 1 | 0 or 1 |
| Cloud SQL for PostgreSQL (two copies) | Allocated share of provisioned cost | 1 | fraction |
| Cloud SQL for PostgreSQL (two copies) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Cloud SQL for PostgreSQL (two copies) | Planning peak / mean work | 2 | multiplier |
| Cloud SQL for PostgreSQL (two copies) | Planning primary CPU utilization | 0.7 | fraction |
| Cloud SQL for PostgreSQL (two copies) | Resident state reserved in RAM | 0.1 | fraction |
| Cloud SQL for PostgreSQL (two copies) | Planning disk utilization | 0.8 | fraction |
| Cloud SQL for PostgreSQL (two copies) | Maintenance and log disk reserve | 20 | GiB |
| Cloud SQL for PostgreSQL (two copies) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Cloud SQL for PostgreSQL (two copies) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Cloud SQL for PostgreSQL (two copies) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Cloud SQL for PostgreSQL (two copies) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Cloud SQL for PostgreSQL (two copies) | Dependent object sink write price guess | 0.000005 | USD/write |

* CPU allocation does not imply an achieved transaction rate. 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. eastus → us-central1, 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.
* Authored planning assumptions, not measured adapter capacity. Origin rates are cited first-tier list prices, before free allowances and discounts.
* A cost scenario does not establish backend availability, protocol fidelity or production readiness. Registry serving status remains independent.
* Provisioned compute and RAM are priced by resource-hour; operations are independently authored. Database size cannot be inferred from dollars alone.
* Aurora/AlloyDB, MySQL/PostgreSQL and proxied targets retain their distinct backend contracts. HA, replicas and proxy allocations must be selected explicitly.
* Flexible Server memory is included in the vCore price; the memory meter is zero so RAM is not counted twice.
* Cloud SQL Enterprise edition (PostgreSQL) publishes separate vCPU, memory and SSD prices for zonal instances; a high-availability (regional) instance bills exactly twice each, which the standby copy reproduces. Enterprise Plus, committed-use discounts, backups (USD 0.08 per GiB-month) and idle IPv4 addresses (0.01 per hour) are not selected.
* 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 workload family already selected resource-hours; the throughput coefficient is not applied again.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
* Azure Retail Prices API: [https://prices.azure.com/api/retail/prices](https://prices.azure.com/api/retail/prices)
* Cloud SQL pricing: [https://cloud.google.com/sql/pricing](https://cloud.google.com/sql/pricing)

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

Excluded costs and workload features:

* Additional network transfer, backups, KMS, one-time migration and operational labor unless an explicit meter includes them.
* Destination application execution and separately billed downstream services; supply those allocations separately.
* Aurora per-IO, serverless-capacity, backup and proxy tariffs; reserved/committed-use purchase options.
* 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-e81f3684e920720bc27e54a724e4a40dc4260a41` / `2026-10-22.planning.2`. Curve: `workload-1`.

Sources: [Azure Retail Prices API](https://prices.azure.com/api/retail/prices), [Cloud SQL pricing](https://cloud.google.com/sql/pricing).

### Azure PostgreSQL Flexible Server · Stored data

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

![Azure PostgreSQL Flexible Server · Stored data: monthly service charges by Stored data. Exact values are in the following table.](/images/diagrams/service-cost/d7266719d0745133b9e1928304c9f62df24a928e7bf276b8e37eeb624b2f7f24-light.svg)

![Azure PostgreSQL Flexible Server · Stored data: monthly service charges by Stored data. Exact values are in the following table.](/images/diagrams/service-cost/3fd302dc087ef6e92545b994dae64270748764591c08300b5089a2f1d9432512-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.

| Stored data (GiB-month) | PostgreSQL Flexible Server | Target scenario | Cloud SQL for PostgreSQL | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | Cloud SQL for PostgreSQL (one copy) | 118.178 | 118.178 |
| 0 | 0 | Cloud SQL for PostgreSQL (two copies) | 236.356 | 236.356 |
| 10 | 1.15 | Cloud SQL for PostgreSQL (one copy) | 118.178 | 117.028 |
| 10 | 1.15 | Cloud SQL for PostgreSQL (two copies) | 236.356 | 235.206 |
| 100 | 11.5 | Cloud SQL for PostgreSQL (one copy) | 136.898 | 125.398 |
| 100 | 11.5 | Cloud SQL for PostgreSQL (two copies) | 273.796 | 262.296 |
| 1000 | 115 | Cloud SQL for PostgreSQL (one copy) | 1210.134 | 1095.134 |
| 1000 | 115 | Cloud SQL for PostgreSQL (two copies) | 2420.268 | 2305.268 |
| 10000 | 1150 | Cloud SQL for PostgreSQL (one copy) | Unpriced | Unavailable |
| 10000 | 1150 | Cloud SQL for PostgreSQL (two copies) | Unpriced | Unavailable |
| 100000 | 11500 | Cloud SQL for PostgreSQL (one copy) | Unpriced | Unavailable |
| 100000 | 11500 | Cloud SQL for PostgreSQL (two copies) | Unpriced | Unavailable |

**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 GiB-month / Cloud SQL for PostgreSQL (one copy) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 0 GiB-month / Cloud SQL for PostgreSQL (two copies) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10 GiB-month / Cloud SQL for PostgreSQL (one copy) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 10 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10 GiB-month / Cloud SQL for PostgreSQL (two copies) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 10 | `service-adapter-planning-2026-10-22.1` | None reported |
| 100 GiB-month / Cloud SQL for PostgreSQL (one copy) | PlanningAssumption | 0 / 0 | 0 | 2 | 10 | 150 | 100 | `service-adapter-planning-2026-10-22.1` | None reported |
| 100 GiB-month / Cloud SQL for PostgreSQL (two copies) | PlanningAssumption | 0 / 0 | 0 | 2 | 10 | 150 | 100 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1000 GiB-month / Cloud SQL for PostgreSQL (one copy) | PlanningAssumption | 0 / 0 | 0 | 16 | 100 | 1275 | 1000 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1000 GiB-month / Cloud SQL for PostgreSQL (two copies) | PlanningAssumption | 0 / 0 | 0 | 16 | 100 | 1275 | 1000 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10000 GiB-month / Cloud SQL for PostgreSQL (one copy) | Unpriced | 0 / 0 | 0 | Unpriced | Unpriced | Unpriced | 10000 | `service-adapter-planning-2026-10-22.1` | Demand exceeds the planning model's joint CPU/RAM allocation bounds (96 vCPU, 624 GiB RAM). |
| 10000 GiB-month / Cloud SQL for PostgreSQL (two copies) | Unpriced | 0 / 0 | 0 | Unpriced | Unpriced | Unpriced | 10000 | `service-adapter-planning-2026-10-22.1` | Demand exceeds the planning model's joint CPU/RAM allocation bounds (96 vCPU, 624 GiB RAM). |
| 100000 GiB-month / Cloud SQL for PostgreSQL (one copy) | Unpriced | 0 / 0 | 0 | Unpriced | Unpriced | Unpriced | 100000 | `service-adapter-planning-2026-10-22.1` | Demand exceeds the planning model's joint CPU/RAM allocation bounds (96 vCPU, 624 GiB RAM).; Required disk exceeds the planning model's 65,536 GiB bound. |
| 100000 GiB-month / Cloud SQL for PostgreSQL (two copies) | Unpriced | 0 / 0 | 0 | Unpriced | Unpriced | Unpriced | 100000 | `service-adapter-planning-2026-10-22.1` | Demand exceeds the planning model's joint CPU/RAM allocation bounds (96 vCPU, 624 GiB RAM).; Required disk exceeds the planning model's 65,536 GiB bound. |

* 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 workload family already selected resource-hours; the throughput coefficient is not applied again.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Cloud SQL for PostgreSQL (one copy) | Origin list price · Primary compute | 0.089 | USD/vCPU-hours |
| Cloud SQL for PostgreSQL (one copy) | Origin list price · Primary memory | 0 | USD/GiB-hours |
| Cloud SQL for PostgreSQL (one copy) | Origin list price · Primary provisioned storage | 0.115 | USD/GiB-month |
| Cloud SQL for PostgreSQL (one copy) | Origin list price · Database reads | 0 | USD/operations |
| Cloud SQL for PostgreSQL (one copy) | Origin list price · Database writes | 0 | USD/operations |
| Cloud SQL for PostgreSQL (one copy) | Target CPU / source CPU | 1 | multiplier |
| Cloud SQL for PostgreSQL (one copy) | Target RAM / source RAM | 1 | multiplier |
| Cloud SQL for PostgreSQL (one copy) | Target disk / source disk | 1 | multiplier |
| Cloud SQL for PostgreSQL (one copy) | Target price guess · read | 0 | USD/read |
| Cloud SQL for PostgreSQL (one copy) | Target price guess · write | 0 | USD/write |
| Cloud SQL for PostgreSQL (one copy) | Target price guess · provider operation | 0 | USD/provider operation |
| Cloud SQL for PostgreSQL (one copy) | Target list price · GiB-month | 0.17 | USD/GiB-month |
| Cloud SQL for PostgreSQL (one copy) | Target price guess · published GiB | 0 | USD/published GiB |
| Cloud SQL for PostgreSQL (one copy) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Cloud SQL for PostgreSQL (one copy) | Target list price · network GiB | 0.19 | USD/network GiB |
| Cloud SQL for PostgreSQL (one copy) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Cloud SQL for PostgreSQL (one copy) | Target list price · vCPU-hour | 0.0413 | USD/vCPU-hour |
| Cloud SQL for PostgreSQL (one copy) | Target list price · GiB-hour | 0.007 | USD/GiB-hour |
| Cloud SQL for PostgreSQL (one copy) | Target price guess · resource-hour | 0 | USD/resource-hour |
| Cloud SQL for PostgreSQL (one copy) | Target price guess · resource-month | 0 | USD/resource-month |
| Cloud SQL for PostgreSQL (one copy) | Target price guess · input token | 0 | USD/input token |
| Cloud SQL for PostgreSQL (one copy) | Target price guess · output token | 0 | USD/output token |
| Cloud SQL for PostgreSQL (one copy) | Target monthly base charge | 0 | USD/month |
| Cloud SQL for PostgreSQL (one copy) | Target service minimum | 9.365 | USD/month |
| Cloud SQL for PostgreSQL (one copy) | Minimum primary CPU | 2 | vCPU |
| Cloud SQL for PostgreSQL (one copy) | Minimum primary RAM | 8 | GiB |
| Cloud SQL for PostgreSQL (one copy) | Minimum primary disk | 100 | GiB |
| Cloud SQL for PostgreSQL (one copy) | Additional full-price standby copy | 0 | 0 or 1 |
| Cloud SQL for PostgreSQL (one copy) | Allocated share of provisioned cost | 1 | fraction |
| Cloud SQL for PostgreSQL (one copy) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Cloud SQL for PostgreSQL (one copy) | Planning peak / mean work | 2 | multiplier |
| Cloud SQL for PostgreSQL (one copy) | Planning primary CPU utilization | 0.7 | fraction |
| Cloud SQL for PostgreSQL (one copy) | Resident state reserved in RAM | 0.1 | fraction |
| Cloud SQL for PostgreSQL (one copy) | Planning disk utilization | 0.8 | fraction |
| Cloud SQL for PostgreSQL (one copy) | Maintenance and log disk reserve | 20 | GiB |
| Cloud SQL for PostgreSQL (one copy) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Cloud SQL for PostgreSQL (one copy) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Cloud SQL for PostgreSQL (one copy) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Cloud SQL for PostgreSQL (one copy) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Cloud SQL for PostgreSQL (one copy) | Dependent object sink write price guess | 0.000005 | USD/write |
| Cloud SQL for PostgreSQL (two copies) | Origin list price · Primary compute | 0.089 | USD/vCPU-hours |
| Cloud SQL for PostgreSQL (two copies) | Origin list price · Primary memory | 0 | USD/GiB-hours |
| Cloud SQL for PostgreSQL (two copies) | Origin list price · Primary provisioned storage | 0.115 | USD/GiB-month |
| Cloud SQL for PostgreSQL (two copies) | Origin list price · Database reads | 0 | USD/operations |
| Cloud SQL for PostgreSQL (two copies) | Origin list price · Database writes | 0 | USD/operations |
| Cloud SQL for PostgreSQL (two copies) | Target CPU / source CPU | 1 | multiplier |
| Cloud SQL for PostgreSQL (two copies) | Target RAM / source RAM | 1 | multiplier |
| Cloud SQL for PostgreSQL (two copies) | Target disk / source disk | 1 | multiplier |
| Cloud SQL for PostgreSQL (two copies) | Target price guess · read | 0 | USD/read |
| Cloud SQL for PostgreSQL (two copies) | Target price guess · write | 0 | USD/write |
| Cloud SQL for PostgreSQL (two copies) | Target price guess · provider operation | 0 | USD/provider operation |
| Cloud SQL for PostgreSQL (two copies) | Target list price · GiB-month | 0.17 | USD/GiB-month |
| Cloud SQL for PostgreSQL (two copies) | Target price guess · published GiB | 0 | USD/published GiB |
| Cloud SQL for PostgreSQL (two copies) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Cloud SQL for PostgreSQL (two copies) | Target list price · network GiB | 0.19 | USD/network GiB |
| Cloud SQL for PostgreSQL (two copies) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Cloud SQL for PostgreSQL (two copies) | Target list price · vCPU-hour | 0.0413 | USD/vCPU-hour |
| Cloud SQL for PostgreSQL (two copies) | Target list price · GiB-hour | 0.007 | USD/GiB-hour |
| Cloud SQL for PostgreSQL (two copies) | Target price guess · resource-hour | 0 | USD/resource-hour |
| Cloud SQL for PostgreSQL (two copies) | Target price guess · resource-month | 0 | USD/resource-month |
| Cloud SQL for PostgreSQL (two copies) | Target price guess · input token | 0 | USD/input token |
| Cloud SQL for PostgreSQL (two copies) | Target price guess · output token | 0 | USD/output token |
| Cloud SQL for PostgreSQL (two copies) | Target monthly base charge | 0 | USD/month |
| Cloud SQL for PostgreSQL (two copies) | Target service minimum | 9.365 | USD/month |
| Cloud SQL for PostgreSQL (two copies) | Minimum primary CPU | 2 | vCPU |
| Cloud SQL for PostgreSQL (two copies) | Minimum primary RAM | 8 | GiB |
| Cloud SQL for PostgreSQL (two copies) | Minimum primary disk | 100 | GiB |
| Cloud SQL for PostgreSQL (two copies) | Additional full-price standby copy | 1 | 0 or 1 |
| Cloud SQL for PostgreSQL (two copies) | Allocated share of provisioned cost | 1 | fraction |
| Cloud SQL for PostgreSQL (two copies) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Cloud SQL for PostgreSQL (two copies) | Planning peak / mean work | 2 | multiplier |
| Cloud SQL for PostgreSQL (two copies) | Planning primary CPU utilization | 0.7 | fraction |
| Cloud SQL for PostgreSQL (two copies) | Resident state reserved in RAM | 0.1 | fraction |
| Cloud SQL for PostgreSQL (two copies) | Planning disk utilization | 0.8 | fraction |
| Cloud SQL for PostgreSQL (two copies) | Maintenance and log disk reserve | 20 | GiB |
| Cloud SQL for PostgreSQL (two copies) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Cloud SQL for PostgreSQL (two copies) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Cloud SQL for PostgreSQL (two copies) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Cloud SQL for PostgreSQL (two copies) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Cloud SQL for PostgreSQL (two copies) | Dependent object sink write price guess | 0.000005 | USD/write |

* Request meters remain at their independently authored 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. eastus → us-central1, 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.
* Authored planning assumptions, not measured adapter capacity. Origin rates are cited first-tier list prices, before free allowances and discounts.
* A cost scenario does not establish backend availability, protocol fidelity or production readiness. Registry serving status remains independent.
* Provisioned compute and RAM are priced by resource-hour; operations are independently authored. Database size cannot be inferred from dollars alone.
* Aurora/AlloyDB, MySQL/PostgreSQL and proxied targets retain their distinct backend contracts. HA, replicas and proxy allocations must be selected explicitly.
* Flexible Server memory is included in the vCore price; the memory meter is zero so RAM is not counted twice.
* Cloud SQL Enterprise edition (PostgreSQL) publishes separate vCPU, memory and SSD prices for zonal instances; a high-availability (regional) instance bills exactly twice each, which the standby copy reproduces. Enterprise Plus, committed-use discounts, backups (USD 0.08 per GiB-month) and idle IPv4 addresses (0.01 per hour) are not selected.
* 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 workload family already selected resource-hours; the throughput coefficient is not applied again.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
* Azure Retail Prices API: [https://prices.azure.com/api/retail/prices](https://prices.azure.com/api/retail/prices)
* Cloud SQL pricing: [https://cloud.google.com/sql/pricing](https://cloud.google.com/sql/pricing)

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

Excluded costs and workload features:

* Additional network transfer, backups, KMS, one-time migration and operational labor unless an explicit meter includes them.
* Destination application execution and separately billed downstream services; supply those allocations separately.
* Aurora per-IO, serverless-capacity, backup and proxy tariffs; reserved/committed-use purchase options.
* 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-e81f3684e920720bc27e54a724e4a40dc4260a41` / `2026-10-22.planning.2`. Curve: `workload-2`.

Sources: [Azure Retail Prices API](https://prices.azure.com/api/retail/prices), [Cloud SQL pricing](https://cloud.google.com/sql/pricing).

### Azure PostgreSQL Flexible Server · Database writes

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

![Azure PostgreSQL Flexible Server · Database writes: monthly service charges by Database writes. Exact values are in the following table.](/images/diagrams/service-cost/69e982114b28bbed3e1c762dde995acfa1d573d7a18a76d565d2d2435cbff825-light.svg)

![Azure PostgreSQL Flexible Server · Database writes: monthly service charges by Database writes. Exact values are in the following table.](/images/diagrams/service-cost/41cea4369151977bfe2df4ea8c8a338aebf982fe1a1b44fc8b8ee77593ad228f-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.

| Database writes (per second) | PostgreSQL Flexible Server | Target scenario | Cloud SQL for PostgreSQL | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | Cloud SQL for PostgreSQL (one copy) | 118.178 | 118.178 |
| 0 | 0 | Cloud SQL for PostgreSQL (two copies) | 236.356 | 236.356 |
| 1 | 0 | Cloud SQL for PostgreSQL (one copy) | 118.178 | 118.178 |
| 1 | 0 | Cloud SQL for PostgreSQL (two copies) | 236.356 | 236.356 |
| 10 | 0 | Cloud SQL for PostgreSQL (one copy) | 118.178 | 118.178 |
| 10 | 0 | Cloud SQL for PostgreSQL (two copies) | 236.356 | 236.356 |
| 100 | 0 | Cloud SQL for PostgreSQL (one copy) | 118.178 | 118.178 |
| 100 | 0 | Cloud SQL for PostgreSQL (two copies) | 236.356 | 236.356 |
| 1000 | 0 | Cloud SQL for PostgreSQL (one copy) | 118.178 | 118.178 |
| 1000 | 0 | Cloud SQL for PostgreSQL (two copies) | 236.356 | 236.356 |
| 10000 | 0 | Cloud SQL for PostgreSQL (one copy) | 118.178 | 118.178 |
| 10000 | 0 | Cloud SQL for PostgreSQL (two copies) | 236.356 | 236.356 |

**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 per second / Cloud SQL for PostgreSQL (one copy) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 0 per second / Cloud SQL for PostgreSQL (two copies) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1 per second / Cloud SQL for PostgreSQL (one copy) | PlanningAssumption | 1 / 2 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1 per second / Cloud SQL for PostgreSQL (two copies) | PlanningAssumption | 1 / 2 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10 per second / Cloud SQL for PostgreSQL (one copy) | PlanningAssumption | 10 / 20 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10 per second / Cloud SQL for PostgreSQL (two copies) | PlanningAssumption | 10 / 20 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 100 per second / Cloud SQL for PostgreSQL (one copy) | PlanningAssumption | 100 / 200 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 100 per second / Cloud SQL for PostgreSQL (two copies) | PlanningAssumption | 100 / 200 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1000 per second / Cloud SQL for PostgreSQL (one copy) | PlanningAssumption | 1000 / 2000 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1000 per second / Cloud SQL for PostgreSQL (two copies) | PlanningAssumption | 1000 / 2000 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10000 per second / Cloud SQL for PostgreSQL (one copy) | PlanningAssumption | 10000 / 20000 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10000 per second / Cloud SQL for PostgreSQL (two copies) | PlanningAssumption | 10000 / 20000 | 0 | 2 | 8 | 100 | 0 | `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 workload family already selected resource-hours; the throughput coefficient is not applied again.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Cloud SQL for PostgreSQL (one copy) | Origin list price · Primary compute | 0.089 | USD/vCPU-hours |
| Cloud SQL for PostgreSQL (one copy) | Origin list price · Primary memory | 0 | USD/GiB-hours |
| Cloud SQL for PostgreSQL (one copy) | Origin list price · Primary provisioned storage | 0.115 | USD/GiB-month |
| Cloud SQL for PostgreSQL (one copy) | Origin list price · Database reads | 0 | USD/operations |
| Cloud SQL for PostgreSQL (one copy) | Origin list price · Database writes | 0 | USD/operations |
| Cloud SQL for PostgreSQL (one copy) | Target CPU / source CPU | 1 | multiplier |
| Cloud SQL for PostgreSQL (one copy) | Target RAM / source RAM | 1 | multiplier |
| Cloud SQL for PostgreSQL (one copy) | Target disk / source disk | 1 | multiplier |
| Cloud SQL for PostgreSQL (one copy) | Target price guess · read | 0 | USD/read |
| Cloud SQL for PostgreSQL (one copy) | Target price guess · write | 0 | USD/write |
| Cloud SQL for PostgreSQL (one copy) | Target price guess · provider operation | 0 | USD/provider operation |
| Cloud SQL for PostgreSQL (one copy) | Target list price · GiB-month | 0.17 | USD/GiB-month |
| Cloud SQL for PostgreSQL (one copy) | Target price guess · published GiB | 0 | USD/published GiB |
| Cloud SQL for PostgreSQL (one copy) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Cloud SQL for PostgreSQL (one copy) | Target list price · network GiB | 0.19 | USD/network GiB |
| Cloud SQL for PostgreSQL (one copy) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Cloud SQL for PostgreSQL (one copy) | Target list price · vCPU-hour | 0.0413 | USD/vCPU-hour |
| Cloud SQL for PostgreSQL (one copy) | Target list price · GiB-hour | 0.007 | USD/GiB-hour |
| Cloud SQL for PostgreSQL (one copy) | Target price guess · resource-hour | 0 | USD/resource-hour |
| Cloud SQL for PostgreSQL (one copy) | Target price guess · resource-month | 0 | USD/resource-month |
| Cloud SQL for PostgreSQL (one copy) | Target price guess · input token | 0 | USD/input token |
| Cloud SQL for PostgreSQL (one copy) | Target price guess · output token | 0 | USD/output token |
| Cloud SQL for PostgreSQL (one copy) | Target monthly base charge | 0 | USD/month |
| Cloud SQL for PostgreSQL (one copy) | Target service minimum | 9.365 | USD/month |
| Cloud SQL for PostgreSQL (one copy) | Minimum primary CPU | 2 | vCPU |
| Cloud SQL for PostgreSQL (one copy) | Minimum primary RAM | 8 | GiB |
| Cloud SQL for PostgreSQL (one copy) | Minimum primary disk | 100 | GiB |
| Cloud SQL for PostgreSQL (one copy) | Additional full-price standby copy | 0 | 0 or 1 |
| Cloud SQL for PostgreSQL (one copy) | Allocated share of provisioned cost | 1 | fraction |
| Cloud SQL for PostgreSQL (one copy) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Cloud SQL for PostgreSQL (one copy) | Planning peak / mean work | 2 | multiplier |
| Cloud SQL for PostgreSQL (one copy) | Planning primary CPU utilization | 0.7 | fraction |
| Cloud SQL for PostgreSQL (one copy) | Resident state reserved in RAM | 0.1 | fraction |
| Cloud SQL for PostgreSQL (one copy) | Planning disk utilization | 0.8 | fraction |
| Cloud SQL for PostgreSQL (one copy) | Maintenance and log disk reserve | 20 | GiB |
| Cloud SQL for PostgreSQL (one copy) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Cloud SQL for PostgreSQL (one copy) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Cloud SQL for PostgreSQL (one copy) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Cloud SQL for PostgreSQL (one copy) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Cloud SQL for PostgreSQL (one copy) | Dependent object sink write price guess | 0.000005 | USD/write |
| Cloud SQL for PostgreSQL (two copies) | Origin list price · Primary compute | 0.089 | USD/vCPU-hours |
| Cloud SQL for PostgreSQL (two copies) | Origin list price · Primary memory | 0 | USD/GiB-hours |
| Cloud SQL for PostgreSQL (two copies) | Origin list price · Primary provisioned storage | 0.115 | USD/GiB-month |
| Cloud SQL for PostgreSQL (two copies) | Origin list price · Database reads | 0 | USD/operations |
| Cloud SQL for PostgreSQL (two copies) | Origin list price · Database writes | 0 | USD/operations |
| Cloud SQL for PostgreSQL (two copies) | Target CPU / source CPU | 1 | multiplier |
| Cloud SQL for PostgreSQL (two copies) | Target RAM / source RAM | 1 | multiplier |
| Cloud SQL for PostgreSQL (two copies) | Target disk / source disk | 1 | multiplier |
| Cloud SQL for PostgreSQL (two copies) | Target price guess · read | 0 | USD/read |
| Cloud SQL for PostgreSQL (two copies) | Target price guess · write | 0 | USD/write |
| Cloud SQL for PostgreSQL (two copies) | Target price guess · provider operation | 0 | USD/provider operation |
| Cloud SQL for PostgreSQL (two copies) | Target list price · GiB-month | 0.17 | USD/GiB-month |
| Cloud SQL for PostgreSQL (two copies) | Target price guess · published GiB | 0 | USD/published GiB |
| Cloud SQL for PostgreSQL (two copies) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Cloud SQL for PostgreSQL (two copies) | Target list price · network GiB | 0.19 | USD/network GiB |
| Cloud SQL for PostgreSQL (two copies) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Cloud SQL for PostgreSQL (two copies) | Target list price · vCPU-hour | 0.0413 | USD/vCPU-hour |
| Cloud SQL for PostgreSQL (two copies) | Target list price · GiB-hour | 0.007 | USD/GiB-hour |
| Cloud SQL for PostgreSQL (two copies) | Target price guess · resource-hour | 0 | USD/resource-hour |
| Cloud SQL for PostgreSQL (two copies) | Target price guess · resource-month | 0 | USD/resource-month |
| Cloud SQL for PostgreSQL (two copies) | Target price guess · input token | 0 | USD/input token |
| Cloud SQL for PostgreSQL (two copies) | Target price guess · output token | 0 | USD/output token |
| Cloud SQL for PostgreSQL (two copies) | Target monthly base charge | 0 | USD/month |
| Cloud SQL for PostgreSQL (two copies) | Target service minimum | 9.365 | USD/month |
| Cloud SQL for PostgreSQL (two copies) | Minimum primary CPU | 2 | vCPU |
| Cloud SQL for PostgreSQL (two copies) | Minimum primary RAM | 8 | GiB |
| Cloud SQL for PostgreSQL (two copies) | Minimum primary disk | 100 | GiB |
| Cloud SQL for PostgreSQL (two copies) | Additional full-price standby copy | 1 | 0 or 1 |
| Cloud SQL for PostgreSQL (two copies) | Allocated share of provisioned cost | 1 | fraction |
| Cloud SQL for PostgreSQL (two copies) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Cloud SQL for PostgreSQL (two copies) | Planning peak / mean work | 2 | multiplier |
| Cloud SQL for PostgreSQL (two copies) | Planning primary CPU utilization | 0.7 | fraction |
| Cloud SQL for PostgreSQL (two copies) | Resident state reserved in RAM | 0.1 | fraction |
| Cloud SQL for PostgreSQL (two copies) | Planning disk utilization | 0.8 | fraction |
| Cloud SQL for PostgreSQL (two copies) | Maintenance and log disk reserve | 20 | GiB |
| Cloud SQL for PostgreSQL (two copies) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Cloud SQL for PostgreSQL (two copies) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Cloud SQL for PostgreSQL (two copies) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Cloud SQL for PostgreSQL (two copies) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Cloud SQL for PostgreSQL (two copies) | Dependent object sink write price guess | 0.000005 | USD/write |

* Source compute and stored data remain independent; a throughput view needs explicit workload inputs. 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. eastus → us-central1, 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.
* Authored planning assumptions, not measured adapter capacity. Origin rates are cited first-tier list prices, before free allowances and discounts.
* A cost scenario does not establish backend availability, protocol fidelity or production readiness. Registry serving status remains independent.
* Provisioned compute and RAM are priced by resource-hour; operations are independently authored. Database size cannot be inferred from dollars alone.
* Aurora/AlloyDB, MySQL/PostgreSQL and proxied targets retain their distinct backend contracts. HA, replicas and proxy allocations must be selected explicitly.
* Flexible Server memory is included in the vCore price; the memory meter is zero so RAM is not counted twice.
* Cloud SQL Enterprise edition (PostgreSQL) publishes separate vCPU, memory and SSD prices for zonal instances; a high-availability (regional) instance bills exactly twice each, which the standby copy reproduces. Enterprise Plus, committed-use discounts, backups (USD 0.08 per GiB-month) and idle IPv4 addresses (0.01 per hour) are not selected.
* 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 workload family already selected resource-hours; the throughput coefficient is not applied again.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
* Azure Retail Prices API: [https://prices.azure.com/api/retail/prices](https://prices.azure.com/api/retail/prices)
* Cloud SQL pricing: [https://cloud.google.com/sql/pricing](https://cloud.google.com/sql/pricing)

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

Excluded costs and workload features:

* Additional network transfer, backups, KMS, one-time migration and operational labor unless an explicit meter includes them.
* Destination application execution and separately billed downstream services; supply those allocations separately.
* Aurora per-IO, serverless-capacity, backup and proxy tariffs; reserved/committed-use purchase options.
* 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-e81f3684e920720bc27e54a724e4a40dc4260a41` / `2026-10-22.planning.2`. Curve: `workload-3`.

Sources: [Azure Retail Prices API](https://prices.azure.com/api/retail/prices), [Cloud SQL pricing](https://cloud.google.com/sql/pricing).

## Azure PostgreSQL Flexible Server → RDS PostgreSQL

Origin API: `azure::1.0.0::postgresql::flexible`. Target backend: `aws::1.0.0::rds::postgresql`.

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

### Azure PostgreSQL Flexible Server · Primary allocated compute

Estimated monthly service charges by Primary allocated compute. Adapter hosting and Tensor9 fees are excluded. Source: eastus; target: us-east-1; currency: USD.

![Azure PostgreSQL Flexible Server · Primary allocated compute: monthly service charges by Primary allocated compute. Exact values are in the following table.](/images/diagrams/service-cost/5e6d6b875a51c995e554c356a4f0741f4c01da4bab66524d2d3a23ffb918eab5-light.svg)

![Azure PostgreSQL Flexible Server · Primary allocated compute: monthly service charges by Primary allocated compute. Exact values are in the following table.](/images/diagrams/service-cost/de2e5f4d5c79dbc57e52615f3457bb8d0fff932e29965f75f648aefe34684c6d-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.

| Primary allocated compute (vCPU-hours/month) | PostgreSQL Flexible Server | Target scenario | RDS PostgreSQL | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | RDS PostgreSQL (one copy) | 141.44 | 141.44 |
| 0 | 0 | RDS PostgreSQL (two copies) | 282.88 | 282.88 |
| 1460 | 129.94 | RDS PostgreSQL (one copy) | 141.44 | 11.5 |
| 1460 | 129.94 | RDS PostgreSQL (two copies) | 282.88 | 152.94 |
| 2920 | 259.88 | RDS PostgreSQL (one copy) | 271.38 | 11.5 |
| 2920 | 259.88 | RDS PostgreSQL (two copies) | 542.76 | 282.88 |
| 5840 | 519.76 | RDS PostgreSQL (one copy) | 531.26 | 11.5 |
| 5840 | 519.76 | RDS PostgreSQL (two copies) | 1062.52 | 542.76 |
| 11680 | 1039.52 | RDS PostgreSQL (one copy) | 1051.02 | 11.5 |
| 11680 | 1039.52 | RDS PostgreSQL (two copies) | 2102.04 | 1062.52 |
| 23360 | 2079.04 | RDS PostgreSQL (one copy) | 2090.54 | 11.5 |
| 23360 | 2079.04 | RDS PostgreSQL (two copies) | 4181.08 | 2102.04 |
| 46720 | 4158.08 | RDS PostgreSQL (one copy) | 4169.58 | 11.5 |
| 46720 | 4158.08 | RDS PostgreSQL (two copies) | 8339.16 | 4181.08 |

**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 vCPU-hours/month / RDS PostgreSQL (one copy) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 0 vCPU-hours/month / RDS PostgreSQL (two copies) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1460 vCPU-hours/month / RDS PostgreSQL (one copy) | PlanningAssumption | 0 / 0 | 2 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1460 vCPU-hours/month / RDS PostgreSQL (two copies) | PlanningAssumption | 0 / 0 | 2 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 2920 vCPU-hours/month / RDS PostgreSQL (one copy) | PlanningAssumption | 0 / 0 | 4 | 4 | 16 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 2920 vCPU-hours/month / RDS PostgreSQL (two copies) | PlanningAssumption | 0 / 0 | 4 | 4 | 16 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 5840 vCPU-hours/month / RDS PostgreSQL (one copy) | PlanningAssumption | 0 / 0 | 8 | 8 | 32 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 5840 vCPU-hours/month / RDS PostgreSQL (two copies) | PlanningAssumption | 0 / 0 | 8 | 8 | 32 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 11680 vCPU-hours/month / RDS PostgreSQL (one copy) | PlanningAssumption | 0 / 0 | 16 | 16 | 64 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 11680 vCPU-hours/month / RDS PostgreSQL (two copies) | PlanningAssumption | 0 / 0 | 16 | 16 | 64 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 23360 vCPU-hours/month / RDS PostgreSQL (one copy) | PlanningAssumption | 0 / 0 | 32 | 32 | 128 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 23360 vCPU-hours/month / RDS PostgreSQL (two copies) | PlanningAssumption | 0 / 0 | 32 | 32 | 128 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 46720 vCPU-hours/month / RDS PostgreSQL (one copy) | PlanningAssumption | 0 / 0 | 64 | 64 | 256 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 46720 vCPU-hours/month / RDS PostgreSQL (two copies) | PlanningAssumption | 0 / 0 | 64 | 64 | 256 | 100 | 0 | `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 workload family already selected resource-hours; the throughput coefficient is not applied again.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| RDS PostgreSQL (one copy) | Origin list price · Primary compute | 0.089 | USD/vCPU-hours |
| RDS PostgreSQL (one copy) | Origin list price · Primary memory | 0 | USD/GiB-hours |
| RDS PostgreSQL (one copy) | Origin list price · Primary provisioned storage | 0.115 | USD/GiB-month |
| RDS PostgreSQL (one copy) | Origin list price · Database reads | 0 | USD/operations |
| RDS PostgreSQL (one copy) | Origin list price · Database writes | 0 | USD/operations |
| RDS PostgreSQL (one copy) | Target CPU / source CPU | 1 | multiplier |
| RDS PostgreSQL (one copy) | Target RAM / source RAM | 1 | multiplier |
| RDS PostgreSQL (one copy) | Target disk / source disk | 1 | multiplier |
| RDS PostgreSQL (one copy) | Target price guess · read | 0 | USD/read |
| RDS PostgreSQL (one copy) | Target price guess · write | 0 | USD/write |
| RDS PostgreSQL (one copy) | Target price guess · provider operation | 0 | USD/provider operation |
| RDS PostgreSQL (one copy) | Target list price · GiB-month | 0.115 | USD/GiB-month |
| RDS PostgreSQL (one copy) | Target price guess · published GiB | 0 | USD/published GiB |
| RDS PostgreSQL (one copy) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| RDS PostgreSQL (one copy) | Target list price · network GiB | 0.09 | USD/network GiB |
| RDS PostgreSQL (one copy) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| RDS PostgreSQL (one copy) | Target list price · vCPU-hour | 0.053 | USD/vCPU-hour |
| RDS PostgreSQL (one copy) | Target list price · GiB-hour | 0.009 | USD/GiB-hour |
| RDS PostgreSQL (one copy) | Target price guess · resource-hour | 0 | USD/resource-hour |
| RDS PostgreSQL (one copy) | Target price guess · resource-month | 0 | USD/resource-month |
| RDS PostgreSQL (one copy) | Target price guess · input token | 0 | USD/input token |
| RDS PostgreSQL (one copy) | Target price guess · output token | 0 | USD/output token |
| RDS PostgreSQL (one copy) | Target monthly base charge | 0 | USD/month |
| RDS PostgreSQL (one copy) | Target service minimum | 13.98 | USD/month |
| RDS PostgreSQL (one copy) | Minimum primary CPU | 2 | vCPU |
| RDS PostgreSQL (one copy) | Minimum primary RAM | 8 | GiB |
| RDS PostgreSQL (one copy) | Minimum primary disk | 100 | GiB |
| RDS PostgreSQL (one copy) | Additional full-price standby copy | 0 | 0 or 1 |
| RDS PostgreSQL (one copy) | Allocated share of provisioned cost | 1 | fraction |
| RDS PostgreSQL (one copy) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| RDS PostgreSQL (one copy) | Planning peak / mean work | 2 | multiplier |
| RDS PostgreSQL (one copy) | Planning primary CPU utilization | 0.7 | fraction |
| RDS PostgreSQL (one copy) | Resident state reserved in RAM | 0.1 | fraction |
| RDS PostgreSQL (one copy) | Planning disk utilization | 0.8 | fraction |
| RDS PostgreSQL (one copy) | Maintenance and log disk reserve | 20 | GiB |
| RDS PostgreSQL (one copy) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| RDS PostgreSQL (one copy) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| RDS PostgreSQL (one copy) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| RDS PostgreSQL (one copy) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| RDS PostgreSQL (one copy) | Dependent object sink write price guess | 0.000005 | USD/write |
| RDS PostgreSQL (two copies) | Origin list price · Primary compute | 0.089 | USD/vCPU-hours |
| RDS PostgreSQL (two copies) | Origin list price · Primary memory | 0 | USD/GiB-hours |
| RDS PostgreSQL (two copies) | Origin list price · Primary provisioned storage | 0.115 | USD/GiB-month |
| RDS PostgreSQL (two copies) | Origin list price · Database reads | 0 | USD/operations |
| RDS PostgreSQL (two copies) | Origin list price · Database writes | 0 | USD/operations |
| RDS PostgreSQL (two copies) | Target CPU / source CPU | 1 | multiplier |
| RDS PostgreSQL (two copies) | Target RAM / source RAM | 1 | multiplier |
| RDS PostgreSQL (two copies) | Target disk / source disk | 1 | multiplier |
| RDS PostgreSQL (two copies) | Target price guess · read | 0 | USD/read |
| RDS PostgreSQL (two copies) | Target price guess · write | 0 | USD/write |
| RDS PostgreSQL (two copies) | Target price guess · provider operation | 0 | USD/provider operation |
| RDS PostgreSQL (two copies) | Target list price · GiB-month | 0.115 | USD/GiB-month |
| RDS PostgreSQL (two copies) | Target price guess · published GiB | 0 | USD/published GiB |
| RDS PostgreSQL (two copies) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| RDS PostgreSQL (two copies) | Target list price · network GiB | 0.09 | USD/network GiB |
| RDS PostgreSQL (two copies) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| RDS PostgreSQL (two copies) | Target list price · vCPU-hour | 0.053 | USD/vCPU-hour |
| RDS PostgreSQL (two copies) | Target list price · GiB-hour | 0.009 | USD/GiB-hour |
| RDS PostgreSQL (two copies) | Target price guess · resource-hour | 0 | USD/resource-hour |
| RDS PostgreSQL (two copies) | Target price guess · resource-month | 0 | USD/resource-month |
| RDS PostgreSQL (two copies) | Target price guess · input token | 0 | USD/input token |
| RDS PostgreSQL (two copies) | Target price guess · output token | 0 | USD/output token |
| RDS PostgreSQL (two copies) | Target monthly base charge | 0 | USD/month |
| RDS PostgreSQL (two copies) | Target service minimum | 13.98 | USD/month |
| RDS PostgreSQL (two copies) | Minimum primary CPU | 2 | vCPU |
| RDS PostgreSQL (two copies) | Minimum primary RAM | 8 | GiB |
| RDS PostgreSQL (two copies) | Minimum primary disk | 100 | GiB |
| RDS PostgreSQL (two copies) | Additional full-price standby copy | 1 | 0 or 1 |
| RDS PostgreSQL (two copies) | Allocated share of provisioned cost | 1 | fraction |
| RDS PostgreSQL (two copies) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| RDS PostgreSQL (two copies) | Planning peak / mean work | 2 | multiplier |
| RDS PostgreSQL (two copies) | Planning primary CPU utilization | 0.7 | fraction |
| RDS PostgreSQL (two copies) | Resident state reserved in RAM | 0.1 | fraction |
| RDS PostgreSQL (two copies) | Planning disk utilization | 0.8 | fraction |
| RDS PostgreSQL (two copies) | Maintenance and log disk reserve | 20 | GiB |
| RDS PostgreSQL (two copies) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| RDS PostgreSQL (two copies) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| RDS PostgreSQL (two copies) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| RDS PostgreSQL (two copies) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| RDS PostgreSQL (two copies) | Dependent object sink write price guess | 0.000005 | USD/write |

* CPU allocation does not imply an achieved transaction rate. 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. eastus → 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.
* Authored planning assumptions, not measured adapter capacity. Origin rates are cited first-tier list prices, before free allowances and discounts.
* A cost scenario does not establish backend availability, protocol fidelity or production readiness. Registry serving status remains independent.
* Provisioned compute and RAM are priced by resource-hour; operations are independently authored. Database size cannot be inferred from dollars alone.
* Aurora/AlloyDB, MySQL/PostgreSQL and proxied targets retain their distinct backend contracts. HA, replicas and proxy allocations must be selected explicitly.
* Flexible Server memory is included in the vCore price; the memory meter is zero so RAM is not counted twice.
* RDS for PostgreSQL on db.m6i, the class the RDS reference model uses: vCPU and memory rates decompose two same-vCPU instances that differ only in memory. Multi-AZ with one standby bills exactly twice the instance and gp3 storage, which the standby copy reproduces. gp3 includes 3,000 IOPS and 125 MiB/s below 400 GiB; provisioned IOPS (USD 0.02 per IOPS-month), throughput (0.08 per MiBps-month), Graviton classes (db.m7g/r7g decompose to 0.0485 per vCPU-hour and 0.008875 per GiB-hour) and reserved instances are not selected.
* 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 workload family already selected resource-hours; the throughput coefficient is not applied again.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
* Azure Retail Prices API: [https://prices.azure.com/api/retail/prices](https://prices.azure.com/api/retail/prices)
* AWS Price List API: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonRDS/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonRDS/current/us-east-1/index.json)
* AWS Price List API, AWSDataTransfer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSDataTransfer/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSDataTransfer/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:

* Additional network transfer, backups, KMS, one-time migration and operational labor unless an explicit meter includes them.
* Destination application execution and separately billed downstream services; supply those allocations separately.
* Aurora per-IO, serverless-capacity, backup and proxy tariffs; reserved/committed-use purchase options.
* 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-b0902835bfed554db338504387e39cef18d0e9e8` / `2026-10-22.planning.2`. Curve: `workload-1`.

Sources: [Azure Retail Prices API](https://prices.azure.com/api/retail/prices), [AWS Price List API](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonRDS/current/us-east-1/index.json), [AWS Price List API, AWSDataTransfer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSDataTransfer/current/us-east-1/index.json).

### Azure PostgreSQL Flexible Server · Stored data

Estimated monthly service charges by Stored data. Adapter hosting and Tensor9 fees are excluded. Source: eastus; target: us-east-1; currency: USD.

![Azure PostgreSQL Flexible Server · Stored data: monthly service charges by Stored data. Exact values are in the following table.](/images/diagrams/service-cost/b0623356dacdf9c7096573c4ab886352a242589e132f9839e0faec467a2c3ea0-light.svg)

![Azure PostgreSQL Flexible Server · Stored data: monthly service charges by Stored data. Exact values are in the following table.](/images/diagrams/service-cost/8352a85c871f95c3cd2b87a4bfe191c53f03afb4e87885c3babf1e2bd74a0d47-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.

| Stored data (GiB-month) | PostgreSQL Flexible Server | Target scenario | RDS PostgreSQL | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | RDS PostgreSQL (one copy) | 141.44 | 141.44 |
| 0 | 0 | RDS PostgreSQL (two copies) | 282.88 | 282.88 |
| 10 | 1.15 | RDS PostgreSQL (one copy) | 141.44 | 140.29 |
| 10 | 1.15 | RDS PostgreSQL (two copies) | 282.88 | 281.73 |
| 100 | 11.5 | RDS PostgreSQL (one copy) | 160.33 | 148.83 |
| 100 | 11.5 | RDS PostgreSQL (two copies) | 320.66 | 309.16 |
| 1000 | 115 | RDS PostgreSQL (one copy) | 1422.665 | 1307.665 |
| 1000 | 115 | RDS PostgreSQL (two copies) | 2845.33 | 2730.33 |
| 10000 | 1150 | RDS PostgreSQL (one copy) | Unpriced | Unavailable |
| 10000 | 1150 | RDS PostgreSQL (two copies) | Unpriced | Unavailable |
| 100000 | 11500 | RDS PostgreSQL (one copy) | Unpriced | Unavailable |
| 100000 | 11500 | RDS PostgreSQL (two copies) | Unpriced | Unavailable |

**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 GiB-month / RDS PostgreSQL (one copy) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 0 GiB-month / RDS PostgreSQL (two copies) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10 GiB-month / RDS PostgreSQL (one copy) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 10 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10 GiB-month / RDS PostgreSQL (two copies) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 10 | `service-adapter-planning-2026-10-22.1` | None reported |
| 100 GiB-month / RDS PostgreSQL (one copy) | PlanningAssumption | 0 / 0 | 0 | 2 | 10 | 150 | 100 | `service-adapter-planning-2026-10-22.1` | None reported |
| 100 GiB-month / RDS PostgreSQL (two copies) | PlanningAssumption | 0 / 0 | 0 | 2 | 10 | 150 | 100 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1000 GiB-month / RDS PostgreSQL (one copy) | PlanningAssumption | 0 / 0 | 0 | 16 | 100 | 1275 | 1000 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1000 GiB-month / RDS PostgreSQL (two copies) | PlanningAssumption | 0 / 0 | 0 | 16 | 100 | 1275 | 1000 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10000 GiB-month / RDS PostgreSQL (one copy) | Unpriced | 0 / 0 | 0 | Unpriced | Unpriced | Unpriced | 10000 | `service-adapter-planning-2026-10-22.1` | Demand exceeds the planning model's joint CPU/RAM allocation bounds (96 vCPU, 624 GiB RAM). |
| 10000 GiB-month / RDS PostgreSQL (two copies) | Unpriced | 0 / 0 | 0 | Unpriced | Unpriced | Unpriced | 10000 | `service-adapter-planning-2026-10-22.1` | Demand exceeds the planning model's joint CPU/RAM allocation bounds (96 vCPU, 624 GiB RAM). |
| 100000 GiB-month / RDS PostgreSQL (one copy) | Unpriced | 0 / 0 | 0 | Unpriced | Unpriced | Unpriced | 100000 | `service-adapter-planning-2026-10-22.1` | Demand exceeds the planning model's joint CPU/RAM allocation bounds (96 vCPU, 624 GiB RAM).; Required disk exceeds the planning model's 65,536 GiB bound. |
| 100000 GiB-month / RDS PostgreSQL (two copies) | Unpriced | 0 / 0 | 0 | Unpriced | Unpriced | Unpriced | 100000 | `service-adapter-planning-2026-10-22.1` | Demand exceeds the planning model's joint CPU/RAM allocation bounds (96 vCPU, 624 GiB RAM).; Required disk exceeds the planning model's 65,536 GiB bound. |

* 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 workload family already selected resource-hours; the throughput coefficient is not applied again.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| RDS PostgreSQL (one copy) | Origin list price · Primary compute | 0.089 | USD/vCPU-hours |
| RDS PostgreSQL (one copy) | Origin list price · Primary memory | 0 | USD/GiB-hours |
| RDS PostgreSQL (one copy) | Origin list price · Primary provisioned storage | 0.115 | USD/GiB-month |
| RDS PostgreSQL (one copy) | Origin list price · Database reads | 0 | USD/operations |
| RDS PostgreSQL (one copy) | Origin list price · Database writes | 0 | USD/operations |
| RDS PostgreSQL (one copy) | Target CPU / source CPU | 1 | multiplier |
| RDS PostgreSQL (one copy) | Target RAM / source RAM | 1 | multiplier |
| RDS PostgreSQL (one copy) | Target disk / source disk | 1 | multiplier |
| RDS PostgreSQL (one copy) | Target price guess · read | 0 | USD/read |
| RDS PostgreSQL (one copy) | Target price guess · write | 0 | USD/write |
| RDS PostgreSQL (one copy) | Target price guess · provider operation | 0 | USD/provider operation |
| RDS PostgreSQL (one copy) | Target list price · GiB-month | 0.115 | USD/GiB-month |
| RDS PostgreSQL (one copy) | Target price guess · published GiB | 0 | USD/published GiB |
| RDS PostgreSQL (one copy) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| RDS PostgreSQL (one copy) | Target list price · network GiB | 0.09 | USD/network GiB |
| RDS PostgreSQL (one copy) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| RDS PostgreSQL (one copy) | Target list price · vCPU-hour | 0.053 | USD/vCPU-hour |
| RDS PostgreSQL (one copy) | Target list price · GiB-hour | 0.009 | USD/GiB-hour |
| RDS PostgreSQL (one copy) | Target price guess · resource-hour | 0 | USD/resource-hour |
| RDS PostgreSQL (one copy) | Target price guess · resource-month | 0 | USD/resource-month |
| RDS PostgreSQL (one copy) | Target price guess · input token | 0 | USD/input token |
| RDS PostgreSQL (one copy) | Target price guess · output token | 0 | USD/output token |
| RDS PostgreSQL (one copy) | Target monthly base charge | 0 | USD/month |
| RDS PostgreSQL (one copy) | Target service minimum | 13.98 | USD/month |
| RDS PostgreSQL (one copy) | Minimum primary CPU | 2 | vCPU |
| RDS PostgreSQL (one copy) | Minimum primary RAM | 8 | GiB |
| RDS PostgreSQL (one copy) | Minimum primary disk | 100 | GiB |
| RDS PostgreSQL (one copy) | Additional full-price standby copy | 0 | 0 or 1 |
| RDS PostgreSQL (one copy) | Allocated share of provisioned cost | 1 | fraction |
| RDS PostgreSQL (one copy) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| RDS PostgreSQL (one copy) | Planning peak / mean work | 2 | multiplier |
| RDS PostgreSQL (one copy) | Planning primary CPU utilization | 0.7 | fraction |
| RDS PostgreSQL (one copy) | Resident state reserved in RAM | 0.1 | fraction |
| RDS PostgreSQL (one copy) | Planning disk utilization | 0.8 | fraction |
| RDS PostgreSQL (one copy) | Maintenance and log disk reserve | 20 | GiB |
| RDS PostgreSQL (one copy) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| RDS PostgreSQL (one copy) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| RDS PostgreSQL (one copy) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| RDS PostgreSQL (one copy) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| RDS PostgreSQL (one copy) | Dependent object sink write price guess | 0.000005 | USD/write |
| RDS PostgreSQL (two copies) | Origin list price · Primary compute | 0.089 | USD/vCPU-hours |
| RDS PostgreSQL (two copies) | Origin list price · Primary memory | 0 | USD/GiB-hours |
| RDS PostgreSQL (two copies) | Origin list price · Primary provisioned storage | 0.115 | USD/GiB-month |
| RDS PostgreSQL (two copies) | Origin list price · Database reads | 0 | USD/operations |
| RDS PostgreSQL (two copies) | Origin list price · Database writes | 0 | USD/operations |
| RDS PostgreSQL (two copies) | Target CPU / source CPU | 1 | multiplier |
| RDS PostgreSQL (two copies) | Target RAM / source RAM | 1 | multiplier |
| RDS PostgreSQL (two copies) | Target disk / source disk | 1 | multiplier |
| RDS PostgreSQL (two copies) | Target price guess · read | 0 | USD/read |
| RDS PostgreSQL (two copies) | Target price guess · write | 0 | USD/write |
| RDS PostgreSQL (two copies) | Target price guess · provider operation | 0 | USD/provider operation |
| RDS PostgreSQL (two copies) | Target list price · GiB-month | 0.115 | USD/GiB-month |
| RDS PostgreSQL (two copies) | Target price guess · published GiB | 0 | USD/published GiB |
| RDS PostgreSQL (two copies) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| RDS PostgreSQL (two copies) | Target list price · network GiB | 0.09 | USD/network GiB |
| RDS PostgreSQL (two copies) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| RDS PostgreSQL (two copies) | Target list price · vCPU-hour | 0.053 | USD/vCPU-hour |
| RDS PostgreSQL (two copies) | Target list price · GiB-hour | 0.009 | USD/GiB-hour |
| RDS PostgreSQL (two copies) | Target price guess · resource-hour | 0 | USD/resource-hour |
| RDS PostgreSQL (two copies) | Target price guess · resource-month | 0 | USD/resource-month |
| RDS PostgreSQL (two copies) | Target price guess · input token | 0 | USD/input token |
| RDS PostgreSQL (two copies) | Target price guess · output token | 0 | USD/output token |
| RDS PostgreSQL (two copies) | Target monthly base charge | 0 | USD/month |
| RDS PostgreSQL (two copies) | Target service minimum | 13.98 | USD/month |
| RDS PostgreSQL (two copies) | Minimum primary CPU | 2 | vCPU |
| RDS PostgreSQL (two copies) | Minimum primary RAM | 8 | GiB |
| RDS PostgreSQL (two copies) | Minimum primary disk | 100 | GiB |
| RDS PostgreSQL (two copies) | Additional full-price standby copy | 1 | 0 or 1 |
| RDS PostgreSQL (two copies) | Allocated share of provisioned cost | 1 | fraction |
| RDS PostgreSQL (two copies) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| RDS PostgreSQL (two copies) | Planning peak / mean work | 2 | multiplier |
| RDS PostgreSQL (two copies) | Planning primary CPU utilization | 0.7 | fraction |
| RDS PostgreSQL (two copies) | Resident state reserved in RAM | 0.1 | fraction |
| RDS PostgreSQL (two copies) | Planning disk utilization | 0.8 | fraction |
| RDS PostgreSQL (two copies) | Maintenance and log disk reserve | 20 | GiB |
| RDS PostgreSQL (two copies) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| RDS PostgreSQL (two copies) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| RDS PostgreSQL (two copies) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| RDS PostgreSQL (two copies) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| RDS PostgreSQL (two copies) | Dependent object sink write price guess | 0.000005 | USD/write |

* Request meters remain at their independently authored 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. eastus → 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.
* Authored planning assumptions, not measured adapter capacity. Origin rates are cited first-tier list prices, before free allowances and discounts.
* A cost scenario does not establish backend availability, protocol fidelity or production readiness. Registry serving status remains independent.
* Provisioned compute and RAM are priced by resource-hour; operations are independently authored. Database size cannot be inferred from dollars alone.
* Aurora/AlloyDB, MySQL/PostgreSQL and proxied targets retain their distinct backend contracts. HA, replicas and proxy allocations must be selected explicitly.
* Flexible Server memory is included in the vCore price; the memory meter is zero so RAM is not counted twice.
* RDS for PostgreSQL on db.m6i, the class the RDS reference model uses: vCPU and memory rates decompose two same-vCPU instances that differ only in memory. Multi-AZ with one standby bills exactly twice the instance and gp3 storage, which the standby copy reproduces. gp3 includes 3,000 IOPS and 125 MiB/s below 400 GiB; provisioned IOPS (USD 0.02 per IOPS-month), throughput (0.08 per MiBps-month), Graviton classes (db.m7g/r7g decompose to 0.0485 per vCPU-hour and 0.008875 per GiB-hour) and reserved instances are not selected.
* 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 workload family already selected resource-hours; the throughput coefficient is not applied again.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
* Azure Retail Prices API: [https://prices.azure.com/api/retail/prices](https://prices.azure.com/api/retail/prices)
* AWS Price List API: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonRDS/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonRDS/current/us-east-1/index.json)
* AWS Price List API, AWSDataTransfer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSDataTransfer/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSDataTransfer/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:

* Additional network transfer, backups, KMS, one-time migration and operational labor unless an explicit meter includes them.
* Destination application execution and separately billed downstream services; supply those allocations separately.
* Aurora per-IO, serverless-capacity, backup and proxy tariffs; reserved/committed-use purchase options.
* 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-b0902835bfed554db338504387e39cef18d0e9e8` / `2026-10-22.planning.2`. Curve: `workload-2`.

Sources: [Azure Retail Prices API](https://prices.azure.com/api/retail/prices), [AWS Price List API](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonRDS/current/us-east-1/index.json), [AWS Price List API, AWSDataTransfer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSDataTransfer/current/us-east-1/index.json).

### Azure PostgreSQL Flexible Server · Database writes

Estimated monthly service charges by Database writes. Adapter hosting and Tensor9 fees are excluded. Source: eastus; target: us-east-1; currency: USD.

![Azure PostgreSQL Flexible Server · Database writes: monthly service charges by Database writes. Exact values are in the following table.](/images/diagrams/service-cost/513b632bfe610e1c7d9dbe7a7bacfcc376d55a05063c36bc67d6a8eb5532da31-light.svg)

![Azure PostgreSQL Flexible Server · Database writes: monthly service charges by Database writes. Exact values are in the following table.](/images/diagrams/service-cost/39263c15d22c221d3a287da8162ca7afe9108c715c0954027f41f64a0bb5e921-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.

| Database writes (per second) | PostgreSQL Flexible Server | Target scenario | RDS PostgreSQL | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | RDS PostgreSQL (one copy) | 141.44 | 141.44 |
| 0 | 0 | RDS PostgreSQL (two copies) | 282.88 | 282.88 |
| 1 | 0 | RDS PostgreSQL (one copy) | 141.44 | 141.44 |
| 1 | 0 | RDS PostgreSQL (two copies) | 282.88 | 282.88 |
| 10 | 0 | RDS PostgreSQL (one copy) | 141.44 | 141.44 |
| 10 | 0 | RDS PostgreSQL (two copies) | 282.88 | 282.88 |
| 100 | 0 | RDS PostgreSQL (one copy) | 141.44 | 141.44 |
| 100 | 0 | RDS PostgreSQL (two copies) | 282.88 | 282.88 |
| 1000 | 0 | RDS PostgreSQL (one copy) | 141.44 | 141.44 |
| 1000 | 0 | RDS PostgreSQL (two copies) | 282.88 | 282.88 |
| 10000 | 0 | RDS PostgreSQL (one copy) | 141.44 | 141.44 |
| 10000 | 0 | RDS PostgreSQL (two copies) | 282.88 | 282.88 |

**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 per second / RDS PostgreSQL (one copy) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 0 per second / RDS PostgreSQL (two copies) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1 per second / RDS PostgreSQL (one copy) | PlanningAssumption | 1 / 2 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1 per second / RDS PostgreSQL (two copies) | PlanningAssumption | 1 / 2 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10 per second / RDS PostgreSQL (one copy) | PlanningAssumption | 10 / 20 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10 per second / RDS PostgreSQL (two copies) | PlanningAssumption | 10 / 20 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 100 per second / RDS PostgreSQL (one copy) | PlanningAssumption | 100 / 200 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 100 per second / RDS PostgreSQL (two copies) | PlanningAssumption | 100 / 200 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1000 per second / RDS PostgreSQL (one copy) | PlanningAssumption | 1000 / 2000 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1000 per second / RDS PostgreSQL (two copies) | PlanningAssumption | 1000 / 2000 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10000 per second / RDS PostgreSQL (one copy) | PlanningAssumption | 10000 / 20000 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10000 per second / RDS PostgreSQL (two copies) | PlanningAssumption | 10000 / 20000 | 0 | 2 | 8 | 100 | 0 | `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 workload family already selected resource-hours; the throughput coefficient is not applied again.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| RDS PostgreSQL (one copy) | Origin list price · Primary compute | 0.089 | USD/vCPU-hours |
| RDS PostgreSQL (one copy) | Origin list price · Primary memory | 0 | USD/GiB-hours |
| RDS PostgreSQL (one copy) | Origin list price · Primary provisioned storage | 0.115 | USD/GiB-month |
| RDS PostgreSQL (one copy) | Origin list price · Database reads | 0 | USD/operations |
| RDS PostgreSQL (one copy) | Origin list price · Database writes | 0 | USD/operations |
| RDS PostgreSQL (one copy) | Target CPU / source CPU | 1 | multiplier |
| RDS PostgreSQL (one copy) | Target RAM / source RAM | 1 | multiplier |
| RDS PostgreSQL (one copy) | Target disk / source disk | 1 | multiplier |
| RDS PostgreSQL (one copy) | Target price guess · read | 0 | USD/read |
| RDS PostgreSQL (one copy) | Target price guess · write | 0 | USD/write |
| RDS PostgreSQL (one copy) | Target price guess · provider operation | 0 | USD/provider operation |
| RDS PostgreSQL (one copy) | Target list price · GiB-month | 0.115 | USD/GiB-month |
| RDS PostgreSQL (one copy) | Target price guess · published GiB | 0 | USD/published GiB |
| RDS PostgreSQL (one copy) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| RDS PostgreSQL (one copy) | Target list price · network GiB | 0.09 | USD/network GiB |
| RDS PostgreSQL (one copy) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| RDS PostgreSQL (one copy) | Target list price · vCPU-hour | 0.053 | USD/vCPU-hour |
| RDS PostgreSQL (one copy) | Target list price · GiB-hour | 0.009 | USD/GiB-hour |
| RDS PostgreSQL (one copy) | Target price guess · resource-hour | 0 | USD/resource-hour |
| RDS PostgreSQL (one copy) | Target price guess · resource-month | 0 | USD/resource-month |
| RDS PostgreSQL (one copy) | Target price guess · input token | 0 | USD/input token |
| RDS PostgreSQL (one copy) | Target price guess · output token | 0 | USD/output token |
| RDS PostgreSQL (one copy) | Target monthly base charge | 0 | USD/month |
| RDS PostgreSQL (one copy) | Target service minimum | 13.98 | USD/month |
| RDS PostgreSQL (one copy) | Minimum primary CPU | 2 | vCPU |
| RDS PostgreSQL (one copy) | Minimum primary RAM | 8 | GiB |
| RDS PostgreSQL (one copy) | Minimum primary disk | 100 | GiB |
| RDS PostgreSQL (one copy) | Additional full-price standby copy | 0 | 0 or 1 |
| RDS PostgreSQL (one copy) | Allocated share of provisioned cost | 1 | fraction |
| RDS PostgreSQL (one copy) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| RDS PostgreSQL (one copy) | Planning peak / mean work | 2 | multiplier |
| RDS PostgreSQL (one copy) | Planning primary CPU utilization | 0.7 | fraction |
| RDS PostgreSQL (one copy) | Resident state reserved in RAM | 0.1 | fraction |
| RDS PostgreSQL (one copy) | Planning disk utilization | 0.8 | fraction |
| RDS PostgreSQL (one copy) | Maintenance and log disk reserve | 20 | GiB |
| RDS PostgreSQL (one copy) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| RDS PostgreSQL (one copy) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| RDS PostgreSQL (one copy) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| RDS PostgreSQL (one copy) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| RDS PostgreSQL (one copy) | Dependent object sink write price guess | 0.000005 | USD/write |
| RDS PostgreSQL (two copies) | Origin list price · Primary compute | 0.089 | USD/vCPU-hours |
| RDS PostgreSQL (two copies) | Origin list price · Primary memory | 0 | USD/GiB-hours |
| RDS PostgreSQL (two copies) | Origin list price · Primary provisioned storage | 0.115 | USD/GiB-month |
| RDS PostgreSQL (two copies) | Origin list price · Database reads | 0 | USD/operations |
| RDS PostgreSQL (two copies) | Origin list price · Database writes | 0 | USD/operations |
| RDS PostgreSQL (two copies) | Target CPU / source CPU | 1 | multiplier |
| RDS PostgreSQL (two copies) | Target RAM / source RAM | 1 | multiplier |
| RDS PostgreSQL (two copies) | Target disk / source disk | 1 | multiplier |
| RDS PostgreSQL (two copies) | Target price guess · read | 0 | USD/read |
| RDS PostgreSQL (two copies) | Target price guess · write | 0 | USD/write |
| RDS PostgreSQL (two copies) | Target price guess · provider operation | 0 | USD/provider operation |
| RDS PostgreSQL (two copies) | Target list price · GiB-month | 0.115 | USD/GiB-month |
| RDS PostgreSQL (two copies) | Target price guess · published GiB | 0 | USD/published GiB |
| RDS PostgreSQL (two copies) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| RDS PostgreSQL (two copies) | Target list price · network GiB | 0.09 | USD/network GiB |
| RDS PostgreSQL (two copies) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| RDS PostgreSQL (two copies) | Target list price · vCPU-hour | 0.053 | USD/vCPU-hour |
| RDS PostgreSQL (two copies) | Target list price · GiB-hour | 0.009 | USD/GiB-hour |
| RDS PostgreSQL (two copies) | Target price guess · resource-hour | 0 | USD/resource-hour |
| RDS PostgreSQL (two copies) | Target price guess · resource-month | 0 | USD/resource-month |
| RDS PostgreSQL (two copies) | Target price guess · input token | 0 | USD/input token |
| RDS PostgreSQL (two copies) | Target price guess · output token | 0 | USD/output token |
| RDS PostgreSQL (two copies) | Target monthly base charge | 0 | USD/month |
| RDS PostgreSQL (two copies) | Target service minimum | 13.98 | USD/month |
| RDS PostgreSQL (two copies) | Minimum primary CPU | 2 | vCPU |
| RDS PostgreSQL (two copies) | Minimum primary RAM | 8 | GiB |
| RDS PostgreSQL (two copies) | Minimum primary disk | 100 | GiB |
| RDS PostgreSQL (two copies) | Additional full-price standby copy | 1 | 0 or 1 |
| RDS PostgreSQL (two copies) | Allocated share of provisioned cost | 1 | fraction |
| RDS PostgreSQL (two copies) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| RDS PostgreSQL (two copies) | Planning peak / mean work | 2 | multiplier |
| RDS PostgreSQL (two copies) | Planning primary CPU utilization | 0.7 | fraction |
| RDS PostgreSQL (two copies) | Resident state reserved in RAM | 0.1 | fraction |
| RDS PostgreSQL (two copies) | Planning disk utilization | 0.8 | fraction |
| RDS PostgreSQL (two copies) | Maintenance and log disk reserve | 20 | GiB |
| RDS PostgreSQL (two copies) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| RDS PostgreSQL (two copies) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| RDS PostgreSQL (two copies) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| RDS PostgreSQL (two copies) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| RDS PostgreSQL (two copies) | Dependent object sink write price guess | 0.000005 | USD/write |

* Source compute and stored data remain independent; a throughput view needs explicit workload inputs. 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. eastus → 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.
* Authored planning assumptions, not measured adapter capacity. Origin rates are cited first-tier list prices, before free allowances and discounts.
* A cost scenario does not establish backend availability, protocol fidelity or production readiness. Registry serving status remains independent.
* Provisioned compute and RAM are priced by resource-hour; operations are independently authored. Database size cannot be inferred from dollars alone.
* Aurora/AlloyDB, MySQL/PostgreSQL and proxied targets retain their distinct backend contracts. HA, replicas and proxy allocations must be selected explicitly.
* Flexible Server memory is included in the vCore price; the memory meter is zero so RAM is not counted twice.
* RDS for PostgreSQL on db.m6i, the class the RDS reference model uses: vCPU and memory rates decompose two same-vCPU instances that differ only in memory. Multi-AZ with one standby bills exactly twice the instance and gp3 storage, which the standby copy reproduces. gp3 includes 3,000 IOPS and 125 MiB/s below 400 GiB; provisioned IOPS (USD 0.02 per IOPS-month), throughput (0.08 per MiBps-month), Graviton classes (db.m7g/r7g decompose to 0.0485 per vCPU-hour and 0.008875 per GiB-hour) and reserved instances are not selected.
* 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 workload family already selected resource-hours; the throughput coefficient is not applied again.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
* Azure Retail Prices API: [https://prices.azure.com/api/retail/prices](https://prices.azure.com/api/retail/prices)
* AWS Price List API: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonRDS/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonRDS/current/us-east-1/index.json)
* AWS Price List API, AWSDataTransfer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSDataTransfer/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSDataTransfer/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:

* Additional network transfer, backups, KMS, one-time migration and operational labor unless an explicit meter includes them.
* Destination application execution and separately billed downstream services; supply those allocations separately.
* Aurora per-IO, serverless-capacity, backup and proxy tariffs; reserved/committed-use purchase options.
* 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-b0902835bfed554db338504387e39cef18d0e9e8` / `2026-10-22.planning.2`. Curve: `workload-3`.

Sources: [Azure Retail Prices API](https://prices.azure.com/api/retail/prices), [AWS Price List API](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonRDS/current/us-east-1/index.json), [AWS Price List API, AWSDataTransfer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSDataTransfer/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.