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

# Amazon DynamoDB costs

> Compare Amazon DynamoDB service-adapter costs across backend choices and scale points.

Tensor9 BYOC reference cost models for Amazon DynamoDB. Read/write mix, item size, consistency, index amplification and retained data determine the comparison. A database configuration price does not establish its supported point-operation throughput.

Read [how Tensor9 estimates service-adapter costs](/byoc/costs/overview.md) for billing scope, fixed versus variable charges, capacity qualification and a worked example. The comparisons below appear without calculator input.

## DynamoDB → Azure Cosmos DB (provisioned)

Origin API: `aws::1.0.0::dynamodb::control`. Target backend: `azure::1.0.0::cosmosdb::provisioned`.

### DynamoDB · DynamoDB read units

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

![DynamoDB · DynamoDB read units: monthly service charges by DynamoDB read units. Exact values are in the following table.](/images/diagrams/service-cost/7d84d4ab9e07a181bd7f57c62d6d931af87786ac5c3fbdfdcadd7a48e1018e23-light.svg)

![DynamoDB · DynamoDB read units: monthly service charges by DynamoDB read units. Exact values are in the following table.](/images/diagrams/service-cost/0636530bc9008b61413465f9b49e1127d41ef4a3e376bdad13987853d122c538-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.

| DynamoDB read units (per second) | DynamoDB | Target scenario | Azure Cosmos DB (provisioned) | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | Azure Cosmos DB (provisioned) | 23.36 | 23.36 |
| 1 | 0.3285 | Azure Cosmos DB (provisioned) | 23.36 | 23.0315 |
| 10 | 3.285 | Azure Cosmos DB (provisioned) | 23.36 | 20.075 |
| 100 | 32.85 | Azure Cosmos DB (provisioned) | 23.36 | -9.49 |
| 1000 | 328.5 | Azure Cosmos DB (provisioned) | 116.8 | -211.7 |
| 10000 | 3285 | Azure Cosmos DB (provisioned) | 1168 | -2117 |

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Azure Cosmos DB (provisioned) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| Azure Cosmos DB (provisioned) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| Azure Cosmos DB (provisioned) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| Azure Cosmos DB (provisioned) | Origin list price · Control-plane calls | 0 | USD/requests |
| Azure Cosmos DB (provisioned) | Representative item size | 1024 | bytes |
| Azure Cosmos DB (provisioned) | Strongly consistent read fraction | 1 | fraction |
| Azure Cosmos DB (provisioned) | Origin write-unit amplification | 1 | multiplier |
| Azure Cosmos DB (provisioned) | Target reads per point read | 1 | operations |
| Azure Cosmos DB (provisioned) | Target writes per item write | 1 | operations |
| Azure Cosmos DB (provisioned) | Target price guess · read | 0 | USD/read |
| Azure Cosmos DB (provisioned) | Target price guess · write | 0 | USD/write |
| Azure Cosmos DB (provisioned) | Target price guess · provider operation | 0 | USD/provider operation |
| Azure Cosmos DB (provisioned) | Target list price · GiB-month | 0.25 | USD/GiB-month |
| Azure Cosmos DB (provisioned) | Target price guess · published GiB | 0 | USD/published GiB |
| Azure Cosmos DB (provisioned) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Azure Cosmos DB (provisioned) | Target list price · network GiB | 0.087 | USD/network GiB |
| Azure Cosmos DB (provisioned) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Azure Cosmos DB (provisioned) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Azure Cosmos DB (provisioned) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Azure Cosmos DB (provisioned) | Target list price · resource-hour | 0.008 | USD/resource-hour |
| Azure Cosmos DB (provisioned) | Target price guess · resource-month | 0 | USD/resource-month |
| Azure Cosmos DB (provisioned) | Target price guess · input token | 0 | USD/input token |
| Azure Cosmos DB (provisioned) | Target price guess · output token | 0 | USD/output token |
| Azure Cosmos DB (provisioned) | Target monthly base charge | 0 | USD/month |
| Azure Cosmos DB (provisioned) | Target service minimum | 23.36 | USD/month |
| Azure Cosmos DB (provisioned) | Minimum primary CPU | 2 | vCPU |
| Azure Cosmos DB (provisioned) | Minimum primary RAM | 8 | GiB |
| Azure Cosmos DB (provisioned) | Minimum primary disk | 100 | GiB |
| Azure Cosmos DB (provisioned) | Additional full-price standby copy | 0 | 0 or 1 |
| Azure Cosmos DB (provisioned) | Allocated share of provisioned cost | 1 | fraction |
| Azure Cosmos DB (provisioned) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Azure Cosmos DB (provisioned) | Planning peak / mean work | 2 | multiplier |
| Azure Cosmos DB (provisioned) | Planning primary CPU utilization | 0.7 | fraction |
| Azure Cosmos DB (provisioned) | Resident state reserved in RAM | 0.1 | fraction |
| Azure Cosmos DB (provisioned) | Planning disk utilization | 0.8 | fraction |
| Azure Cosmos DB (provisioned) | Maintenance and log disk reserve | 20 | GiB |
| Azure Cosmos DB (provisioned) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Azure Cosmos DB (provisioned) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Azure Cosmos DB (provisioned) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Azure Cosmos DB (provisioned) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Azure Cosmos DB (provisioned) | Dependent object sink write price guess | 0.000005 | USD/write |

* Writes and storage remain independent. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
* Planning estimate · editable authored rates and sizing assumptions dated 2026-10-22; not verified provider prices. us-east-1 → eastus, USD/month.
* Source prices are reference charges, not an invoice. Target lines cover selected service usage/configuration only; adapter hosting and Tensor9 fees are excluded.
* Explicit tariff samples are not performance measurements or capacity qualification. No interpolation or break-even guarantee is implied.
* Variant assumptions show the first axis sample; any axis-dependent configuration is described by this curve's workload note.
* Rates are cited provider list prices, editable for discounts, commitments or another region. Workload translation and capacity coefficients remain editable planning assumptions, not benchmark measurements or a commercial quote.
* Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free.
* Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified.
* Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity.
* A declared adapter mapping and cost model do not establish implementation availability or service equivalence.
* This is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* 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.
* The control plane and table facet describe the same family workload; allocate shared capacity once, not once per catalog facet.
* No transactional, global-table, Streams or scan tariff is inferred from ordinary on-demand point units.
* Provisioned Cosmos DB bills reserved throughput in 100 RU/s blocks per hour, not consumed operations: planning-peak reads at 1 RU and writes at about 5.5 RU each are summed and rounded up to whole 100 RU/s blocks, with the documented 400 RU/s manual minimum ([https://learn.microsoft.com/en-us/azure/cosmos-db/set-throughput](https://learn.microsoft.com/en-us/azure/cosmos-db/set-throughput)). The blocks are a hard throughput limit, so they are planned at full utilization of the planning peak. Autoscale (USD 0.012 per 100 RU/s-hour, 100-1,000 RU/s entry) and the free tier (1,000 RU/s and 25 GB on one account) are not selected. Each additional region bills its own RU/s and storage.
* AWS Price List API, AmazonDynamoDB offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json)
* Amazon DynamoDB pricing: [https://aws.amazon.com/dynamodb/pricing/](https://aws.amazon.com/dynamodb/pricing/)
* Azure Retail Prices API: [https://prices.azure.com/api/retail/prices](https://prices.azure.com/api/retail/prices)

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

Excluded costs and workload features:

* 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.
* 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-c920be7e617e9f0a40743bb26db180c9036769e6` / `2026-10-22.planning.2`. Curve: `workload-1`.

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

### DynamoDB · DynamoDB write units

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

![DynamoDB · DynamoDB write units: monthly service charges by DynamoDB write units. Exact values are in the following table.](/images/diagrams/service-cost/03e0594fd4ff5c4604f4759a5c569af8d49bdcd4f97a2127e2f8c768061b8e15-light.svg)

![DynamoDB · DynamoDB write units: monthly service charges by DynamoDB write units. Exact values are in the following table.](/images/diagrams/service-cost/1c4aedc1bbd6ed0dbc8a26e69b50bcc6d05d1e18d0cada46574a4371e19e05d4-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.

| DynamoDB write units (per second) | DynamoDB | Target scenario | Azure Cosmos DB (provisioned) | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | Azure Cosmos DB (provisioned) | 23.36 | 23.36 |
| 1 | 1.6425 | Azure Cosmos DB (provisioned) | 23.36 | 21.7175 |
| 10 | 16.425 | Azure Cosmos DB (provisioned) | 23.36 | 6.935 |
| 100 | 164.25 | Azure Cosmos DB (provisioned) | 70.08 | -94.17 |
| 1000 | 1642.5 | Azure Cosmos DB (provisioned) | 648.24 | -994.26 |
| 10000 | 16425 | Azure Cosmos DB (provisioned) | 6429.84 | -9995.16 |

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Azure Cosmos DB (provisioned) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| Azure Cosmos DB (provisioned) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| Azure Cosmos DB (provisioned) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| Azure Cosmos DB (provisioned) | Origin list price · Control-plane calls | 0 | USD/requests |
| Azure Cosmos DB (provisioned) | Representative item size | 1024 | bytes |
| Azure Cosmos DB (provisioned) | Strongly consistent read fraction | 1 | fraction |
| Azure Cosmos DB (provisioned) | Origin write-unit amplification | 1 | multiplier |
| Azure Cosmos DB (provisioned) | Target reads per point read | 1 | operations |
| Azure Cosmos DB (provisioned) | Target writes per item write | 1 | operations |
| Azure Cosmos DB (provisioned) | Target price guess · read | 0 | USD/read |
| Azure Cosmos DB (provisioned) | Target price guess · write | 0 | USD/write |
| Azure Cosmos DB (provisioned) | Target price guess · provider operation | 0 | USD/provider operation |
| Azure Cosmos DB (provisioned) | Target list price · GiB-month | 0.25 | USD/GiB-month |
| Azure Cosmos DB (provisioned) | Target price guess · published GiB | 0 | USD/published GiB |
| Azure Cosmos DB (provisioned) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Azure Cosmos DB (provisioned) | Target list price · network GiB | 0.087 | USD/network GiB |
| Azure Cosmos DB (provisioned) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Azure Cosmos DB (provisioned) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Azure Cosmos DB (provisioned) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Azure Cosmos DB (provisioned) | Target list price · resource-hour | 0.008 | USD/resource-hour |
| Azure Cosmos DB (provisioned) | Target price guess · resource-month | 0 | USD/resource-month |
| Azure Cosmos DB (provisioned) | Target price guess · input token | 0 | USD/input token |
| Azure Cosmos DB (provisioned) | Target price guess · output token | 0 | USD/output token |
| Azure Cosmos DB (provisioned) | Target monthly base charge | 0 | USD/month |
| Azure Cosmos DB (provisioned) | Target service minimum | 23.36 | USD/month |
| Azure Cosmos DB (provisioned) | Minimum primary CPU | 2 | vCPU |
| Azure Cosmos DB (provisioned) | Minimum primary RAM | 8 | GiB |
| Azure Cosmos DB (provisioned) | Minimum primary disk | 100 | GiB |
| Azure Cosmos DB (provisioned) | Additional full-price standby copy | 0 | 0 or 1 |
| Azure Cosmos DB (provisioned) | Allocated share of provisioned cost | 1 | fraction |
| Azure Cosmos DB (provisioned) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Azure Cosmos DB (provisioned) | Planning peak / mean work | 2 | multiplier |
| Azure Cosmos DB (provisioned) | Planning primary CPU utilization | 0.7 | fraction |
| Azure Cosmos DB (provisioned) | Resident state reserved in RAM | 0.1 | fraction |
| Azure Cosmos DB (provisioned) | Planning disk utilization | 0.8 | fraction |
| Azure Cosmos DB (provisioned) | Maintenance and log disk reserve | 20 | GiB |
| Azure Cosmos DB (provisioned) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Azure Cosmos DB (provisioned) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Azure Cosmos DB (provisioned) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Azure Cosmos DB (provisioned) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Azure Cosmos DB (provisioned) | Dependent object sink write price guess | 0.000005 | USD/write |

* Reads and storage remain independent. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
* Planning estimate · editable authored rates and sizing assumptions dated 2026-10-22; not verified provider prices. us-east-1 → eastus, USD/month.
* Source prices are reference charges, not an invoice. Target lines cover selected service usage/configuration only; adapter hosting and Tensor9 fees are excluded.
* Explicit tariff samples are not performance measurements or capacity qualification. No interpolation or break-even guarantee is implied.
* Variant assumptions show the first axis sample; any axis-dependent configuration is described by this curve's workload note.
* Rates are cited provider list prices, editable for discounts, commitments or another region. Workload translation and capacity coefficients remain editable planning assumptions, not benchmark measurements or a commercial quote.
* Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free.
* Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified.
* Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity.
* A declared adapter mapping and cost model do not establish implementation availability or service equivalence.
* This is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* 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.
* The control plane and table facet describe the same family workload; allocate shared capacity once, not once per catalog facet.
* No transactional, global-table, Streams or scan tariff is inferred from ordinary on-demand point units.
* Provisioned Cosmos DB bills reserved throughput in 100 RU/s blocks per hour, not consumed operations: planning-peak reads at 1 RU and writes at about 5.5 RU each are summed and rounded up to whole 100 RU/s blocks, with the documented 400 RU/s manual minimum ([https://learn.microsoft.com/en-us/azure/cosmos-db/set-throughput](https://learn.microsoft.com/en-us/azure/cosmos-db/set-throughput)). The blocks are a hard throughput limit, so they are planned at full utilization of the planning peak. Autoscale (USD 0.012 per 100 RU/s-hour, 100-1,000 RU/s entry) and the free tier (1,000 RU/s and 25 GB on one account) are not selected. Each additional region bills its own RU/s and storage.
* AWS Price List API, AmazonDynamoDB offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json)
* Amazon DynamoDB pricing: [https://aws.amazon.com/dynamodb/pricing/](https://aws.amazon.com/dynamodb/pricing/)
* Azure Retail Prices API: [https://prices.azure.com/api/retail/prices](https://prices.azure.com/api/retail/prices)

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

Excluded costs and workload features:

* 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.
* 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-c920be7e617e9f0a40743bb26db180c9036769e6` / `2026-10-22.planning.2`. Curve: `workload-2`.

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

### DynamoDB · Stored data

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

![DynamoDB · Stored data: monthly service charges by Stored data. Exact values are in the following table.](/images/diagrams/service-cost/98e14e28a46d8996149058858e36a39cf5536a811cc6076675085e6a244bef30-light.svg)

![DynamoDB · Stored data: monthly service charges by Stored data. Exact values are in the following table.](/images/diagrams/service-cost/6c19648a87f8c0af3ca7fae7a84bcc6b4505a2f824f8947b1aef7b19c4e31d0f-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.

| Stored data (GiB-month) | DynamoDB | Target scenario | Azure Cosmos DB (provisioned) | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | Azure Cosmos DB (provisioned) | 23.36 | 23.36 |
| 10 | 2.5 | Azure Cosmos DB (provisioned) | 25.86 | 23.36 |
| 100 | 25 | Azure Cosmos DB (provisioned) | 48.36 | 23.36 |
| 1000 | 250 | Azure Cosmos DB (provisioned) | 273.36 | 23.36 |
| 10000 | 2500 | Azure Cosmos DB (provisioned) | 2523.36 | 23.36 |
| 100000 | 25000 | Azure Cosmos DB (provisioned) | 25023.36 | 23.36 |

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Azure Cosmos DB (provisioned) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| Azure Cosmos DB (provisioned) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| Azure Cosmos DB (provisioned) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| Azure Cosmos DB (provisioned) | Origin list price · Control-plane calls | 0 | USD/requests |
| Azure Cosmos DB (provisioned) | Representative item size | 1024 | bytes |
| Azure Cosmos DB (provisioned) | Strongly consistent read fraction | 1 | fraction |
| Azure Cosmos DB (provisioned) | Origin write-unit amplification | 1 | multiplier |
| Azure Cosmos DB (provisioned) | Target reads per point read | 1 | operations |
| Azure Cosmos DB (provisioned) | Target writes per item write | 1 | operations |
| Azure Cosmos DB (provisioned) | Target price guess · read | 0 | USD/read |
| Azure Cosmos DB (provisioned) | Target price guess · write | 0 | USD/write |
| Azure Cosmos DB (provisioned) | Target price guess · provider operation | 0 | USD/provider operation |
| Azure Cosmos DB (provisioned) | Target list price · GiB-month | 0.25 | USD/GiB-month |
| Azure Cosmos DB (provisioned) | Target price guess · published GiB | 0 | USD/published GiB |
| Azure Cosmos DB (provisioned) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Azure Cosmos DB (provisioned) | Target list price · network GiB | 0.087 | USD/network GiB |
| Azure Cosmos DB (provisioned) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Azure Cosmos DB (provisioned) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Azure Cosmos DB (provisioned) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Azure Cosmos DB (provisioned) | Target list price · resource-hour | 0.008 | USD/resource-hour |
| Azure Cosmos DB (provisioned) | Target price guess · resource-month | 0 | USD/resource-month |
| Azure Cosmos DB (provisioned) | Target price guess · input token | 0 | USD/input token |
| Azure Cosmos DB (provisioned) | Target price guess · output token | 0 | USD/output token |
| Azure Cosmos DB (provisioned) | Target monthly base charge | 0 | USD/month |
| Azure Cosmos DB (provisioned) | Target service minimum | 23.36 | USD/month |
| Azure Cosmos DB (provisioned) | Minimum primary CPU | 2 | vCPU |
| Azure Cosmos DB (provisioned) | Minimum primary RAM | 8 | GiB |
| Azure Cosmos DB (provisioned) | Minimum primary disk | 100 | GiB |
| Azure Cosmos DB (provisioned) | Additional full-price standby copy | 0 | 0 or 1 |
| Azure Cosmos DB (provisioned) | Allocated share of provisioned cost | 1 | fraction |
| Azure Cosmos DB (provisioned) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Azure Cosmos DB (provisioned) | Planning peak / mean work | 2 | multiplier |
| Azure Cosmos DB (provisioned) | Planning primary CPU utilization | 0.7 | fraction |
| Azure Cosmos DB (provisioned) | Resident state reserved in RAM | 0.1 | fraction |
| Azure Cosmos DB (provisioned) | Planning disk utilization | 0.8 | fraction |
| Azure Cosmos DB (provisioned) | Maintenance and log disk reserve | 20 | GiB |
| Azure Cosmos DB (provisioned) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Azure Cosmos DB (provisioned) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Azure Cosmos DB (provisioned) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Azure Cosmos DB (provisioned) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Azure Cosmos DB (provisioned) | 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. us-east-1 → eastus, USD/month.
* Source prices are reference charges, not an invoice. Target lines cover selected service usage/configuration only; adapter hosting and Tensor9 fees are excluded.
* Explicit tariff samples are not performance measurements or capacity qualification. No interpolation or break-even guarantee is implied.
* Variant assumptions show the first axis sample; any axis-dependent configuration is described by this curve's workload note.
* Rates are cited provider list prices, editable for discounts, commitments or another region. Workload translation and capacity coefficients remain editable planning assumptions, not benchmark measurements or a commercial quote.
* Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free.
* Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified.
* Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity.
* A declared adapter mapping and cost model do not establish implementation availability or service equivalence.
* This is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* 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.
* The control plane and table facet describe the same family workload; allocate shared capacity once, not once per catalog facet.
* No transactional, global-table, Streams or scan tariff is inferred from ordinary on-demand point units.
* Provisioned Cosmos DB bills reserved throughput in 100 RU/s blocks per hour, not consumed operations: planning-peak reads at 1 RU and writes at about 5.5 RU each are summed and rounded up to whole 100 RU/s blocks, with the documented 400 RU/s manual minimum ([https://learn.microsoft.com/en-us/azure/cosmos-db/set-throughput](https://learn.microsoft.com/en-us/azure/cosmos-db/set-throughput)). The blocks are a hard throughput limit, so they are planned at full utilization of the planning peak. Autoscale (USD 0.012 per 100 RU/s-hour, 100-1,000 RU/s entry) and the free tier (1,000 RU/s and 25 GB on one account) are not selected. Each additional region bills its own RU/s and storage.
* AWS Price List API, AmazonDynamoDB offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json)
* Amazon DynamoDB pricing: [https://aws.amazon.com/dynamodb/pricing/](https://aws.amazon.com/dynamodb/pricing/)
* Azure Retail Prices API: [https://prices.azure.com/api/retail/prices](https://prices.azure.com/api/retail/prices)

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

Excluded costs and workload features:

* 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.
* 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-c920be7e617e9f0a40743bb26db180c9036769e6` / `2026-10-22.planning.2`. Curve: `workload-3`.

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

## DynamoDB → Azure Cosmos DB (provisioned)

Origin API: `aws::1.0.0::dynamodb::table`. Target backend: `azure::1.0.0::cosmosdb::provisioned`.

### DynamoDB · DynamoDB read units

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

![DynamoDB · DynamoDB read units: monthly service charges by DynamoDB read units. Exact values are in the following table.](/images/diagrams/service-cost/7d84d4ab9e07a181bd7f57c62d6d931af87786ac5c3fbdfdcadd7a48e1018e23-light.svg)

![DynamoDB · DynamoDB read units: monthly service charges by DynamoDB read units. Exact values are in the following table.](/images/diagrams/service-cost/0636530bc9008b61413465f9b49e1127d41ef4a3e376bdad13987853d122c538-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.

| DynamoDB read units (per second) | DynamoDB | Target scenario | Azure Cosmos DB (provisioned) | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | Azure Cosmos DB (provisioned) | 23.36 | 23.36 |
| 1 | 0.3285 | Azure Cosmos DB (provisioned) | 23.36 | 23.0315 |
| 10 | 3.285 | Azure Cosmos DB (provisioned) | 23.36 | 20.075 |
| 100 | 32.85 | Azure Cosmos DB (provisioned) | 23.36 | -9.49 |
| 1000 | 328.5 | Azure Cosmos DB (provisioned) | 116.8 | -211.7 |
| 10000 | 3285 | Azure Cosmos DB (provisioned) | 1168 | -2117 |

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Azure Cosmos DB (provisioned) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| Azure Cosmos DB (provisioned) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| Azure Cosmos DB (provisioned) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| Azure Cosmos DB (provisioned) | Origin list price · Control-plane calls | 0 | USD/requests |
| Azure Cosmos DB (provisioned) | Representative item size | 1024 | bytes |
| Azure Cosmos DB (provisioned) | Strongly consistent read fraction | 1 | fraction |
| Azure Cosmos DB (provisioned) | Origin write-unit amplification | 1 | multiplier |
| Azure Cosmos DB (provisioned) | Target reads per point read | 1 | operations |
| Azure Cosmos DB (provisioned) | Target writes per item write | 1 | operations |
| Azure Cosmos DB (provisioned) | Target price guess · read | 0 | USD/read |
| Azure Cosmos DB (provisioned) | Target price guess · write | 0 | USD/write |
| Azure Cosmos DB (provisioned) | Target price guess · provider operation | 0 | USD/provider operation |
| Azure Cosmos DB (provisioned) | Target list price · GiB-month | 0.25 | USD/GiB-month |
| Azure Cosmos DB (provisioned) | Target price guess · published GiB | 0 | USD/published GiB |
| Azure Cosmos DB (provisioned) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Azure Cosmos DB (provisioned) | Target list price · network GiB | 0.087 | USD/network GiB |
| Azure Cosmos DB (provisioned) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Azure Cosmos DB (provisioned) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Azure Cosmos DB (provisioned) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Azure Cosmos DB (provisioned) | Target list price · resource-hour | 0.008 | USD/resource-hour |
| Azure Cosmos DB (provisioned) | Target price guess · resource-month | 0 | USD/resource-month |
| Azure Cosmos DB (provisioned) | Target price guess · input token | 0 | USD/input token |
| Azure Cosmos DB (provisioned) | Target price guess · output token | 0 | USD/output token |
| Azure Cosmos DB (provisioned) | Target monthly base charge | 0 | USD/month |
| Azure Cosmos DB (provisioned) | Target service minimum | 23.36 | USD/month |
| Azure Cosmos DB (provisioned) | Minimum primary CPU | 2 | vCPU |
| Azure Cosmos DB (provisioned) | Minimum primary RAM | 8 | GiB |
| Azure Cosmos DB (provisioned) | Minimum primary disk | 100 | GiB |
| Azure Cosmos DB (provisioned) | Additional full-price standby copy | 0 | 0 or 1 |
| Azure Cosmos DB (provisioned) | Allocated share of provisioned cost | 1 | fraction |
| Azure Cosmos DB (provisioned) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Azure Cosmos DB (provisioned) | Planning peak / mean work | 2 | multiplier |
| Azure Cosmos DB (provisioned) | Planning primary CPU utilization | 0.7 | fraction |
| Azure Cosmos DB (provisioned) | Resident state reserved in RAM | 0.1 | fraction |
| Azure Cosmos DB (provisioned) | Planning disk utilization | 0.8 | fraction |
| Azure Cosmos DB (provisioned) | Maintenance and log disk reserve | 20 | GiB |
| Azure Cosmos DB (provisioned) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Azure Cosmos DB (provisioned) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Azure Cosmos DB (provisioned) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Azure Cosmos DB (provisioned) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Azure Cosmos DB (provisioned) | Dependent object sink write price guess | 0.000005 | USD/write |

* Writes and storage remain independent. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
* Planning estimate · editable authored rates and sizing assumptions dated 2026-10-22; not verified provider prices. us-east-1 → eastus, USD/month.
* Source prices are reference charges, not an invoice. Target lines cover selected service usage/configuration only; adapter hosting and Tensor9 fees are excluded.
* Explicit tariff samples are not performance measurements or capacity qualification. No interpolation or break-even guarantee is implied.
* Variant assumptions show the first axis sample; any axis-dependent configuration is described by this curve's workload note.
* Rates are cited provider list prices, editable for discounts, commitments or another region. Workload translation and capacity coefficients remain editable planning assumptions, not benchmark measurements or a commercial quote.
* Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free.
* Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified.
* Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity.
* A declared adapter mapping and cost model do not establish implementation availability or service equivalence.
* This is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* 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.
* The control plane and table facet describe the same family workload; allocate shared capacity once, not once per catalog facet.
* No transactional, global-table, Streams or scan tariff is inferred from ordinary on-demand point units.
* Provisioned Cosmos DB bills reserved throughput in 100 RU/s blocks per hour, not consumed operations: planning-peak reads at 1 RU and writes at about 5.5 RU each are summed and rounded up to whole 100 RU/s blocks, with the documented 400 RU/s manual minimum ([https://learn.microsoft.com/en-us/azure/cosmos-db/set-throughput](https://learn.microsoft.com/en-us/azure/cosmos-db/set-throughput)). The blocks are a hard throughput limit, so they are planned at full utilization of the planning peak. Autoscale (USD 0.012 per 100 RU/s-hour, 100-1,000 RU/s entry) and the free tier (1,000 RU/s and 25 GB on one account) are not selected. Each additional region bills its own RU/s and storage.
* AWS Price List API, AmazonDynamoDB offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json)
* Amazon DynamoDB pricing: [https://aws.amazon.com/dynamodb/pricing/](https://aws.amazon.com/dynamodb/pricing/)
* Azure Retail Prices API: [https://prices.azure.com/api/retail/prices](https://prices.azure.com/api/retail/prices)

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

Excluded costs and workload features:

* 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.
* 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-fa502df1b7bcaf6b86688cf2258a7216e475f489` / `2026-10-22.planning.2`. Curve: `workload-1`.

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

### DynamoDB · DynamoDB write units

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

![DynamoDB · DynamoDB write units: monthly service charges by DynamoDB write units. Exact values are in the following table.](/images/diagrams/service-cost/03e0594fd4ff5c4604f4759a5c569af8d49bdcd4f97a2127e2f8c768061b8e15-light.svg)

![DynamoDB · DynamoDB write units: monthly service charges by DynamoDB write units. Exact values are in the following table.](/images/diagrams/service-cost/1c4aedc1bbd6ed0dbc8a26e69b50bcc6d05d1e18d0cada46574a4371e19e05d4-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.

| DynamoDB write units (per second) | DynamoDB | Target scenario | Azure Cosmos DB (provisioned) | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | Azure Cosmos DB (provisioned) | 23.36 | 23.36 |
| 1 | 1.6425 | Azure Cosmos DB (provisioned) | 23.36 | 21.7175 |
| 10 | 16.425 | Azure Cosmos DB (provisioned) | 23.36 | 6.935 |
| 100 | 164.25 | Azure Cosmos DB (provisioned) | 70.08 | -94.17 |
| 1000 | 1642.5 | Azure Cosmos DB (provisioned) | 648.24 | -994.26 |
| 10000 | 16425 | Azure Cosmos DB (provisioned) | 6429.84 | -9995.16 |

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Azure Cosmos DB (provisioned) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| Azure Cosmos DB (provisioned) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| Azure Cosmos DB (provisioned) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| Azure Cosmos DB (provisioned) | Origin list price · Control-plane calls | 0 | USD/requests |
| Azure Cosmos DB (provisioned) | Representative item size | 1024 | bytes |
| Azure Cosmos DB (provisioned) | Strongly consistent read fraction | 1 | fraction |
| Azure Cosmos DB (provisioned) | Origin write-unit amplification | 1 | multiplier |
| Azure Cosmos DB (provisioned) | Target reads per point read | 1 | operations |
| Azure Cosmos DB (provisioned) | Target writes per item write | 1 | operations |
| Azure Cosmos DB (provisioned) | Target price guess · read | 0 | USD/read |
| Azure Cosmos DB (provisioned) | Target price guess · write | 0 | USD/write |
| Azure Cosmos DB (provisioned) | Target price guess · provider operation | 0 | USD/provider operation |
| Azure Cosmos DB (provisioned) | Target list price · GiB-month | 0.25 | USD/GiB-month |
| Azure Cosmos DB (provisioned) | Target price guess · published GiB | 0 | USD/published GiB |
| Azure Cosmos DB (provisioned) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Azure Cosmos DB (provisioned) | Target list price · network GiB | 0.087 | USD/network GiB |
| Azure Cosmos DB (provisioned) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Azure Cosmos DB (provisioned) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Azure Cosmos DB (provisioned) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Azure Cosmos DB (provisioned) | Target list price · resource-hour | 0.008 | USD/resource-hour |
| Azure Cosmos DB (provisioned) | Target price guess · resource-month | 0 | USD/resource-month |
| Azure Cosmos DB (provisioned) | Target price guess · input token | 0 | USD/input token |
| Azure Cosmos DB (provisioned) | Target price guess · output token | 0 | USD/output token |
| Azure Cosmos DB (provisioned) | Target monthly base charge | 0 | USD/month |
| Azure Cosmos DB (provisioned) | Target service minimum | 23.36 | USD/month |
| Azure Cosmos DB (provisioned) | Minimum primary CPU | 2 | vCPU |
| Azure Cosmos DB (provisioned) | Minimum primary RAM | 8 | GiB |
| Azure Cosmos DB (provisioned) | Minimum primary disk | 100 | GiB |
| Azure Cosmos DB (provisioned) | Additional full-price standby copy | 0 | 0 or 1 |
| Azure Cosmos DB (provisioned) | Allocated share of provisioned cost | 1 | fraction |
| Azure Cosmos DB (provisioned) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Azure Cosmos DB (provisioned) | Planning peak / mean work | 2 | multiplier |
| Azure Cosmos DB (provisioned) | Planning primary CPU utilization | 0.7 | fraction |
| Azure Cosmos DB (provisioned) | Resident state reserved in RAM | 0.1 | fraction |
| Azure Cosmos DB (provisioned) | Planning disk utilization | 0.8 | fraction |
| Azure Cosmos DB (provisioned) | Maintenance and log disk reserve | 20 | GiB |
| Azure Cosmos DB (provisioned) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Azure Cosmos DB (provisioned) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Azure Cosmos DB (provisioned) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Azure Cosmos DB (provisioned) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Azure Cosmos DB (provisioned) | Dependent object sink write price guess | 0.000005 | USD/write |

* Reads and storage remain independent. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
* Planning estimate · editable authored rates and sizing assumptions dated 2026-10-22; not verified provider prices. us-east-1 → eastus, USD/month.
* Source prices are reference charges, not an invoice. Target lines cover selected service usage/configuration only; adapter hosting and Tensor9 fees are excluded.
* Explicit tariff samples are not performance measurements or capacity qualification. No interpolation or break-even guarantee is implied.
* Variant assumptions show the first axis sample; any axis-dependent configuration is described by this curve's workload note.
* Rates are cited provider list prices, editable for discounts, commitments or another region. Workload translation and capacity coefficients remain editable planning assumptions, not benchmark measurements or a commercial quote.
* Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free.
* Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified.
* Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity.
* A declared adapter mapping and cost model do not establish implementation availability or service equivalence.
* This is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* 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.
* The control plane and table facet describe the same family workload; allocate shared capacity once, not once per catalog facet.
* No transactional, global-table, Streams or scan tariff is inferred from ordinary on-demand point units.
* Provisioned Cosmos DB bills reserved throughput in 100 RU/s blocks per hour, not consumed operations: planning-peak reads at 1 RU and writes at about 5.5 RU each are summed and rounded up to whole 100 RU/s blocks, with the documented 400 RU/s manual minimum ([https://learn.microsoft.com/en-us/azure/cosmos-db/set-throughput](https://learn.microsoft.com/en-us/azure/cosmos-db/set-throughput)). The blocks are a hard throughput limit, so they are planned at full utilization of the planning peak. Autoscale (USD 0.012 per 100 RU/s-hour, 100-1,000 RU/s entry) and the free tier (1,000 RU/s and 25 GB on one account) are not selected. Each additional region bills its own RU/s and storage.
* AWS Price List API, AmazonDynamoDB offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json)
* Amazon DynamoDB pricing: [https://aws.amazon.com/dynamodb/pricing/](https://aws.amazon.com/dynamodb/pricing/)
* Azure Retail Prices API: [https://prices.azure.com/api/retail/prices](https://prices.azure.com/api/retail/prices)

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

Excluded costs and workload features:

* 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.
* 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-fa502df1b7bcaf6b86688cf2258a7216e475f489` / `2026-10-22.planning.2`. Curve: `workload-2`.

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

### DynamoDB · Stored data

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

![DynamoDB · Stored data: monthly service charges by Stored data. Exact values are in the following table.](/images/diagrams/service-cost/98e14e28a46d8996149058858e36a39cf5536a811cc6076675085e6a244bef30-light.svg)

![DynamoDB · Stored data: monthly service charges by Stored data. Exact values are in the following table.](/images/diagrams/service-cost/6c19648a87f8c0af3ca7fae7a84bcc6b4505a2f824f8947b1aef7b19c4e31d0f-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.

| Stored data (GiB-month) | DynamoDB | Target scenario | Azure Cosmos DB (provisioned) | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | Azure Cosmos DB (provisioned) | 23.36 | 23.36 |
| 10 | 2.5 | Azure Cosmos DB (provisioned) | 25.86 | 23.36 |
| 100 | 25 | Azure Cosmos DB (provisioned) | 48.36 | 23.36 |
| 1000 | 250 | Azure Cosmos DB (provisioned) | 273.36 | 23.36 |
| 10000 | 2500 | Azure Cosmos DB (provisioned) | 2523.36 | 23.36 |
| 100000 | 25000 | Azure Cosmos DB (provisioned) | 25023.36 | 23.36 |

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Azure Cosmos DB (provisioned) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| Azure Cosmos DB (provisioned) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| Azure Cosmos DB (provisioned) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| Azure Cosmos DB (provisioned) | Origin list price · Control-plane calls | 0 | USD/requests |
| Azure Cosmos DB (provisioned) | Representative item size | 1024 | bytes |
| Azure Cosmos DB (provisioned) | Strongly consistent read fraction | 1 | fraction |
| Azure Cosmos DB (provisioned) | Origin write-unit amplification | 1 | multiplier |
| Azure Cosmos DB (provisioned) | Target reads per point read | 1 | operations |
| Azure Cosmos DB (provisioned) | Target writes per item write | 1 | operations |
| Azure Cosmos DB (provisioned) | Target price guess · read | 0 | USD/read |
| Azure Cosmos DB (provisioned) | Target price guess · write | 0 | USD/write |
| Azure Cosmos DB (provisioned) | Target price guess · provider operation | 0 | USD/provider operation |
| Azure Cosmos DB (provisioned) | Target list price · GiB-month | 0.25 | USD/GiB-month |
| Azure Cosmos DB (provisioned) | Target price guess · published GiB | 0 | USD/published GiB |
| Azure Cosmos DB (provisioned) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Azure Cosmos DB (provisioned) | Target list price · network GiB | 0.087 | USD/network GiB |
| Azure Cosmos DB (provisioned) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Azure Cosmos DB (provisioned) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Azure Cosmos DB (provisioned) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Azure Cosmos DB (provisioned) | Target list price · resource-hour | 0.008 | USD/resource-hour |
| Azure Cosmos DB (provisioned) | Target price guess · resource-month | 0 | USD/resource-month |
| Azure Cosmos DB (provisioned) | Target price guess · input token | 0 | USD/input token |
| Azure Cosmos DB (provisioned) | Target price guess · output token | 0 | USD/output token |
| Azure Cosmos DB (provisioned) | Target monthly base charge | 0 | USD/month |
| Azure Cosmos DB (provisioned) | Target service minimum | 23.36 | USD/month |
| Azure Cosmos DB (provisioned) | Minimum primary CPU | 2 | vCPU |
| Azure Cosmos DB (provisioned) | Minimum primary RAM | 8 | GiB |
| Azure Cosmos DB (provisioned) | Minimum primary disk | 100 | GiB |
| Azure Cosmos DB (provisioned) | Additional full-price standby copy | 0 | 0 or 1 |
| Azure Cosmos DB (provisioned) | Allocated share of provisioned cost | 1 | fraction |
| Azure Cosmos DB (provisioned) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Azure Cosmos DB (provisioned) | Planning peak / mean work | 2 | multiplier |
| Azure Cosmos DB (provisioned) | Planning primary CPU utilization | 0.7 | fraction |
| Azure Cosmos DB (provisioned) | Resident state reserved in RAM | 0.1 | fraction |
| Azure Cosmos DB (provisioned) | Planning disk utilization | 0.8 | fraction |
| Azure Cosmos DB (provisioned) | Maintenance and log disk reserve | 20 | GiB |
| Azure Cosmos DB (provisioned) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Azure Cosmos DB (provisioned) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Azure Cosmos DB (provisioned) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Azure Cosmos DB (provisioned) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Azure Cosmos DB (provisioned) | 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. us-east-1 → eastus, USD/month.
* Source prices are reference charges, not an invoice. Target lines cover selected service usage/configuration only; adapter hosting and Tensor9 fees are excluded.
* Explicit tariff samples are not performance measurements or capacity qualification. No interpolation or break-even guarantee is implied.
* Variant assumptions show the first axis sample; any axis-dependent configuration is described by this curve's workload note.
* Rates are cited provider list prices, editable for discounts, commitments or another region. Workload translation and capacity coefficients remain editable planning assumptions, not benchmark measurements or a commercial quote.
* Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free.
* Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified.
* Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity.
* A declared adapter mapping and cost model do not establish implementation availability or service equivalence.
* This is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* 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.
* The control plane and table facet describe the same family workload; allocate shared capacity once, not once per catalog facet.
* No transactional, global-table, Streams or scan tariff is inferred from ordinary on-demand point units.
* Provisioned Cosmos DB bills reserved throughput in 100 RU/s blocks per hour, not consumed operations: planning-peak reads at 1 RU and writes at about 5.5 RU each are summed and rounded up to whole 100 RU/s blocks, with the documented 400 RU/s manual minimum ([https://learn.microsoft.com/en-us/azure/cosmos-db/set-throughput](https://learn.microsoft.com/en-us/azure/cosmos-db/set-throughput)). The blocks are a hard throughput limit, so they are planned at full utilization of the planning peak. Autoscale (USD 0.012 per 100 RU/s-hour, 100-1,000 RU/s entry) and the free tier (1,000 RU/s and 25 GB on one account) are not selected. Each additional region bills its own RU/s and storage.
* AWS Price List API, AmazonDynamoDB offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json)
* Amazon DynamoDB pricing: [https://aws.amazon.com/dynamodb/pricing/](https://aws.amazon.com/dynamodb/pricing/)
* Azure Retail Prices API: [https://prices.azure.com/api/retail/prices](https://prices.azure.com/api/retail/prices)

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

Excluded costs and workload features:

* 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.
* 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-fa502df1b7bcaf6b86688cf2258a7216e475f489` / `2026-10-22.planning.2`. Curve: `workload-3`.

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

## DynamoDB → Azure Cosmos DB (serverless)

Origin API: `aws::1.0.0::dynamodb::control`. Target backend: `azure::1.0.0::cosmosdb::serverless`.

### DynamoDB · DynamoDB read units

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

![DynamoDB · DynamoDB read units: monthly service charges by DynamoDB read units. Exact values are in the following table.](/images/diagrams/service-cost/ea3bc9090b548f3dc6a61de0d2afe660848573007bdf228e9d9669b31dcb7a04-light.svg)

![DynamoDB · DynamoDB read units: monthly service charges by DynamoDB read units. Exact values are in the following table.](/images/diagrams/service-cost/424d72576778a35c05a00f8912c871c6e04a42a41dea3085eab8392709c56474-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.

| DynamoDB read units (per second) | DynamoDB | Target scenario | Azure Cosmos DB (serverless) | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | Azure Cosmos DB (serverless) | 0 | 0 |
| 1 | 0.3285 | Azure Cosmos DB (serverless) | 0.657 | 0.3285 |
| 10 | 3.285 | Azure Cosmos DB (serverless) | 6.57 | 3.285 |
| 100 | 32.85 | Azure Cosmos DB (serverless) | 65.7 | 32.85 |
| 1000 | 328.5 | Azure Cosmos DB (serverless) | 657 | 328.5 |
| 10000 | 3285 | Azure Cosmos DB (serverless) | 6570 | 3285 |

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Azure Cosmos DB (serverless) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| Azure Cosmos DB (serverless) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| Azure Cosmos DB (serverless) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| Azure Cosmos DB (serverless) | Origin list price · Control-plane calls | 0 | USD/requests |
| Azure Cosmos DB (serverless) | Representative item size | 1024 | bytes |
| Azure Cosmos DB (serverless) | Strongly consistent read fraction | 1 | fraction |
| Azure Cosmos DB (serverless) | Origin write-unit amplification | 1 | multiplier |
| Azure Cosmos DB (serverless) | Target reads per point read | 1 | operations |
| Azure Cosmos DB (serverless) | Target writes per item write | 1 | operations |
| Azure Cosmos DB (serverless) | Target list price · read | 0.00000025 | USD/read |
| Azure Cosmos DB (serverless) | Target list price · write | 0.000001375 | USD/write |
| Azure Cosmos DB (serverless) | Target price guess · provider operation | 0 | USD/provider operation |
| Azure Cosmos DB (serverless) | Target list price · GiB-month | 0.25 | USD/GiB-month |
| Azure Cosmos DB (serverless) | Target price guess · published GiB | 0 | USD/published GiB |
| Azure Cosmos DB (serverless) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Azure Cosmos DB (serverless) | Target list price · network GiB | 0.087 | USD/network GiB |
| Azure Cosmos DB (serverless) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Azure Cosmos DB (serverless) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Azure Cosmos DB (serverless) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Azure Cosmos DB (serverless) | Target price guess · resource-hour | 0 | USD/resource-hour |
| Azure Cosmos DB (serverless) | Target price guess · resource-month | 0 | USD/resource-month |
| Azure Cosmos DB (serverless) | Target price guess · input token | 0 | USD/input token |
| Azure Cosmos DB (serverless) | Target price guess · output token | 0 | USD/output token |
| Azure Cosmos DB (serverless) | Target monthly base charge | 0 | USD/month |
| Azure Cosmos DB (serverless) | Approximate target service minimum | 0 | USD/month |
| Azure Cosmos DB (serverless) | Minimum primary CPU | 2 | vCPU |
| Azure Cosmos DB (serverless) | Minimum primary RAM | 8 | GiB |
| Azure Cosmos DB (serverless) | Minimum primary disk | 100 | GiB |
| Azure Cosmos DB (serverless) | Additional full-price standby copy | 0 | 0 or 1 |
| Azure Cosmos DB (serverless) | Allocated share of provisioned cost | 1 | fraction |
| Azure Cosmos DB (serverless) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Azure Cosmos DB (serverless) | Planning peak / mean work | 2 | multiplier |
| Azure Cosmos DB (serverless) | Planning primary CPU utilization | 0.7 | fraction |
| Azure Cosmos DB (serverless) | Resident state reserved in RAM | 0.1 | fraction |
| Azure Cosmos DB (serverless) | Planning disk utilization | 0.8 | fraction |
| Azure Cosmos DB (serverless) | Maintenance and log disk reserve | 20 | GiB |
| Azure Cosmos DB (serverless) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Azure Cosmos DB (serverless) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Azure Cosmos DB (serverless) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Azure Cosmos DB (serverless) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Azure Cosmos DB (serverless) | Dependent object sink write price guess | 0.000005 | USD/write |

* Writes and storage remain independent. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
* Planning estimate · editable authored rates and sizing assumptions dated 2026-10-22; not verified provider prices. us-east-1 → eastus, USD/month.
* Source prices are reference charges, not an invoice. Target lines cover selected service usage/configuration only; adapter hosting and Tensor9 fees are excluded.
* Explicit tariff samples are not performance measurements or capacity qualification. No interpolation or break-even guarantee is implied.
* Variant assumptions show the first axis sample; any axis-dependent configuration is described by this curve's workload note.
* Rates are cited provider list prices, editable for discounts, commitments or another region. Workload translation and capacity coefficients remain editable planning assumptions, not benchmark measurements or a commercial quote.
* Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free.
* Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified.
* Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity.
* A declared adapter mapping and cost model do not establish implementation availability or service equivalence.
* This is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* 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.
* The control plane and table facet describe the same family workload; allocate shared capacity once, not once per catalog facet.
* No transactional, global-table, Streams or scan tariff is inferred from ordinary on-demand point units.
* Cosmos DB serverless bills consumed Request Units (USD 0.25 per million) and stored GB. Per-operation rates assume Microsoft's published 1 KB costs: a point read is 1 RU and an unindexed insert about 5.5 RU ([https://learn.microsoft.com/en-us/azure/cosmos-db/optimize-cost-reads-writes](https://learn.microsoft.com/en-us/azure/cosmos-db/optimize-cost-reads-writes)). Larger items, default indexing of every property, replaces (2x an insert) and strong or bounded-staleness reads (2x) cost more RU than these rates assume.
* AWS Price List API, AmazonDynamoDB offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json)
* Amazon DynamoDB pricing: [https://aws.amazon.com/dynamodb/pricing/](https://aws.amazon.com/dynamodb/pricing/)
* Azure Retail Prices API: [https://prices.azure.com/api/retail/prices](https://prices.azure.com/api/retail/prices)

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

Excluded costs and workload features:

* 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.
* 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-193a4d8c9f7cdd8a1e2cad0fae8d95ed44aad86e` / `2026-10-22.planning.2`. Curve: `workload-1`.

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

### DynamoDB · DynamoDB write units

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

![DynamoDB · DynamoDB write units: monthly service charges by DynamoDB write units. Exact values are in the following table.](/images/diagrams/service-cost/9224f35abbe760c618be7e2441e81fe628b4e868e11afd4b77ec10208e39bada-light.svg)

![DynamoDB · DynamoDB write units: monthly service charges by DynamoDB write units. Exact values are in the following table.](/images/diagrams/service-cost/571fa6bb2ff5764a717cbbf803186018e1f0600298442ee4d53c2709dee11911-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.

| DynamoDB write units (per second) | DynamoDB | Target scenario | Azure Cosmos DB (serverless) | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | Azure Cosmos DB (serverless) | 0 | 0 |
| 1 | 1.6425 | Azure Cosmos DB (serverless) | 3.6135 | 1.971 |
| 10 | 16.425 | Azure Cosmos DB (serverless) | 36.135 | 19.71 |
| 100 | 164.25 | Azure Cosmos DB (serverless) | 361.35 | 197.1 |
| 1000 | 1642.5 | Azure Cosmos DB (serverless) | 3613.5 | 1971 |
| 10000 | 16425 | Azure Cosmos DB (serverless) | 36135 | 19710 |

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Azure Cosmos DB (serverless) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| Azure Cosmos DB (serverless) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| Azure Cosmos DB (serverless) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| Azure Cosmos DB (serverless) | Origin list price · Control-plane calls | 0 | USD/requests |
| Azure Cosmos DB (serverless) | Representative item size | 1024 | bytes |
| Azure Cosmos DB (serverless) | Strongly consistent read fraction | 1 | fraction |
| Azure Cosmos DB (serverless) | Origin write-unit amplification | 1 | multiplier |
| Azure Cosmos DB (serverless) | Target reads per point read | 1 | operations |
| Azure Cosmos DB (serverless) | Target writes per item write | 1 | operations |
| Azure Cosmos DB (serverless) | Target list price · read | 0.00000025 | USD/read |
| Azure Cosmos DB (serverless) | Target list price · write | 0.000001375 | USD/write |
| Azure Cosmos DB (serverless) | Target price guess · provider operation | 0 | USD/provider operation |
| Azure Cosmos DB (serverless) | Target list price · GiB-month | 0.25 | USD/GiB-month |
| Azure Cosmos DB (serverless) | Target price guess · published GiB | 0 | USD/published GiB |
| Azure Cosmos DB (serverless) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Azure Cosmos DB (serverless) | Target list price · network GiB | 0.087 | USD/network GiB |
| Azure Cosmos DB (serverless) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Azure Cosmos DB (serverless) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Azure Cosmos DB (serverless) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Azure Cosmos DB (serverless) | Target price guess · resource-hour | 0 | USD/resource-hour |
| Azure Cosmos DB (serverless) | Target price guess · resource-month | 0 | USD/resource-month |
| Azure Cosmos DB (serverless) | Target price guess · input token | 0 | USD/input token |
| Azure Cosmos DB (serverless) | Target price guess · output token | 0 | USD/output token |
| Azure Cosmos DB (serverless) | Target monthly base charge | 0 | USD/month |
| Azure Cosmos DB (serverless) | Approximate target service minimum | 0 | USD/month |
| Azure Cosmos DB (serverless) | Minimum primary CPU | 2 | vCPU |
| Azure Cosmos DB (serverless) | Minimum primary RAM | 8 | GiB |
| Azure Cosmos DB (serverless) | Minimum primary disk | 100 | GiB |
| Azure Cosmos DB (serverless) | Additional full-price standby copy | 0 | 0 or 1 |
| Azure Cosmos DB (serverless) | Allocated share of provisioned cost | 1 | fraction |
| Azure Cosmos DB (serverless) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Azure Cosmos DB (serverless) | Planning peak / mean work | 2 | multiplier |
| Azure Cosmos DB (serverless) | Planning primary CPU utilization | 0.7 | fraction |
| Azure Cosmos DB (serverless) | Resident state reserved in RAM | 0.1 | fraction |
| Azure Cosmos DB (serverless) | Planning disk utilization | 0.8 | fraction |
| Azure Cosmos DB (serverless) | Maintenance and log disk reserve | 20 | GiB |
| Azure Cosmos DB (serverless) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Azure Cosmos DB (serverless) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Azure Cosmos DB (serverless) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Azure Cosmos DB (serverless) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Azure Cosmos DB (serverless) | Dependent object sink write price guess | 0.000005 | USD/write |

* Reads and storage remain independent. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
* Planning estimate · editable authored rates and sizing assumptions dated 2026-10-22; not verified provider prices. us-east-1 → eastus, USD/month.
* Source prices are reference charges, not an invoice. Target lines cover selected service usage/configuration only; adapter hosting and Tensor9 fees are excluded.
* Explicit tariff samples are not performance measurements or capacity qualification. No interpolation or break-even guarantee is implied.
* Variant assumptions show the first axis sample; any axis-dependent configuration is described by this curve's workload note.
* Rates are cited provider list prices, editable for discounts, commitments or another region. Workload translation and capacity coefficients remain editable planning assumptions, not benchmark measurements or a commercial quote.
* Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free.
* Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified.
* Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity.
* A declared adapter mapping and cost model do not establish implementation availability or service equivalence.
* This is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* 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.
* The control plane and table facet describe the same family workload; allocate shared capacity once, not once per catalog facet.
* No transactional, global-table, Streams or scan tariff is inferred from ordinary on-demand point units.
* Cosmos DB serverless bills consumed Request Units (USD 0.25 per million) and stored GB. Per-operation rates assume Microsoft's published 1 KB costs: a point read is 1 RU and an unindexed insert about 5.5 RU ([https://learn.microsoft.com/en-us/azure/cosmos-db/optimize-cost-reads-writes](https://learn.microsoft.com/en-us/azure/cosmos-db/optimize-cost-reads-writes)). Larger items, default indexing of every property, replaces (2x an insert) and strong or bounded-staleness reads (2x) cost more RU than these rates assume.
* AWS Price List API, AmazonDynamoDB offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json)
* Amazon DynamoDB pricing: [https://aws.amazon.com/dynamodb/pricing/](https://aws.amazon.com/dynamodb/pricing/)
* Azure Retail Prices API: [https://prices.azure.com/api/retail/prices](https://prices.azure.com/api/retail/prices)

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

Excluded costs and workload features:

* 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.
* 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-193a4d8c9f7cdd8a1e2cad0fae8d95ed44aad86e` / `2026-10-22.planning.2`. Curve: `workload-2`.

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

### DynamoDB · Stored data

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

![DynamoDB · Stored data: monthly service charges by Stored data. Exact values are in the following table.](/images/diagrams/service-cost/7eac70dec153e94542fbe600d8b03ee31e5ff355c62fbbfc7bdfa802c82ca979-light.svg)

![DynamoDB · Stored data: monthly service charges by Stored data. Exact values are in the following table.](/images/diagrams/service-cost/1851b13cf3e2d0c953d96e597c27782ce3964ce93e527259bb6b35b749ed049e-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.

| Stored data (GiB-month) | DynamoDB | Target scenario | Azure Cosmos DB (serverless) | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | Azure Cosmos DB (serverless) | 0 | 0 |
| 10 | 2.5 | Azure Cosmos DB (serverless) | 2.5 | 0 |
| 100 | 25 | Azure Cosmos DB (serverless) | 25 | 0 |
| 1000 | 250 | Azure Cosmos DB (serverless) | 250 | 0 |
| 10000 | 2500 | Azure Cosmos DB (serverless) | 2500 | 0 |
| 100000 | 25000 | Azure Cosmos DB (serverless) | 25000 | 0 |

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Azure Cosmos DB (serverless) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| Azure Cosmos DB (serverless) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| Azure Cosmos DB (serverless) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| Azure Cosmos DB (serverless) | Origin list price · Control-plane calls | 0 | USD/requests |
| Azure Cosmos DB (serverless) | Representative item size | 1024 | bytes |
| Azure Cosmos DB (serverless) | Strongly consistent read fraction | 1 | fraction |
| Azure Cosmos DB (serverless) | Origin write-unit amplification | 1 | multiplier |
| Azure Cosmos DB (serverless) | Target reads per point read | 1 | operations |
| Azure Cosmos DB (serverless) | Target writes per item write | 1 | operations |
| Azure Cosmos DB (serverless) | Target list price · read | 0.00000025 | USD/read |
| Azure Cosmos DB (serverless) | Target list price · write | 0.000001375 | USD/write |
| Azure Cosmos DB (serverless) | Target price guess · provider operation | 0 | USD/provider operation |
| Azure Cosmos DB (serverless) | Target list price · GiB-month | 0.25 | USD/GiB-month |
| Azure Cosmos DB (serverless) | Target price guess · published GiB | 0 | USD/published GiB |
| Azure Cosmos DB (serverless) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Azure Cosmos DB (serverless) | Target list price · network GiB | 0.087 | USD/network GiB |
| Azure Cosmos DB (serverless) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Azure Cosmos DB (serverless) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Azure Cosmos DB (serverless) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Azure Cosmos DB (serverless) | Target price guess · resource-hour | 0 | USD/resource-hour |
| Azure Cosmos DB (serverless) | Target price guess · resource-month | 0 | USD/resource-month |
| Azure Cosmos DB (serverless) | Target price guess · input token | 0 | USD/input token |
| Azure Cosmos DB (serverless) | Target price guess · output token | 0 | USD/output token |
| Azure Cosmos DB (serverless) | Target monthly base charge | 0 | USD/month |
| Azure Cosmos DB (serverless) | Approximate target service minimum | 0 | USD/month |
| Azure Cosmos DB (serverless) | Minimum primary CPU | 2 | vCPU |
| Azure Cosmos DB (serverless) | Minimum primary RAM | 8 | GiB |
| Azure Cosmos DB (serverless) | Minimum primary disk | 100 | GiB |
| Azure Cosmos DB (serverless) | Additional full-price standby copy | 0 | 0 or 1 |
| Azure Cosmos DB (serverless) | Allocated share of provisioned cost | 1 | fraction |
| Azure Cosmos DB (serverless) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Azure Cosmos DB (serverless) | Planning peak / mean work | 2 | multiplier |
| Azure Cosmos DB (serverless) | Planning primary CPU utilization | 0.7 | fraction |
| Azure Cosmos DB (serverless) | Resident state reserved in RAM | 0.1 | fraction |
| Azure Cosmos DB (serverless) | Planning disk utilization | 0.8 | fraction |
| Azure Cosmos DB (serverless) | Maintenance and log disk reserve | 20 | GiB |
| Azure Cosmos DB (serverless) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Azure Cosmos DB (serverless) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Azure Cosmos DB (serverless) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Azure Cosmos DB (serverless) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Azure Cosmos DB (serverless) | 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. us-east-1 → eastus, USD/month.
* Source prices are reference charges, not an invoice. Target lines cover selected service usage/configuration only; adapter hosting and Tensor9 fees are excluded.
* Explicit tariff samples are not performance measurements or capacity qualification. No interpolation or break-even guarantee is implied.
* Variant assumptions show the first axis sample; any axis-dependent configuration is described by this curve's workload note.
* Rates are cited provider list prices, editable for discounts, commitments or another region. Workload translation and capacity coefficients remain editable planning assumptions, not benchmark measurements or a commercial quote.
* Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free.
* Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified.
* Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity.
* A declared adapter mapping and cost model do not establish implementation availability or service equivalence.
* This is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* 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.
* The control plane and table facet describe the same family workload; allocate shared capacity once, not once per catalog facet.
* No transactional, global-table, Streams or scan tariff is inferred from ordinary on-demand point units.
* Cosmos DB serverless bills consumed Request Units (USD 0.25 per million) and stored GB. Per-operation rates assume Microsoft's published 1 KB costs: a point read is 1 RU and an unindexed insert about 5.5 RU ([https://learn.microsoft.com/en-us/azure/cosmos-db/optimize-cost-reads-writes](https://learn.microsoft.com/en-us/azure/cosmos-db/optimize-cost-reads-writes)). Larger items, default indexing of every property, replaces (2x an insert) and strong or bounded-staleness reads (2x) cost more RU than these rates assume.
* AWS Price List API, AmazonDynamoDB offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json)
* Amazon DynamoDB pricing: [https://aws.amazon.com/dynamodb/pricing/](https://aws.amazon.com/dynamodb/pricing/)
* Azure Retail Prices API: [https://prices.azure.com/api/retail/prices](https://prices.azure.com/api/retail/prices)

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

Excluded costs and workload features:

* 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.
* 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-193a4d8c9f7cdd8a1e2cad0fae8d95ed44aad86e` / `2026-10-22.planning.2`. Curve: `workload-3`.

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

## DynamoDB → Azure Cosmos DB (serverless)

Origin API: `aws::1.0.0::dynamodb::table`. Target backend: `azure::1.0.0::cosmosdb::serverless`.

### DynamoDB · DynamoDB read units

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

![DynamoDB · DynamoDB read units: monthly service charges by DynamoDB read units. Exact values are in the following table.](/images/diagrams/service-cost/ea3bc9090b548f3dc6a61de0d2afe660848573007bdf228e9d9669b31dcb7a04-light.svg)

![DynamoDB · DynamoDB read units: monthly service charges by DynamoDB read units. Exact values are in the following table.](/images/diagrams/service-cost/424d72576778a35c05a00f8912c871c6e04a42a41dea3085eab8392709c56474-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.

| DynamoDB read units (per second) | DynamoDB | Target scenario | Azure Cosmos DB (serverless) | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | Azure Cosmos DB (serverless) | 0 | 0 |
| 1 | 0.3285 | Azure Cosmos DB (serverless) | 0.657 | 0.3285 |
| 10 | 3.285 | Azure Cosmos DB (serverless) | 6.57 | 3.285 |
| 100 | 32.85 | Azure Cosmos DB (serverless) | 65.7 | 32.85 |
| 1000 | 328.5 | Azure Cosmos DB (serverless) | 657 | 328.5 |
| 10000 | 3285 | Azure Cosmos DB (serverless) | 6570 | 3285 |

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Azure Cosmos DB (serverless) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| Azure Cosmos DB (serverless) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| Azure Cosmos DB (serverless) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| Azure Cosmos DB (serverless) | Origin list price · Control-plane calls | 0 | USD/requests |
| Azure Cosmos DB (serverless) | Representative item size | 1024 | bytes |
| Azure Cosmos DB (serverless) | Strongly consistent read fraction | 1 | fraction |
| Azure Cosmos DB (serverless) | Origin write-unit amplification | 1 | multiplier |
| Azure Cosmos DB (serverless) | Target reads per point read | 1 | operations |
| Azure Cosmos DB (serverless) | Target writes per item write | 1 | operations |
| Azure Cosmos DB (serverless) | Target list price · read | 0.00000025 | USD/read |
| Azure Cosmos DB (serverless) | Target list price · write | 0.000001375 | USD/write |
| Azure Cosmos DB (serverless) | Target price guess · provider operation | 0 | USD/provider operation |
| Azure Cosmos DB (serverless) | Target list price · GiB-month | 0.25 | USD/GiB-month |
| Azure Cosmos DB (serverless) | Target price guess · published GiB | 0 | USD/published GiB |
| Azure Cosmos DB (serverless) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Azure Cosmos DB (serverless) | Target list price · network GiB | 0.087 | USD/network GiB |
| Azure Cosmos DB (serverless) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Azure Cosmos DB (serverless) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Azure Cosmos DB (serverless) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Azure Cosmos DB (serverless) | Target price guess · resource-hour | 0 | USD/resource-hour |
| Azure Cosmos DB (serverless) | Target price guess · resource-month | 0 | USD/resource-month |
| Azure Cosmos DB (serverless) | Target price guess · input token | 0 | USD/input token |
| Azure Cosmos DB (serverless) | Target price guess · output token | 0 | USD/output token |
| Azure Cosmos DB (serverless) | Target monthly base charge | 0 | USD/month |
| Azure Cosmos DB (serverless) | Approximate target service minimum | 0 | USD/month |
| Azure Cosmos DB (serverless) | Minimum primary CPU | 2 | vCPU |
| Azure Cosmos DB (serverless) | Minimum primary RAM | 8 | GiB |
| Azure Cosmos DB (serverless) | Minimum primary disk | 100 | GiB |
| Azure Cosmos DB (serverless) | Additional full-price standby copy | 0 | 0 or 1 |
| Azure Cosmos DB (serverless) | Allocated share of provisioned cost | 1 | fraction |
| Azure Cosmos DB (serverless) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Azure Cosmos DB (serverless) | Planning peak / mean work | 2 | multiplier |
| Azure Cosmos DB (serverless) | Planning primary CPU utilization | 0.7 | fraction |
| Azure Cosmos DB (serverless) | Resident state reserved in RAM | 0.1 | fraction |
| Azure Cosmos DB (serverless) | Planning disk utilization | 0.8 | fraction |
| Azure Cosmos DB (serverless) | Maintenance and log disk reserve | 20 | GiB |
| Azure Cosmos DB (serverless) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Azure Cosmos DB (serverless) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Azure Cosmos DB (serverless) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Azure Cosmos DB (serverless) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Azure Cosmos DB (serverless) | Dependent object sink write price guess | 0.000005 | USD/write |

* Writes and storage remain independent. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
* Planning estimate · editable authored rates and sizing assumptions dated 2026-10-22; not verified provider prices. us-east-1 → eastus, USD/month.
* Source prices are reference charges, not an invoice. Target lines cover selected service usage/configuration only; adapter hosting and Tensor9 fees are excluded.
* Explicit tariff samples are not performance measurements or capacity qualification. No interpolation or break-even guarantee is implied.
* Variant assumptions show the first axis sample; any axis-dependent configuration is described by this curve's workload note.
* Rates are cited provider list prices, editable for discounts, commitments or another region. Workload translation and capacity coefficients remain editable planning assumptions, not benchmark measurements or a commercial quote.
* Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free.
* Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified.
* Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity.
* A declared adapter mapping and cost model do not establish implementation availability or service equivalence.
* This is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* 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.
* The control plane and table facet describe the same family workload; allocate shared capacity once, not once per catalog facet.
* No transactional, global-table, Streams or scan tariff is inferred from ordinary on-demand point units.
* Cosmos DB serverless bills consumed Request Units (USD 0.25 per million) and stored GB. Per-operation rates assume Microsoft's published 1 KB costs: a point read is 1 RU and an unindexed insert about 5.5 RU ([https://learn.microsoft.com/en-us/azure/cosmos-db/optimize-cost-reads-writes](https://learn.microsoft.com/en-us/azure/cosmos-db/optimize-cost-reads-writes)). Larger items, default indexing of every property, replaces (2x an insert) and strong or bounded-staleness reads (2x) cost more RU than these rates assume.
* AWS Price List API, AmazonDynamoDB offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json)
* Amazon DynamoDB pricing: [https://aws.amazon.com/dynamodb/pricing/](https://aws.amazon.com/dynamodb/pricing/)
* Azure Retail Prices API: [https://prices.azure.com/api/retail/prices](https://prices.azure.com/api/retail/prices)

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

Excluded costs and workload features:

* 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.
* 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-26501e747dcdbd0b7586f4ab58235e0ced69b13c` / `2026-10-22.planning.2`. Curve: `workload-1`.

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

### DynamoDB · DynamoDB write units

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

![DynamoDB · DynamoDB write units: monthly service charges by DynamoDB write units. Exact values are in the following table.](/images/diagrams/service-cost/9224f35abbe760c618be7e2441e81fe628b4e868e11afd4b77ec10208e39bada-light.svg)

![DynamoDB · DynamoDB write units: monthly service charges by DynamoDB write units. Exact values are in the following table.](/images/diagrams/service-cost/571fa6bb2ff5764a717cbbf803186018e1f0600298442ee4d53c2709dee11911-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.

| DynamoDB write units (per second) | DynamoDB | Target scenario | Azure Cosmos DB (serverless) | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | Azure Cosmos DB (serverless) | 0 | 0 |
| 1 | 1.6425 | Azure Cosmos DB (serverless) | 3.6135 | 1.971 |
| 10 | 16.425 | Azure Cosmos DB (serverless) | 36.135 | 19.71 |
| 100 | 164.25 | Azure Cosmos DB (serverless) | 361.35 | 197.1 |
| 1000 | 1642.5 | Azure Cosmos DB (serverless) | 3613.5 | 1971 |
| 10000 | 16425 | Azure Cosmos DB (serverless) | 36135 | 19710 |

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Azure Cosmos DB (serverless) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| Azure Cosmos DB (serverless) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| Azure Cosmos DB (serverless) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| Azure Cosmos DB (serverless) | Origin list price · Control-plane calls | 0 | USD/requests |
| Azure Cosmos DB (serverless) | Representative item size | 1024 | bytes |
| Azure Cosmos DB (serverless) | Strongly consistent read fraction | 1 | fraction |
| Azure Cosmos DB (serverless) | Origin write-unit amplification | 1 | multiplier |
| Azure Cosmos DB (serverless) | Target reads per point read | 1 | operations |
| Azure Cosmos DB (serverless) | Target writes per item write | 1 | operations |
| Azure Cosmos DB (serverless) | Target list price · read | 0.00000025 | USD/read |
| Azure Cosmos DB (serverless) | Target list price · write | 0.000001375 | USD/write |
| Azure Cosmos DB (serverless) | Target price guess · provider operation | 0 | USD/provider operation |
| Azure Cosmos DB (serverless) | Target list price · GiB-month | 0.25 | USD/GiB-month |
| Azure Cosmos DB (serverless) | Target price guess · published GiB | 0 | USD/published GiB |
| Azure Cosmos DB (serverless) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Azure Cosmos DB (serverless) | Target list price · network GiB | 0.087 | USD/network GiB |
| Azure Cosmos DB (serverless) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Azure Cosmos DB (serverless) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Azure Cosmos DB (serverless) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Azure Cosmos DB (serverless) | Target price guess · resource-hour | 0 | USD/resource-hour |
| Azure Cosmos DB (serverless) | Target price guess · resource-month | 0 | USD/resource-month |
| Azure Cosmos DB (serverless) | Target price guess · input token | 0 | USD/input token |
| Azure Cosmos DB (serverless) | Target price guess · output token | 0 | USD/output token |
| Azure Cosmos DB (serverless) | Target monthly base charge | 0 | USD/month |
| Azure Cosmos DB (serverless) | Approximate target service minimum | 0 | USD/month |
| Azure Cosmos DB (serverless) | Minimum primary CPU | 2 | vCPU |
| Azure Cosmos DB (serverless) | Minimum primary RAM | 8 | GiB |
| Azure Cosmos DB (serverless) | Minimum primary disk | 100 | GiB |
| Azure Cosmos DB (serverless) | Additional full-price standby copy | 0 | 0 or 1 |
| Azure Cosmos DB (serverless) | Allocated share of provisioned cost | 1 | fraction |
| Azure Cosmos DB (serverless) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Azure Cosmos DB (serverless) | Planning peak / mean work | 2 | multiplier |
| Azure Cosmos DB (serverless) | Planning primary CPU utilization | 0.7 | fraction |
| Azure Cosmos DB (serverless) | Resident state reserved in RAM | 0.1 | fraction |
| Azure Cosmos DB (serverless) | Planning disk utilization | 0.8 | fraction |
| Azure Cosmos DB (serverless) | Maintenance and log disk reserve | 20 | GiB |
| Azure Cosmos DB (serverless) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Azure Cosmos DB (serverless) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Azure Cosmos DB (serverless) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Azure Cosmos DB (serverless) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Azure Cosmos DB (serverless) | Dependent object sink write price guess | 0.000005 | USD/write |

* Reads and storage remain independent. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
* Planning estimate · editable authored rates and sizing assumptions dated 2026-10-22; not verified provider prices. us-east-1 → eastus, USD/month.
* Source prices are reference charges, not an invoice. Target lines cover selected service usage/configuration only; adapter hosting and Tensor9 fees are excluded.
* Explicit tariff samples are not performance measurements or capacity qualification. No interpolation or break-even guarantee is implied.
* Variant assumptions show the first axis sample; any axis-dependent configuration is described by this curve's workload note.
* Rates are cited provider list prices, editable for discounts, commitments or another region. Workload translation and capacity coefficients remain editable planning assumptions, not benchmark measurements or a commercial quote.
* Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free.
* Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified.
* Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity.
* A declared adapter mapping and cost model do not establish implementation availability or service equivalence.
* This is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* 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.
* The control plane and table facet describe the same family workload; allocate shared capacity once, not once per catalog facet.
* No transactional, global-table, Streams or scan tariff is inferred from ordinary on-demand point units.
* Cosmos DB serverless bills consumed Request Units (USD 0.25 per million) and stored GB. Per-operation rates assume Microsoft's published 1 KB costs: a point read is 1 RU and an unindexed insert about 5.5 RU ([https://learn.microsoft.com/en-us/azure/cosmos-db/optimize-cost-reads-writes](https://learn.microsoft.com/en-us/azure/cosmos-db/optimize-cost-reads-writes)). Larger items, default indexing of every property, replaces (2x an insert) and strong or bounded-staleness reads (2x) cost more RU than these rates assume.
* AWS Price List API, AmazonDynamoDB offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json)
* Amazon DynamoDB pricing: [https://aws.amazon.com/dynamodb/pricing/](https://aws.amazon.com/dynamodb/pricing/)
* Azure Retail Prices API: [https://prices.azure.com/api/retail/prices](https://prices.azure.com/api/retail/prices)

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

Excluded costs and workload features:

* 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.
* 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-26501e747dcdbd0b7586f4ab58235e0ced69b13c` / `2026-10-22.planning.2`. Curve: `workload-2`.

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

### DynamoDB · Stored data

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

![DynamoDB · Stored data: monthly service charges by Stored data. Exact values are in the following table.](/images/diagrams/service-cost/7eac70dec153e94542fbe600d8b03ee31e5ff355c62fbbfc7bdfa802c82ca979-light.svg)

![DynamoDB · Stored data: monthly service charges by Stored data. Exact values are in the following table.](/images/diagrams/service-cost/1851b13cf3e2d0c953d96e597c27782ce3964ce93e527259bb6b35b749ed049e-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.

| Stored data (GiB-month) | DynamoDB | Target scenario | Azure Cosmos DB (serverless) | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | Azure Cosmos DB (serverless) | 0 | 0 |
| 10 | 2.5 | Azure Cosmos DB (serverless) | 2.5 | 0 |
| 100 | 25 | Azure Cosmos DB (serverless) | 25 | 0 |
| 1000 | 250 | Azure Cosmos DB (serverless) | 250 | 0 |
| 10000 | 2500 | Azure Cosmos DB (serverless) | 2500 | 0 |
| 100000 | 25000 | Azure Cosmos DB (serverless) | 25000 | 0 |

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Azure Cosmos DB (serverless) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| Azure Cosmos DB (serverless) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| Azure Cosmos DB (serverless) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| Azure Cosmos DB (serverless) | Origin list price · Control-plane calls | 0 | USD/requests |
| Azure Cosmos DB (serverless) | Representative item size | 1024 | bytes |
| Azure Cosmos DB (serverless) | Strongly consistent read fraction | 1 | fraction |
| Azure Cosmos DB (serverless) | Origin write-unit amplification | 1 | multiplier |
| Azure Cosmos DB (serverless) | Target reads per point read | 1 | operations |
| Azure Cosmos DB (serverless) | Target writes per item write | 1 | operations |
| Azure Cosmos DB (serverless) | Target list price · read | 0.00000025 | USD/read |
| Azure Cosmos DB (serverless) | Target list price · write | 0.000001375 | USD/write |
| Azure Cosmos DB (serverless) | Target price guess · provider operation | 0 | USD/provider operation |
| Azure Cosmos DB (serverless) | Target list price · GiB-month | 0.25 | USD/GiB-month |
| Azure Cosmos DB (serverless) | Target price guess · published GiB | 0 | USD/published GiB |
| Azure Cosmos DB (serverless) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Azure Cosmos DB (serverless) | Target list price · network GiB | 0.087 | USD/network GiB |
| Azure Cosmos DB (serverless) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Azure Cosmos DB (serverless) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Azure Cosmos DB (serverless) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Azure Cosmos DB (serverless) | Target price guess · resource-hour | 0 | USD/resource-hour |
| Azure Cosmos DB (serverless) | Target price guess · resource-month | 0 | USD/resource-month |
| Azure Cosmos DB (serverless) | Target price guess · input token | 0 | USD/input token |
| Azure Cosmos DB (serverless) | Target price guess · output token | 0 | USD/output token |
| Azure Cosmos DB (serverless) | Target monthly base charge | 0 | USD/month |
| Azure Cosmos DB (serverless) | Approximate target service minimum | 0 | USD/month |
| Azure Cosmos DB (serverless) | Minimum primary CPU | 2 | vCPU |
| Azure Cosmos DB (serverless) | Minimum primary RAM | 8 | GiB |
| Azure Cosmos DB (serverless) | Minimum primary disk | 100 | GiB |
| Azure Cosmos DB (serverless) | Additional full-price standby copy | 0 | 0 or 1 |
| Azure Cosmos DB (serverless) | Allocated share of provisioned cost | 1 | fraction |
| Azure Cosmos DB (serverless) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Azure Cosmos DB (serverless) | Planning peak / mean work | 2 | multiplier |
| Azure Cosmos DB (serverless) | Planning primary CPU utilization | 0.7 | fraction |
| Azure Cosmos DB (serverless) | Resident state reserved in RAM | 0.1 | fraction |
| Azure Cosmos DB (serverless) | Planning disk utilization | 0.8 | fraction |
| Azure Cosmos DB (serverless) | Maintenance and log disk reserve | 20 | GiB |
| Azure Cosmos DB (serverless) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Azure Cosmos DB (serverless) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Azure Cosmos DB (serverless) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Azure Cosmos DB (serverless) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Azure Cosmos DB (serverless) | 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. us-east-1 → eastus, USD/month.
* Source prices are reference charges, not an invoice. Target lines cover selected service usage/configuration only; adapter hosting and Tensor9 fees are excluded.
* Explicit tariff samples are not performance measurements or capacity qualification. No interpolation or break-even guarantee is implied.
* Variant assumptions show the first axis sample; any axis-dependent configuration is described by this curve's workload note.
* Rates are cited provider list prices, editable for discounts, commitments or another region. Workload translation and capacity coefficients remain editable planning assumptions, not benchmark measurements or a commercial quote.
* Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free.
* Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified.
* Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity.
* A declared adapter mapping and cost model do not establish implementation availability or service equivalence.
* This is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* 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.
* The control plane and table facet describe the same family workload; allocate shared capacity once, not once per catalog facet.
* No transactional, global-table, Streams or scan tariff is inferred from ordinary on-demand point units.
* Cosmos DB serverless bills consumed Request Units (USD 0.25 per million) and stored GB. Per-operation rates assume Microsoft's published 1 KB costs: a point read is 1 RU and an unindexed insert about 5.5 RU ([https://learn.microsoft.com/en-us/azure/cosmos-db/optimize-cost-reads-writes](https://learn.microsoft.com/en-us/azure/cosmos-db/optimize-cost-reads-writes)). Larger items, default indexing of every property, replaces (2x an insert) and strong or bounded-staleness reads (2x) cost more RU than these rates assume.
* AWS Price List API, AmazonDynamoDB offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json)
* Amazon DynamoDB pricing: [https://aws.amazon.com/dynamodb/pricing/](https://aws.amazon.com/dynamodb/pricing/)
* Azure Retail Prices API: [https://prices.azure.com/api/retail/prices](https://prices.azure.com/api/retail/prices)

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

Excluded costs and workload features:

* 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.
* 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-26501e747dcdbd0b7586f4ab58235e0ced69b13c` / `2026-10-22.planning.2`. Curve: `workload-3`.

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

## DynamoDB → Cloud Bigtable

Origin API: `aws::1.0.0::dynamodb::control`. Target backend: `google::1.0.0::bigtable`.

### DynamoDB · DynamoDB read units

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

![DynamoDB · DynamoDB read units: monthly service charges by DynamoDB read units. Exact values are in the following table.](/images/diagrams/service-cost/0dd02f4b41b43c68a3abd70bb3ab83ee7eb26f2ab2ac0f2bd884278c5eb9dacb-light.svg)

![DynamoDB · DynamoDB read units: monthly service charges by DynamoDB read units. Exact values are in the following table.](/images/diagrams/service-cost/163abfdbf86e279c4809dba6d166b6b690d7a2981ec8af2791aa38671e2e2323-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.

| DynamoDB read units (per second) | DynamoDB | Target scenario | Cloud Bigtable | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | Cloud Bigtable (one copy) | 474.5 | 474.5 |
| 0 | 0 | Cloud Bigtable (two copies) | 474.5 | 474.5 |
| 1 | 0.3285 | Cloud Bigtable (one copy) | 474.5 | 474.1715 |
| 1 | 0.3285 | Cloud Bigtable (two copies) | 474.5 | 474.1715 |
| 10 | 3.285 | Cloud Bigtable (one copy) | 474.5 | 471.215 |
| 10 | 3.285 | Cloud Bigtable (two copies) | 474.5 | 471.215 |
| 100 | 32.85 | Cloud Bigtable (one copy) | 474.5 | 441.65 |
| 100 | 32.85 | Cloud Bigtable (two copies) | 474.5 | 441.65 |
| 1000 | 328.5 | Cloud Bigtable (one copy) | 474.5 | 146 |
| 1000 | 328.5 | Cloud Bigtable (two copies) | 474.5 | 146 |
| 10000 | 3285 | Cloud Bigtable (one copy) | 949 | -2336 |
| 10000 | 3285 | Cloud Bigtable (two copies) | 949 | -2336 |

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Cloud Bigtable (one copy) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| Cloud Bigtable (one copy) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| Cloud Bigtable (one copy) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| Cloud Bigtable (one copy) | Origin list price · Control-plane calls | 0 | USD/requests |
| Cloud Bigtable (one copy) | Representative item size | 1024 | bytes |
| Cloud Bigtable (one copy) | Strongly consistent read fraction | 1 | fraction |
| Cloud Bigtable (one copy) | Origin write-unit amplification | 1 | multiplier |
| Cloud Bigtable (one copy) | Target reads per point read | 1 | operations |
| Cloud Bigtable (one copy) | Target writes per item write | 1 | operations |
| Cloud Bigtable (one copy) | Target price guess · read | 0 | USD/read |
| Cloud Bigtable (one copy) | Target price guess · write | 0 | USD/write |
| Cloud Bigtable (one copy) | Target price guess · provider operation | 0 | USD/provider operation |
| Cloud Bigtable (one copy) | Target list price · GiB-month | 0.17 | USD/GiB-month |
| Cloud Bigtable (one copy) | Target price guess · published GiB | 0 | USD/published GiB |
| Cloud Bigtable (one copy) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Cloud Bigtable (one copy) | Target list price · network GiB | 0.12 | USD/network GiB |
| Cloud Bigtable (one copy) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Cloud Bigtable (one copy) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Cloud Bigtable (one copy) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Cloud Bigtable (one copy) | Target list price · resource-hour | 0.65 | USD/resource-hour |
| Cloud Bigtable (one copy) | Target price guess · resource-month | 0 | USD/resource-month |
| Cloud Bigtable (one copy) | Target price guess · input token | 0 | USD/input token |
| Cloud Bigtable (one copy) | Target price guess · output token | 0 | USD/output token |
| Cloud Bigtable (one copy) | Target monthly base charge | 0 | USD/month |
| Cloud Bigtable (one copy) | Target service minimum | 474.5 | USD/month |
| Cloud Bigtable (one copy) | Minimum primary CPU | 2 | vCPU |
| Cloud Bigtable (one copy) | Minimum primary RAM | 8 | GiB |
| Cloud Bigtable (one copy) | Minimum primary disk | 100 | GiB |
| Cloud Bigtable (one copy) | Additional full-price standby copy | 0 | 0 or 1 |
| Cloud Bigtable (one copy) | Allocated share of provisioned cost | 1 | fraction |
| Cloud Bigtable (one copy) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Cloud Bigtable (one copy) | Planning peak / mean work | 2 | multiplier |
| Cloud Bigtable (one copy) | Planning primary CPU utilization | 0.7 | fraction |
| Cloud Bigtable (one copy) | Resident state reserved in RAM | 0.1 | fraction |
| Cloud Bigtable (one copy) | Planning disk utilization | 0.8 | fraction |
| Cloud Bigtable (one copy) | Maintenance and log disk reserve | 20 | GiB |
| Cloud Bigtable (one copy) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Cloud Bigtable (one copy) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Cloud Bigtable (one copy) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Cloud Bigtable (one copy) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Cloud Bigtable (one copy) | Dependent object sink write price guess | 0.000005 | USD/write |
| Cloud Bigtable (two copies) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| Cloud Bigtable (two copies) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| Cloud Bigtable (two copies) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| Cloud Bigtable (two copies) | Origin list price · Control-plane calls | 0 | USD/requests |
| Cloud Bigtable (two copies) | Representative item size | 1024 | bytes |
| Cloud Bigtable (two copies) | Strongly consistent read fraction | 1 | fraction |
| Cloud Bigtable (two copies) | Origin write-unit amplification | 1 | multiplier |
| Cloud Bigtable (two copies) | Target reads per point read | 1 | operations |
| Cloud Bigtable (two copies) | Target writes per item write | 1 | operations |
| Cloud Bigtable (two copies) | Target price guess · read | 0 | USD/read |
| Cloud Bigtable (two copies) | Target price guess · write | 0 | USD/write |
| Cloud Bigtable (two copies) | Target price guess · provider operation | 0 | USD/provider operation |
| Cloud Bigtable (two copies) | Target list price · GiB-month | 0.17 | USD/GiB-month |
| Cloud Bigtable (two copies) | Target price guess · published GiB | 0 | USD/published GiB |
| Cloud Bigtable (two copies) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Cloud Bigtable (two copies) | Target list price · network GiB | 0.12 | USD/network GiB |
| Cloud Bigtable (two copies) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Cloud Bigtable (two copies) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Cloud Bigtable (two copies) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Cloud Bigtable (two copies) | Target list price · resource-hour | 0.65 | USD/resource-hour |
| Cloud Bigtable (two copies) | Target price guess · resource-month | 0 | USD/resource-month |
| Cloud Bigtable (two copies) | Target price guess · input token | 0 | USD/input token |
| Cloud Bigtable (two copies) | Target price guess · output token | 0 | USD/output token |
| Cloud Bigtable (two copies) | Target monthly base charge | 0 | USD/month |
| Cloud Bigtable (two copies) | Target service minimum | 474.5 | USD/month |
| Cloud Bigtable (two copies) | Minimum primary CPU | 2 | vCPU |
| Cloud Bigtable (two copies) | Minimum primary RAM | 8 | GiB |
| Cloud Bigtable (two copies) | Minimum primary disk | 100 | GiB |
| Cloud Bigtable (two copies) | Additional full-price standby copy | 1 | 0 or 1 |
| Cloud Bigtable (two copies) | Allocated share of provisioned cost | 1 | fraction |
| Cloud Bigtable (two copies) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Cloud Bigtable (two copies) | Planning peak / mean work | 2 | multiplier |
| Cloud Bigtable (two copies) | Planning primary CPU utilization | 0.7 | fraction |
| Cloud Bigtable (two copies) | Resident state reserved in RAM | 0.1 | fraction |
| Cloud Bigtable (two copies) | Planning disk utilization | 0.8 | fraction |
| Cloud Bigtable (two copies) | Maintenance and log disk reserve | 20 | GiB |
| Cloud Bigtable (two copies) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Cloud Bigtable (two copies) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Cloud Bigtable (two copies) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Cloud Bigtable (two copies) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Cloud Bigtable (two copies) | Dependent object sink write price guess | 0.000005 | USD/write |

* Writes and storage remain independent. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
* Planning estimate · editable authored rates and sizing assumptions dated 2026-10-22; not verified provider prices. us-east-1 → 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 is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* 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.
* The control plane and table facet describe the same family workload; allocate shared capacity once, not once per catalog facet.
* No transactional, global-table, Streams or scan tariff is inferred from ordinary on-demand point units.
* Bigtable bills whole provisioned nodes per hour, not vCPU or RAM, plus SSD storage of the compressed physical data. Nodes are sized from planning-peak reads and writes against Google's per-node SSD throughput, with a one-node minimum. A replicated instance bills every cluster's nodes and its own copy of the data; this profile prices one cluster, so the standby selection does not add a cluster.
* AWS Price List API, AmazonDynamoDB offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json)
* Amazon DynamoDB pricing: [https://aws.amazon.com/dynamodb/pricing/](https://aws.amazon.com/dynamodb/pricing/)
* Bigtable pricing: [https://cloud.google.com/bigtable/pricing](https://cloud.google.com/bigtable/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.
* 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-54c656ab4ad36cede3d0182c3bf9faef6669d51d` / `2026-10-22.planning.2`. Curve: `workload-1`.

Sources: [AWS Price List API, AmazonDynamoDB offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json), [Amazon DynamoDB pricing](https://aws.amazon.com/dynamodb/pricing/), [Bigtable pricing](https://cloud.google.com/bigtable/pricing).

### DynamoDB · DynamoDB write units

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

![DynamoDB · DynamoDB write units: monthly service charges by DynamoDB write units. Exact values are in the following table.](/images/diagrams/service-cost/1c5ea8c6fe4ac29383abb12b8bcabc6178137361caa4576231b10dc44cb48b0e-light.svg)

![DynamoDB · DynamoDB write units: monthly service charges by DynamoDB write units. Exact values are in the following table.](/images/diagrams/service-cost/6f1400a375cb14883894d528c6f81e8edf9d275f8ae0757ab1ff99319e46b2d7-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.

| DynamoDB write units (per second) | DynamoDB | Target scenario | Cloud Bigtable | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | Cloud Bigtable (one copy) | 474.5 | 474.5 |
| 0 | 0 | Cloud Bigtable (two copies) | 474.5 | 474.5 |
| 1 | 1.6425 | Cloud Bigtable (one copy) | 474.5 | 472.8575 |
| 1 | 1.6425 | Cloud Bigtable (two copies) | 474.5 | 472.8575 |
| 10 | 16.425 | Cloud Bigtable (one copy) | 474.5 | 458.075 |
| 10 | 16.425 | Cloud Bigtable (two copies) | 474.5 | 458.075 |
| 100 | 164.25 | Cloud Bigtable (one copy) | 474.5 | 310.25 |
| 100 | 164.25 | Cloud Bigtable (two copies) | 474.5 | 310.25 |
| 1000 | 1642.5 | Cloud Bigtable (one copy) | 474.5 | -1168 |
| 1000 | 1642.5 | Cloud Bigtable (two copies) | 474.5 | -1168 |
| 10000 | 16425 | Cloud Bigtable (one copy) | 1423.5 | -15001.5 |
| 10000 | 16425 | Cloud Bigtable (two copies) | 1423.5 | -15001.5 |

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Cloud Bigtable (one copy) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| Cloud Bigtable (one copy) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| Cloud Bigtable (one copy) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| Cloud Bigtable (one copy) | Origin list price · Control-plane calls | 0 | USD/requests |
| Cloud Bigtable (one copy) | Representative item size | 1024 | bytes |
| Cloud Bigtable (one copy) | Strongly consistent read fraction | 1 | fraction |
| Cloud Bigtable (one copy) | Origin write-unit amplification | 1 | multiplier |
| Cloud Bigtable (one copy) | Target reads per point read | 1 | operations |
| Cloud Bigtable (one copy) | Target writes per item write | 1 | operations |
| Cloud Bigtable (one copy) | Target price guess · read | 0 | USD/read |
| Cloud Bigtable (one copy) | Target price guess · write | 0 | USD/write |
| Cloud Bigtable (one copy) | Target price guess · provider operation | 0 | USD/provider operation |
| Cloud Bigtable (one copy) | Target list price · GiB-month | 0.17 | USD/GiB-month |
| Cloud Bigtable (one copy) | Target price guess · published GiB | 0 | USD/published GiB |
| Cloud Bigtable (one copy) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Cloud Bigtable (one copy) | Target list price · network GiB | 0.12 | USD/network GiB |
| Cloud Bigtable (one copy) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Cloud Bigtable (one copy) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Cloud Bigtable (one copy) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Cloud Bigtable (one copy) | Target list price · resource-hour | 0.65 | USD/resource-hour |
| Cloud Bigtable (one copy) | Target price guess · resource-month | 0 | USD/resource-month |
| Cloud Bigtable (one copy) | Target price guess · input token | 0 | USD/input token |
| Cloud Bigtable (one copy) | Target price guess · output token | 0 | USD/output token |
| Cloud Bigtable (one copy) | Target monthly base charge | 0 | USD/month |
| Cloud Bigtable (one copy) | Target service minimum | 474.5 | USD/month |
| Cloud Bigtable (one copy) | Minimum primary CPU | 2 | vCPU |
| Cloud Bigtable (one copy) | Minimum primary RAM | 8 | GiB |
| Cloud Bigtable (one copy) | Minimum primary disk | 100 | GiB |
| Cloud Bigtable (one copy) | Additional full-price standby copy | 0 | 0 or 1 |
| Cloud Bigtable (one copy) | Allocated share of provisioned cost | 1 | fraction |
| Cloud Bigtable (one copy) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Cloud Bigtable (one copy) | Planning peak / mean work | 2 | multiplier |
| Cloud Bigtable (one copy) | Planning primary CPU utilization | 0.7 | fraction |
| Cloud Bigtable (one copy) | Resident state reserved in RAM | 0.1 | fraction |
| Cloud Bigtable (one copy) | Planning disk utilization | 0.8 | fraction |
| Cloud Bigtable (one copy) | Maintenance and log disk reserve | 20 | GiB |
| Cloud Bigtable (one copy) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Cloud Bigtable (one copy) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Cloud Bigtable (one copy) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Cloud Bigtable (one copy) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Cloud Bigtable (one copy) | Dependent object sink write price guess | 0.000005 | USD/write |
| Cloud Bigtable (two copies) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| Cloud Bigtable (two copies) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| Cloud Bigtable (two copies) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| Cloud Bigtable (two copies) | Origin list price · Control-plane calls | 0 | USD/requests |
| Cloud Bigtable (two copies) | Representative item size | 1024 | bytes |
| Cloud Bigtable (two copies) | Strongly consistent read fraction | 1 | fraction |
| Cloud Bigtable (two copies) | Origin write-unit amplification | 1 | multiplier |
| Cloud Bigtable (two copies) | Target reads per point read | 1 | operations |
| Cloud Bigtable (two copies) | Target writes per item write | 1 | operations |
| Cloud Bigtable (two copies) | Target price guess · read | 0 | USD/read |
| Cloud Bigtable (two copies) | Target price guess · write | 0 | USD/write |
| Cloud Bigtable (two copies) | Target price guess · provider operation | 0 | USD/provider operation |
| Cloud Bigtable (two copies) | Target list price · GiB-month | 0.17 | USD/GiB-month |
| Cloud Bigtable (two copies) | Target price guess · published GiB | 0 | USD/published GiB |
| Cloud Bigtable (two copies) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Cloud Bigtable (two copies) | Target list price · network GiB | 0.12 | USD/network GiB |
| Cloud Bigtable (two copies) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Cloud Bigtable (two copies) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Cloud Bigtable (two copies) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Cloud Bigtable (two copies) | Target list price · resource-hour | 0.65 | USD/resource-hour |
| Cloud Bigtable (two copies) | Target price guess · resource-month | 0 | USD/resource-month |
| Cloud Bigtable (two copies) | Target price guess · input token | 0 | USD/input token |
| Cloud Bigtable (two copies) | Target price guess · output token | 0 | USD/output token |
| Cloud Bigtable (two copies) | Target monthly base charge | 0 | USD/month |
| Cloud Bigtable (two copies) | Target service minimum | 474.5 | USD/month |
| Cloud Bigtable (two copies) | Minimum primary CPU | 2 | vCPU |
| Cloud Bigtable (two copies) | Minimum primary RAM | 8 | GiB |
| Cloud Bigtable (two copies) | Minimum primary disk | 100 | GiB |
| Cloud Bigtable (two copies) | Additional full-price standby copy | 1 | 0 or 1 |
| Cloud Bigtable (two copies) | Allocated share of provisioned cost | 1 | fraction |
| Cloud Bigtable (two copies) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Cloud Bigtable (two copies) | Planning peak / mean work | 2 | multiplier |
| Cloud Bigtable (two copies) | Planning primary CPU utilization | 0.7 | fraction |
| Cloud Bigtable (two copies) | Resident state reserved in RAM | 0.1 | fraction |
| Cloud Bigtable (two copies) | Planning disk utilization | 0.8 | fraction |
| Cloud Bigtable (two copies) | Maintenance and log disk reserve | 20 | GiB |
| Cloud Bigtable (two copies) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Cloud Bigtable (two copies) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Cloud Bigtable (two copies) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Cloud Bigtable (two copies) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Cloud Bigtable (two copies) | Dependent object sink write price guess | 0.000005 | USD/write |

* Reads and storage remain independent. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
* Planning estimate · editable authored rates and sizing assumptions dated 2026-10-22; not verified provider prices. us-east-1 → 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 is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* 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.
* The control plane and table facet describe the same family workload; allocate shared capacity once, not once per catalog facet.
* No transactional, global-table, Streams or scan tariff is inferred from ordinary on-demand point units.
* Bigtable bills whole provisioned nodes per hour, not vCPU or RAM, plus SSD storage of the compressed physical data. Nodes are sized from planning-peak reads and writes against Google's per-node SSD throughput, with a one-node minimum. A replicated instance bills every cluster's nodes and its own copy of the data; this profile prices one cluster, so the standby selection does not add a cluster.
* AWS Price List API, AmazonDynamoDB offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json)
* Amazon DynamoDB pricing: [https://aws.amazon.com/dynamodb/pricing/](https://aws.amazon.com/dynamodb/pricing/)
* Bigtable pricing: [https://cloud.google.com/bigtable/pricing](https://cloud.google.com/bigtable/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.
* 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-54c656ab4ad36cede3d0182c3bf9faef6669d51d` / `2026-10-22.planning.2`. Curve: `workload-2`.

Sources: [AWS Price List API, AmazonDynamoDB offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json), [Amazon DynamoDB pricing](https://aws.amazon.com/dynamodb/pricing/), [Bigtable pricing](https://cloud.google.com/bigtable/pricing).

### DynamoDB · Stored data

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

![DynamoDB · Stored data: monthly service charges by Stored data. Exact values are in the following table.](/images/diagrams/service-cost/46c8598a45f64e1bdd92ecd34405ca67065483452cc2021645029c00cba85c4f-light.svg)

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

| Stored data (GiB-month) | DynamoDB | Target scenario | Cloud Bigtable | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | Cloud Bigtable (one copy) | 474.5 | 474.5 |
| 0 | 0 | Cloud Bigtable (two copies) | 474.5 | 474.5 |
| 10 | 2.5 | Cloud Bigtable (one copy) | 476.2 | 473.7 |
| 10 | 2.5 | Cloud Bigtable (two copies) | 476.2 | 473.7 |
| 100 | 25 | Cloud Bigtable (one copy) | 491.5 | 466.5 |
| 100 | 25 | Cloud Bigtable (two copies) | 491.5 | 466.5 |
| 1000 | 250 | Cloud Bigtable (one copy) | 644.5 | 394.5 |
| 1000 | 250 | Cloud Bigtable (two copies) | 644.5 | 394.5 |
| 10000 | 2500 | Cloud Bigtable (one copy) | 2174.5 | -325.5 |
| 10000 | 2500 | Cloud Bigtable (two copies) | 2174.5 | -325.5 |
| 100000 | 25000 | Cloud Bigtable (one copy) | 17474.5 | -7525.5 |
| 100000 | 25000 | Cloud Bigtable (two copies) | 17474.5 | -7525.5 |

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Cloud Bigtable (one copy) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| Cloud Bigtable (one copy) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| Cloud Bigtable (one copy) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| Cloud Bigtable (one copy) | Origin list price · Control-plane calls | 0 | USD/requests |
| Cloud Bigtable (one copy) | Representative item size | 1024 | bytes |
| Cloud Bigtable (one copy) | Strongly consistent read fraction | 1 | fraction |
| Cloud Bigtable (one copy) | Origin write-unit amplification | 1 | multiplier |
| Cloud Bigtable (one copy) | Target reads per point read | 1 | operations |
| Cloud Bigtable (one copy) | Target writes per item write | 1 | operations |
| Cloud Bigtable (one copy) | Target price guess · read | 0 | USD/read |
| Cloud Bigtable (one copy) | Target price guess · write | 0 | USD/write |
| Cloud Bigtable (one copy) | Target price guess · provider operation | 0 | USD/provider operation |
| Cloud Bigtable (one copy) | Target list price · GiB-month | 0.17 | USD/GiB-month |
| Cloud Bigtable (one copy) | Target price guess · published GiB | 0 | USD/published GiB |
| Cloud Bigtable (one copy) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Cloud Bigtable (one copy) | Target list price · network GiB | 0.12 | USD/network GiB |
| Cloud Bigtable (one copy) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Cloud Bigtable (one copy) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Cloud Bigtable (one copy) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Cloud Bigtable (one copy) | Target list price · resource-hour | 0.65 | USD/resource-hour |
| Cloud Bigtable (one copy) | Target price guess · resource-month | 0 | USD/resource-month |
| Cloud Bigtable (one copy) | Target price guess · input token | 0 | USD/input token |
| Cloud Bigtable (one copy) | Target price guess · output token | 0 | USD/output token |
| Cloud Bigtable (one copy) | Target monthly base charge | 0 | USD/month |
| Cloud Bigtable (one copy) | Target service minimum | 474.5 | USD/month |
| Cloud Bigtable (one copy) | Minimum primary CPU | 2 | vCPU |
| Cloud Bigtable (one copy) | Minimum primary RAM | 8 | GiB |
| Cloud Bigtable (one copy) | Minimum primary disk | 100 | GiB |
| Cloud Bigtable (one copy) | Additional full-price standby copy | 0 | 0 or 1 |
| Cloud Bigtable (one copy) | Allocated share of provisioned cost | 1 | fraction |
| Cloud Bigtable (one copy) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Cloud Bigtable (one copy) | Planning peak / mean work | 2 | multiplier |
| Cloud Bigtable (one copy) | Planning primary CPU utilization | 0.7 | fraction |
| Cloud Bigtable (one copy) | Resident state reserved in RAM | 0.1 | fraction |
| Cloud Bigtable (one copy) | Planning disk utilization | 0.8 | fraction |
| Cloud Bigtable (one copy) | Maintenance and log disk reserve | 20 | GiB |
| Cloud Bigtable (one copy) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Cloud Bigtable (one copy) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Cloud Bigtable (one copy) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Cloud Bigtable (one copy) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Cloud Bigtable (one copy) | Dependent object sink write price guess | 0.000005 | USD/write |
| Cloud Bigtable (two copies) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| Cloud Bigtable (two copies) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| Cloud Bigtable (two copies) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| Cloud Bigtable (two copies) | Origin list price · Control-plane calls | 0 | USD/requests |
| Cloud Bigtable (two copies) | Representative item size | 1024 | bytes |
| Cloud Bigtable (two copies) | Strongly consistent read fraction | 1 | fraction |
| Cloud Bigtable (two copies) | Origin write-unit amplification | 1 | multiplier |
| Cloud Bigtable (two copies) | Target reads per point read | 1 | operations |
| Cloud Bigtable (two copies) | Target writes per item write | 1 | operations |
| Cloud Bigtable (two copies) | Target price guess · read | 0 | USD/read |
| Cloud Bigtable (two copies) | Target price guess · write | 0 | USD/write |
| Cloud Bigtable (two copies) | Target price guess · provider operation | 0 | USD/provider operation |
| Cloud Bigtable (two copies) | Target list price · GiB-month | 0.17 | USD/GiB-month |
| Cloud Bigtable (two copies) | Target price guess · published GiB | 0 | USD/published GiB |
| Cloud Bigtable (two copies) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Cloud Bigtable (two copies) | Target list price · network GiB | 0.12 | USD/network GiB |
| Cloud Bigtable (two copies) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Cloud Bigtable (two copies) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Cloud Bigtable (two copies) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Cloud Bigtable (two copies) | Target list price · resource-hour | 0.65 | USD/resource-hour |
| Cloud Bigtable (two copies) | Target price guess · resource-month | 0 | USD/resource-month |
| Cloud Bigtable (two copies) | Target price guess · input token | 0 | USD/input token |
| Cloud Bigtable (two copies) | Target price guess · output token | 0 | USD/output token |
| Cloud Bigtable (two copies) | Target monthly base charge | 0 | USD/month |
| Cloud Bigtable (two copies) | Target service minimum | 474.5 | USD/month |
| Cloud Bigtable (two copies) | Minimum primary CPU | 2 | vCPU |
| Cloud Bigtable (two copies) | Minimum primary RAM | 8 | GiB |
| Cloud Bigtable (two copies) | Minimum primary disk | 100 | GiB |
| Cloud Bigtable (two copies) | Additional full-price standby copy | 1 | 0 or 1 |
| Cloud Bigtable (two copies) | Allocated share of provisioned cost | 1 | fraction |
| Cloud Bigtable (two copies) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Cloud Bigtable (two copies) | Planning peak / mean work | 2 | multiplier |
| Cloud Bigtable (two copies) | Planning primary CPU utilization | 0.7 | fraction |
| Cloud Bigtable (two copies) | Resident state reserved in RAM | 0.1 | fraction |
| Cloud Bigtable (two copies) | Planning disk utilization | 0.8 | fraction |
| Cloud Bigtable (two copies) | Maintenance and log disk reserve | 20 | GiB |
| Cloud Bigtable (two copies) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Cloud Bigtable (two copies) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Cloud Bigtable (two copies) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Cloud Bigtable (two copies) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Cloud Bigtable (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. us-east-1 → 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 is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* 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.
* The control plane and table facet describe the same family workload; allocate shared capacity once, not once per catalog facet.
* No transactional, global-table, Streams or scan tariff is inferred from ordinary on-demand point units.
* Bigtable bills whole provisioned nodes per hour, not vCPU or RAM, plus SSD storage of the compressed physical data. Nodes are sized from planning-peak reads and writes against Google's per-node SSD throughput, with a one-node minimum. A replicated instance bills every cluster's nodes and its own copy of the data; this profile prices one cluster, so the standby selection does not add a cluster.
* AWS Price List API, AmazonDynamoDB offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json)
* Amazon DynamoDB pricing: [https://aws.amazon.com/dynamodb/pricing/](https://aws.amazon.com/dynamodb/pricing/)
* Bigtable pricing: [https://cloud.google.com/bigtable/pricing](https://cloud.google.com/bigtable/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.
* 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-54c656ab4ad36cede3d0182c3bf9faef6669d51d` / `2026-10-22.planning.2`. Curve: `workload-3`.

Sources: [AWS Price List API, AmazonDynamoDB offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json), [Amazon DynamoDB pricing](https://aws.amazon.com/dynamodb/pricing/), [Bigtable pricing](https://cloud.google.com/bigtable/pricing).

## DynamoDB → Cloud Bigtable

Origin API: `aws::1.0.0::dynamodb::table`. Target backend: `google::1.0.0::bigtable`.

### DynamoDB · DynamoDB read units

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

![DynamoDB · DynamoDB read units: monthly service charges by DynamoDB read units. Exact values are in the following table.](/images/diagrams/service-cost/0dd02f4b41b43c68a3abd70bb3ab83ee7eb26f2ab2ac0f2bd884278c5eb9dacb-light.svg)

![DynamoDB · DynamoDB read units: monthly service charges by DynamoDB read units. Exact values are in the following table.](/images/diagrams/service-cost/163abfdbf86e279c4809dba6d166b6b690d7a2981ec8af2791aa38671e2e2323-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.

| DynamoDB read units (per second) | DynamoDB | Target scenario | Cloud Bigtable | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | Cloud Bigtable (one copy) | 474.5 | 474.5 |
| 0 | 0 | Cloud Bigtable (two copies) | 474.5 | 474.5 |
| 1 | 0.3285 | Cloud Bigtable (one copy) | 474.5 | 474.1715 |
| 1 | 0.3285 | Cloud Bigtable (two copies) | 474.5 | 474.1715 |
| 10 | 3.285 | Cloud Bigtable (one copy) | 474.5 | 471.215 |
| 10 | 3.285 | Cloud Bigtable (two copies) | 474.5 | 471.215 |
| 100 | 32.85 | Cloud Bigtable (one copy) | 474.5 | 441.65 |
| 100 | 32.85 | Cloud Bigtable (two copies) | 474.5 | 441.65 |
| 1000 | 328.5 | Cloud Bigtable (one copy) | 474.5 | 146 |
| 1000 | 328.5 | Cloud Bigtable (two copies) | 474.5 | 146 |
| 10000 | 3285 | Cloud Bigtable (one copy) | 949 | -2336 |
| 10000 | 3285 | Cloud Bigtable (two copies) | 949 | -2336 |

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Cloud Bigtable (one copy) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| Cloud Bigtable (one copy) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| Cloud Bigtable (one copy) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| Cloud Bigtable (one copy) | Origin list price · Control-plane calls | 0 | USD/requests |
| Cloud Bigtable (one copy) | Representative item size | 1024 | bytes |
| Cloud Bigtable (one copy) | Strongly consistent read fraction | 1 | fraction |
| Cloud Bigtable (one copy) | Origin write-unit amplification | 1 | multiplier |
| Cloud Bigtable (one copy) | Target reads per point read | 1 | operations |
| Cloud Bigtable (one copy) | Target writes per item write | 1 | operations |
| Cloud Bigtable (one copy) | Target price guess · read | 0 | USD/read |
| Cloud Bigtable (one copy) | Target price guess · write | 0 | USD/write |
| Cloud Bigtable (one copy) | Target price guess · provider operation | 0 | USD/provider operation |
| Cloud Bigtable (one copy) | Target list price · GiB-month | 0.17 | USD/GiB-month |
| Cloud Bigtable (one copy) | Target price guess · published GiB | 0 | USD/published GiB |
| Cloud Bigtable (one copy) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Cloud Bigtable (one copy) | Target list price · network GiB | 0.12 | USD/network GiB |
| Cloud Bigtable (one copy) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Cloud Bigtable (one copy) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Cloud Bigtable (one copy) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Cloud Bigtable (one copy) | Target list price · resource-hour | 0.65 | USD/resource-hour |
| Cloud Bigtable (one copy) | Target price guess · resource-month | 0 | USD/resource-month |
| Cloud Bigtable (one copy) | Target price guess · input token | 0 | USD/input token |
| Cloud Bigtable (one copy) | Target price guess · output token | 0 | USD/output token |
| Cloud Bigtable (one copy) | Target monthly base charge | 0 | USD/month |
| Cloud Bigtable (one copy) | Target service minimum | 474.5 | USD/month |
| Cloud Bigtable (one copy) | Minimum primary CPU | 2 | vCPU |
| Cloud Bigtable (one copy) | Minimum primary RAM | 8 | GiB |
| Cloud Bigtable (one copy) | Minimum primary disk | 100 | GiB |
| Cloud Bigtable (one copy) | Additional full-price standby copy | 0 | 0 or 1 |
| Cloud Bigtable (one copy) | Allocated share of provisioned cost | 1 | fraction |
| Cloud Bigtable (one copy) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Cloud Bigtable (one copy) | Planning peak / mean work | 2 | multiplier |
| Cloud Bigtable (one copy) | Planning primary CPU utilization | 0.7 | fraction |
| Cloud Bigtable (one copy) | Resident state reserved in RAM | 0.1 | fraction |
| Cloud Bigtable (one copy) | Planning disk utilization | 0.8 | fraction |
| Cloud Bigtable (one copy) | Maintenance and log disk reserve | 20 | GiB |
| Cloud Bigtable (one copy) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Cloud Bigtable (one copy) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Cloud Bigtable (one copy) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Cloud Bigtable (one copy) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Cloud Bigtable (one copy) | Dependent object sink write price guess | 0.000005 | USD/write |
| Cloud Bigtable (two copies) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| Cloud Bigtable (two copies) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| Cloud Bigtable (two copies) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| Cloud Bigtable (two copies) | Origin list price · Control-plane calls | 0 | USD/requests |
| Cloud Bigtable (two copies) | Representative item size | 1024 | bytes |
| Cloud Bigtable (two copies) | Strongly consistent read fraction | 1 | fraction |
| Cloud Bigtable (two copies) | Origin write-unit amplification | 1 | multiplier |
| Cloud Bigtable (two copies) | Target reads per point read | 1 | operations |
| Cloud Bigtable (two copies) | Target writes per item write | 1 | operations |
| Cloud Bigtable (two copies) | Target price guess · read | 0 | USD/read |
| Cloud Bigtable (two copies) | Target price guess · write | 0 | USD/write |
| Cloud Bigtable (two copies) | Target price guess · provider operation | 0 | USD/provider operation |
| Cloud Bigtable (two copies) | Target list price · GiB-month | 0.17 | USD/GiB-month |
| Cloud Bigtable (two copies) | Target price guess · published GiB | 0 | USD/published GiB |
| Cloud Bigtable (two copies) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Cloud Bigtable (two copies) | Target list price · network GiB | 0.12 | USD/network GiB |
| Cloud Bigtable (two copies) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Cloud Bigtable (two copies) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Cloud Bigtable (two copies) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Cloud Bigtable (two copies) | Target list price · resource-hour | 0.65 | USD/resource-hour |
| Cloud Bigtable (two copies) | Target price guess · resource-month | 0 | USD/resource-month |
| Cloud Bigtable (two copies) | Target price guess · input token | 0 | USD/input token |
| Cloud Bigtable (two copies) | Target price guess · output token | 0 | USD/output token |
| Cloud Bigtable (two copies) | Target monthly base charge | 0 | USD/month |
| Cloud Bigtable (two copies) | Target service minimum | 474.5 | USD/month |
| Cloud Bigtable (two copies) | Minimum primary CPU | 2 | vCPU |
| Cloud Bigtable (two copies) | Minimum primary RAM | 8 | GiB |
| Cloud Bigtable (two copies) | Minimum primary disk | 100 | GiB |
| Cloud Bigtable (two copies) | Additional full-price standby copy | 1 | 0 or 1 |
| Cloud Bigtable (two copies) | Allocated share of provisioned cost | 1 | fraction |
| Cloud Bigtable (two copies) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Cloud Bigtable (two copies) | Planning peak / mean work | 2 | multiplier |
| Cloud Bigtable (two copies) | Planning primary CPU utilization | 0.7 | fraction |
| Cloud Bigtable (two copies) | Resident state reserved in RAM | 0.1 | fraction |
| Cloud Bigtable (two copies) | Planning disk utilization | 0.8 | fraction |
| Cloud Bigtable (two copies) | Maintenance and log disk reserve | 20 | GiB |
| Cloud Bigtable (two copies) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Cloud Bigtable (two copies) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Cloud Bigtable (two copies) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Cloud Bigtable (two copies) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Cloud Bigtable (two copies) | Dependent object sink write price guess | 0.000005 | USD/write |

* Writes and storage remain independent. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
* Planning estimate · editable authored rates and sizing assumptions dated 2026-10-22; not verified provider prices. us-east-1 → 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 is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* 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.
* The control plane and table facet describe the same family workload; allocate shared capacity once, not once per catalog facet.
* No transactional, global-table, Streams or scan tariff is inferred from ordinary on-demand point units.
* Bigtable bills whole provisioned nodes per hour, not vCPU or RAM, plus SSD storage of the compressed physical data. Nodes are sized from planning-peak reads and writes against Google's per-node SSD throughput, with a one-node minimum. A replicated instance bills every cluster's nodes and its own copy of the data; this profile prices one cluster, so the standby selection does not add a cluster.
* AWS Price List API, AmazonDynamoDB offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json)
* Amazon DynamoDB pricing: [https://aws.amazon.com/dynamodb/pricing/](https://aws.amazon.com/dynamodb/pricing/)
* Bigtable pricing: [https://cloud.google.com/bigtable/pricing](https://cloud.google.com/bigtable/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.
* 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-320830a9a89c06c228905dd61fe8054528d71731` / `2026-10-22.planning.2`. Curve: `workload-1`.

Sources: [AWS Price List API, AmazonDynamoDB offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json), [Amazon DynamoDB pricing](https://aws.amazon.com/dynamodb/pricing/), [Bigtable pricing](https://cloud.google.com/bigtable/pricing).

### DynamoDB · DynamoDB write units

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

![DynamoDB · DynamoDB write units: monthly service charges by DynamoDB write units. Exact values are in the following table.](/images/diagrams/service-cost/1c5ea8c6fe4ac29383abb12b8bcabc6178137361caa4576231b10dc44cb48b0e-light.svg)

![DynamoDB · DynamoDB write units: monthly service charges by DynamoDB write units. Exact values are in the following table.](/images/diagrams/service-cost/6f1400a375cb14883894d528c6f81e8edf9d275f8ae0757ab1ff99319e46b2d7-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.

| DynamoDB write units (per second) | DynamoDB | Target scenario | Cloud Bigtable | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | Cloud Bigtable (one copy) | 474.5 | 474.5 |
| 0 | 0 | Cloud Bigtable (two copies) | 474.5 | 474.5 |
| 1 | 1.6425 | Cloud Bigtable (one copy) | 474.5 | 472.8575 |
| 1 | 1.6425 | Cloud Bigtable (two copies) | 474.5 | 472.8575 |
| 10 | 16.425 | Cloud Bigtable (one copy) | 474.5 | 458.075 |
| 10 | 16.425 | Cloud Bigtable (two copies) | 474.5 | 458.075 |
| 100 | 164.25 | Cloud Bigtable (one copy) | 474.5 | 310.25 |
| 100 | 164.25 | Cloud Bigtable (two copies) | 474.5 | 310.25 |
| 1000 | 1642.5 | Cloud Bigtable (one copy) | 474.5 | -1168 |
| 1000 | 1642.5 | Cloud Bigtable (two copies) | 474.5 | -1168 |
| 10000 | 16425 | Cloud Bigtable (one copy) | 1423.5 | -15001.5 |
| 10000 | 16425 | Cloud Bigtable (two copies) | 1423.5 | -15001.5 |

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Cloud Bigtable (one copy) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| Cloud Bigtable (one copy) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| Cloud Bigtable (one copy) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| Cloud Bigtable (one copy) | Origin list price · Control-plane calls | 0 | USD/requests |
| Cloud Bigtable (one copy) | Representative item size | 1024 | bytes |
| Cloud Bigtable (one copy) | Strongly consistent read fraction | 1 | fraction |
| Cloud Bigtable (one copy) | Origin write-unit amplification | 1 | multiplier |
| Cloud Bigtable (one copy) | Target reads per point read | 1 | operations |
| Cloud Bigtable (one copy) | Target writes per item write | 1 | operations |
| Cloud Bigtable (one copy) | Target price guess · read | 0 | USD/read |
| Cloud Bigtable (one copy) | Target price guess · write | 0 | USD/write |
| Cloud Bigtable (one copy) | Target price guess · provider operation | 0 | USD/provider operation |
| Cloud Bigtable (one copy) | Target list price · GiB-month | 0.17 | USD/GiB-month |
| Cloud Bigtable (one copy) | Target price guess · published GiB | 0 | USD/published GiB |
| Cloud Bigtable (one copy) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Cloud Bigtable (one copy) | Target list price · network GiB | 0.12 | USD/network GiB |
| Cloud Bigtable (one copy) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Cloud Bigtable (one copy) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Cloud Bigtable (one copy) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Cloud Bigtable (one copy) | Target list price · resource-hour | 0.65 | USD/resource-hour |
| Cloud Bigtable (one copy) | Target price guess · resource-month | 0 | USD/resource-month |
| Cloud Bigtable (one copy) | Target price guess · input token | 0 | USD/input token |
| Cloud Bigtable (one copy) | Target price guess · output token | 0 | USD/output token |
| Cloud Bigtable (one copy) | Target monthly base charge | 0 | USD/month |
| Cloud Bigtable (one copy) | Target service minimum | 474.5 | USD/month |
| Cloud Bigtable (one copy) | Minimum primary CPU | 2 | vCPU |
| Cloud Bigtable (one copy) | Minimum primary RAM | 8 | GiB |
| Cloud Bigtable (one copy) | Minimum primary disk | 100 | GiB |
| Cloud Bigtable (one copy) | Additional full-price standby copy | 0 | 0 or 1 |
| Cloud Bigtable (one copy) | Allocated share of provisioned cost | 1 | fraction |
| Cloud Bigtable (one copy) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Cloud Bigtable (one copy) | Planning peak / mean work | 2 | multiplier |
| Cloud Bigtable (one copy) | Planning primary CPU utilization | 0.7 | fraction |
| Cloud Bigtable (one copy) | Resident state reserved in RAM | 0.1 | fraction |
| Cloud Bigtable (one copy) | Planning disk utilization | 0.8 | fraction |
| Cloud Bigtable (one copy) | Maintenance and log disk reserve | 20 | GiB |
| Cloud Bigtable (one copy) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Cloud Bigtable (one copy) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Cloud Bigtable (one copy) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Cloud Bigtable (one copy) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Cloud Bigtable (one copy) | Dependent object sink write price guess | 0.000005 | USD/write |
| Cloud Bigtable (two copies) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| Cloud Bigtable (two copies) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| Cloud Bigtable (two copies) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| Cloud Bigtable (two copies) | Origin list price · Control-plane calls | 0 | USD/requests |
| Cloud Bigtable (two copies) | Representative item size | 1024 | bytes |
| Cloud Bigtable (two copies) | Strongly consistent read fraction | 1 | fraction |
| Cloud Bigtable (two copies) | Origin write-unit amplification | 1 | multiplier |
| Cloud Bigtable (two copies) | Target reads per point read | 1 | operations |
| Cloud Bigtable (two copies) | Target writes per item write | 1 | operations |
| Cloud Bigtable (two copies) | Target price guess · read | 0 | USD/read |
| Cloud Bigtable (two copies) | Target price guess · write | 0 | USD/write |
| Cloud Bigtable (two copies) | Target price guess · provider operation | 0 | USD/provider operation |
| Cloud Bigtable (two copies) | Target list price · GiB-month | 0.17 | USD/GiB-month |
| Cloud Bigtable (two copies) | Target price guess · published GiB | 0 | USD/published GiB |
| Cloud Bigtable (two copies) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Cloud Bigtable (two copies) | Target list price · network GiB | 0.12 | USD/network GiB |
| Cloud Bigtable (two copies) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Cloud Bigtable (two copies) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Cloud Bigtable (two copies) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Cloud Bigtable (two copies) | Target list price · resource-hour | 0.65 | USD/resource-hour |
| Cloud Bigtable (two copies) | Target price guess · resource-month | 0 | USD/resource-month |
| Cloud Bigtable (two copies) | Target price guess · input token | 0 | USD/input token |
| Cloud Bigtable (two copies) | Target price guess · output token | 0 | USD/output token |
| Cloud Bigtable (two copies) | Target monthly base charge | 0 | USD/month |
| Cloud Bigtable (two copies) | Target service minimum | 474.5 | USD/month |
| Cloud Bigtable (two copies) | Minimum primary CPU | 2 | vCPU |
| Cloud Bigtable (two copies) | Minimum primary RAM | 8 | GiB |
| Cloud Bigtable (two copies) | Minimum primary disk | 100 | GiB |
| Cloud Bigtable (two copies) | Additional full-price standby copy | 1 | 0 or 1 |
| Cloud Bigtable (two copies) | Allocated share of provisioned cost | 1 | fraction |
| Cloud Bigtable (two copies) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Cloud Bigtable (two copies) | Planning peak / mean work | 2 | multiplier |
| Cloud Bigtable (two copies) | Planning primary CPU utilization | 0.7 | fraction |
| Cloud Bigtable (two copies) | Resident state reserved in RAM | 0.1 | fraction |
| Cloud Bigtable (two copies) | Planning disk utilization | 0.8 | fraction |
| Cloud Bigtable (two copies) | Maintenance and log disk reserve | 20 | GiB |
| Cloud Bigtable (two copies) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Cloud Bigtable (two copies) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Cloud Bigtable (two copies) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Cloud Bigtable (two copies) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Cloud Bigtable (two copies) | Dependent object sink write price guess | 0.000005 | USD/write |

* Reads and storage remain independent. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
* Planning estimate · editable authored rates and sizing assumptions dated 2026-10-22; not verified provider prices. us-east-1 → 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 is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* 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.
* The control plane and table facet describe the same family workload; allocate shared capacity once, not once per catalog facet.
* No transactional, global-table, Streams or scan tariff is inferred from ordinary on-demand point units.
* Bigtable bills whole provisioned nodes per hour, not vCPU or RAM, plus SSD storage of the compressed physical data. Nodes are sized from planning-peak reads and writes against Google's per-node SSD throughput, with a one-node minimum. A replicated instance bills every cluster's nodes and its own copy of the data; this profile prices one cluster, so the standby selection does not add a cluster.
* AWS Price List API, AmazonDynamoDB offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json)
* Amazon DynamoDB pricing: [https://aws.amazon.com/dynamodb/pricing/](https://aws.amazon.com/dynamodb/pricing/)
* Bigtable pricing: [https://cloud.google.com/bigtable/pricing](https://cloud.google.com/bigtable/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.
* 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-320830a9a89c06c228905dd61fe8054528d71731` / `2026-10-22.planning.2`. Curve: `workload-2`.

Sources: [AWS Price List API, AmazonDynamoDB offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json), [Amazon DynamoDB pricing](https://aws.amazon.com/dynamodb/pricing/), [Bigtable pricing](https://cloud.google.com/bigtable/pricing).

### DynamoDB · Stored data

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

![DynamoDB · Stored data: monthly service charges by Stored data. Exact values are in the following table.](/images/diagrams/service-cost/46c8598a45f64e1bdd92ecd34405ca67065483452cc2021645029c00cba85c4f-light.svg)

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

| Stored data (GiB-month) | DynamoDB | Target scenario | Cloud Bigtable | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | Cloud Bigtable (one copy) | 474.5 | 474.5 |
| 0 | 0 | Cloud Bigtable (two copies) | 474.5 | 474.5 |
| 10 | 2.5 | Cloud Bigtable (one copy) | 476.2 | 473.7 |
| 10 | 2.5 | Cloud Bigtable (two copies) | 476.2 | 473.7 |
| 100 | 25 | Cloud Bigtable (one copy) | 491.5 | 466.5 |
| 100 | 25 | Cloud Bigtable (two copies) | 491.5 | 466.5 |
| 1000 | 250 | Cloud Bigtable (one copy) | 644.5 | 394.5 |
| 1000 | 250 | Cloud Bigtable (two copies) | 644.5 | 394.5 |
| 10000 | 2500 | Cloud Bigtable (one copy) | 2174.5 | -325.5 |
| 10000 | 2500 | Cloud Bigtable (two copies) | 2174.5 | -325.5 |
| 100000 | 25000 | Cloud Bigtable (one copy) | 17474.5 | -7525.5 |
| 100000 | 25000 | Cloud Bigtable (two copies) | 17474.5 | -7525.5 |

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Cloud Bigtable (one copy) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| Cloud Bigtable (one copy) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| Cloud Bigtable (one copy) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| Cloud Bigtable (one copy) | Origin list price · Control-plane calls | 0 | USD/requests |
| Cloud Bigtable (one copy) | Representative item size | 1024 | bytes |
| Cloud Bigtable (one copy) | Strongly consistent read fraction | 1 | fraction |
| Cloud Bigtable (one copy) | Origin write-unit amplification | 1 | multiplier |
| Cloud Bigtable (one copy) | Target reads per point read | 1 | operations |
| Cloud Bigtable (one copy) | Target writes per item write | 1 | operations |
| Cloud Bigtable (one copy) | Target price guess · read | 0 | USD/read |
| Cloud Bigtable (one copy) | Target price guess · write | 0 | USD/write |
| Cloud Bigtable (one copy) | Target price guess · provider operation | 0 | USD/provider operation |
| Cloud Bigtable (one copy) | Target list price · GiB-month | 0.17 | USD/GiB-month |
| Cloud Bigtable (one copy) | Target price guess · published GiB | 0 | USD/published GiB |
| Cloud Bigtable (one copy) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Cloud Bigtable (one copy) | Target list price · network GiB | 0.12 | USD/network GiB |
| Cloud Bigtable (one copy) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Cloud Bigtable (one copy) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Cloud Bigtable (one copy) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Cloud Bigtable (one copy) | Target list price · resource-hour | 0.65 | USD/resource-hour |
| Cloud Bigtable (one copy) | Target price guess · resource-month | 0 | USD/resource-month |
| Cloud Bigtable (one copy) | Target price guess · input token | 0 | USD/input token |
| Cloud Bigtable (one copy) | Target price guess · output token | 0 | USD/output token |
| Cloud Bigtable (one copy) | Target monthly base charge | 0 | USD/month |
| Cloud Bigtable (one copy) | Target service minimum | 474.5 | USD/month |
| Cloud Bigtable (one copy) | Minimum primary CPU | 2 | vCPU |
| Cloud Bigtable (one copy) | Minimum primary RAM | 8 | GiB |
| Cloud Bigtable (one copy) | Minimum primary disk | 100 | GiB |
| Cloud Bigtable (one copy) | Additional full-price standby copy | 0 | 0 or 1 |
| Cloud Bigtable (one copy) | Allocated share of provisioned cost | 1 | fraction |
| Cloud Bigtable (one copy) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Cloud Bigtable (one copy) | Planning peak / mean work | 2 | multiplier |
| Cloud Bigtable (one copy) | Planning primary CPU utilization | 0.7 | fraction |
| Cloud Bigtable (one copy) | Resident state reserved in RAM | 0.1 | fraction |
| Cloud Bigtable (one copy) | Planning disk utilization | 0.8 | fraction |
| Cloud Bigtable (one copy) | Maintenance and log disk reserve | 20 | GiB |
| Cloud Bigtable (one copy) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Cloud Bigtable (one copy) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Cloud Bigtable (one copy) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Cloud Bigtable (one copy) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Cloud Bigtable (one copy) | Dependent object sink write price guess | 0.000005 | USD/write |
| Cloud Bigtable (two copies) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| Cloud Bigtable (two copies) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| Cloud Bigtable (two copies) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| Cloud Bigtable (two copies) | Origin list price · Control-plane calls | 0 | USD/requests |
| Cloud Bigtable (two copies) | Representative item size | 1024 | bytes |
| Cloud Bigtable (two copies) | Strongly consistent read fraction | 1 | fraction |
| Cloud Bigtable (two copies) | Origin write-unit amplification | 1 | multiplier |
| Cloud Bigtable (two copies) | Target reads per point read | 1 | operations |
| Cloud Bigtable (two copies) | Target writes per item write | 1 | operations |
| Cloud Bigtable (two copies) | Target price guess · read | 0 | USD/read |
| Cloud Bigtable (two copies) | Target price guess · write | 0 | USD/write |
| Cloud Bigtable (two copies) | Target price guess · provider operation | 0 | USD/provider operation |
| Cloud Bigtable (two copies) | Target list price · GiB-month | 0.17 | USD/GiB-month |
| Cloud Bigtable (two copies) | Target price guess · published GiB | 0 | USD/published GiB |
| Cloud Bigtable (two copies) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Cloud Bigtable (two copies) | Target list price · network GiB | 0.12 | USD/network GiB |
| Cloud Bigtable (two copies) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Cloud Bigtable (two copies) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Cloud Bigtable (two copies) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Cloud Bigtable (two copies) | Target list price · resource-hour | 0.65 | USD/resource-hour |
| Cloud Bigtable (two copies) | Target price guess · resource-month | 0 | USD/resource-month |
| Cloud Bigtable (two copies) | Target price guess · input token | 0 | USD/input token |
| Cloud Bigtable (two copies) | Target price guess · output token | 0 | USD/output token |
| Cloud Bigtable (two copies) | Target monthly base charge | 0 | USD/month |
| Cloud Bigtable (two copies) | Target service minimum | 474.5 | USD/month |
| Cloud Bigtable (two copies) | Minimum primary CPU | 2 | vCPU |
| Cloud Bigtable (two copies) | Minimum primary RAM | 8 | GiB |
| Cloud Bigtable (two copies) | Minimum primary disk | 100 | GiB |
| Cloud Bigtable (two copies) | Additional full-price standby copy | 1 | 0 or 1 |
| Cloud Bigtable (two copies) | Allocated share of provisioned cost | 1 | fraction |
| Cloud Bigtable (two copies) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Cloud Bigtable (two copies) | Planning peak / mean work | 2 | multiplier |
| Cloud Bigtable (two copies) | Planning primary CPU utilization | 0.7 | fraction |
| Cloud Bigtable (two copies) | Resident state reserved in RAM | 0.1 | fraction |
| Cloud Bigtable (two copies) | Planning disk utilization | 0.8 | fraction |
| Cloud Bigtable (two copies) | Maintenance and log disk reserve | 20 | GiB |
| Cloud Bigtable (two copies) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Cloud Bigtable (two copies) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Cloud Bigtable (two copies) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Cloud Bigtable (two copies) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Cloud Bigtable (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. us-east-1 → 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 is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* 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.
* The control plane and table facet describe the same family workload; allocate shared capacity once, not once per catalog facet.
* No transactional, global-table, Streams or scan tariff is inferred from ordinary on-demand point units.
* Bigtable bills whole provisioned nodes per hour, not vCPU or RAM, plus SSD storage of the compressed physical data. Nodes are sized from planning-peak reads and writes against Google's per-node SSD throughput, with a one-node minimum. A replicated instance bills every cluster's nodes and its own copy of the data; this profile prices one cluster, so the standby selection does not add a cluster.
* AWS Price List API, AmazonDynamoDB offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json)
* Amazon DynamoDB pricing: [https://aws.amazon.com/dynamodb/pricing/](https://aws.amazon.com/dynamodb/pricing/)
* Bigtable pricing: [https://cloud.google.com/bigtable/pricing](https://cloud.google.com/bigtable/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.
* 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-320830a9a89c06c228905dd61fe8054528d71731` / `2026-10-22.planning.2`. Curve: `workload-3`.

Sources: [AWS Price List API, AmazonDynamoDB offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json), [Amazon DynamoDB pricing](https://aws.amazon.com/dynamodb/pricing/), [Bigtable pricing](https://cloud.google.com/bigtable/pricing).

## DynamoDB → Cloud SQL for PostgreSQL

Origin API: `aws::1.0.0::dynamodb::table`. Target backend: `google::1.0.0::cloudsql::postgresql`.

### Monthly cost by DynamoDB point-read rate

Reference monthly service charges by Read operations/s. Adapter hosting and Tensor9 fees are excluded. Source: us-east-1; target: us-central1; currency: USD.

![Monthly cost by DynamoDB point-read rate: monthly service charges by Read operations/s. Exact values are in the following table.](/images/diagrams/service-cost/7e7ace4e310d7bc3b8ac14beadf4a08252341f6033a06f5dde7b7af719b68e4c-light.svg)

![Monthly cost by DynamoDB point-read rate: monthly service charges by Read operations/s. Exact values are in the following table.](/images/diagrams/service-cost/d14ae6a5b9e6f08b54fd5b5f468177d4f2fe65b94e58c404d817a10d8eb09e51-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.

| Read operations/s (reads/s) | DynamoDB | Target scenario | Cloud SQL for PostgreSQL | Difference |
| -: | -: | - | -: | -: |
| 0 | 25 | Cloud SQL for PostgreSQL (HA) | 270.356 | 245.356 |
| 0 | 25 | Cloud SQL for PostgreSQL (zonal) | 135.178 | 110.178 |
| 1 | 25.49275 | Cloud SQL for PostgreSQL (HA) | 270.356 | 244.86325 |
| 1 | 25.49275 | Cloud SQL for PostgreSQL (zonal) | 135.178 | 109.68525 |
| 10 | 29.9275 | Cloud SQL for PostgreSQL (HA) | 270.356 | 240.4285 |
| 10 | 29.9275 | Cloud SQL for PostgreSQL (zonal) | 135.178 | 105.2505 |
| 100 | 74.275 | Cloud SQL for PostgreSQL (HA) | 270.356 | 196.081 |
| 100 | 74.275 | Cloud SQL for PostgreSQL (zonal) | 135.178 | 60.903 |
| 1000 | 517.75 | Cloud SQL for PostgreSQL (HA) | 270.356 | -247.394 |
| 1000 | 517.75 | Cloud SQL for PostgreSQL (zonal) | 135.178 | -382.572 |
| 10000 | 4952.5 | Cloud SQL for PostgreSQL (HA) | 270.356 | -4682.144 |
| 10000 | 4952.5 | Cloud SQL for PostgreSQL (zonal) | 135.178 | -4817.322 |

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Cloud SQL for PostgreSQL (HA) | Representative DynamoDB item size | 1024 | bytes |
| Cloud SQL for PostgreSQL (HA) | Strongly consistent origin reads | 1 | 0 = eventual, 1 = strong |
| Cloud SQL for PostgreSQL (HA) | Origin write-unit amplification | 1 | multiplier |
| Cloud SQL for PostgreSQL (HA) | Cloud SQL vCPUs | 2 | vCPU |
| Cloud SQL for PostgreSQL (HA) | Cloud SQL memory | 8 | GiB |
| Cloud SQL for PostgreSQL (HA) | Provisioned Cloud SQL SSD | 200 | GiB |
| Cloud SQL for PostgreSQL (HA) | Cloud SQL high availability | 1 | 0 = zonal, 1 = HA |
| Cloud SQL for PostgreSQL (HA) | Share of database cost allocated here | 1 | fraction |
| Cloud SQL for PostgreSQL (zonal) | Representative DynamoDB item size | 1024 | bytes |
| Cloud SQL for PostgreSQL (zonal) | Strongly consistent origin reads | 1 | 0 = eventual, 1 = strong |
| Cloud SQL for PostgreSQL (zonal) | Origin write-unit amplification | 1 | multiplier |
| Cloud SQL for PostgreSQL (zonal) | Cloud SQL vCPUs | 2 | vCPU |
| Cloud SQL for PostgreSQL (zonal) | Cloud SQL memory | 8 | GiB |
| Cloud SQL for PostgreSQL (zonal) | Provisioned Cloud SQL SSD | 200 | GiB |
| Cloud SQL for PostgreSQL (zonal) | Cloud SQL high availability | 0 | 0 = zonal, 1 = HA |
| Cloud SQL for PostgreSQL (zonal) | Share of database cost allocated here | 1 | fraction |

* Strong 1 KiB point reads and plain writes; one write per ten reads, no origin index amplification. 730 hours/month; retained source data stays at 100 GiB. Cloud SQL has 2 vCPU, 8 GiB memory and 200 GiB SSD. Twice source storage is an authored reserve, not a measured sizing rule; throughput remains unqualified.
* Reference list rates as of 2026-10-18: us-east-1 → 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.
* Cloud SQL configuration pricing only: throughput, peak load, latency and storage suitability are unqualified. No capacity benchmark is implied.
* 730 running hours per modeled month. Dedicated database compute and disk cost money even with zero origin traffic.
* Shared database allocation is a caller assumption. Do not sum a full database charge for every adapter sharing that database.
* Origin workload is point GetItem and plain PutItem on Standard on-demand tables. Queries, transactions and Streams are not modeled.
* Source usage is priced at reference rates; source lines are not actual invoice charges. Free or discounted usage still consumes target resources.
* AWS DynamoDB Standard on-demand pricing: [https://aws.amazon.com/dynamodb/pricing/](https://aws.amazon.com/dynamodb/pricing/)
* Cloud SQL Enterprise PostgreSQL pricing: [https://cloud.google.com/sql/pricing/](https://cloud.google.com/sql/pricing/)

Cost scope: Modeled monthly service usage and selected database allocation; adapter hosting and Tensor9 fees only when explicitly supplied.

Excluded costs and workload features:

* Free allowances, negotiated discounts, credits, tax and one-time migration charges.
* Charges not listed in the breakdown, including additional network transfer, backups and encryption/KMS.
* Application compute changes, operational labor and portfolio-wide sharing or deduplication of infrastructure.
* DynamoDB provisioned capacity, global replicas, transactions, queries/scans and Streams; unqualified database sizing.

Rate snapshot: 2026-10-18. Model: `dynamodb-cloudsql` / `2026-10-18.4`. Curve: `read-rate`.

Sources: [AWS DynamoDB Standard on-demand pricing](https://aws.amazon.com/dynamodb/pricing/), [Cloud SQL Enterprise PostgreSQL pricing](https://cloud.google.com/sql/pricing/).

### Monthly cost by retained DynamoDB data

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

![Monthly cost by retained DynamoDB data: monthly service charges by Retained source data. Exact values are in the following table.](/images/diagrams/service-cost/1770104fab7425a60a515a44978e5d1e60648eff1f56dbaf3f86b63ccfa634aa-light.svg)

![Monthly cost by retained DynamoDB data: monthly service charges by Retained source data. Exact values are in the following table.](/images/diagrams/service-cost/61778c60b55a46ff4a856d33ac003fe883624e9f6fbc83beef6fffd3dfd77d2f-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.

| Retained source data (GiB-month) | DynamoDB | Target scenario | Cloud SQL for PostgreSQL | Difference |
| -: | -: | - | -: | -: |
| 0 | 18.75 | Cloud SQL for PostgreSQL (HA) | 205.756 | 187.006 |
| 0 | 18.75 | Cloud SQL for PostgreSQL (zonal) | 102.878 | 84.128 |
| 10 | 21.25 | Cloud SQL for PostgreSQL (HA) | 209.156 | 187.906 |
| 10 | 21.25 | Cloud SQL for PostgreSQL (zonal) | 104.578 | 83.328 |
| 100 | 43.75 | Cloud SQL for PostgreSQL (HA) | 270.356 | 226.606 |
| 100 | 43.75 | Cloud SQL for PostgreSQL (zonal) | 135.178 | 91.428 |
| 1000 | 268.75 | Cloud SQL for PostgreSQL (HA) | 882.356 | 613.606 |
| 1000 | 268.75 | Cloud SQL for PostgreSQL (zonal) | 441.178 | 172.428 |
| 10000 | 2518.75 | Cloud SQL for PostgreSQL (HA) | 7002.356 | 4483.606 |
| 10000 | 2518.75 | Cloud SQL for PostgreSQL (zonal) | 3501.178 | 982.428 |

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Cloud SQL for PostgreSQL (HA) | Representative DynamoDB item size | 1024 | bytes |
| Cloud SQL for PostgreSQL (HA) | Strongly consistent origin reads | 1 | 0 = eventual, 1 = strong |
| Cloud SQL for PostgreSQL (HA) | Origin write-unit amplification | 1 | multiplier |
| Cloud SQL for PostgreSQL (HA) | Cloud SQL vCPUs | 2 | vCPU |
| Cloud SQL for PostgreSQL (HA) | Cloud SQL memory | 8 | GiB |
| Cloud SQL for PostgreSQL (HA) | Provisioned Cloud SQL SSD | 10 | GiB |
| Cloud SQL for PostgreSQL (HA) | Cloud SQL high availability | 1 | 0 = zonal, 1 = HA |
| Cloud SQL for PostgreSQL (HA) | Share of database cost allocated here | 1 | fraction |
| Cloud SQL for PostgreSQL (zonal) | Representative DynamoDB item size | 1024 | bytes |
| Cloud SQL for PostgreSQL (zonal) | Strongly consistent origin reads | 1 | 0 = eventual, 1 = strong |
| Cloud SQL for PostgreSQL (zonal) | Origin write-unit amplification | 1 | multiplier |
| Cloud SQL for PostgreSQL (zonal) | Cloud SQL vCPUs | 2 | vCPU |
| Cloud SQL for PostgreSQL (zonal) | Cloud SQL memory | 8 | GiB |
| Cloud SQL for PostgreSQL (zonal) | Provisioned Cloud SQL SSD | 10 | GiB |
| Cloud SQL for PostgreSQL (zonal) | Cloud SQL high availability | 0 | 0 = zonal, 1 = HA |
| Cloud SQL for PostgreSQL (zonal) | Share of database cost allocated here | 1 | fraction |

* Source traffic stays at 100 million strong 1 KiB read units and 10 million plain write units/month, with no origin index amplification. Cloud SQL uses 2 vCPU and 8 GiB memory; SSD provision is twice source GiB, rounded up to whole GiB with a 10 GiB minimum. This reserve is an authored assumption, not a measured expansion factor or capacity qualification.
* Reference list rates as of 2026-10-18: us-east-1 → 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.
* Cloud SQL configuration pricing only: throughput, peak load, latency and storage suitability are unqualified. No capacity benchmark is implied.
* 730 running hours per modeled month. Dedicated database compute and disk cost money even with zero origin traffic.
* Shared database allocation is a caller assumption. Do not sum a full database charge for every adapter sharing that database.
* Origin workload is point GetItem and plain PutItem on Standard on-demand tables. Queries, transactions and Streams are not modeled.
* Source usage is priced at reference rates; source lines are not actual invoice charges. Free or discounted usage still consumes target resources.
* AWS DynamoDB Standard on-demand pricing: [https://aws.amazon.com/dynamodb/pricing/](https://aws.amazon.com/dynamodb/pricing/)
* Cloud SQL Enterprise PostgreSQL pricing: [https://cloud.google.com/sql/pricing/](https://cloud.google.com/sql/pricing/)

Cost scope: Modeled monthly service usage and selected database allocation; adapter hosting and Tensor9 fees only when explicitly supplied.

Excluded costs and workload features:

* Free allowances, negotiated discounts, credits, tax and one-time migration charges.
* Charges not listed in the breakdown, including additional network transfer, backups and encryption/KMS.
* Application compute changes, operational labor and portfolio-wide sharing or deduplication of infrastructure.
* DynamoDB provisioned capacity, global replicas, transactions, queries/scans and Streams; unqualified database sizing.

Rate snapshot: 2026-10-18. Model: `dynamodb-cloudsql` / `2026-10-18.4`. Curve: `retained-data`.

Sources: [AWS DynamoDB Standard on-demand pricing](https://aws.amazon.com/dynamodb/pricing/), [Cloud SQL Enterprise PostgreSQL pricing](https://cloud.google.com/sql/pricing/).

## DynamoDB → Cloud SQL for PostgreSQL

Origin API: `aws::1.0.0::dynamodb::control`. Target backend: `google::1.0.0::cloudsql::postgresql`.

### DynamoDB · DynamoDB read units

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

![DynamoDB · DynamoDB read units: monthly service charges by DynamoDB read units. Exact values are in the following table.](/images/diagrams/service-cost/51b2e937612b31704f373dc0c996f0409fe6abd7e2f167204e5dd8fa73f44718-light.svg)

![DynamoDB · DynamoDB read units: monthly service charges by DynamoDB read units. Exact values are in the following table.](/images/diagrams/service-cost/79f8e78b2dc12962c03ada22654f68d51d16d2054b0c129cdb714df32439d8a5-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.

| DynamoDB read units (per second) | DynamoDB | 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.3285 | Cloud SQL for PostgreSQL (one copy) | 118.178 | 117.8495 |
| 1 | 0.3285 | Cloud SQL for PostgreSQL (two copies) | 236.356 | 236.0275 |
| 10 | 3.285 | Cloud SQL for PostgreSQL (one copy) | 118.178 | 114.893 |
| 10 | 3.285 | Cloud SQL for PostgreSQL (two copies) | 236.356 | 233.071 |
| 100 | 32.85 | Cloud SQL for PostgreSQL (one copy) | 118.178 | 85.328 |
| 100 | 32.85 | Cloud SQL for PostgreSQL (two copies) | 236.356 | 203.506 |
| 1000 | 328.5 | Cloud SQL for PostgreSQL (one copy) | 118.178 | -210.322 |
| 1000 | 328.5 | Cloud SQL for PostgreSQL (two copies) | 236.356 | -92.144 |
| 10000 | 3285 | Cloud SQL for PostgreSQL (one copy) | 1635.848 | -1649.152 |
| 10000 | 3285 | Cloud SQL for PostgreSQL (two copies) | 3271.696 | -13.304 |

**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.001904761904761904761904761904761905 | 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.001904761904761904761904761904761905 | 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.01904761904761904761904761904761905 | 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.01904761904761904761904761904761905 | 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.1904761904761904761904761904761905 | 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.1904761904761904761904761904761905 | 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 | 1.904761904761904761904761904761905 | 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 | 1.904761904761904761904761904761905 | 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 | 19.04761904761904761904761904761905 | 32 | 128 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10000 per second / Cloud SQL for PostgreSQL (two copies) | PlanningAssumption | 10000 / 20000 | 19.04761904761904761904761904761905 | 32 | 128 | 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 operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Cloud SQL for PostgreSQL (one copy) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| Cloud SQL for PostgreSQL (one copy) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| Cloud SQL for PostgreSQL (one copy) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| Cloud SQL for PostgreSQL (one copy) | Origin list price · Control-plane calls | 0 | USD/requests |
| Cloud SQL for PostgreSQL (one copy) | Representative item size | 1024 | bytes |
| Cloud SQL for PostgreSQL (one copy) | Strongly consistent read fraction | 1 | fraction |
| Cloud SQL for PostgreSQL (one copy) | Origin write-unit amplification | 1 | multiplier |
| Cloud SQL for PostgreSQL (one copy) | Target reads per point read | 1 | operations |
| Cloud SQL for PostgreSQL (one copy) | Target writes per item write | 1 | operations |
| 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 · DynamoDB read units | 0.000000125 | USD/read request units |
| Cloud SQL for PostgreSQL (two copies) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| Cloud SQL for PostgreSQL (two copies) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| Cloud SQL for PostgreSQL (two copies) | Origin list price · Control-plane calls | 0 | USD/requests |
| Cloud SQL for PostgreSQL (two copies) | Representative item size | 1024 | bytes |
| Cloud SQL for PostgreSQL (two copies) | Strongly consistent read fraction | 1 | fraction |
| Cloud SQL for PostgreSQL (two copies) | Origin write-unit amplification | 1 | multiplier |
| Cloud SQL for PostgreSQL (two copies) | Target reads per point read | 1 | operations |
| Cloud SQL for PostgreSQL (two copies) | Target writes per item write | 1 | operations |
| 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 |

* Writes and storage remain independent. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
* Planning estimate · editable authored rates and sizing assumptions dated 2026-10-22; not verified provider prices. us-east-1 → 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 is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* 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.
* The control plane and table facet describe the same family workload; allocate shared capacity once, not once per catalog facet.
* No transactional, global-table, Streams or scan tariff is inferred from ordinary on-demand point units.
* 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 operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
* AWS Price List API, AmazonDynamoDB offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json)
* Amazon DynamoDB pricing: [https://aws.amazon.com/dynamodb/pricing/](https://aws.amazon.com/dynamodb/pricing/)
* 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.
* 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-f1008577e0cf5d5cb82de2bf437390d5c3a08962` / `2026-10-22.planning.2`. Curve: `workload-1`.

Sources: [AWS Price List API, AmazonDynamoDB offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json), [Amazon DynamoDB pricing](https://aws.amazon.com/dynamodb/pricing/), [Cloud SQL pricing](https://cloud.google.com/sql/pricing).

### DynamoDB · DynamoDB write units

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

![DynamoDB · DynamoDB write units: monthly service charges by DynamoDB write units. Exact values are in the following table.](/images/diagrams/service-cost/24249690579195717d3faee84c50595190aee95a5fd488410b7f3dd9d5325132-light.svg)

![DynamoDB · DynamoDB write units: monthly service charges by DynamoDB write units. Exact values are in the following table.](/images/diagrams/service-cost/c7d8e0f58e54bfbd1a10a1b3f317eb7eae9cef72e10b929548cccfdffbca2d38-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.

| DynamoDB write units (per second) | DynamoDB | 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 | 1.6425 | Cloud SQL for PostgreSQL (one copy) | 118.178 | 116.5355 |
| 1 | 1.6425 | Cloud SQL for PostgreSQL (two copies) | 236.356 | 234.7135 |
| 10 | 16.425 | Cloud SQL for PostgreSQL (one copy) | 118.178 | 101.753 |
| 10 | 16.425 | Cloud SQL for PostgreSQL (two copies) | 236.356 | 219.931 |
| 100 | 164.25 | Cloud SQL for PostgreSQL (one copy) | 118.178 | -46.072 |
| 100 | 164.25 | Cloud SQL for PostgreSQL (two copies) | 236.356 | 72.106 |
| 1000 | 1642.5 | Cloud SQL for PostgreSQL (one copy) | 118.178 | -1524.322 |
| 1000 | 1642.5 | Cloud SQL for PostgreSQL (two copies) | 236.356 | -1406.144 |
| 10000 | 16425 | Cloud SQL for PostgreSQL (one copy) | 1635.848 | -14789.152 |
| 10000 | 16425 | Cloud SQL for PostgreSQL (two copies) | 3271.696 | -13153.304 |

**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.001904761904761904761904761904761905 | 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.001904761904761904761904761904761905 | 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.01904761904761904761904761904761905 | 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.01904761904761904761904761904761905 | 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.1904761904761904761904761904761905 | 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.1904761904761904761904761904761905 | 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 | 1.904761904761904761904761904761905 | 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 | 1.904761904761904761904761904761905 | 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 | 19.04761904761904761904761904761905 | 32 | 128 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10000 per second / Cloud SQL for PostgreSQL (two copies) | PlanningAssumption | 10000 / 20000 | 19.04761904761904761904761904761905 | 32 | 128 | 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 operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Cloud SQL for PostgreSQL (one copy) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| Cloud SQL for PostgreSQL (one copy) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| Cloud SQL for PostgreSQL (one copy) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| Cloud SQL for PostgreSQL (one copy) | Origin list price · Control-plane calls | 0 | USD/requests |
| Cloud SQL for PostgreSQL (one copy) | Representative item size | 1024 | bytes |
| Cloud SQL for PostgreSQL (one copy) | Strongly consistent read fraction | 1 | fraction |
| Cloud SQL for PostgreSQL (one copy) | Origin write-unit amplification | 1 | multiplier |
| Cloud SQL for PostgreSQL (one copy) | Target reads per point read | 1 | operations |
| Cloud SQL for PostgreSQL (one copy) | Target writes per item write | 1 | operations |
| 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 · DynamoDB read units | 0.000000125 | USD/read request units |
| Cloud SQL for PostgreSQL (two copies) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| Cloud SQL for PostgreSQL (two copies) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| Cloud SQL for PostgreSQL (two copies) | Origin list price · Control-plane calls | 0 | USD/requests |
| Cloud SQL for PostgreSQL (two copies) | Representative item size | 1024 | bytes |
| Cloud SQL for PostgreSQL (two copies) | Strongly consistent read fraction | 1 | fraction |
| Cloud SQL for PostgreSQL (two copies) | Origin write-unit amplification | 1 | multiplier |
| Cloud SQL for PostgreSQL (two copies) | Target reads per point read | 1 | operations |
| Cloud SQL for PostgreSQL (two copies) | Target writes per item write | 1 | operations |
| 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 |

* Reads and storage remain independent. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
* Planning estimate · editable authored rates and sizing assumptions dated 2026-10-22; not verified provider prices. us-east-1 → 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 is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* 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.
* The control plane and table facet describe the same family workload; allocate shared capacity once, not once per catalog facet.
* No transactional, global-table, Streams or scan tariff is inferred from ordinary on-demand point units.
* 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 operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
* AWS Price List API, AmazonDynamoDB offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json)
* Amazon DynamoDB pricing: [https://aws.amazon.com/dynamodb/pricing/](https://aws.amazon.com/dynamodb/pricing/)
* 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.
* 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-f1008577e0cf5d5cb82de2bf437390d5c3a08962` / `2026-10-22.planning.2`. Curve: `workload-2`.

Sources: [AWS Price List API, AmazonDynamoDB offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json), [Amazon DynamoDB pricing](https://aws.amazon.com/dynamodb/pricing/), [Cloud SQL pricing](https://cloud.google.com/sql/pricing).

### DynamoDB · Stored data

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

![DynamoDB · Stored data: monthly service charges by Stored data. Exact values are in the following table.](/images/diagrams/service-cost/3b256cabcb506f93122d005e9094485b20d4157eeb1eed678645c1b08831ab30-light.svg)

![DynamoDB · Stored data: monthly service charges by Stored data. Exact values are in the following table.](/images/diagrams/service-cost/c523d9ec3d316cf28499074ac7ad92daa25fd328fc1e35980171272441cac354-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) | DynamoDB | 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 | 2.5 | Cloud SQL for PostgreSQL (one copy) | 118.178 | 115.678 |
| 10 | 2.5 | Cloud SQL for PostgreSQL (two copies) | 236.356 | 233.856 |
| 100 | 25 | Cloud SQL for PostgreSQL (one copy) | 136.898 | 111.898 |
| 100 | 25 | Cloud SQL for PostgreSQL (two copies) | 273.796 | 248.796 |
| 1000 | 250 | Cloud SQL for PostgreSQL (one copy) | 1210.134 | 960.134 |
| 1000 | 250 | Cloud SQL for PostgreSQL (two copies) | 2420.268 | 2170.268 |
| 10000 | 2500 | Cloud SQL for PostgreSQL (one copy) | Unpriced | Unavailable |
| 10000 | 2500 | Cloud SQL for PostgreSQL (two copies) | Unpriced | Unavailable |
| 100000 | 25000 | Cloud SQL for PostgreSQL (one copy) | Unpriced | Unavailable |
| 100000 | 25000 | 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 operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Cloud SQL for PostgreSQL (one copy) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| Cloud SQL for PostgreSQL (one copy) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| Cloud SQL for PostgreSQL (one copy) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| Cloud SQL for PostgreSQL (one copy) | Origin list price · Control-plane calls | 0 | USD/requests |
| Cloud SQL for PostgreSQL (one copy) | Representative item size | 1024 | bytes |
| Cloud SQL for PostgreSQL (one copy) | Strongly consistent read fraction | 1 | fraction |
| Cloud SQL for PostgreSQL (one copy) | Origin write-unit amplification | 1 | multiplier |
| Cloud SQL for PostgreSQL (one copy) | Target reads per point read | 1 | operations |
| Cloud SQL for PostgreSQL (one copy) | Target writes per item write | 1 | operations |
| 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 · DynamoDB read units | 0.000000125 | USD/read request units |
| Cloud SQL for PostgreSQL (two copies) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| Cloud SQL for PostgreSQL (two copies) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| Cloud SQL for PostgreSQL (two copies) | Origin list price · Control-plane calls | 0 | USD/requests |
| Cloud SQL for PostgreSQL (two copies) | Representative item size | 1024 | bytes |
| Cloud SQL for PostgreSQL (two copies) | Strongly consistent read fraction | 1 | fraction |
| Cloud SQL for PostgreSQL (two copies) | Origin write-unit amplification | 1 | multiplier |
| Cloud SQL for PostgreSQL (two copies) | Target reads per point read | 1 | operations |
| Cloud SQL for PostgreSQL (two copies) | Target writes per item write | 1 | operations |
| 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. us-east-1 → 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 is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* 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.
* The control plane and table facet describe the same family workload; allocate shared capacity once, not once per catalog facet.
* No transactional, global-table, Streams or scan tariff is inferred from ordinary on-demand point units.
* 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 operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
* AWS Price List API, AmazonDynamoDB offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json)
* Amazon DynamoDB pricing: [https://aws.amazon.com/dynamodb/pricing/](https://aws.amazon.com/dynamodb/pricing/)
* 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.
* 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-f1008577e0cf5d5cb82de2bf437390d5c3a08962` / `2026-10-22.planning.2`. Curve: `workload-3`.

Sources: [AWS Price List API, AmazonDynamoDB offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json), [Amazon DynamoDB pricing](https://aws.amazon.com/dynamodb/pricing/), [Cloud SQL pricing](https://cloud.google.com/sql/pricing).

## DynamoDB → Cloud Spanner

Origin API: `aws::1.0.0::dynamodb::control`. Target backend: `google::1.0.0::spanner`.

### DynamoDB · DynamoDB read units

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

![DynamoDB · DynamoDB read units: monthly service charges by DynamoDB read units. Exact values are in the following table.](/images/diagrams/service-cost/ee876907d75c2451d2ebf67b24578b29b6646c6e97da6d5e7c46c2af1ae46c75-light.svg)

![DynamoDB · DynamoDB read units: monthly service charges by DynamoDB read units. Exact values are in the following table.](/images/diagrams/service-cost/a62a180bd5139d37e744372815e8773a01bbc0df49617a94512dc61aa3fb0d1b-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.

| DynamoDB read units (per second) | DynamoDB | Target scenario | Cloud Spanner | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | Cloud Spanner (one copy) | 65.7 | 65.7 |
| 0 | 0 | Cloud Spanner (two copies) | 65.7 | 65.7 |
| 1 | 0.3285 | Cloud Spanner (one copy) | 65.7 | 65.3715 |
| 1 | 0.3285 | Cloud Spanner (two copies) | 65.7 | 65.3715 |
| 10 | 3.285 | Cloud Spanner (one copy) | 65.7 | 62.415 |
| 10 | 3.285 | Cloud Spanner (two copies) | 65.7 | 62.415 |
| 100 | 32.85 | Cloud Spanner (one copy) | 65.7 | 32.85 |
| 100 | 32.85 | Cloud Spanner (two copies) | 65.7 | 32.85 |
| 1000 | 328.5 | Cloud Spanner (one copy) | 131.4 | -197.1 |
| 1000 | 328.5 | Cloud Spanner (two copies) | 131.4 | -197.1 |
| 10000 | 3285 | Cloud Spanner (one copy) | 919.8 | -2365.2 |
| 10000 | 3285 | Cloud Spanner (two copies) | 919.8 | -2365.2 |

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Cloud Spanner (one copy) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| Cloud Spanner (one copy) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| Cloud Spanner (one copy) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| Cloud Spanner (one copy) | Origin list price · Control-plane calls | 0 | USD/requests |
| Cloud Spanner (one copy) | Representative item size | 1024 | bytes |
| Cloud Spanner (one copy) | Strongly consistent read fraction | 1 | fraction |
| Cloud Spanner (one copy) | Origin write-unit amplification | 1 | multiplier |
| Cloud Spanner (one copy) | Target reads per point read | 1 | operations |
| Cloud Spanner (one copy) | Target writes per item write | 1 | operations |
| Cloud Spanner (one copy) | Target price guess · read | 0 | USD/read |
| Cloud Spanner (one copy) | Target price guess · write | 0 | USD/write |
| Cloud Spanner (one copy) | Target price guess · provider operation | 0 | USD/provider operation |
| Cloud Spanner (one copy) | Target list price · GiB-month | 0.3 | USD/GiB-month |
| Cloud Spanner (one copy) | Target price guess · published GiB | 0 | USD/published GiB |
| Cloud Spanner (one copy) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Cloud Spanner (one copy) | Target list price · network GiB | 0.12 | USD/network GiB |
| Cloud Spanner (one copy) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Cloud Spanner (one copy) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Cloud Spanner (one copy) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Cloud Spanner (one copy) | Target list price · resource-hour | 0.9 | USD/resource-hour |
| Cloud Spanner (one copy) | Target price guess · resource-month | 0 | USD/resource-month |
| Cloud Spanner (one copy) | Target price guess · input token | 0 | USD/input token |
| Cloud Spanner (one copy) | Target price guess · output token | 0 | USD/output token |
| Cloud Spanner (one copy) | Target monthly base charge | 0 | USD/month |
| Cloud Spanner (one copy) | Target service minimum | 65.7 | USD/month |
| Cloud Spanner (one copy) | Minimum primary CPU | 2 | vCPU |
| Cloud Spanner (one copy) | Minimum primary RAM | 8 | GiB |
| Cloud Spanner (one copy) | Minimum primary disk | 100 | GiB |
| Cloud Spanner (one copy) | Additional full-price standby copy | 0 | 0 or 1 |
| Cloud Spanner (one copy) | Allocated share of provisioned cost | 1 | fraction |
| Cloud Spanner (one copy) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Cloud Spanner (one copy) | Planning peak / mean work | 2 | multiplier |
| Cloud Spanner (one copy) | Planning primary CPU utilization | 0.7 | fraction |
| Cloud Spanner (one copy) | Resident state reserved in RAM | 0.1 | fraction |
| Cloud Spanner (one copy) | Planning disk utilization | 0.8 | fraction |
| Cloud Spanner (one copy) | Maintenance and log disk reserve | 20 | GiB |
| Cloud Spanner (one copy) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Cloud Spanner (one copy) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Cloud Spanner (one copy) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Cloud Spanner (one copy) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Cloud Spanner (one copy) | Dependent object sink write price guess | 0.000005 | USD/write |
| Cloud Spanner (two copies) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| Cloud Spanner (two copies) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| Cloud Spanner (two copies) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| Cloud Spanner (two copies) | Origin list price · Control-plane calls | 0 | USD/requests |
| Cloud Spanner (two copies) | Representative item size | 1024 | bytes |
| Cloud Spanner (two copies) | Strongly consistent read fraction | 1 | fraction |
| Cloud Spanner (two copies) | Origin write-unit amplification | 1 | multiplier |
| Cloud Spanner (two copies) | Target reads per point read | 1 | operations |
| Cloud Spanner (two copies) | Target writes per item write | 1 | operations |
| Cloud Spanner (two copies) | Target price guess · read | 0 | USD/read |
| Cloud Spanner (two copies) | Target price guess · write | 0 | USD/write |
| Cloud Spanner (two copies) | Target price guess · provider operation | 0 | USD/provider operation |
| Cloud Spanner (two copies) | Target list price · GiB-month | 0.3 | USD/GiB-month |
| Cloud Spanner (two copies) | Target price guess · published GiB | 0 | USD/published GiB |
| Cloud Spanner (two copies) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Cloud Spanner (two copies) | Target list price · network GiB | 0.12 | USD/network GiB |
| Cloud Spanner (two copies) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Cloud Spanner (two copies) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Cloud Spanner (two copies) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Cloud Spanner (two copies) | Target list price · resource-hour | 0.9 | USD/resource-hour |
| Cloud Spanner (two copies) | Target price guess · resource-month | 0 | USD/resource-month |
| Cloud Spanner (two copies) | Target price guess · input token | 0 | USD/input token |
| Cloud Spanner (two copies) | Target price guess · output token | 0 | USD/output token |
| Cloud Spanner (two copies) | Target monthly base charge | 0 | USD/month |
| Cloud Spanner (two copies) | Target service minimum | 65.7 | USD/month |
| Cloud Spanner (two copies) | Minimum primary CPU | 2 | vCPU |
| Cloud Spanner (two copies) | Minimum primary RAM | 8 | GiB |
| Cloud Spanner (two copies) | Minimum primary disk | 100 | GiB |
| Cloud Spanner (two copies) | Additional full-price standby copy | 1 | 0 or 1 |
| Cloud Spanner (two copies) | Allocated share of provisioned cost | 1 | fraction |
| Cloud Spanner (two copies) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Cloud Spanner (two copies) | Planning peak / mean work | 2 | multiplier |
| Cloud Spanner (two copies) | Planning primary CPU utilization | 0.7 | fraction |
| Cloud Spanner (two copies) | Resident state reserved in RAM | 0.1 | fraction |
| Cloud Spanner (two copies) | Planning disk utilization | 0.8 | fraction |
| Cloud Spanner (two copies) | Maintenance and log disk reserve | 20 | GiB |
| Cloud Spanner (two copies) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Cloud Spanner (two copies) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Cloud Spanner (two copies) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Cloud Spanner (two copies) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Cloud Spanner (two copies) | Dependent object sink write price guess | 0.000005 | USD/write |

* Writes and storage remain independent. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
* Planning estimate · editable authored rates and sizing assumptions dated 2026-10-22; not verified provider prices. us-east-1 → 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 is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* 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.
* The control plane and table facet describe the same family workload; allocate shared capacity once, not once per catalog facet.
* No transactional, global-table, Streams or scan tariff is inferred from ordinary on-demand point units.
* Spanner bills compute capacity in processing units (100 PU minimum and steps, 1,000 PU per node) whose price includes the three replicas of a regional configuration, plus SSD storage including all replicas. Capacity is sized from planning-peak reads and writes against Google's per-node throughput; replication is built in, so the standby selection adds no copy. Enterprise (USD 1.23) and Enterprise Plus (1.71 per node-hour) editions, dual- and multi-region configurations and per-node storage limits are not selected.
* AWS Price List API, AmazonDynamoDB offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json)
* Amazon DynamoDB pricing: [https://aws.amazon.com/dynamodb/pricing/](https://aws.amazon.com/dynamodb/pricing/)
* Spanner pricing: [https://cloud.google.com/spanner/pricing](https://cloud.google.com/spanner/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.
* 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-1f7602bf670b04f3676190fd832f3a586a145caa` / `2026-10-22.planning.2`. Curve: `workload-1`.

Sources: [AWS Price List API, AmazonDynamoDB offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json), [Amazon DynamoDB pricing](https://aws.amazon.com/dynamodb/pricing/), [Spanner pricing](https://cloud.google.com/spanner/pricing).

### DynamoDB · DynamoDB write units

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

![DynamoDB · DynamoDB write units: monthly service charges by DynamoDB write units. Exact values are in the following table.](/images/diagrams/service-cost/55bc3f848f10bd26d18edd5f717cda85d1f3bfac985581765d6217188fa95761-light.svg)

![DynamoDB · DynamoDB write units: monthly service charges by DynamoDB write units. Exact values are in the following table.](/images/diagrams/service-cost/13321879ea39fc63277fbbc2a8bb7899a42fb9082e48b2b3b6ed95e2dcce86db-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.

| DynamoDB write units (per second) | DynamoDB | Target scenario | Cloud Spanner | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | Cloud Spanner (one copy) | 65.7 | 65.7 |
| 0 | 0 | Cloud Spanner (two copies) | 65.7 | 65.7 |
| 1 | 1.6425 | Cloud Spanner (one copy) | 65.7 | 64.0575 |
| 1 | 1.6425 | Cloud Spanner (two copies) | 65.7 | 64.0575 |
| 10 | 16.425 | Cloud Spanner (one copy) | 65.7 | 49.275 |
| 10 | 16.425 | Cloud Spanner (two copies) | 65.7 | 49.275 |
| 100 | 164.25 | Cloud Spanner (one copy) | 65.7 | -98.55 |
| 100 | 164.25 | Cloud Spanner (two copies) | 65.7 | -98.55 |
| 1000 | 1642.5 | Cloud Spanner (one copy) | 591.3 | -1051.2 |
| 1000 | 1642.5 | Cloud Spanner (two copies) | 591.3 | -1051.2 |
| 10000 | 16425 | Cloud Spanner (one copy) | 5781.6 | -10643.4 |
| 10000 | 16425 | Cloud Spanner (two copies) | 5781.6 | -10643.4 |

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Cloud Spanner (one copy) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| Cloud Spanner (one copy) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| Cloud Spanner (one copy) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| Cloud Spanner (one copy) | Origin list price · Control-plane calls | 0 | USD/requests |
| Cloud Spanner (one copy) | Representative item size | 1024 | bytes |
| Cloud Spanner (one copy) | Strongly consistent read fraction | 1 | fraction |
| Cloud Spanner (one copy) | Origin write-unit amplification | 1 | multiplier |
| Cloud Spanner (one copy) | Target reads per point read | 1 | operations |
| Cloud Spanner (one copy) | Target writes per item write | 1 | operations |
| Cloud Spanner (one copy) | Target price guess · read | 0 | USD/read |
| Cloud Spanner (one copy) | Target price guess · write | 0 | USD/write |
| Cloud Spanner (one copy) | Target price guess · provider operation | 0 | USD/provider operation |
| Cloud Spanner (one copy) | Target list price · GiB-month | 0.3 | USD/GiB-month |
| Cloud Spanner (one copy) | Target price guess · published GiB | 0 | USD/published GiB |
| Cloud Spanner (one copy) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Cloud Spanner (one copy) | Target list price · network GiB | 0.12 | USD/network GiB |
| Cloud Spanner (one copy) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Cloud Spanner (one copy) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Cloud Spanner (one copy) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Cloud Spanner (one copy) | Target list price · resource-hour | 0.9 | USD/resource-hour |
| Cloud Spanner (one copy) | Target price guess · resource-month | 0 | USD/resource-month |
| Cloud Spanner (one copy) | Target price guess · input token | 0 | USD/input token |
| Cloud Spanner (one copy) | Target price guess · output token | 0 | USD/output token |
| Cloud Spanner (one copy) | Target monthly base charge | 0 | USD/month |
| Cloud Spanner (one copy) | Target service minimum | 65.7 | USD/month |
| Cloud Spanner (one copy) | Minimum primary CPU | 2 | vCPU |
| Cloud Spanner (one copy) | Minimum primary RAM | 8 | GiB |
| Cloud Spanner (one copy) | Minimum primary disk | 100 | GiB |
| Cloud Spanner (one copy) | Additional full-price standby copy | 0 | 0 or 1 |
| Cloud Spanner (one copy) | Allocated share of provisioned cost | 1 | fraction |
| Cloud Spanner (one copy) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Cloud Spanner (one copy) | Planning peak / mean work | 2 | multiplier |
| Cloud Spanner (one copy) | Planning primary CPU utilization | 0.7 | fraction |
| Cloud Spanner (one copy) | Resident state reserved in RAM | 0.1 | fraction |
| Cloud Spanner (one copy) | Planning disk utilization | 0.8 | fraction |
| Cloud Spanner (one copy) | Maintenance and log disk reserve | 20 | GiB |
| Cloud Spanner (one copy) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Cloud Spanner (one copy) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Cloud Spanner (one copy) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Cloud Spanner (one copy) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Cloud Spanner (one copy) | Dependent object sink write price guess | 0.000005 | USD/write |
| Cloud Spanner (two copies) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| Cloud Spanner (two copies) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| Cloud Spanner (two copies) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| Cloud Spanner (two copies) | Origin list price · Control-plane calls | 0 | USD/requests |
| Cloud Spanner (two copies) | Representative item size | 1024 | bytes |
| Cloud Spanner (two copies) | Strongly consistent read fraction | 1 | fraction |
| Cloud Spanner (two copies) | Origin write-unit amplification | 1 | multiplier |
| Cloud Spanner (two copies) | Target reads per point read | 1 | operations |
| Cloud Spanner (two copies) | Target writes per item write | 1 | operations |
| Cloud Spanner (two copies) | Target price guess · read | 0 | USD/read |
| Cloud Spanner (two copies) | Target price guess · write | 0 | USD/write |
| Cloud Spanner (two copies) | Target price guess · provider operation | 0 | USD/provider operation |
| Cloud Spanner (two copies) | Target list price · GiB-month | 0.3 | USD/GiB-month |
| Cloud Spanner (two copies) | Target price guess · published GiB | 0 | USD/published GiB |
| Cloud Spanner (two copies) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Cloud Spanner (two copies) | Target list price · network GiB | 0.12 | USD/network GiB |
| Cloud Spanner (two copies) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Cloud Spanner (two copies) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Cloud Spanner (two copies) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Cloud Spanner (two copies) | Target list price · resource-hour | 0.9 | USD/resource-hour |
| Cloud Spanner (two copies) | Target price guess · resource-month | 0 | USD/resource-month |
| Cloud Spanner (two copies) | Target price guess · input token | 0 | USD/input token |
| Cloud Spanner (two copies) | Target price guess · output token | 0 | USD/output token |
| Cloud Spanner (two copies) | Target monthly base charge | 0 | USD/month |
| Cloud Spanner (two copies) | Target service minimum | 65.7 | USD/month |
| Cloud Spanner (two copies) | Minimum primary CPU | 2 | vCPU |
| Cloud Spanner (two copies) | Minimum primary RAM | 8 | GiB |
| Cloud Spanner (two copies) | Minimum primary disk | 100 | GiB |
| Cloud Spanner (two copies) | Additional full-price standby copy | 1 | 0 or 1 |
| Cloud Spanner (two copies) | Allocated share of provisioned cost | 1 | fraction |
| Cloud Spanner (two copies) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Cloud Spanner (two copies) | Planning peak / mean work | 2 | multiplier |
| Cloud Spanner (two copies) | Planning primary CPU utilization | 0.7 | fraction |
| Cloud Spanner (two copies) | Resident state reserved in RAM | 0.1 | fraction |
| Cloud Spanner (two copies) | Planning disk utilization | 0.8 | fraction |
| Cloud Spanner (two copies) | Maintenance and log disk reserve | 20 | GiB |
| Cloud Spanner (two copies) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Cloud Spanner (two copies) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Cloud Spanner (two copies) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Cloud Spanner (two copies) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Cloud Spanner (two copies) | Dependent object sink write price guess | 0.000005 | USD/write |

* Reads and storage remain independent. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
* Planning estimate · editable authored rates and sizing assumptions dated 2026-10-22; not verified provider prices. us-east-1 → 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 is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* 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.
* The control plane and table facet describe the same family workload; allocate shared capacity once, not once per catalog facet.
* No transactional, global-table, Streams or scan tariff is inferred from ordinary on-demand point units.
* Spanner bills compute capacity in processing units (100 PU minimum and steps, 1,000 PU per node) whose price includes the three replicas of a regional configuration, plus SSD storage including all replicas. Capacity is sized from planning-peak reads and writes against Google's per-node throughput; replication is built in, so the standby selection adds no copy. Enterprise (USD 1.23) and Enterprise Plus (1.71 per node-hour) editions, dual- and multi-region configurations and per-node storage limits are not selected.
* AWS Price List API, AmazonDynamoDB offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json)
* Amazon DynamoDB pricing: [https://aws.amazon.com/dynamodb/pricing/](https://aws.amazon.com/dynamodb/pricing/)
* Spanner pricing: [https://cloud.google.com/spanner/pricing](https://cloud.google.com/spanner/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.
* 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-1f7602bf670b04f3676190fd832f3a586a145caa` / `2026-10-22.planning.2`. Curve: `workload-2`.

Sources: [AWS Price List API, AmazonDynamoDB offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json), [Amazon DynamoDB pricing](https://aws.amazon.com/dynamodb/pricing/), [Spanner pricing](https://cloud.google.com/spanner/pricing).

### DynamoDB · Stored data

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

![DynamoDB · Stored data: monthly service charges by Stored data. Exact values are in the following table.](/images/diagrams/service-cost/628e4c131a8ca1fd7e3d2ebecb1c7acea3c261bc8b2213fa0434784d67b5c7b2-light.svg)

![DynamoDB · Stored data: monthly service charges by Stored data. Exact values are in the following table.](/images/diagrams/service-cost/73f4e3eed78a7bd85459db05b9aee0c415ea523825934c43d64457ecab32e507-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.

| Stored data (GiB-month) | DynamoDB | Target scenario | Cloud Spanner | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | Cloud Spanner (one copy) | 65.7 | 65.7 |
| 0 | 0 | Cloud Spanner (two copies) | 65.7 | 65.7 |
| 10 | 2.5 | Cloud Spanner (one copy) | 68.7 | 66.2 |
| 10 | 2.5 | Cloud Spanner (two copies) | 68.7 | 66.2 |
| 100 | 25 | Cloud Spanner (one copy) | 95.7 | 70.7 |
| 100 | 25 | Cloud Spanner (two copies) | 95.7 | 70.7 |
| 1000 | 250 | Cloud Spanner (one copy) | 365.7 | 115.7 |
| 1000 | 250 | Cloud Spanner (two copies) | 365.7 | 115.7 |
| 10000 | 2500 | Cloud Spanner (one copy) | 3065.7 | 565.7 |
| 10000 | 2500 | Cloud Spanner (two copies) | 3065.7 | 565.7 |
| 100000 | 25000 | Cloud Spanner (one copy) | 30065.7 | 5065.7 |
| 100000 | 25000 | Cloud Spanner (two copies) | 30065.7 | 5065.7 |

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Cloud Spanner (one copy) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| Cloud Spanner (one copy) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| Cloud Spanner (one copy) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| Cloud Spanner (one copy) | Origin list price · Control-plane calls | 0 | USD/requests |
| Cloud Spanner (one copy) | Representative item size | 1024 | bytes |
| Cloud Spanner (one copy) | Strongly consistent read fraction | 1 | fraction |
| Cloud Spanner (one copy) | Origin write-unit amplification | 1 | multiplier |
| Cloud Spanner (one copy) | Target reads per point read | 1 | operations |
| Cloud Spanner (one copy) | Target writes per item write | 1 | operations |
| Cloud Spanner (one copy) | Target price guess · read | 0 | USD/read |
| Cloud Spanner (one copy) | Target price guess · write | 0 | USD/write |
| Cloud Spanner (one copy) | Target price guess · provider operation | 0 | USD/provider operation |
| Cloud Spanner (one copy) | Target list price · GiB-month | 0.3 | USD/GiB-month |
| Cloud Spanner (one copy) | Target price guess · published GiB | 0 | USD/published GiB |
| Cloud Spanner (one copy) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Cloud Spanner (one copy) | Target list price · network GiB | 0.12 | USD/network GiB |
| Cloud Spanner (one copy) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Cloud Spanner (one copy) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Cloud Spanner (one copy) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Cloud Spanner (one copy) | Target list price · resource-hour | 0.9 | USD/resource-hour |
| Cloud Spanner (one copy) | Target price guess · resource-month | 0 | USD/resource-month |
| Cloud Spanner (one copy) | Target price guess · input token | 0 | USD/input token |
| Cloud Spanner (one copy) | Target price guess · output token | 0 | USD/output token |
| Cloud Spanner (one copy) | Target monthly base charge | 0 | USD/month |
| Cloud Spanner (one copy) | Target service minimum | 65.7 | USD/month |
| Cloud Spanner (one copy) | Minimum primary CPU | 2 | vCPU |
| Cloud Spanner (one copy) | Minimum primary RAM | 8 | GiB |
| Cloud Spanner (one copy) | Minimum primary disk | 100 | GiB |
| Cloud Spanner (one copy) | Additional full-price standby copy | 0 | 0 or 1 |
| Cloud Spanner (one copy) | Allocated share of provisioned cost | 1 | fraction |
| Cloud Spanner (one copy) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Cloud Spanner (one copy) | Planning peak / mean work | 2 | multiplier |
| Cloud Spanner (one copy) | Planning primary CPU utilization | 0.7 | fraction |
| Cloud Spanner (one copy) | Resident state reserved in RAM | 0.1 | fraction |
| Cloud Spanner (one copy) | Planning disk utilization | 0.8 | fraction |
| Cloud Spanner (one copy) | Maintenance and log disk reserve | 20 | GiB |
| Cloud Spanner (one copy) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Cloud Spanner (one copy) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Cloud Spanner (one copy) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Cloud Spanner (one copy) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Cloud Spanner (one copy) | Dependent object sink write price guess | 0.000005 | USD/write |
| Cloud Spanner (two copies) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| Cloud Spanner (two copies) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| Cloud Spanner (two copies) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| Cloud Spanner (two copies) | Origin list price · Control-plane calls | 0 | USD/requests |
| Cloud Spanner (two copies) | Representative item size | 1024 | bytes |
| Cloud Spanner (two copies) | Strongly consistent read fraction | 1 | fraction |
| Cloud Spanner (two copies) | Origin write-unit amplification | 1 | multiplier |
| Cloud Spanner (two copies) | Target reads per point read | 1 | operations |
| Cloud Spanner (two copies) | Target writes per item write | 1 | operations |
| Cloud Spanner (two copies) | Target price guess · read | 0 | USD/read |
| Cloud Spanner (two copies) | Target price guess · write | 0 | USD/write |
| Cloud Spanner (two copies) | Target price guess · provider operation | 0 | USD/provider operation |
| Cloud Spanner (two copies) | Target list price · GiB-month | 0.3 | USD/GiB-month |
| Cloud Spanner (two copies) | Target price guess · published GiB | 0 | USD/published GiB |
| Cloud Spanner (two copies) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Cloud Spanner (two copies) | Target list price · network GiB | 0.12 | USD/network GiB |
| Cloud Spanner (two copies) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Cloud Spanner (two copies) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Cloud Spanner (two copies) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Cloud Spanner (two copies) | Target list price · resource-hour | 0.9 | USD/resource-hour |
| Cloud Spanner (two copies) | Target price guess · resource-month | 0 | USD/resource-month |
| Cloud Spanner (two copies) | Target price guess · input token | 0 | USD/input token |
| Cloud Spanner (two copies) | Target price guess · output token | 0 | USD/output token |
| Cloud Spanner (two copies) | Target monthly base charge | 0 | USD/month |
| Cloud Spanner (two copies) | Target service minimum | 65.7 | USD/month |
| Cloud Spanner (two copies) | Minimum primary CPU | 2 | vCPU |
| Cloud Spanner (two copies) | Minimum primary RAM | 8 | GiB |
| Cloud Spanner (two copies) | Minimum primary disk | 100 | GiB |
| Cloud Spanner (two copies) | Additional full-price standby copy | 1 | 0 or 1 |
| Cloud Spanner (two copies) | Allocated share of provisioned cost | 1 | fraction |
| Cloud Spanner (two copies) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Cloud Spanner (two copies) | Planning peak / mean work | 2 | multiplier |
| Cloud Spanner (two copies) | Planning primary CPU utilization | 0.7 | fraction |
| Cloud Spanner (two copies) | Resident state reserved in RAM | 0.1 | fraction |
| Cloud Spanner (two copies) | Planning disk utilization | 0.8 | fraction |
| Cloud Spanner (two copies) | Maintenance and log disk reserve | 20 | GiB |
| Cloud Spanner (two copies) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Cloud Spanner (two copies) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Cloud Spanner (two copies) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Cloud Spanner (two copies) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Cloud Spanner (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. us-east-1 → 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 is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* 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.
* The control plane and table facet describe the same family workload; allocate shared capacity once, not once per catalog facet.
* No transactional, global-table, Streams or scan tariff is inferred from ordinary on-demand point units.
* Spanner bills compute capacity in processing units (100 PU minimum and steps, 1,000 PU per node) whose price includes the three replicas of a regional configuration, plus SSD storage including all replicas. Capacity is sized from planning-peak reads and writes against Google's per-node throughput; replication is built in, so the standby selection adds no copy. Enterprise (USD 1.23) and Enterprise Plus (1.71 per node-hour) editions, dual- and multi-region configurations and per-node storage limits are not selected.
* AWS Price List API, AmazonDynamoDB offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json)
* Amazon DynamoDB pricing: [https://aws.amazon.com/dynamodb/pricing/](https://aws.amazon.com/dynamodb/pricing/)
* Spanner pricing: [https://cloud.google.com/spanner/pricing](https://cloud.google.com/spanner/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.
* 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-1f7602bf670b04f3676190fd832f3a586a145caa` / `2026-10-22.planning.2`. Curve: `workload-3`.

Sources: [AWS Price List API, AmazonDynamoDB offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json), [Amazon DynamoDB pricing](https://aws.amazon.com/dynamodb/pricing/), [Spanner pricing](https://cloud.google.com/spanner/pricing).

## DynamoDB → Cloud Spanner

Origin API: `aws::1.0.0::dynamodb::table`. Target backend: `google::1.0.0::spanner`.

### DynamoDB · DynamoDB read units

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

![DynamoDB · DynamoDB read units: monthly service charges by DynamoDB read units. Exact values are in the following table.](/images/diagrams/service-cost/ee876907d75c2451d2ebf67b24578b29b6646c6e97da6d5e7c46c2af1ae46c75-light.svg)

![DynamoDB · DynamoDB read units: monthly service charges by DynamoDB read units. Exact values are in the following table.](/images/diagrams/service-cost/a62a180bd5139d37e744372815e8773a01bbc0df49617a94512dc61aa3fb0d1b-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.

| DynamoDB read units (per second) | DynamoDB | Target scenario | Cloud Spanner | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | Cloud Spanner (one copy) | 65.7 | 65.7 |
| 0 | 0 | Cloud Spanner (two copies) | 65.7 | 65.7 |
| 1 | 0.3285 | Cloud Spanner (one copy) | 65.7 | 65.3715 |
| 1 | 0.3285 | Cloud Spanner (two copies) | 65.7 | 65.3715 |
| 10 | 3.285 | Cloud Spanner (one copy) | 65.7 | 62.415 |
| 10 | 3.285 | Cloud Spanner (two copies) | 65.7 | 62.415 |
| 100 | 32.85 | Cloud Spanner (one copy) | 65.7 | 32.85 |
| 100 | 32.85 | Cloud Spanner (two copies) | 65.7 | 32.85 |
| 1000 | 328.5 | Cloud Spanner (one copy) | 131.4 | -197.1 |
| 1000 | 328.5 | Cloud Spanner (two copies) | 131.4 | -197.1 |
| 10000 | 3285 | Cloud Spanner (one copy) | 919.8 | -2365.2 |
| 10000 | 3285 | Cloud Spanner (two copies) | 919.8 | -2365.2 |

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Cloud Spanner (one copy) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| Cloud Spanner (one copy) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| Cloud Spanner (one copy) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| Cloud Spanner (one copy) | Origin list price · Control-plane calls | 0 | USD/requests |
| Cloud Spanner (one copy) | Representative item size | 1024 | bytes |
| Cloud Spanner (one copy) | Strongly consistent read fraction | 1 | fraction |
| Cloud Spanner (one copy) | Origin write-unit amplification | 1 | multiplier |
| Cloud Spanner (one copy) | Target reads per point read | 1 | operations |
| Cloud Spanner (one copy) | Target writes per item write | 1 | operations |
| Cloud Spanner (one copy) | Target price guess · read | 0 | USD/read |
| Cloud Spanner (one copy) | Target price guess · write | 0 | USD/write |
| Cloud Spanner (one copy) | Target price guess · provider operation | 0 | USD/provider operation |
| Cloud Spanner (one copy) | Target list price · GiB-month | 0.3 | USD/GiB-month |
| Cloud Spanner (one copy) | Target price guess · published GiB | 0 | USD/published GiB |
| Cloud Spanner (one copy) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Cloud Spanner (one copy) | Target list price · network GiB | 0.12 | USD/network GiB |
| Cloud Spanner (one copy) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Cloud Spanner (one copy) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Cloud Spanner (one copy) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Cloud Spanner (one copy) | Target list price · resource-hour | 0.9 | USD/resource-hour |
| Cloud Spanner (one copy) | Target price guess · resource-month | 0 | USD/resource-month |
| Cloud Spanner (one copy) | Target price guess · input token | 0 | USD/input token |
| Cloud Spanner (one copy) | Target price guess · output token | 0 | USD/output token |
| Cloud Spanner (one copy) | Target monthly base charge | 0 | USD/month |
| Cloud Spanner (one copy) | Target service minimum | 65.7 | USD/month |
| Cloud Spanner (one copy) | Minimum primary CPU | 2 | vCPU |
| Cloud Spanner (one copy) | Minimum primary RAM | 8 | GiB |
| Cloud Spanner (one copy) | Minimum primary disk | 100 | GiB |
| Cloud Spanner (one copy) | Additional full-price standby copy | 0 | 0 or 1 |
| Cloud Spanner (one copy) | Allocated share of provisioned cost | 1 | fraction |
| Cloud Spanner (one copy) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Cloud Spanner (one copy) | Planning peak / mean work | 2 | multiplier |
| Cloud Spanner (one copy) | Planning primary CPU utilization | 0.7 | fraction |
| Cloud Spanner (one copy) | Resident state reserved in RAM | 0.1 | fraction |
| Cloud Spanner (one copy) | Planning disk utilization | 0.8 | fraction |
| Cloud Spanner (one copy) | Maintenance and log disk reserve | 20 | GiB |
| Cloud Spanner (one copy) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Cloud Spanner (one copy) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Cloud Spanner (one copy) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Cloud Spanner (one copy) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Cloud Spanner (one copy) | Dependent object sink write price guess | 0.000005 | USD/write |
| Cloud Spanner (two copies) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| Cloud Spanner (two copies) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| Cloud Spanner (two copies) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| Cloud Spanner (two copies) | Origin list price · Control-plane calls | 0 | USD/requests |
| Cloud Spanner (two copies) | Representative item size | 1024 | bytes |
| Cloud Spanner (two copies) | Strongly consistent read fraction | 1 | fraction |
| Cloud Spanner (two copies) | Origin write-unit amplification | 1 | multiplier |
| Cloud Spanner (two copies) | Target reads per point read | 1 | operations |
| Cloud Spanner (two copies) | Target writes per item write | 1 | operations |
| Cloud Spanner (two copies) | Target price guess · read | 0 | USD/read |
| Cloud Spanner (two copies) | Target price guess · write | 0 | USD/write |
| Cloud Spanner (two copies) | Target price guess · provider operation | 0 | USD/provider operation |
| Cloud Spanner (two copies) | Target list price · GiB-month | 0.3 | USD/GiB-month |
| Cloud Spanner (two copies) | Target price guess · published GiB | 0 | USD/published GiB |
| Cloud Spanner (two copies) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Cloud Spanner (two copies) | Target list price · network GiB | 0.12 | USD/network GiB |
| Cloud Spanner (two copies) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Cloud Spanner (two copies) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Cloud Spanner (two copies) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Cloud Spanner (two copies) | Target list price · resource-hour | 0.9 | USD/resource-hour |
| Cloud Spanner (two copies) | Target price guess · resource-month | 0 | USD/resource-month |
| Cloud Spanner (two copies) | Target price guess · input token | 0 | USD/input token |
| Cloud Spanner (two copies) | Target price guess · output token | 0 | USD/output token |
| Cloud Spanner (two copies) | Target monthly base charge | 0 | USD/month |
| Cloud Spanner (two copies) | Target service minimum | 65.7 | USD/month |
| Cloud Spanner (two copies) | Minimum primary CPU | 2 | vCPU |
| Cloud Spanner (two copies) | Minimum primary RAM | 8 | GiB |
| Cloud Spanner (two copies) | Minimum primary disk | 100 | GiB |
| Cloud Spanner (two copies) | Additional full-price standby copy | 1 | 0 or 1 |
| Cloud Spanner (two copies) | Allocated share of provisioned cost | 1 | fraction |
| Cloud Spanner (two copies) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Cloud Spanner (two copies) | Planning peak / mean work | 2 | multiplier |
| Cloud Spanner (two copies) | Planning primary CPU utilization | 0.7 | fraction |
| Cloud Spanner (two copies) | Resident state reserved in RAM | 0.1 | fraction |
| Cloud Spanner (two copies) | Planning disk utilization | 0.8 | fraction |
| Cloud Spanner (two copies) | Maintenance and log disk reserve | 20 | GiB |
| Cloud Spanner (two copies) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Cloud Spanner (two copies) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Cloud Spanner (two copies) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Cloud Spanner (two copies) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Cloud Spanner (two copies) | Dependent object sink write price guess | 0.000005 | USD/write |

* Writes and storage remain independent. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
* Planning estimate · editable authored rates and sizing assumptions dated 2026-10-22; not verified provider prices. us-east-1 → 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 is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* 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.
* The control plane and table facet describe the same family workload; allocate shared capacity once, not once per catalog facet.
* No transactional, global-table, Streams or scan tariff is inferred from ordinary on-demand point units.
* Spanner bills compute capacity in processing units (100 PU minimum and steps, 1,000 PU per node) whose price includes the three replicas of a regional configuration, plus SSD storage including all replicas. Capacity is sized from planning-peak reads and writes against Google's per-node throughput; replication is built in, so the standby selection adds no copy. Enterprise (USD 1.23) and Enterprise Plus (1.71 per node-hour) editions, dual- and multi-region configurations and per-node storage limits are not selected.
* AWS Price List API, AmazonDynamoDB offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json)
* Amazon DynamoDB pricing: [https://aws.amazon.com/dynamodb/pricing/](https://aws.amazon.com/dynamodb/pricing/)
* Spanner pricing: [https://cloud.google.com/spanner/pricing](https://cloud.google.com/spanner/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.
* 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-610b516e23e900c58eeb455757b30a011c363c10` / `2026-10-22.planning.2`. Curve: `workload-1`.

Sources: [AWS Price List API, AmazonDynamoDB offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json), [Amazon DynamoDB pricing](https://aws.amazon.com/dynamodb/pricing/), [Spanner pricing](https://cloud.google.com/spanner/pricing).

### DynamoDB · DynamoDB write units

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

![DynamoDB · DynamoDB write units: monthly service charges by DynamoDB write units. Exact values are in the following table.](/images/diagrams/service-cost/55bc3f848f10bd26d18edd5f717cda85d1f3bfac985581765d6217188fa95761-light.svg)

![DynamoDB · DynamoDB write units: monthly service charges by DynamoDB write units. Exact values are in the following table.](/images/diagrams/service-cost/13321879ea39fc63277fbbc2a8bb7899a42fb9082e48b2b3b6ed95e2dcce86db-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.

| DynamoDB write units (per second) | DynamoDB | Target scenario | Cloud Spanner | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | Cloud Spanner (one copy) | 65.7 | 65.7 |
| 0 | 0 | Cloud Spanner (two copies) | 65.7 | 65.7 |
| 1 | 1.6425 | Cloud Spanner (one copy) | 65.7 | 64.0575 |
| 1 | 1.6425 | Cloud Spanner (two copies) | 65.7 | 64.0575 |
| 10 | 16.425 | Cloud Spanner (one copy) | 65.7 | 49.275 |
| 10 | 16.425 | Cloud Spanner (two copies) | 65.7 | 49.275 |
| 100 | 164.25 | Cloud Spanner (one copy) | 65.7 | -98.55 |
| 100 | 164.25 | Cloud Spanner (two copies) | 65.7 | -98.55 |
| 1000 | 1642.5 | Cloud Spanner (one copy) | 591.3 | -1051.2 |
| 1000 | 1642.5 | Cloud Spanner (two copies) | 591.3 | -1051.2 |
| 10000 | 16425 | Cloud Spanner (one copy) | 5781.6 | -10643.4 |
| 10000 | 16425 | Cloud Spanner (two copies) | 5781.6 | -10643.4 |

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Cloud Spanner (one copy) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| Cloud Spanner (one copy) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| Cloud Spanner (one copy) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| Cloud Spanner (one copy) | Origin list price · Control-plane calls | 0 | USD/requests |
| Cloud Spanner (one copy) | Representative item size | 1024 | bytes |
| Cloud Spanner (one copy) | Strongly consistent read fraction | 1 | fraction |
| Cloud Spanner (one copy) | Origin write-unit amplification | 1 | multiplier |
| Cloud Spanner (one copy) | Target reads per point read | 1 | operations |
| Cloud Spanner (one copy) | Target writes per item write | 1 | operations |
| Cloud Spanner (one copy) | Target price guess · read | 0 | USD/read |
| Cloud Spanner (one copy) | Target price guess · write | 0 | USD/write |
| Cloud Spanner (one copy) | Target price guess · provider operation | 0 | USD/provider operation |
| Cloud Spanner (one copy) | Target list price · GiB-month | 0.3 | USD/GiB-month |
| Cloud Spanner (one copy) | Target price guess · published GiB | 0 | USD/published GiB |
| Cloud Spanner (one copy) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Cloud Spanner (one copy) | Target list price · network GiB | 0.12 | USD/network GiB |
| Cloud Spanner (one copy) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Cloud Spanner (one copy) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Cloud Spanner (one copy) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Cloud Spanner (one copy) | Target list price · resource-hour | 0.9 | USD/resource-hour |
| Cloud Spanner (one copy) | Target price guess · resource-month | 0 | USD/resource-month |
| Cloud Spanner (one copy) | Target price guess · input token | 0 | USD/input token |
| Cloud Spanner (one copy) | Target price guess · output token | 0 | USD/output token |
| Cloud Spanner (one copy) | Target monthly base charge | 0 | USD/month |
| Cloud Spanner (one copy) | Target service minimum | 65.7 | USD/month |
| Cloud Spanner (one copy) | Minimum primary CPU | 2 | vCPU |
| Cloud Spanner (one copy) | Minimum primary RAM | 8 | GiB |
| Cloud Spanner (one copy) | Minimum primary disk | 100 | GiB |
| Cloud Spanner (one copy) | Additional full-price standby copy | 0 | 0 or 1 |
| Cloud Spanner (one copy) | Allocated share of provisioned cost | 1 | fraction |
| Cloud Spanner (one copy) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Cloud Spanner (one copy) | Planning peak / mean work | 2 | multiplier |
| Cloud Spanner (one copy) | Planning primary CPU utilization | 0.7 | fraction |
| Cloud Spanner (one copy) | Resident state reserved in RAM | 0.1 | fraction |
| Cloud Spanner (one copy) | Planning disk utilization | 0.8 | fraction |
| Cloud Spanner (one copy) | Maintenance and log disk reserve | 20 | GiB |
| Cloud Spanner (one copy) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Cloud Spanner (one copy) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Cloud Spanner (one copy) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Cloud Spanner (one copy) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Cloud Spanner (one copy) | Dependent object sink write price guess | 0.000005 | USD/write |
| Cloud Spanner (two copies) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| Cloud Spanner (two copies) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| Cloud Spanner (two copies) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| Cloud Spanner (two copies) | Origin list price · Control-plane calls | 0 | USD/requests |
| Cloud Spanner (two copies) | Representative item size | 1024 | bytes |
| Cloud Spanner (two copies) | Strongly consistent read fraction | 1 | fraction |
| Cloud Spanner (two copies) | Origin write-unit amplification | 1 | multiplier |
| Cloud Spanner (two copies) | Target reads per point read | 1 | operations |
| Cloud Spanner (two copies) | Target writes per item write | 1 | operations |
| Cloud Spanner (two copies) | Target price guess · read | 0 | USD/read |
| Cloud Spanner (two copies) | Target price guess · write | 0 | USD/write |
| Cloud Spanner (two copies) | Target price guess · provider operation | 0 | USD/provider operation |
| Cloud Spanner (two copies) | Target list price · GiB-month | 0.3 | USD/GiB-month |
| Cloud Spanner (two copies) | Target price guess · published GiB | 0 | USD/published GiB |
| Cloud Spanner (two copies) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Cloud Spanner (two copies) | Target list price · network GiB | 0.12 | USD/network GiB |
| Cloud Spanner (two copies) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Cloud Spanner (two copies) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Cloud Spanner (two copies) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Cloud Spanner (two copies) | Target list price · resource-hour | 0.9 | USD/resource-hour |
| Cloud Spanner (two copies) | Target price guess · resource-month | 0 | USD/resource-month |
| Cloud Spanner (two copies) | Target price guess · input token | 0 | USD/input token |
| Cloud Spanner (two copies) | Target price guess · output token | 0 | USD/output token |
| Cloud Spanner (two copies) | Target monthly base charge | 0 | USD/month |
| Cloud Spanner (two copies) | Target service minimum | 65.7 | USD/month |
| Cloud Spanner (two copies) | Minimum primary CPU | 2 | vCPU |
| Cloud Spanner (two copies) | Minimum primary RAM | 8 | GiB |
| Cloud Spanner (two copies) | Minimum primary disk | 100 | GiB |
| Cloud Spanner (two copies) | Additional full-price standby copy | 1 | 0 or 1 |
| Cloud Spanner (two copies) | Allocated share of provisioned cost | 1 | fraction |
| Cloud Spanner (two copies) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Cloud Spanner (two copies) | Planning peak / mean work | 2 | multiplier |
| Cloud Spanner (two copies) | Planning primary CPU utilization | 0.7 | fraction |
| Cloud Spanner (two copies) | Resident state reserved in RAM | 0.1 | fraction |
| Cloud Spanner (two copies) | Planning disk utilization | 0.8 | fraction |
| Cloud Spanner (two copies) | Maintenance and log disk reserve | 20 | GiB |
| Cloud Spanner (two copies) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Cloud Spanner (two copies) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Cloud Spanner (two copies) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Cloud Spanner (two copies) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Cloud Spanner (two copies) | Dependent object sink write price guess | 0.000005 | USD/write |

* Reads and storage remain independent. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
* Planning estimate · editable authored rates and sizing assumptions dated 2026-10-22; not verified provider prices. us-east-1 → 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 is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* 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.
* The control plane and table facet describe the same family workload; allocate shared capacity once, not once per catalog facet.
* No transactional, global-table, Streams or scan tariff is inferred from ordinary on-demand point units.
* Spanner bills compute capacity in processing units (100 PU minimum and steps, 1,000 PU per node) whose price includes the three replicas of a regional configuration, plus SSD storage including all replicas. Capacity is sized from planning-peak reads and writes against Google's per-node throughput; replication is built in, so the standby selection adds no copy. Enterprise (USD 1.23) and Enterprise Plus (1.71 per node-hour) editions, dual- and multi-region configurations and per-node storage limits are not selected.
* AWS Price List API, AmazonDynamoDB offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json)
* Amazon DynamoDB pricing: [https://aws.amazon.com/dynamodb/pricing/](https://aws.amazon.com/dynamodb/pricing/)
* Spanner pricing: [https://cloud.google.com/spanner/pricing](https://cloud.google.com/spanner/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.
* 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-610b516e23e900c58eeb455757b30a011c363c10` / `2026-10-22.planning.2`. Curve: `workload-2`.

Sources: [AWS Price List API, AmazonDynamoDB offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json), [Amazon DynamoDB pricing](https://aws.amazon.com/dynamodb/pricing/), [Spanner pricing](https://cloud.google.com/spanner/pricing).

### DynamoDB · Stored data

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

![DynamoDB · Stored data: monthly service charges by Stored data. Exact values are in the following table.](/images/diagrams/service-cost/628e4c131a8ca1fd7e3d2ebecb1c7acea3c261bc8b2213fa0434784d67b5c7b2-light.svg)

![DynamoDB · Stored data: monthly service charges by Stored data. Exact values are in the following table.](/images/diagrams/service-cost/73f4e3eed78a7bd85459db05b9aee0c415ea523825934c43d64457ecab32e507-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.

| Stored data (GiB-month) | DynamoDB | Target scenario | Cloud Spanner | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | Cloud Spanner (one copy) | 65.7 | 65.7 |
| 0 | 0 | Cloud Spanner (two copies) | 65.7 | 65.7 |
| 10 | 2.5 | Cloud Spanner (one copy) | 68.7 | 66.2 |
| 10 | 2.5 | Cloud Spanner (two copies) | 68.7 | 66.2 |
| 100 | 25 | Cloud Spanner (one copy) | 95.7 | 70.7 |
| 100 | 25 | Cloud Spanner (two copies) | 95.7 | 70.7 |
| 1000 | 250 | Cloud Spanner (one copy) | 365.7 | 115.7 |
| 1000 | 250 | Cloud Spanner (two copies) | 365.7 | 115.7 |
| 10000 | 2500 | Cloud Spanner (one copy) | 3065.7 | 565.7 |
| 10000 | 2500 | Cloud Spanner (two copies) | 3065.7 | 565.7 |
| 100000 | 25000 | Cloud Spanner (one copy) | 30065.7 | 5065.7 |
| 100000 | 25000 | Cloud Spanner (two copies) | 30065.7 | 5065.7 |

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Cloud Spanner (one copy) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| Cloud Spanner (one copy) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| Cloud Spanner (one copy) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| Cloud Spanner (one copy) | Origin list price · Control-plane calls | 0 | USD/requests |
| Cloud Spanner (one copy) | Representative item size | 1024 | bytes |
| Cloud Spanner (one copy) | Strongly consistent read fraction | 1 | fraction |
| Cloud Spanner (one copy) | Origin write-unit amplification | 1 | multiplier |
| Cloud Spanner (one copy) | Target reads per point read | 1 | operations |
| Cloud Spanner (one copy) | Target writes per item write | 1 | operations |
| Cloud Spanner (one copy) | Target price guess · read | 0 | USD/read |
| Cloud Spanner (one copy) | Target price guess · write | 0 | USD/write |
| Cloud Spanner (one copy) | Target price guess · provider operation | 0 | USD/provider operation |
| Cloud Spanner (one copy) | Target list price · GiB-month | 0.3 | USD/GiB-month |
| Cloud Spanner (one copy) | Target price guess · published GiB | 0 | USD/published GiB |
| Cloud Spanner (one copy) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Cloud Spanner (one copy) | Target list price · network GiB | 0.12 | USD/network GiB |
| Cloud Spanner (one copy) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Cloud Spanner (one copy) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Cloud Spanner (one copy) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Cloud Spanner (one copy) | Target list price · resource-hour | 0.9 | USD/resource-hour |
| Cloud Spanner (one copy) | Target price guess · resource-month | 0 | USD/resource-month |
| Cloud Spanner (one copy) | Target price guess · input token | 0 | USD/input token |
| Cloud Spanner (one copy) | Target price guess · output token | 0 | USD/output token |
| Cloud Spanner (one copy) | Target monthly base charge | 0 | USD/month |
| Cloud Spanner (one copy) | Target service minimum | 65.7 | USD/month |
| Cloud Spanner (one copy) | Minimum primary CPU | 2 | vCPU |
| Cloud Spanner (one copy) | Minimum primary RAM | 8 | GiB |
| Cloud Spanner (one copy) | Minimum primary disk | 100 | GiB |
| Cloud Spanner (one copy) | Additional full-price standby copy | 0 | 0 or 1 |
| Cloud Spanner (one copy) | Allocated share of provisioned cost | 1 | fraction |
| Cloud Spanner (one copy) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Cloud Spanner (one copy) | Planning peak / mean work | 2 | multiplier |
| Cloud Spanner (one copy) | Planning primary CPU utilization | 0.7 | fraction |
| Cloud Spanner (one copy) | Resident state reserved in RAM | 0.1 | fraction |
| Cloud Spanner (one copy) | Planning disk utilization | 0.8 | fraction |
| Cloud Spanner (one copy) | Maintenance and log disk reserve | 20 | GiB |
| Cloud Spanner (one copy) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Cloud Spanner (one copy) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Cloud Spanner (one copy) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Cloud Spanner (one copy) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Cloud Spanner (one copy) | Dependent object sink write price guess | 0.000005 | USD/write |
| Cloud Spanner (two copies) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| Cloud Spanner (two copies) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| Cloud Spanner (two copies) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| Cloud Spanner (two copies) | Origin list price · Control-plane calls | 0 | USD/requests |
| Cloud Spanner (two copies) | Representative item size | 1024 | bytes |
| Cloud Spanner (two copies) | Strongly consistent read fraction | 1 | fraction |
| Cloud Spanner (two copies) | Origin write-unit amplification | 1 | multiplier |
| Cloud Spanner (two copies) | Target reads per point read | 1 | operations |
| Cloud Spanner (two copies) | Target writes per item write | 1 | operations |
| Cloud Spanner (two copies) | Target price guess · read | 0 | USD/read |
| Cloud Spanner (two copies) | Target price guess · write | 0 | USD/write |
| Cloud Spanner (two copies) | Target price guess · provider operation | 0 | USD/provider operation |
| Cloud Spanner (two copies) | Target list price · GiB-month | 0.3 | USD/GiB-month |
| Cloud Spanner (two copies) | Target price guess · published GiB | 0 | USD/published GiB |
| Cloud Spanner (two copies) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Cloud Spanner (two copies) | Target list price · network GiB | 0.12 | USD/network GiB |
| Cloud Spanner (two copies) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Cloud Spanner (two copies) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Cloud Spanner (two copies) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Cloud Spanner (two copies) | Target list price · resource-hour | 0.9 | USD/resource-hour |
| Cloud Spanner (two copies) | Target price guess · resource-month | 0 | USD/resource-month |
| Cloud Spanner (two copies) | Target price guess · input token | 0 | USD/input token |
| Cloud Spanner (two copies) | Target price guess · output token | 0 | USD/output token |
| Cloud Spanner (two copies) | Target monthly base charge | 0 | USD/month |
| Cloud Spanner (two copies) | Target service minimum | 65.7 | USD/month |
| Cloud Spanner (two copies) | Minimum primary CPU | 2 | vCPU |
| Cloud Spanner (two copies) | Minimum primary RAM | 8 | GiB |
| Cloud Spanner (two copies) | Minimum primary disk | 100 | GiB |
| Cloud Spanner (two copies) | Additional full-price standby copy | 1 | 0 or 1 |
| Cloud Spanner (two copies) | Allocated share of provisioned cost | 1 | fraction |
| Cloud Spanner (two copies) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Cloud Spanner (two copies) | Planning peak / mean work | 2 | multiplier |
| Cloud Spanner (two copies) | Planning primary CPU utilization | 0.7 | fraction |
| Cloud Spanner (two copies) | Resident state reserved in RAM | 0.1 | fraction |
| Cloud Spanner (two copies) | Planning disk utilization | 0.8 | fraction |
| Cloud Spanner (two copies) | Maintenance and log disk reserve | 20 | GiB |
| Cloud Spanner (two copies) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Cloud Spanner (two copies) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Cloud Spanner (two copies) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Cloud Spanner (two copies) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Cloud Spanner (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. us-east-1 → 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 is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* 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.
* The control plane and table facet describe the same family workload; allocate shared capacity once, not once per catalog facet.
* No transactional, global-table, Streams or scan tariff is inferred from ordinary on-demand point units.
* Spanner bills compute capacity in processing units (100 PU minimum and steps, 1,000 PU per node) whose price includes the three replicas of a regional configuration, plus SSD storage including all replicas. Capacity is sized from planning-peak reads and writes against Google's per-node throughput; replication is built in, so the standby selection adds no copy. Enterprise (USD 1.23) and Enterprise Plus (1.71 per node-hour) editions, dual- and multi-region configurations and per-node storage limits are not selected.
* AWS Price List API, AmazonDynamoDB offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json)
* Amazon DynamoDB pricing: [https://aws.amazon.com/dynamodb/pricing/](https://aws.amazon.com/dynamodb/pricing/)
* Spanner pricing: [https://cloud.google.com/spanner/pricing](https://cloud.google.com/spanner/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.
* 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-610b516e23e900c58eeb455757b30a011c363c10` / `2026-10-22.planning.2`. Curve: `workload-3`.

Sources: [AWS Price List API, AmazonDynamoDB offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json), [Amazon DynamoDB pricing](https://aws.amazon.com/dynamodb/pricing/), [Spanner pricing](https://cloud.google.com/spanner/pricing).

## DynamoDB → Firestore

Origin API: `aws::1.0.0::dynamodb::table`. Target backend: `google::1.0.0::firestore`.

### Monthly cost by DynamoDB point-read rate

Reference monthly service charges by Read operations/s. Adapter hosting and Tensor9 fees are excluded. Source: us-east-1; target: us-central1; currency: USD.

![Monthly cost by DynamoDB point-read rate: monthly service charges by Read operations/s. Exact values are in the following table.](/images/diagrams/service-cost/aea5d9a20f125b1a1ce64f6b835d1067a3e1ca2071909720444048f35d3d21d7-light.svg)

![Monthly cost by DynamoDB point-read rate: monthly service charges by Read operations/s. Exact values are in the following table.](/images/diagrams/service-cost/bc6e5b8683cb8f29b1026125d3da8fa4f291ae1a1b8396df0235f2caf977a852-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.

| Read operations/s (reads/s) | DynamoDB | Target scenario | Firestore | Difference |
| -: | -: | - | -: | -: |
| 0 | 25 | Firestore | 15 | -10 |
| 1 | 25.49275 | Firestore | 16.02492 | -9.46783 |
| 10 | 29.9275 | Firestore | 25.2492 | -4.6783 |
| 100 | 74.275 | Firestore | 117.492 | 43.217 |
| 1000 | 517.75 | Firestore | 1039.92 | 522.17 |
| 10000 | 4952.5 | Firestore | 10264.2 | 5311.7 |

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Firestore | Representative DynamoDB item size | 1024 | bytes |
| Firestore | Strongly consistent origin reads | 1 | 0 = eventual, 1 = strong |
| Firestore | Origin write-unit amplification | 1 | multiplier |
| Firestore | Additional document reads per write | 0 | reads/write |
| Firestore | Document writes per origin write | 1 | writes/write |
| Firestore | Firestore physical storage / source billed bytes | 1 | multiplier |

* Strong 1 KiB point reads and plain writes; one write per ten reads, no origin index amplification. 730 hours/month; retained source data stays at 100 GiB. Firestore uses one document per item, blind writes, no extra reads and equal billed storage; this is an illustrative storage assumption.
* Reference list rates as of 2026-10-18: us-east-1 → 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.
* Firestore Standard edition, regional us-central1. One document read per origin point read; explicit reads/writes per write.
* Plain unconditioned PutItem can use the blind write path; read-modify-write, conditions and retries increase document reads.
* Equal physical storage is an illustrative assumption; tagged item envelopes, metadata and indexes can change billed bytes.
* Source usage is priced at reference rates; source lines are not actual invoice charges. Free or discounted usage still consumes target resources.
* AWS DynamoDB Standard on-demand pricing: [https://aws.amazon.com/dynamodb/pricing/](https://aws.amazon.com/dynamodb/pricing/)
* Firestore Standard regional pricing: [https://cloud.google.com/firestore/pricing/](https://cloud.google.com/firestore/pricing/)

Cost scope: Modeled monthly service usage and selected database allocation; adapter hosting and Tensor9 fees only when explicitly supplied.

Excluded costs and workload features:

* Free allowances, negotiated discounts, credits, tax and one-time migration charges.
* Charges not listed in the breakdown, including additional network transfer, backups and encryption/KMS.
* Application compute changes, operational labor and portfolio-wide sharing or deduplication of infrastructure.
* Queries, scans and index-entry reads, transactions, Streams, document deletes/TTL and unsupported item domains.

Rate snapshot: 2026-10-18. Model: `dynamodb-firestore` / `2026-10-18.4`. Curve: `read-rate`.

Sources: [AWS DynamoDB Standard on-demand pricing](https://aws.amazon.com/dynamodb/pricing/), [Firestore Standard regional pricing](https://cloud.google.com/firestore/pricing/).

### Monthly cost by retained DynamoDB data

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

![Monthly cost by retained DynamoDB data: monthly service charges by Retained source data. Exact values are in the following table.](/images/diagrams/service-cost/2c0c85bc7bded1b3a955398d59995409f98b4273d8500fa54c1a85d965604ecd-light.svg)

![Monthly cost by retained DynamoDB data: monthly service charges by Retained source data. Exact values are in the following table.](/images/diagrams/service-cost/89dac0dce073f137f21d6c2fe84984a4dbe2d2d212b648d621f7eeb8f8dc0b95-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.

| Retained source data (GiB-month) | DynamoDB | Target scenario | Firestore | Difference |
| -: | -: | - | -: | -: |
| 0 | 18.75 | Firestore | 39 | 20.25 |
| 10 | 21.25 | Firestore | 40.5 | 19.25 |
| 100 | 43.75 | Firestore | 54 | 10.25 |
| 1000 | 268.75 | Firestore | 189 | -79.75 |
| 10000 | 2518.75 | Firestore | 1539 | -979.75 |

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Firestore | Representative DynamoDB item size | 1024 | bytes |
| Firestore | Strongly consistent origin reads | 1 | 0 = eventual, 1 = strong |
| Firestore | Origin write-unit amplification | 1 | multiplier |
| Firestore | Additional document reads per write | 0 | reads/write |
| Firestore | Document writes per origin write | 1 | writes/write |
| Firestore | Firestore physical storage / source billed bytes | 1 | multiplier |

* Source traffic stays at 100 million strong 1 KiB read units and 10 million plain write units/month, with no origin index amplification. Firestore assumes equal billed storage, one document per item and blind writes; physical expansion and indexing require separate qualification.
* Reference list rates as of 2026-10-18: us-east-1 → 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.
* Firestore Standard edition, regional us-central1. One document read per origin point read; explicit reads/writes per write.
* Plain unconditioned PutItem can use the blind write path; read-modify-write, conditions and retries increase document reads.
* Equal physical storage is an illustrative assumption; tagged item envelopes, metadata and indexes can change billed bytes.
* Source usage is priced at reference rates; source lines are not actual invoice charges. Free or discounted usage still consumes target resources.
* AWS DynamoDB Standard on-demand pricing: [https://aws.amazon.com/dynamodb/pricing/](https://aws.amazon.com/dynamodb/pricing/)
* Firestore Standard regional pricing: [https://cloud.google.com/firestore/pricing/](https://cloud.google.com/firestore/pricing/)

Cost scope: Modeled monthly service usage and selected database allocation; adapter hosting and Tensor9 fees only when explicitly supplied.

Excluded costs and workload features:

* Free allowances, negotiated discounts, credits, tax and one-time migration charges.
* Charges not listed in the breakdown, including additional network transfer, backups and encryption/KMS.
* Application compute changes, operational labor and portfolio-wide sharing or deduplication of infrastructure.
* Queries, scans and index-entry reads, transactions, Streams, document deletes/TTL and unsupported item domains.

Rate snapshot: 2026-10-18. Model: `dynamodb-firestore` / `2026-10-18.4`. Curve: `retained-data`.

Sources: [AWS DynamoDB Standard on-demand pricing](https://aws.amazon.com/dynamodb/pricing/), [Firestore Standard regional pricing](https://cloud.google.com/firestore/pricing/).

## DynamoDB → Firestore

Origin API: `aws::1.0.0::dynamodb::control`. Target backend: `google::1.0.0::firestore`.

### DynamoDB · DynamoDB read units

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

![DynamoDB · DynamoDB read units: monthly service charges by DynamoDB read units. Exact values are in the following table.](/images/diagrams/service-cost/54c3642ea499f84580bef2b1ce771ee0b919a3bdf5d40273da339631fbc2c0b5-light.svg)

![DynamoDB · DynamoDB read units: monthly service charges by DynamoDB read units. Exact values are in the following table.](/images/diagrams/service-cost/9127b17e4867e83e0bea02fbc8f0625d500bcb58c7aa9f87693bfa194383f18a-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.

| DynamoDB read units (per second) | DynamoDB | Target scenario | Firestore | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | Firestore | 0 | 0 |
| 1 | 0.3285 | Firestore | 0.7884 | 0.4599 |
| 10 | 3.285 | Firestore | 7.884 | 4.599 |
| 100 | 32.85 | Firestore | 78.84 | 45.99 |
| 1000 | 328.5 | Firestore | 788.4 | 459.9 |
| 10000 | 3285 | Firestore | 7884 | 4599 |

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Firestore | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| Firestore | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| Firestore | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| Firestore | Origin list price · Control-plane calls | 0 | USD/requests |
| Firestore | Representative item size | 1024 | bytes |
| Firestore | Strongly consistent read fraction | 1 | fraction |
| Firestore | Origin write-unit amplification | 1 | multiplier |
| Firestore | Target reads per point read | 1 | operations |
| Firestore | Target writes per item write | 1 | operations |
| Firestore | Target list price · read | 0.0000003 | USD/read |
| Firestore | Target list price · write | 0.0000009 | USD/write |
| Firestore | Target price guess · provider operation | 0 | USD/provider operation |
| Firestore | Target list price · GiB-month | 0.15 | USD/GiB-month |
| Firestore | Target price guess · published GiB | 0 | USD/published GiB |
| Firestore | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Firestore | Target list price · network GiB | 0.12 | USD/network GiB |
| Firestore | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Firestore | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Firestore | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Firestore | Target price guess · resource-hour | 0 | USD/resource-hour |
| Firestore | Target price guess · resource-month | 0 | USD/resource-month |
| Firestore | Target price guess · input token | 0 | USD/input token |
| Firestore | Target price guess · output token | 0 | USD/output token |
| Firestore | Target monthly base charge | 0 | USD/month |
| Firestore | Approximate target service minimum | 0 | USD/month |
| Firestore | Minimum primary CPU | 2 | vCPU |
| Firestore | Minimum primary RAM | 8 | GiB |
| Firestore | Minimum primary disk | 100 | GiB |
| Firestore | Additional full-price standby copy | 0 | 0 or 1 |
| Firestore | Allocated share of provisioned cost | 1 | fraction |
| Firestore | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Firestore | Planning peak / mean work | 2 | multiplier |
| Firestore | Planning primary CPU utilization | 0.7 | fraction |
| Firestore | Resident state reserved in RAM | 0.1 | fraction |
| Firestore | Planning disk utilization | 0.8 | fraction |
| Firestore | Maintenance and log disk reserve | 20 | GiB |
| Firestore | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Firestore | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Firestore | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Firestore | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Firestore | Dependent object sink write price guess | 0.000005 | USD/write |

* Writes and storage remain independent. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
* Planning estimate · editable authored rates and sizing assumptions dated 2026-10-22; not verified provider prices. us-east-1 → 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 is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* 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.
* The control plane and table facet describe the same family workload; allocate shared capacity once, not once per catalog facet.
* No transactional, global-table, Streams or scan tariff is inferred from ordinary on-demand point units.
* Firestore Standard edition in us-central1 bills document reads, writes and deletes per operation and stored GiB-months. Index-entry reads (one read per batch of up to 1,000 entries) and query fan-out belong in workload translation. Deletes bill USD 0.01 per 100,000 (one ninth of a write), but this profile has no delete rate, so deletes the workload translates as writes are overstated. The daily free quota (50,000 reads, 20,000 writes, 20,000 deletes, 1 GiB) applies only to a project's default database and is not applied; the first 10 GiB/month of internet egress are free and are not applied.
* AWS Price List API, AmazonDynamoDB offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json)
* Amazon DynamoDB pricing: [https://aws.amazon.com/dynamodb/pricing/](https://aws.amazon.com/dynamodb/pricing/)
* Firestore pricing: [https://cloud.google.com/firestore/pricing](https://cloud.google.com/firestore/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.
* 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-4ac0e0ca0267692d3ee4ec3549bf7a6dc8998ba8` / `2026-10-22.planning.2`. Curve: `workload-1`.

Sources: [AWS Price List API, AmazonDynamoDB offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json), [Amazon DynamoDB pricing](https://aws.amazon.com/dynamodb/pricing/), [Firestore pricing](https://cloud.google.com/firestore/pricing).

### DynamoDB · DynamoDB write units

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

![DynamoDB · DynamoDB write units: monthly service charges by DynamoDB write units. Exact values are in the following table.](/images/diagrams/service-cost/4e276c91907f9328e696cd7b40eaa3c61abde6d95655ff991ed19972e5be4dfe-light.svg)

![DynamoDB · DynamoDB write units: monthly service charges by DynamoDB write units. Exact values are in the following table.](/images/diagrams/service-cost/7238982b34684eaa8615118e6232665f5a3b1e2c73e4f892371f0c806b03e181-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.

| DynamoDB write units (per second) | DynamoDB | Target scenario | Firestore | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | Firestore | 0 | 0 |
| 1 | 1.6425 | Firestore | 2.3652 | 0.7227 |
| 10 | 16.425 | Firestore | 23.652 | 7.227 |
| 100 | 164.25 | Firestore | 236.52 | 72.27 |
| 1000 | 1642.5 | Firestore | 2365.2 | 722.7 |
| 10000 | 16425 | Firestore | 23652 | 7227 |

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Firestore | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| Firestore | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| Firestore | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| Firestore | Origin list price · Control-plane calls | 0 | USD/requests |
| Firestore | Representative item size | 1024 | bytes |
| Firestore | Strongly consistent read fraction | 1 | fraction |
| Firestore | Origin write-unit amplification | 1 | multiplier |
| Firestore | Target reads per point read | 1 | operations |
| Firestore | Target writes per item write | 1 | operations |
| Firestore | Target list price · read | 0.0000003 | USD/read |
| Firestore | Target list price · write | 0.0000009 | USD/write |
| Firestore | Target price guess · provider operation | 0 | USD/provider operation |
| Firestore | Target list price · GiB-month | 0.15 | USD/GiB-month |
| Firestore | Target price guess · published GiB | 0 | USD/published GiB |
| Firestore | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Firestore | Target list price · network GiB | 0.12 | USD/network GiB |
| Firestore | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Firestore | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Firestore | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Firestore | Target price guess · resource-hour | 0 | USD/resource-hour |
| Firestore | Target price guess · resource-month | 0 | USD/resource-month |
| Firestore | Target price guess · input token | 0 | USD/input token |
| Firestore | Target price guess · output token | 0 | USD/output token |
| Firestore | Target monthly base charge | 0 | USD/month |
| Firestore | Approximate target service minimum | 0 | USD/month |
| Firestore | Minimum primary CPU | 2 | vCPU |
| Firestore | Minimum primary RAM | 8 | GiB |
| Firestore | Minimum primary disk | 100 | GiB |
| Firestore | Additional full-price standby copy | 0 | 0 or 1 |
| Firestore | Allocated share of provisioned cost | 1 | fraction |
| Firestore | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Firestore | Planning peak / mean work | 2 | multiplier |
| Firestore | Planning primary CPU utilization | 0.7 | fraction |
| Firestore | Resident state reserved in RAM | 0.1 | fraction |
| Firestore | Planning disk utilization | 0.8 | fraction |
| Firestore | Maintenance and log disk reserve | 20 | GiB |
| Firestore | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Firestore | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Firestore | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Firestore | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Firestore | Dependent object sink write price guess | 0.000005 | USD/write |

* Reads and storage remain independent. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
* Planning estimate · editable authored rates and sizing assumptions dated 2026-10-22; not verified provider prices. us-east-1 → 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 is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* 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.
* The control plane and table facet describe the same family workload; allocate shared capacity once, not once per catalog facet.
* No transactional, global-table, Streams or scan tariff is inferred from ordinary on-demand point units.
* Firestore Standard edition in us-central1 bills document reads, writes and deletes per operation and stored GiB-months. Index-entry reads (one read per batch of up to 1,000 entries) and query fan-out belong in workload translation. Deletes bill USD 0.01 per 100,000 (one ninth of a write), but this profile has no delete rate, so deletes the workload translates as writes are overstated. The daily free quota (50,000 reads, 20,000 writes, 20,000 deletes, 1 GiB) applies only to a project's default database and is not applied; the first 10 GiB/month of internet egress are free and are not applied.
* AWS Price List API, AmazonDynamoDB offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json)
* Amazon DynamoDB pricing: [https://aws.amazon.com/dynamodb/pricing/](https://aws.amazon.com/dynamodb/pricing/)
* Firestore pricing: [https://cloud.google.com/firestore/pricing](https://cloud.google.com/firestore/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.
* 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-4ac0e0ca0267692d3ee4ec3549bf7a6dc8998ba8` / `2026-10-22.planning.2`. Curve: `workload-2`.

Sources: [AWS Price List API, AmazonDynamoDB offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json), [Amazon DynamoDB pricing](https://aws.amazon.com/dynamodb/pricing/), [Firestore pricing](https://cloud.google.com/firestore/pricing).

### DynamoDB · Stored data

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

![DynamoDB · Stored data: monthly service charges by Stored data. Exact values are in the following table.](/images/diagrams/service-cost/7685988cd2da78798448f13bf5f4b3c92a40ef31e7a3e7f1b98d92fcc437751b-light.svg)

![DynamoDB · Stored data: monthly service charges by Stored data. Exact values are in the following table.](/images/diagrams/service-cost/5430d4cf65965d99ca2f73dff476d61d72b48c65bccf4d6f13d9b5d1c77981cc-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.

| Stored data (GiB-month) | DynamoDB | Target scenario | Firestore | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | Firestore | 0 | 0 |
| 10 | 2.5 | Firestore | 1.5 | -1 |
| 100 | 25 | Firestore | 15 | -10 |
| 1000 | 250 | Firestore | 150 | -100 |
| 10000 | 2500 | Firestore | 1500 | -1000 |
| 100000 | 25000 | Firestore | 15000 | -10000 |

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Firestore | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| Firestore | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| Firestore | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| Firestore | Origin list price · Control-plane calls | 0 | USD/requests |
| Firestore | Representative item size | 1024 | bytes |
| Firestore | Strongly consistent read fraction | 1 | fraction |
| Firestore | Origin write-unit amplification | 1 | multiplier |
| Firestore | Target reads per point read | 1 | operations |
| Firestore | Target writes per item write | 1 | operations |
| Firestore | Target list price · read | 0.0000003 | USD/read |
| Firestore | Target list price · write | 0.0000009 | USD/write |
| Firestore | Target price guess · provider operation | 0 | USD/provider operation |
| Firestore | Target list price · GiB-month | 0.15 | USD/GiB-month |
| Firestore | Target price guess · published GiB | 0 | USD/published GiB |
| Firestore | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Firestore | Target list price · network GiB | 0.12 | USD/network GiB |
| Firestore | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Firestore | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Firestore | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Firestore | Target price guess · resource-hour | 0 | USD/resource-hour |
| Firestore | Target price guess · resource-month | 0 | USD/resource-month |
| Firestore | Target price guess · input token | 0 | USD/input token |
| Firestore | Target price guess · output token | 0 | USD/output token |
| Firestore | Target monthly base charge | 0 | USD/month |
| Firestore | Approximate target service minimum | 0 | USD/month |
| Firestore | Minimum primary CPU | 2 | vCPU |
| Firestore | Minimum primary RAM | 8 | GiB |
| Firestore | Minimum primary disk | 100 | GiB |
| Firestore | Additional full-price standby copy | 0 | 0 or 1 |
| Firestore | Allocated share of provisioned cost | 1 | fraction |
| Firestore | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Firestore | Planning peak / mean work | 2 | multiplier |
| Firestore | Planning primary CPU utilization | 0.7 | fraction |
| Firestore | Resident state reserved in RAM | 0.1 | fraction |
| Firestore | Planning disk utilization | 0.8 | fraction |
| Firestore | Maintenance and log disk reserve | 20 | GiB |
| Firestore | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Firestore | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Firestore | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Firestore | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Firestore | 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. us-east-1 → 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 is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* 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.
* The control plane and table facet describe the same family workload; allocate shared capacity once, not once per catalog facet.
* No transactional, global-table, Streams or scan tariff is inferred from ordinary on-demand point units.
* Firestore Standard edition in us-central1 bills document reads, writes and deletes per operation and stored GiB-months. Index-entry reads (one read per batch of up to 1,000 entries) and query fan-out belong in workload translation. Deletes bill USD 0.01 per 100,000 (one ninth of a write), but this profile has no delete rate, so deletes the workload translates as writes are overstated. The daily free quota (50,000 reads, 20,000 writes, 20,000 deletes, 1 GiB) applies only to a project's default database and is not applied; the first 10 GiB/month of internet egress are free and are not applied.
* AWS Price List API, AmazonDynamoDB offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json)
* Amazon DynamoDB pricing: [https://aws.amazon.com/dynamodb/pricing/](https://aws.amazon.com/dynamodb/pricing/)
* Firestore pricing: [https://cloud.google.com/firestore/pricing](https://cloud.google.com/firestore/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.
* 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-4ac0e0ca0267692d3ee4ec3549bf7a6dc8998ba8` / `2026-10-22.planning.2`. Curve: `workload-3`.

Sources: [AWS Price List API, AmazonDynamoDB offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json), [Amazon DynamoDB pricing](https://aws.amazon.com/dynamodb/pricing/), [Firestore pricing](https://cloud.google.com/firestore/pricing).

## DynamoDB → OCI NoSQL Database

Origin API: `aws::1.0.0::dynamodb::control`. Target backend: `oci::1.0.0::nosql`.

**Native or deployment mapping.** The mapping provisions OCI NoSQL tables without exposing a DynamoDB management endpoint. There is no DynamoDB request-serving fabric on this path. Cost estimates describe the selected service resources; operation coverage remains separate.

### DynamoDB · DynamoDB read units

Estimated monthly service charges by DynamoDB read units. Adapter hosting and Tensor9 fees are excluded. Source: us-east-1; target: us-ashburn-1 (global list); currency: USD.

![DynamoDB · DynamoDB read units: monthly service charges by DynamoDB read units. Exact values are in the following table.](/images/diagrams/service-cost/f28690bbcfe133c53922e38fb688ee53a1e1a34682497c46c322a63028a2c1a5-light.svg)

![DynamoDB · DynamoDB read units: monthly service charges by DynamoDB read units. Exact values are in the following table.](/images/diagrams/service-cost/2d9b3bc9fb5a96a2f82477a9bd4541bddd7531105857ee068885b2dcd71c4a70-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.

| DynamoDB read units (per second) | DynamoDB | Target scenario | OCI NoSQL Database | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | OCI NoSQL Database | 0 | 0 |
| 1 | 0.3285 | OCI NoSQL Database | 0.156988836 | -0.171511164 |
| 10 | 3.285 | OCI NoSQL Database | 1.56988836 | -1.71511164 |
| 100 | 32.85 | OCI NoSQL Database | 15.6988836 | -17.1511164 |
| 1000 | 328.5 | OCI NoSQL Database | 156.988836 | -171.511164 |
| 10000 | 3285 | OCI NoSQL Database | 1569.88836 | -1715.11164 |

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| OCI NoSQL Database | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| OCI NoSQL Database | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| OCI NoSQL Database | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| OCI NoSQL Database | Origin list price · Control-plane calls | 0 | USD/requests |
| OCI NoSQL Database | Representative item size | 1024 | bytes |
| OCI NoSQL Database | Strongly consistent read fraction | 1 | fraction |
| OCI NoSQL Database | Origin write-unit amplification | 1 | multiplier |
| OCI NoSQL Database | Target reads per point read | 1 | operations |
| OCI NoSQL Database | Target writes per item write | 1 | operations |
| OCI NoSQL Database | Target list price · read | 0.000000059737 | USD/read |
| OCI NoSQL Database | Target list price · write | 0.000001170475 | USD/write |
| OCI NoSQL Database | Target price guess · provider operation | 0 | USD/provider operation |
| OCI NoSQL Database | Target list price · GiB-month | 0.066 | USD/GiB-month |
| OCI NoSQL Database | Target price guess · published GiB | 0 | USD/published GiB |
| OCI NoSQL Database | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| OCI NoSQL Database | Target list price · network GiB | 0 | USD/network GiB |
| OCI NoSQL Database | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| OCI NoSQL Database | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| OCI NoSQL Database | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| OCI NoSQL Database | Target price guess · resource-hour | 0 | USD/resource-hour |
| OCI NoSQL Database | Target price guess · resource-month | 0 | USD/resource-month |
| OCI NoSQL Database | Target price guess · input token | 0 | USD/input token |
| OCI NoSQL Database | Target price guess · output token | 0 | USD/output token |
| OCI NoSQL Database | Target monthly base charge | 0 | USD/month |
| OCI NoSQL Database | Approximate target service minimum | 0 | USD/month |
| OCI NoSQL Database | Minimum primary CPU | 2 | vCPU |
| OCI NoSQL Database | Minimum primary RAM | 8 | GiB |
| OCI NoSQL Database | Minimum primary disk | 100 | GiB |
| OCI NoSQL Database | Additional full-price standby copy | 0 | 0 or 1 |
| OCI NoSQL Database | Allocated share of provisioned cost | 1 | fraction |
| OCI NoSQL Database | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| OCI NoSQL Database | Planning peak / mean work | 2 | multiplier |
| OCI NoSQL Database | Planning primary CPU utilization | 0.7 | fraction |
| OCI NoSQL Database | Resident state reserved in RAM | 0.1 | fraction |
| OCI NoSQL Database | Planning disk utilization | 0.8 | fraction |
| OCI NoSQL Database | Maintenance and log disk reserve | 20 | GiB |
| OCI NoSQL Database | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| OCI NoSQL Database | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| OCI NoSQL Database | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| OCI NoSQL Database | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| OCI NoSQL Database | Dependent object sink write price guess | 0.000005 | USD/write |

* Writes and storage remain independent. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
* Planning estimate · editable authored rates and sizing assumptions dated 2026-10-22; not verified provider prices. us-east-1 → us-ashburn-1 (global list), 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 is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* Native/deployment comparison scope: The mapping provisions OCI NoSQL tables without exposing a DynamoDB management endpoint. There is no DynamoDB request-serving fabric on this path.
* 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.
* The control plane and table facet describe the same family workload; allocate shared capacity once, not once per catalog facet.
* No transactional, global-table, Streams or scan tariff is inferred from ordinary on-demand point units.
* Oracle NoSQL Database Cloud on-demand capacity bills consumed 1 KB read and write units and stored GB. Absolute-consistency reads cost two read units; larger records cost one unit per KB. Provisioned capacity (USD 0.0064 per read unit-month and 0.1254 per write unit-month, parts B89738 and B89737) and the Always Free tables are not selected.
* AWS Price List API, AmazonDynamoDB offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json)
* Amazon DynamoDB pricing: [https://aws.amazon.com/dynamodb/pricing/](https://aws.amazon.com/dynamodb/pricing/)
* OCI price list API: [https://apexapps.oracle.com/pls/apex/cetools/api/v1/products/](https://apexapps.oracle.com/pls/apex/cetools/api/v1/products/)

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.
* 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-a45d0e6d8b183b039aefa956c723cea5c9269d3d` / `2026-10-22.planning.2`. Curve: `workload-1`.

Sources: [AWS Price List API, AmazonDynamoDB offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json), [Amazon DynamoDB pricing](https://aws.amazon.com/dynamodb/pricing/), [OCI price list API](https://apexapps.oracle.com/pls/apex/cetools/api/v1/products/).

### DynamoDB · DynamoDB write units

Estimated monthly service charges by DynamoDB write units. Adapter hosting and Tensor9 fees are excluded. Source: us-east-1; target: us-ashburn-1 (global list); currency: USD.

![DynamoDB · DynamoDB write units: monthly service charges by DynamoDB write units. Exact values are in the following table.](/images/diagrams/service-cost/bba2f6b62d9c383c7e2ecfcb7011b4cff1382104d3e9741cd3193713690a36b7-light.svg)

![DynamoDB · DynamoDB write units: monthly service charges by DynamoDB write units. Exact values are in the following table.](/images/diagrams/service-cost/b78c742ebca02f1454683d345996a3c8c3c39794edca90e43f67495b5e0df11b-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.

| DynamoDB write units (per second) | DynamoDB | Target scenario | OCI NoSQL Database | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | OCI NoSQL Database | 0 | 0 |
| 1 | 1.6425 | OCI NoSQL Database | 3.0760083 | 1.4335083 |
| 10 | 16.425 | OCI NoSQL Database | 30.760083 | 14.335083 |
| 100 | 164.25 | OCI NoSQL Database | 307.60083 | 143.35083 |
| 1000 | 1642.5 | OCI NoSQL Database | 3076.0083 | 1433.5083 |
| 10000 | 16425 | OCI NoSQL Database | 30760.083 | 14335.083 |

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| OCI NoSQL Database | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| OCI NoSQL Database | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| OCI NoSQL Database | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| OCI NoSQL Database | Origin list price · Control-plane calls | 0 | USD/requests |
| OCI NoSQL Database | Representative item size | 1024 | bytes |
| OCI NoSQL Database | Strongly consistent read fraction | 1 | fraction |
| OCI NoSQL Database | Origin write-unit amplification | 1 | multiplier |
| OCI NoSQL Database | Target reads per point read | 1 | operations |
| OCI NoSQL Database | Target writes per item write | 1 | operations |
| OCI NoSQL Database | Target list price · read | 0.000000059737 | USD/read |
| OCI NoSQL Database | Target list price · write | 0.000001170475 | USD/write |
| OCI NoSQL Database | Target price guess · provider operation | 0 | USD/provider operation |
| OCI NoSQL Database | Target list price · GiB-month | 0.066 | USD/GiB-month |
| OCI NoSQL Database | Target price guess · published GiB | 0 | USD/published GiB |
| OCI NoSQL Database | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| OCI NoSQL Database | Target list price · network GiB | 0 | USD/network GiB |
| OCI NoSQL Database | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| OCI NoSQL Database | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| OCI NoSQL Database | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| OCI NoSQL Database | Target price guess · resource-hour | 0 | USD/resource-hour |
| OCI NoSQL Database | Target price guess · resource-month | 0 | USD/resource-month |
| OCI NoSQL Database | Target price guess · input token | 0 | USD/input token |
| OCI NoSQL Database | Target price guess · output token | 0 | USD/output token |
| OCI NoSQL Database | Target monthly base charge | 0 | USD/month |
| OCI NoSQL Database | Approximate target service minimum | 0 | USD/month |
| OCI NoSQL Database | Minimum primary CPU | 2 | vCPU |
| OCI NoSQL Database | Minimum primary RAM | 8 | GiB |
| OCI NoSQL Database | Minimum primary disk | 100 | GiB |
| OCI NoSQL Database | Additional full-price standby copy | 0 | 0 or 1 |
| OCI NoSQL Database | Allocated share of provisioned cost | 1 | fraction |
| OCI NoSQL Database | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| OCI NoSQL Database | Planning peak / mean work | 2 | multiplier |
| OCI NoSQL Database | Planning primary CPU utilization | 0.7 | fraction |
| OCI NoSQL Database | Resident state reserved in RAM | 0.1 | fraction |
| OCI NoSQL Database | Planning disk utilization | 0.8 | fraction |
| OCI NoSQL Database | Maintenance and log disk reserve | 20 | GiB |
| OCI NoSQL Database | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| OCI NoSQL Database | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| OCI NoSQL Database | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| OCI NoSQL Database | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| OCI NoSQL Database | Dependent object sink write price guess | 0.000005 | USD/write |

* Reads and storage remain independent. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
* Planning estimate · editable authored rates and sizing assumptions dated 2026-10-22; not verified provider prices. us-east-1 → us-ashburn-1 (global list), 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 is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* Native/deployment comparison scope: The mapping provisions OCI NoSQL tables without exposing a DynamoDB management endpoint. There is no DynamoDB request-serving fabric on this path.
* 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.
* The control plane and table facet describe the same family workload; allocate shared capacity once, not once per catalog facet.
* No transactional, global-table, Streams or scan tariff is inferred from ordinary on-demand point units.
* Oracle NoSQL Database Cloud on-demand capacity bills consumed 1 KB read and write units and stored GB. Absolute-consistency reads cost two read units; larger records cost one unit per KB. Provisioned capacity (USD 0.0064 per read unit-month and 0.1254 per write unit-month, parts B89738 and B89737) and the Always Free tables are not selected.
* AWS Price List API, AmazonDynamoDB offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json)
* Amazon DynamoDB pricing: [https://aws.amazon.com/dynamodb/pricing/](https://aws.amazon.com/dynamodb/pricing/)
* OCI price list API: [https://apexapps.oracle.com/pls/apex/cetools/api/v1/products/](https://apexapps.oracle.com/pls/apex/cetools/api/v1/products/)

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.
* 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-a45d0e6d8b183b039aefa956c723cea5c9269d3d` / `2026-10-22.planning.2`. Curve: `workload-2`.

Sources: [AWS Price List API, AmazonDynamoDB offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json), [Amazon DynamoDB pricing](https://aws.amazon.com/dynamodb/pricing/), [OCI price list API](https://apexapps.oracle.com/pls/apex/cetools/api/v1/products/).

### DynamoDB · Stored data

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

![DynamoDB · Stored data: monthly service charges by Stored data. Exact values are in the following table.](/images/diagrams/service-cost/1046d98d64dab9db344c50a2bf5c28a5ed2e492b454e7af339424776303110f5-light.svg)

![DynamoDB · Stored data: monthly service charges by Stored data. Exact values are in the following table.](/images/diagrams/service-cost/89c1a57e4eb2b199cdf0d89a20e0f3807893db09ca6c6fff7cc0c6c64c717e64-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.

| Stored data (GiB-month) | DynamoDB | Target scenario | OCI NoSQL Database | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | OCI NoSQL Database | 0 | 0 |
| 10 | 2.5 | OCI NoSQL Database | 0.66 | -1.84 |
| 100 | 25 | OCI NoSQL Database | 6.6 | -18.4 |
| 1000 | 250 | OCI NoSQL Database | 66 | -184 |
| 10000 | 2500 | OCI NoSQL Database | 660 | -1840 |
| 100000 | 25000 | OCI NoSQL Database | 6600 | -18400 |

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| OCI NoSQL Database | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| OCI NoSQL Database | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| OCI NoSQL Database | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| OCI NoSQL Database | Origin list price · Control-plane calls | 0 | USD/requests |
| OCI NoSQL Database | Representative item size | 1024 | bytes |
| OCI NoSQL Database | Strongly consistent read fraction | 1 | fraction |
| OCI NoSQL Database | Origin write-unit amplification | 1 | multiplier |
| OCI NoSQL Database | Target reads per point read | 1 | operations |
| OCI NoSQL Database | Target writes per item write | 1 | operations |
| OCI NoSQL Database | Target list price · read | 0.000000059737 | USD/read |
| OCI NoSQL Database | Target list price · write | 0.000001170475 | USD/write |
| OCI NoSQL Database | Target price guess · provider operation | 0 | USD/provider operation |
| OCI NoSQL Database | Target list price · GiB-month | 0.066 | USD/GiB-month |
| OCI NoSQL Database | Target price guess · published GiB | 0 | USD/published GiB |
| OCI NoSQL Database | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| OCI NoSQL Database | Target list price · network GiB | 0 | USD/network GiB |
| OCI NoSQL Database | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| OCI NoSQL Database | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| OCI NoSQL Database | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| OCI NoSQL Database | Target price guess · resource-hour | 0 | USD/resource-hour |
| OCI NoSQL Database | Target price guess · resource-month | 0 | USD/resource-month |
| OCI NoSQL Database | Target price guess · input token | 0 | USD/input token |
| OCI NoSQL Database | Target price guess · output token | 0 | USD/output token |
| OCI NoSQL Database | Target monthly base charge | 0 | USD/month |
| OCI NoSQL Database | Approximate target service minimum | 0 | USD/month |
| OCI NoSQL Database | Minimum primary CPU | 2 | vCPU |
| OCI NoSQL Database | Minimum primary RAM | 8 | GiB |
| OCI NoSQL Database | Minimum primary disk | 100 | GiB |
| OCI NoSQL Database | Additional full-price standby copy | 0 | 0 or 1 |
| OCI NoSQL Database | Allocated share of provisioned cost | 1 | fraction |
| OCI NoSQL Database | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| OCI NoSQL Database | Planning peak / mean work | 2 | multiplier |
| OCI NoSQL Database | Planning primary CPU utilization | 0.7 | fraction |
| OCI NoSQL Database | Resident state reserved in RAM | 0.1 | fraction |
| OCI NoSQL Database | Planning disk utilization | 0.8 | fraction |
| OCI NoSQL Database | Maintenance and log disk reserve | 20 | GiB |
| OCI NoSQL Database | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| OCI NoSQL Database | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| OCI NoSQL Database | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| OCI NoSQL Database | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| OCI NoSQL Database | 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. us-east-1 → us-ashburn-1 (global list), 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 is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* Native/deployment comparison scope: The mapping provisions OCI NoSQL tables without exposing a DynamoDB management endpoint. There is no DynamoDB request-serving fabric on this path.
* 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.
* The control plane and table facet describe the same family workload; allocate shared capacity once, not once per catalog facet.
* No transactional, global-table, Streams or scan tariff is inferred from ordinary on-demand point units.
* Oracle NoSQL Database Cloud on-demand capacity bills consumed 1 KB read and write units and stored GB. Absolute-consistency reads cost two read units; larger records cost one unit per KB. Provisioned capacity (USD 0.0064 per read unit-month and 0.1254 per write unit-month, parts B89738 and B89737) and the Always Free tables are not selected.
* AWS Price List API, AmazonDynamoDB offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json)
* Amazon DynamoDB pricing: [https://aws.amazon.com/dynamodb/pricing/](https://aws.amazon.com/dynamodb/pricing/)
* OCI price list API: [https://apexapps.oracle.com/pls/apex/cetools/api/v1/products/](https://apexapps.oracle.com/pls/apex/cetools/api/v1/products/)

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.
* 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-a45d0e6d8b183b039aefa956c723cea5c9269d3d` / `2026-10-22.planning.2`. Curve: `workload-3`.

Sources: [AWS Price List API, AmazonDynamoDB offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json), [Amazon DynamoDB pricing](https://aws.amazon.com/dynamodb/pricing/), [OCI price list API](https://apexapps.oracle.com/pls/apex/cetools/api/v1/products/).

## DynamoDB → OCI NoSQL Database

Origin API: `aws::1.0.0::dynamodb::table`. Target backend: `oci::1.0.0::nosql`.

**Native or deployment mapping.** The application uses the OCI NoSQL API on this mapping. It does not provide a DynamoDB request translator, so DynamoDB fabric latency does not apply. Cost estimates describe the selected service resources; operation coverage remains separate.

### DynamoDB · DynamoDB read units

Estimated monthly service charges by DynamoDB read units. Adapter hosting and Tensor9 fees are excluded. Source: us-east-1; target: us-ashburn-1 (global list); currency: USD.

![DynamoDB · DynamoDB read units: monthly service charges by DynamoDB read units. Exact values are in the following table.](/images/diagrams/service-cost/f28690bbcfe133c53922e38fb688ee53a1e1a34682497c46c322a63028a2c1a5-light.svg)

![DynamoDB · DynamoDB read units: monthly service charges by DynamoDB read units. Exact values are in the following table.](/images/diagrams/service-cost/2d9b3bc9fb5a96a2f82477a9bd4541bddd7531105857ee068885b2dcd71c4a70-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.

| DynamoDB read units (per second) | DynamoDB | Target scenario | OCI NoSQL Database | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | OCI NoSQL Database | 0 | 0 |
| 1 | 0.3285 | OCI NoSQL Database | 0.156988836 | -0.171511164 |
| 10 | 3.285 | OCI NoSQL Database | 1.56988836 | -1.71511164 |
| 100 | 32.85 | OCI NoSQL Database | 15.6988836 | -17.1511164 |
| 1000 | 328.5 | OCI NoSQL Database | 156.988836 | -171.511164 |
| 10000 | 3285 | OCI NoSQL Database | 1569.88836 | -1715.11164 |

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| OCI NoSQL Database | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| OCI NoSQL Database | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| OCI NoSQL Database | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| OCI NoSQL Database | Origin list price · Control-plane calls | 0 | USD/requests |
| OCI NoSQL Database | Representative item size | 1024 | bytes |
| OCI NoSQL Database | Strongly consistent read fraction | 1 | fraction |
| OCI NoSQL Database | Origin write-unit amplification | 1 | multiplier |
| OCI NoSQL Database | Target reads per point read | 1 | operations |
| OCI NoSQL Database | Target writes per item write | 1 | operations |
| OCI NoSQL Database | Target list price · read | 0.000000059737 | USD/read |
| OCI NoSQL Database | Target list price · write | 0.000001170475 | USD/write |
| OCI NoSQL Database | Target price guess · provider operation | 0 | USD/provider operation |
| OCI NoSQL Database | Target list price · GiB-month | 0.066 | USD/GiB-month |
| OCI NoSQL Database | Target price guess · published GiB | 0 | USD/published GiB |
| OCI NoSQL Database | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| OCI NoSQL Database | Target list price · network GiB | 0 | USD/network GiB |
| OCI NoSQL Database | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| OCI NoSQL Database | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| OCI NoSQL Database | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| OCI NoSQL Database | Target price guess · resource-hour | 0 | USD/resource-hour |
| OCI NoSQL Database | Target price guess · resource-month | 0 | USD/resource-month |
| OCI NoSQL Database | Target price guess · input token | 0 | USD/input token |
| OCI NoSQL Database | Target price guess · output token | 0 | USD/output token |
| OCI NoSQL Database | Target monthly base charge | 0 | USD/month |
| OCI NoSQL Database | Approximate target service minimum | 0 | USD/month |
| OCI NoSQL Database | Minimum primary CPU | 2 | vCPU |
| OCI NoSQL Database | Minimum primary RAM | 8 | GiB |
| OCI NoSQL Database | Minimum primary disk | 100 | GiB |
| OCI NoSQL Database | Additional full-price standby copy | 0 | 0 or 1 |
| OCI NoSQL Database | Allocated share of provisioned cost | 1 | fraction |
| OCI NoSQL Database | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| OCI NoSQL Database | Planning peak / mean work | 2 | multiplier |
| OCI NoSQL Database | Planning primary CPU utilization | 0.7 | fraction |
| OCI NoSQL Database | Resident state reserved in RAM | 0.1 | fraction |
| OCI NoSQL Database | Planning disk utilization | 0.8 | fraction |
| OCI NoSQL Database | Maintenance and log disk reserve | 20 | GiB |
| OCI NoSQL Database | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| OCI NoSQL Database | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| OCI NoSQL Database | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| OCI NoSQL Database | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| OCI NoSQL Database | Dependent object sink write price guess | 0.000005 | USD/write |

* Writes and storage remain independent. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
* Planning estimate · editable authored rates and sizing assumptions dated 2026-10-22; not verified provider prices. us-east-1 → us-ashburn-1 (global list), 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 is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* Native/deployment comparison scope: The application uses the OCI NoSQL API on this mapping. It does not provide a DynamoDB request translator, so DynamoDB fabric latency does not apply.
* 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.
* The control plane and table facet describe the same family workload; allocate shared capacity once, not once per catalog facet.
* No transactional, global-table, Streams or scan tariff is inferred from ordinary on-demand point units.
* Oracle NoSQL Database Cloud on-demand capacity bills consumed 1 KB read and write units and stored GB. Absolute-consistency reads cost two read units; larger records cost one unit per KB. Provisioned capacity (USD 0.0064 per read unit-month and 0.1254 per write unit-month, parts B89738 and B89737) and the Always Free tables are not selected.
* AWS Price List API, AmazonDynamoDB offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json)
* Amazon DynamoDB pricing: [https://aws.amazon.com/dynamodb/pricing/](https://aws.amazon.com/dynamodb/pricing/)
* OCI price list API: [https://apexapps.oracle.com/pls/apex/cetools/api/v1/products/](https://apexapps.oracle.com/pls/apex/cetools/api/v1/products/)

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.
* 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-d4b2a3538a1c61e563246f36c48dc1568328d822` / `2026-10-22.planning.2`. Curve: `workload-1`.

Sources: [AWS Price List API, AmazonDynamoDB offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json), [Amazon DynamoDB pricing](https://aws.amazon.com/dynamodb/pricing/), [OCI price list API](https://apexapps.oracle.com/pls/apex/cetools/api/v1/products/).

### DynamoDB · DynamoDB write units

Estimated monthly service charges by DynamoDB write units. Adapter hosting and Tensor9 fees are excluded. Source: us-east-1; target: us-ashburn-1 (global list); currency: USD.

![DynamoDB · DynamoDB write units: monthly service charges by DynamoDB write units. Exact values are in the following table.](/images/diagrams/service-cost/bba2f6b62d9c383c7e2ecfcb7011b4cff1382104d3e9741cd3193713690a36b7-light.svg)

![DynamoDB · DynamoDB write units: monthly service charges by DynamoDB write units. Exact values are in the following table.](/images/diagrams/service-cost/b78c742ebca02f1454683d345996a3c8c3c39794edca90e43f67495b5e0df11b-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.

| DynamoDB write units (per second) | DynamoDB | Target scenario | OCI NoSQL Database | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | OCI NoSQL Database | 0 | 0 |
| 1 | 1.6425 | OCI NoSQL Database | 3.0760083 | 1.4335083 |
| 10 | 16.425 | OCI NoSQL Database | 30.760083 | 14.335083 |
| 100 | 164.25 | OCI NoSQL Database | 307.60083 | 143.35083 |
| 1000 | 1642.5 | OCI NoSQL Database | 3076.0083 | 1433.5083 |
| 10000 | 16425 | OCI NoSQL Database | 30760.083 | 14335.083 |

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| OCI NoSQL Database | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| OCI NoSQL Database | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| OCI NoSQL Database | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| OCI NoSQL Database | Origin list price · Control-plane calls | 0 | USD/requests |
| OCI NoSQL Database | Representative item size | 1024 | bytes |
| OCI NoSQL Database | Strongly consistent read fraction | 1 | fraction |
| OCI NoSQL Database | Origin write-unit amplification | 1 | multiplier |
| OCI NoSQL Database | Target reads per point read | 1 | operations |
| OCI NoSQL Database | Target writes per item write | 1 | operations |
| OCI NoSQL Database | Target list price · read | 0.000000059737 | USD/read |
| OCI NoSQL Database | Target list price · write | 0.000001170475 | USD/write |
| OCI NoSQL Database | Target price guess · provider operation | 0 | USD/provider operation |
| OCI NoSQL Database | Target list price · GiB-month | 0.066 | USD/GiB-month |
| OCI NoSQL Database | Target price guess · published GiB | 0 | USD/published GiB |
| OCI NoSQL Database | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| OCI NoSQL Database | Target list price · network GiB | 0 | USD/network GiB |
| OCI NoSQL Database | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| OCI NoSQL Database | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| OCI NoSQL Database | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| OCI NoSQL Database | Target price guess · resource-hour | 0 | USD/resource-hour |
| OCI NoSQL Database | Target price guess · resource-month | 0 | USD/resource-month |
| OCI NoSQL Database | Target price guess · input token | 0 | USD/input token |
| OCI NoSQL Database | Target price guess · output token | 0 | USD/output token |
| OCI NoSQL Database | Target monthly base charge | 0 | USD/month |
| OCI NoSQL Database | Approximate target service minimum | 0 | USD/month |
| OCI NoSQL Database | Minimum primary CPU | 2 | vCPU |
| OCI NoSQL Database | Minimum primary RAM | 8 | GiB |
| OCI NoSQL Database | Minimum primary disk | 100 | GiB |
| OCI NoSQL Database | Additional full-price standby copy | 0 | 0 or 1 |
| OCI NoSQL Database | Allocated share of provisioned cost | 1 | fraction |
| OCI NoSQL Database | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| OCI NoSQL Database | Planning peak / mean work | 2 | multiplier |
| OCI NoSQL Database | Planning primary CPU utilization | 0.7 | fraction |
| OCI NoSQL Database | Resident state reserved in RAM | 0.1 | fraction |
| OCI NoSQL Database | Planning disk utilization | 0.8 | fraction |
| OCI NoSQL Database | Maintenance and log disk reserve | 20 | GiB |
| OCI NoSQL Database | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| OCI NoSQL Database | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| OCI NoSQL Database | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| OCI NoSQL Database | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| OCI NoSQL Database | Dependent object sink write price guess | 0.000005 | USD/write |

* Reads and storage remain independent. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
* Planning estimate · editable authored rates and sizing assumptions dated 2026-10-22; not verified provider prices. us-east-1 → us-ashburn-1 (global list), 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 is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* Native/deployment comparison scope: The application uses the OCI NoSQL API on this mapping. It does not provide a DynamoDB request translator, so DynamoDB fabric latency does not apply.
* 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.
* The control plane and table facet describe the same family workload; allocate shared capacity once, not once per catalog facet.
* No transactional, global-table, Streams or scan tariff is inferred from ordinary on-demand point units.
* Oracle NoSQL Database Cloud on-demand capacity bills consumed 1 KB read and write units and stored GB. Absolute-consistency reads cost two read units; larger records cost one unit per KB. Provisioned capacity (USD 0.0064 per read unit-month and 0.1254 per write unit-month, parts B89738 and B89737) and the Always Free tables are not selected.
* AWS Price List API, AmazonDynamoDB offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json)
* Amazon DynamoDB pricing: [https://aws.amazon.com/dynamodb/pricing/](https://aws.amazon.com/dynamodb/pricing/)
* OCI price list API: [https://apexapps.oracle.com/pls/apex/cetools/api/v1/products/](https://apexapps.oracle.com/pls/apex/cetools/api/v1/products/)

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.
* 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-d4b2a3538a1c61e563246f36c48dc1568328d822` / `2026-10-22.planning.2`. Curve: `workload-2`.

Sources: [AWS Price List API, AmazonDynamoDB offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json), [Amazon DynamoDB pricing](https://aws.amazon.com/dynamodb/pricing/), [OCI price list API](https://apexapps.oracle.com/pls/apex/cetools/api/v1/products/).

### DynamoDB · Stored data

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

![DynamoDB · Stored data: monthly service charges by Stored data. Exact values are in the following table.](/images/diagrams/service-cost/1046d98d64dab9db344c50a2bf5c28a5ed2e492b454e7af339424776303110f5-light.svg)

![DynamoDB · Stored data: monthly service charges by Stored data. Exact values are in the following table.](/images/diagrams/service-cost/89c1a57e4eb2b199cdf0d89a20e0f3807893db09ca6c6fff7cc0c6c64c717e64-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.

| Stored data (GiB-month) | DynamoDB | Target scenario | OCI NoSQL Database | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | OCI NoSQL Database | 0 | 0 |
| 10 | 2.5 | OCI NoSQL Database | 0.66 | -1.84 |
| 100 | 25 | OCI NoSQL Database | 6.6 | -18.4 |
| 1000 | 250 | OCI NoSQL Database | 66 | -184 |
| 10000 | 2500 | OCI NoSQL Database | 660 | -1840 |
| 100000 | 25000 | OCI NoSQL Database | 6600 | -18400 |

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| OCI NoSQL Database | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| OCI NoSQL Database | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| OCI NoSQL Database | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| OCI NoSQL Database | Origin list price · Control-plane calls | 0 | USD/requests |
| OCI NoSQL Database | Representative item size | 1024 | bytes |
| OCI NoSQL Database | Strongly consistent read fraction | 1 | fraction |
| OCI NoSQL Database | Origin write-unit amplification | 1 | multiplier |
| OCI NoSQL Database | Target reads per point read | 1 | operations |
| OCI NoSQL Database | Target writes per item write | 1 | operations |
| OCI NoSQL Database | Target list price · read | 0.000000059737 | USD/read |
| OCI NoSQL Database | Target list price · write | 0.000001170475 | USD/write |
| OCI NoSQL Database | Target price guess · provider operation | 0 | USD/provider operation |
| OCI NoSQL Database | Target list price · GiB-month | 0.066 | USD/GiB-month |
| OCI NoSQL Database | Target price guess · published GiB | 0 | USD/published GiB |
| OCI NoSQL Database | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| OCI NoSQL Database | Target list price · network GiB | 0 | USD/network GiB |
| OCI NoSQL Database | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| OCI NoSQL Database | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| OCI NoSQL Database | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| OCI NoSQL Database | Target price guess · resource-hour | 0 | USD/resource-hour |
| OCI NoSQL Database | Target price guess · resource-month | 0 | USD/resource-month |
| OCI NoSQL Database | Target price guess · input token | 0 | USD/input token |
| OCI NoSQL Database | Target price guess · output token | 0 | USD/output token |
| OCI NoSQL Database | Target monthly base charge | 0 | USD/month |
| OCI NoSQL Database | Approximate target service minimum | 0 | USD/month |
| OCI NoSQL Database | Minimum primary CPU | 2 | vCPU |
| OCI NoSQL Database | Minimum primary RAM | 8 | GiB |
| OCI NoSQL Database | Minimum primary disk | 100 | GiB |
| OCI NoSQL Database | Additional full-price standby copy | 0 | 0 or 1 |
| OCI NoSQL Database | Allocated share of provisioned cost | 1 | fraction |
| OCI NoSQL Database | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| OCI NoSQL Database | Planning peak / mean work | 2 | multiplier |
| OCI NoSQL Database | Planning primary CPU utilization | 0.7 | fraction |
| OCI NoSQL Database | Resident state reserved in RAM | 0.1 | fraction |
| OCI NoSQL Database | Planning disk utilization | 0.8 | fraction |
| OCI NoSQL Database | Maintenance and log disk reserve | 20 | GiB |
| OCI NoSQL Database | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| OCI NoSQL Database | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| OCI NoSQL Database | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| OCI NoSQL Database | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| OCI NoSQL Database | 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. us-east-1 → us-ashburn-1 (global list), 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 is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* Native/deployment comparison scope: The application uses the OCI NoSQL API on this mapping. It does not provide a DynamoDB request translator, so DynamoDB fabric latency does not apply.
* 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.
* The control plane and table facet describe the same family workload; allocate shared capacity once, not once per catalog facet.
* No transactional, global-table, Streams or scan tariff is inferred from ordinary on-demand point units.
* Oracle NoSQL Database Cloud on-demand capacity bills consumed 1 KB read and write units and stored GB. Absolute-consistency reads cost two read units; larger records cost one unit per KB. Provisioned capacity (USD 0.0064 per read unit-month and 0.1254 per write unit-month, parts B89738 and B89737) and the Always Free tables are not selected.
* AWS Price List API, AmazonDynamoDB offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json)
* Amazon DynamoDB pricing: [https://aws.amazon.com/dynamodb/pricing/](https://aws.amazon.com/dynamodb/pricing/)
* OCI price list API: [https://apexapps.oracle.com/pls/apex/cetools/api/v1/products/](https://apexapps.oracle.com/pls/apex/cetools/api/v1/products/)

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.
* 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-d4b2a3538a1c61e563246f36c48dc1568328d822` / `2026-10-22.planning.2`. Curve: `workload-3`.

Sources: [AWS Price List API, AmazonDynamoDB offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json), [Amazon DynamoDB pricing](https://aws.amazon.com/dynamodb/pricing/), [OCI price list API](https://apexapps.oracle.com/pls/apex/cetools/api/v1/products/).

## DynamoDB → PostgreSQL

Origin API: `aws::1.0.0::dynamodb::control`. Target backend: `postgres::1.0.0::database`.

### DynamoDB · DynamoDB read units

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

![DynamoDB · DynamoDB read units: monthly service charges by DynamoDB read units. Exact values are in the following table.](/images/diagrams/service-cost/8382fef517eda76f19e611cff06433dc02cd8c7f577d733a69e8c0b16b31e60a-light.svg)

![DynamoDB · DynamoDB read units: monthly service charges by DynamoDB read units. Exact values are in the following table.](/images/diagrams/service-cost/e74af201710e1424ddeb5ddaa5965e321fb9ab1f7fdf2d26491b5031e8fdbb1c-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.

| DynamoDB read units (per second) | DynamoDB | Target scenario | PostgreSQL | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | PostgreSQL (one copy) | 80.89614 | 80.89614 |
| 0 | 0 | PostgreSQL (two copies) | 161.79228 | 161.79228 |
| 1 | 0.3285 | PostgreSQL (one copy) | 80.89614 | 80.56764 |
| 1 | 0.3285 | PostgreSQL (two copies) | 161.79228 | 161.46378 |
| 10 | 3.285 | PostgreSQL (one copy) | 80.89614 | 77.61114 |
| 10 | 3.285 | PostgreSQL (two copies) | 161.79228 | 158.50728 |
| 100 | 32.85 | PostgreSQL (one copy) | 80.89614 | 48.04614 |
| 100 | 32.85 | PostgreSQL (two copies) | 161.79228 | 128.94228 |
| 1000 | 328.5 | PostgreSQL (one copy) | 80.89614 | -247.60386 |
| 1000 | 328.5 | PostgreSQL (two copies) | 161.79228 | -166.70772 |
| 10000 | 3285 | PostgreSQL (one copy) | 1144.33824 | -2140.66176 |
| 10000 | 3285 | PostgreSQL (two copies) | 2288.67648 | -996.32352 |

**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 / PostgreSQL (one copy) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 0 per second / PostgreSQL (two copies) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1 per second / PostgreSQL (one copy) | PlanningAssumption | 1 / 2 | 0.001904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1 per second / PostgreSQL (two copies) | PlanningAssumption | 1 / 2 | 0.001904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10 per second / PostgreSQL (one copy) | PlanningAssumption | 10 / 20 | 0.01904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10 per second / PostgreSQL (two copies) | PlanningAssumption | 10 / 20 | 0.01904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 100 per second / PostgreSQL (one copy) | PlanningAssumption | 100 / 200 | 0.1904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 100 per second / PostgreSQL (two copies) | PlanningAssumption | 100 / 200 | 0.1904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1000 per second / PostgreSQL (one copy) | PlanningAssumption | 1000 / 2000 | 1.904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1000 per second / PostgreSQL (two copies) | PlanningAssumption | 1000 / 2000 | 1.904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10000 per second / PostgreSQL (one copy) | PlanningAssumption | 10000 / 20000 | 19.04761904761904761904761904761905 | 32 | 128 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10000 per second / PostgreSQL (two copies) | PlanningAssumption | 10000 / 20000 | 19.04761904761904761904761904761905 | 32 | 128 | 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 operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| PostgreSQL (one copy) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| PostgreSQL (one copy) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| PostgreSQL (one copy) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| PostgreSQL (one copy) | Origin list price · Control-plane calls | 0 | USD/requests |
| PostgreSQL (one copy) | Representative item size | 1024 | bytes |
| PostgreSQL (one copy) | Strongly consistent read fraction | 1 | fraction |
| PostgreSQL (one copy) | Origin write-unit amplification | 1 | multiplier |
| PostgreSQL (one copy) | Target reads per point read | 1 | operations |
| PostgreSQL (one copy) | Target writes per item write | 1 | operations |
| PostgreSQL (one copy) | Target price guess · read | 0 | USD/read |
| PostgreSQL (one copy) | Target price guess · write | 0 | USD/write |
| PostgreSQL (one copy) | Target price guess · provider operation | 0 | USD/provider operation |
| PostgreSQL (one copy) | Target list price · GiB-month | 0.1 | USD/GiB-month |
| PostgreSQL (one copy) | Target price guess · published GiB | 0 | USD/published GiB |
| PostgreSQL (one copy) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| PostgreSQL (one copy) | Target list price · network GiB | 0.12 | USD/network GiB |
| PostgreSQL (one copy) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| PostgreSQL (one copy) | Target list price · vCPU-hour | 0.031611 | USD/vCPU-hour |
| PostgreSQL (one copy) | Target list price · GiB-hour | 0.004237 | USD/GiB-hour |
| PostgreSQL (one copy) | Target price guess · resource-hour | 0 | USD/resource-hour |
| PostgreSQL (one copy) | Target price guess · resource-month | 0 | USD/resource-month |
| PostgreSQL (one copy) | Target price guess · input token | 0 | USD/input token |
| PostgreSQL (one copy) | Target price guess · output token | 0 | USD/output token |
| PostgreSQL (one copy) | Target monthly base charge | 0 | USD/month |
| PostgreSQL (one copy) | Approximate target service minimum | 0 | USD/month |
| PostgreSQL (one copy) | Minimum primary CPU | 2 | vCPU |
| PostgreSQL (one copy) | Minimum primary RAM | 8 | GiB |
| PostgreSQL (one copy) | Minimum primary disk | 100 | GiB |
| PostgreSQL (one copy) | Additional full-price standby copy | 0 | 0 or 1 |
| PostgreSQL (one copy) | Allocated share of provisioned cost | 1 | fraction |
| PostgreSQL (one copy) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| PostgreSQL (one copy) | Planning peak / mean work | 2 | multiplier |
| PostgreSQL (one copy) | Planning primary CPU utilization | 0.7 | fraction |
| PostgreSQL (one copy) | Resident state reserved in RAM | 0.1 | fraction |
| PostgreSQL (one copy) | Planning disk utilization | 0.8 | fraction |
| PostgreSQL (one copy) | Maintenance and log disk reserve | 20 | GiB |
| PostgreSQL (one copy) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| PostgreSQL (one copy) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| PostgreSQL (one copy) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| PostgreSQL (one copy) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| PostgreSQL (one copy) | Dependent object sink write price guess | 0.000005 | USD/write |
| PostgreSQL (two copies) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| PostgreSQL (two copies) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| PostgreSQL (two copies) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| PostgreSQL (two copies) | Origin list price · Control-plane calls | 0 | USD/requests |
| PostgreSQL (two copies) | Representative item size | 1024 | bytes |
| PostgreSQL (two copies) | Strongly consistent read fraction | 1 | fraction |
| PostgreSQL (two copies) | Origin write-unit amplification | 1 | multiplier |
| PostgreSQL (two copies) | Target reads per point read | 1 | operations |
| PostgreSQL (two copies) | Target writes per item write | 1 | operations |
| PostgreSQL (two copies) | Target price guess · read | 0 | USD/read |
| PostgreSQL (two copies) | Target price guess · write | 0 | USD/write |
| PostgreSQL (two copies) | Target price guess · provider operation | 0 | USD/provider operation |
| PostgreSQL (two copies) | Target list price · GiB-month | 0.1 | USD/GiB-month |
| PostgreSQL (two copies) | Target price guess · published GiB | 0 | USD/published GiB |
| PostgreSQL (two copies) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| PostgreSQL (two copies) | Target list price · network GiB | 0.12 | USD/network GiB |
| PostgreSQL (two copies) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| PostgreSQL (two copies) | Target list price · vCPU-hour | 0.031611 | USD/vCPU-hour |
| PostgreSQL (two copies) | Target list price · GiB-hour | 0.004237 | USD/GiB-hour |
| PostgreSQL (two copies) | Target price guess · resource-hour | 0 | USD/resource-hour |
| PostgreSQL (two copies) | Target price guess · resource-month | 0 | USD/resource-month |
| PostgreSQL (two copies) | Target price guess · input token | 0 | USD/input token |
| PostgreSQL (two copies) | Target price guess · output token | 0 | USD/output token |
| PostgreSQL (two copies) | Target monthly base charge | 0 | USD/month |
| PostgreSQL (two copies) | Approximate target service minimum | 0 | USD/month |
| PostgreSQL (two copies) | Minimum primary CPU | 2 | vCPU |
| PostgreSQL (two copies) | Minimum primary RAM | 8 | GiB |
| PostgreSQL (two copies) | Minimum primary disk | 100 | GiB |
| PostgreSQL (two copies) | Additional full-price standby copy | 1 | 0 or 1 |
| PostgreSQL (two copies) | Allocated share of provisioned cost | 1 | fraction |
| PostgreSQL (two copies) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| PostgreSQL (two copies) | Planning peak / mean work | 2 | multiplier |
| PostgreSQL (two copies) | Planning primary CPU utilization | 0.7 | fraction |
| PostgreSQL (two copies) | Resident state reserved in RAM | 0.1 | fraction |
| PostgreSQL (two copies) | Planning disk utilization | 0.8 | fraction |
| PostgreSQL (two copies) | Maintenance and log disk reserve | 20 | GiB |
| PostgreSQL (two copies) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| PostgreSQL (two copies) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| PostgreSQL (two copies) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| PostgreSQL (two copies) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| PostgreSQL (two copies) | Dependent object sink write price guess | 0.000005 | USD/write |

* Writes and storage remain independent. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
* Planning estimate · editable authored rates and sizing assumptions dated 2026-10-22; not verified provider prices. us-east-1 → 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 is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* 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.
* The control plane and table facet describe the same family workload; allocate shared capacity once, not once per catalog facet.
* No transactional, global-table, Streams or scan tariff is inferred from ordinary on-demand point units.
* Self-hosted target: PostgreSQL (PostgreSQL License, [https://www.postgresql.org/about/licence/](https://www.postgresql.org/about/licence/)). Selected CPU, RAM and physical disk allocation grow with workload; no per-operation price is assumed. No vendor tariff: the target runs on the customer's Kubernetes nodes, so CPU, RAM and disk bill at the Kubernetes node reference rates, Compute Engine N2 in us-central1 (USD 0.031611/vCPU-hour, 0.004237/GiB-hour) with pd-balanced disk (0.10/GiB-month) and Premium Tier egress. The cost-optimized E2 series lists 0.02181159/vCPU-hour and 0.00292353/GiB-hour; AWS m6i/r6i and Azure D2s v5/E2s v5 both decompose to 0.033/vCPU-hour and 0.00375/GiB-hour. Requested CPU and RAM are billed; node bin-packing waste, system reservations and the cluster control-plane fee are not.
* Row-store throughput (capacityOpsPerVcpuSecond, default 1500) is measured-by-tensor9 as a lower bound: the DynamoDB adapter on Cloud SQL db-custom-2-7680 (2 vCPU, PostgreSQL 16, us-west1) served 2,974 ops/s of YCSB-A at 16 threads without recorded saturation (src/main/kotlin/t9/prime/equiv/generated/eval/CloudsqlPostgresqlYcsbAT16GoYcsbV1\_0\_0.kt). Published CPU-bound pgbench reaches 3,101 read-write transactions and 20,289 point reads per vCPU-second (AWS z1d.2xlarge, PostgreSQL 14.5), so actual capacity is likely higher. Reads and writes share one coefficient: at the same adapter version, read-only YCSB-C was not faster than 50%-update YCSB-A.
* Log-broker throughput (capacityStreamMiBPerVcpuSecond 20 at 0.5 utilization, 4 GiB RAM per vCPU) is provider-documented by Google Managed Service for Apache Kafka sizing ([https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size](https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size)): write-equivalent bytes are replicated writes plus a quarter of reads. Producer batches below 10 KB lower per-CPU throughput; that penalty is not modeled.
* Disk utilization 0.8 is provider-documented headroom below Cloud SQL automatic storage increase, which triggers near 91-95% full ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)). The 20 GiB reserve exceeds PostgreSQL's 1 GB default max\_wal\_size; the remainder of that reserve is unmeasured.
* CPU tiers, 4 GiB per vCPU, at most 6.5 GiB per vCPU, 96 vCPU and 65,536 GiB disk follow Cloud SQL Enterprise custom machine limits (provider-documented, same page); 624 GiB is 96 × 6.5. Targets billed per node, unit or throughput unit are sized by their backend instead.
* No public evidence: peak/mean work (2) and the RAM working-set fraction (0.1). Proposed measurements: the p99 one-minute rate over the monthly mean from customer CloudWatch metrics; the buffer hit ratio while stepping RAM under a fixed YCSB-B load.
* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.
* The operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
* AWS Price List API, AmazonDynamoDB offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json)
* Amazon DynamoDB pricing: [https://aws.amazon.com/dynamodb/pricing/](https://aws.amazon.com/dynamodb/pricing/)
* Compute Engine general-purpose machine pricing: [https://cloud.google.com/products/compute/pricing/general-purpose](https://cloud.google.com/products/compute/pricing/general-purpose)
* Disk and image pricing: [https://cloud.google.com/compute/disks-image-pricing](https://cloud.google.com/compute/disks-image-pricing)
* Network pricing: [https://cloud.google.com/vpc/network-pricing](https://cloud.google.com/vpc/network-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.
* 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-67ab648398db063f54620ef99fe9513d4263793e` / `2026-10-22.planning.2`. Curve: `workload-1`.

Sources: [AWS Price List API, AmazonDynamoDB offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json), [Amazon DynamoDB pricing](https://aws.amazon.com/dynamodb/pricing/), [Compute Engine general-purpose machine pricing](https://cloud.google.com/products/compute/pricing/general-purpose), [Disk and image pricing](https://cloud.google.com/compute/disks-image-pricing), [Network pricing](https://cloud.google.com/vpc/network-pricing).

### DynamoDB · DynamoDB write units

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

![DynamoDB · DynamoDB write units: monthly service charges by DynamoDB write units. Exact values are in the following table.](/images/diagrams/service-cost/b64afff892b6d04b36878388f5929bc0266b61e687f82e46a5a17b3c1ff1bf56-light.svg)

![DynamoDB · DynamoDB write units: monthly service charges by DynamoDB write units. Exact values are in the following table.](/images/diagrams/service-cost/cd8ce963f13c4564ff3d2f80f2e5c3d0d7efd08aba503ffb3e0de58c5ff928e3-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.

| DynamoDB write units (per second) | DynamoDB | Target scenario | PostgreSQL | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | PostgreSQL (one copy) | 80.89614 | 80.89614 |
| 0 | 0 | PostgreSQL (two copies) | 161.79228 | 161.79228 |
| 1 | 1.6425 | PostgreSQL (one copy) | 80.89614 | 79.25364 |
| 1 | 1.6425 | PostgreSQL (two copies) | 161.79228 | 160.14978 |
| 10 | 16.425 | PostgreSQL (one copy) | 80.89614 | 64.47114 |
| 10 | 16.425 | PostgreSQL (two copies) | 161.79228 | 145.36728 |
| 100 | 164.25 | PostgreSQL (one copy) | 80.89614 | -83.35386 |
| 100 | 164.25 | PostgreSQL (two copies) | 161.79228 | -2.45772 |
| 1000 | 1642.5 | PostgreSQL (one copy) | 80.89614 | -1561.60386 |
| 1000 | 1642.5 | PostgreSQL (two copies) | 161.79228 | -1480.70772 |
| 10000 | 16425 | PostgreSQL (one copy) | 1144.33824 | -15280.66176 |
| 10000 | 16425 | PostgreSQL (two copies) | 2288.67648 | -14136.32352 |

**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 / PostgreSQL (one copy) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 0 per second / PostgreSQL (two copies) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1 per second / PostgreSQL (one copy) | PlanningAssumption | 1 / 2 | 0.001904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1 per second / PostgreSQL (two copies) | PlanningAssumption | 1 / 2 | 0.001904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10 per second / PostgreSQL (one copy) | PlanningAssumption | 10 / 20 | 0.01904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10 per second / PostgreSQL (two copies) | PlanningAssumption | 10 / 20 | 0.01904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 100 per second / PostgreSQL (one copy) | PlanningAssumption | 100 / 200 | 0.1904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 100 per second / PostgreSQL (two copies) | PlanningAssumption | 100 / 200 | 0.1904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1000 per second / PostgreSQL (one copy) | PlanningAssumption | 1000 / 2000 | 1.904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1000 per second / PostgreSQL (two copies) | PlanningAssumption | 1000 / 2000 | 1.904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10000 per second / PostgreSQL (one copy) | PlanningAssumption | 10000 / 20000 | 19.04761904761904761904761904761905 | 32 | 128 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10000 per second / PostgreSQL (two copies) | PlanningAssumption | 10000 / 20000 | 19.04761904761904761904761904761905 | 32 | 128 | 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 operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| PostgreSQL (one copy) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| PostgreSQL (one copy) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| PostgreSQL (one copy) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| PostgreSQL (one copy) | Origin list price · Control-plane calls | 0 | USD/requests |
| PostgreSQL (one copy) | Representative item size | 1024 | bytes |
| PostgreSQL (one copy) | Strongly consistent read fraction | 1 | fraction |
| PostgreSQL (one copy) | Origin write-unit amplification | 1 | multiplier |
| PostgreSQL (one copy) | Target reads per point read | 1 | operations |
| PostgreSQL (one copy) | Target writes per item write | 1 | operations |
| PostgreSQL (one copy) | Target price guess · read | 0 | USD/read |
| PostgreSQL (one copy) | Target price guess · write | 0 | USD/write |
| PostgreSQL (one copy) | Target price guess · provider operation | 0 | USD/provider operation |
| PostgreSQL (one copy) | Target list price · GiB-month | 0.1 | USD/GiB-month |
| PostgreSQL (one copy) | Target price guess · published GiB | 0 | USD/published GiB |
| PostgreSQL (one copy) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| PostgreSQL (one copy) | Target list price · network GiB | 0.12 | USD/network GiB |
| PostgreSQL (one copy) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| PostgreSQL (one copy) | Target list price · vCPU-hour | 0.031611 | USD/vCPU-hour |
| PostgreSQL (one copy) | Target list price · GiB-hour | 0.004237 | USD/GiB-hour |
| PostgreSQL (one copy) | Target price guess · resource-hour | 0 | USD/resource-hour |
| PostgreSQL (one copy) | Target price guess · resource-month | 0 | USD/resource-month |
| PostgreSQL (one copy) | Target price guess · input token | 0 | USD/input token |
| PostgreSQL (one copy) | Target price guess · output token | 0 | USD/output token |
| PostgreSQL (one copy) | Target monthly base charge | 0 | USD/month |
| PostgreSQL (one copy) | Approximate target service minimum | 0 | USD/month |
| PostgreSQL (one copy) | Minimum primary CPU | 2 | vCPU |
| PostgreSQL (one copy) | Minimum primary RAM | 8 | GiB |
| PostgreSQL (one copy) | Minimum primary disk | 100 | GiB |
| PostgreSQL (one copy) | Additional full-price standby copy | 0 | 0 or 1 |
| PostgreSQL (one copy) | Allocated share of provisioned cost | 1 | fraction |
| PostgreSQL (one copy) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| PostgreSQL (one copy) | Planning peak / mean work | 2 | multiplier |
| PostgreSQL (one copy) | Planning primary CPU utilization | 0.7 | fraction |
| PostgreSQL (one copy) | Resident state reserved in RAM | 0.1 | fraction |
| PostgreSQL (one copy) | Planning disk utilization | 0.8 | fraction |
| PostgreSQL (one copy) | Maintenance and log disk reserve | 20 | GiB |
| PostgreSQL (one copy) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| PostgreSQL (one copy) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| PostgreSQL (one copy) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| PostgreSQL (one copy) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| PostgreSQL (one copy) | Dependent object sink write price guess | 0.000005 | USD/write |
| PostgreSQL (two copies) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| PostgreSQL (two copies) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| PostgreSQL (two copies) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| PostgreSQL (two copies) | Origin list price · Control-plane calls | 0 | USD/requests |
| PostgreSQL (two copies) | Representative item size | 1024 | bytes |
| PostgreSQL (two copies) | Strongly consistent read fraction | 1 | fraction |
| PostgreSQL (two copies) | Origin write-unit amplification | 1 | multiplier |
| PostgreSQL (two copies) | Target reads per point read | 1 | operations |
| PostgreSQL (two copies) | Target writes per item write | 1 | operations |
| PostgreSQL (two copies) | Target price guess · read | 0 | USD/read |
| PostgreSQL (two copies) | Target price guess · write | 0 | USD/write |
| PostgreSQL (two copies) | Target price guess · provider operation | 0 | USD/provider operation |
| PostgreSQL (two copies) | Target list price · GiB-month | 0.1 | USD/GiB-month |
| PostgreSQL (two copies) | Target price guess · published GiB | 0 | USD/published GiB |
| PostgreSQL (two copies) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| PostgreSQL (two copies) | Target list price · network GiB | 0.12 | USD/network GiB |
| PostgreSQL (two copies) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| PostgreSQL (two copies) | Target list price · vCPU-hour | 0.031611 | USD/vCPU-hour |
| PostgreSQL (two copies) | Target list price · GiB-hour | 0.004237 | USD/GiB-hour |
| PostgreSQL (two copies) | Target price guess · resource-hour | 0 | USD/resource-hour |
| PostgreSQL (two copies) | Target price guess · resource-month | 0 | USD/resource-month |
| PostgreSQL (two copies) | Target price guess · input token | 0 | USD/input token |
| PostgreSQL (two copies) | Target price guess · output token | 0 | USD/output token |
| PostgreSQL (two copies) | Target monthly base charge | 0 | USD/month |
| PostgreSQL (two copies) | Approximate target service minimum | 0 | USD/month |
| PostgreSQL (two copies) | Minimum primary CPU | 2 | vCPU |
| PostgreSQL (two copies) | Minimum primary RAM | 8 | GiB |
| PostgreSQL (two copies) | Minimum primary disk | 100 | GiB |
| PostgreSQL (two copies) | Additional full-price standby copy | 1 | 0 or 1 |
| PostgreSQL (two copies) | Allocated share of provisioned cost | 1 | fraction |
| PostgreSQL (two copies) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| PostgreSQL (two copies) | Planning peak / mean work | 2 | multiplier |
| PostgreSQL (two copies) | Planning primary CPU utilization | 0.7 | fraction |
| PostgreSQL (two copies) | Resident state reserved in RAM | 0.1 | fraction |
| PostgreSQL (two copies) | Planning disk utilization | 0.8 | fraction |
| PostgreSQL (two copies) | Maintenance and log disk reserve | 20 | GiB |
| PostgreSQL (two copies) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| PostgreSQL (two copies) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| PostgreSQL (two copies) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| PostgreSQL (two copies) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| PostgreSQL (two copies) | Dependent object sink write price guess | 0.000005 | USD/write |

* Reads and storage remain independent. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
* Planning estimate · editable authored rates and sizing assumptions dated 2026-10-22; not verified provider prices. us-east-1 → 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 is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* 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.
* The control plane and table facet describe the same family workload; allocate shared capacity once, not once per catalog facet.
* No transactional, global-table, Streams or scan tariff is inferred from ordinary on-demand point units.
* Self-hosted target: PostgreSQL (PostgreSQL License, [https://www.postgresql.org/about/licence/](https://www.postgresql.org/about/licence/)). Selected CPU, RAM and physical disk allocation grow with workload; no per-operation price is assumed. No vendor tariff: the target runs on the customer's Kubernetes nodes, so CPU, RAM and disk bill at the Kubernetes node reference rates, Compute Engine N2 in us-central1 (USD 0.031611/vCPU-hour, 0.004237/GiB-hour) with pd-balanced disk (0.10/GiB-month) and Premium Tier egress. The cost-optimized E2 series lists 0.02181159/vCPU-hour and 0.00292353/GiB-hour; AWS m6i/r6i and Azure D2s v5/E2s v5 both decompose to 0.033/vCPU-hour and 0.00375/GiB-hour. Requested CPU and RAM are billed; node bin-packing waste, system reservations and the cluster control-plane fee are not.
* Row-store throughput (capacityOpsPerVcpuSecond, default 1500) is measured-by-tensor9 as a lower bound: the DynamoDB adapter on Cloud SQL db-custom-2-7680 (2 vCPU, PostgreSQL 16, us-west1) served 2,974 ops/s of YCSB-A at 16 threads without recorded saturation (src/main/kotlin/t9/prime/equiv/generated/eval/CloudsqlPostgresqlYcsbAT16GoYcsbV1\_0\_0.kt). Published CPU-bound pgbench reaches 3,101 read-write transactions and 20,289 point reads per vCPU-second (AWS z1d.2xlarge, PostgreSQL 14.5), so actual capacity is likely higher. Reads and writes share one coefficient: at the same adapter version, read-only YCSB-C was not faster than 50%-update YCSB-A.
* Log-broker throughput (capacityStreamMiBPerVcpuSecond 20 at 0.5 utilization, 4 GiB RAM per vCPU) is provider-documented by Google Managed Service for Apache Kafka sizing ([https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size](https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size)): write-equivalent bytes are replicated writes plus a quarter of reads. Producer batches below 10 KB lower per-CPU throughput; that penalty is not modeled.
* Disk utilization 0.8 is provider-documented headroom below Cloud SQL automatic storage increase, which triggers near 91-95% full ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)). The 20 GiB reserve exceeds PostgreSQL's 1 GB default max\_wal\_size; the remainder of that reserve is unmeasured.
* CPU tiers, 4 GiB per vCPU, at most 6.5 GiB per vCPU, 96 vCPU and 65,536 GiB disk follow Cloud SQL Enterprise custom machine limits (provider-documented, same page); 624 GiB is 96 × 6.5. Targets billed per node, unit or throughput unit are sized by their backend instead.
* No public evidence: peak/mean work (2) and the RAM working-set fraction (0.1). Proposed measurements: the p99 one-minute rate over the monthly mean from customer CloudWatch metrics; the buffer hit ratio while stepping RAM under a fixed YCSB-B load.
* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.
* The operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
* AWS Price List API, AmazonDynamoDB offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json)
* Amazon DynamoDB pricing: [https://aws.amazon.com/dynamodb/pricing/](https://aws.amazon.com/dynamodb/pricing/)
* Compute Engine general-purpose machine pricing: [https://cloud.google.com/products/compute/pricing/general-purpose](https://cloud.google.com/products/compute/pricing/general-purpose)
* Disk and image pricing: [https://cloud.google.com/compute/disks-image-pricing](https://cloud.google.com/compute/disks-image-pricing)
* Network pricing: [https://cloud.google.com/vpc/network-pricing](https://cloud.google.com/vpc/network-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.
* 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-67ab648398db063f54620ef99fe9513d4263793e` / `2026-10-22.planning.2`. Curve: `workload-2`.

Sources: [AWS Price List API, AmazonDynamoDB offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json), [Amazon DynamoDB pricing](https://aws.amazon.com/dynamodb/pricing/), [Compute Engine general-purpose machine pricing](https://cloud.google.com/products/compute/pricing/general-purpose), [Disk and image pricing](https://cloud.google.com/compute/disks-image-pricing), [Network pricing](https://cloud.google.com/vpc/network-pricing).

### DynamoDB · Stored data

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

![DynamoDB · Stored data: monthly service charges by Stored data. Exact values are in the following table.](/images/diagrams/service-cost/7a693bc45223c29b46495062c12da4f5dbdf996d9c61806494dfd1dc0ba299ed-light.svg)

![DynamoDB · Stored data: monthly service charges by Stored data. Exact values are in the following table.](/images/diagrams/service-cost/40b2cf0abca756564400e26e6c1d6b630229d29285168629b2aed1215bb5b3a1-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) | DynamoDB | Target scenario | PostgreSQL | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | PostgreSQL (one copy) | 80.89614 | 80.89614 |
| 0 | 0 | PostgreSQL (two copies) | 161.79228 | 161.79228 |
| 10 | 2.5 | PostgreSQL (one copy) | 80.89614 | 78.39614 |
| 10 | 2.5 | PostgreSQL (two copies) | 161.79228 | 159.29228 |
| 100 | 25 | PostgreSQL (one copy) | 92.08216 | 67.08216 |
| 100 | 25 | PostgreSQL (two copies) | 184.16432 | 159.16432 |
| 1000 | 250 | PostgreSQL (one copy) | 806.01748 | 556.01748 |
| 1000 | 250 | PostgreSQL (two copies) | 1612.03496 | 1362.03496 |
| 10000 | 2500 | PostgreSQL (one copy) | Unpriced | Unavailable |
| 10000 | 2500 | PostgreSQL (two copies) | Unpriced | Unavailable |
| 100000 | 25000 | PostgreSQL (one copy) | Unpriced | Unavailable |
| 100000 | 25000 | 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 / PostgreSQL (one copy) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 0 GiB-month / PostgreSQL (two copies) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10 GiB-month / PostgreSQL (one copy) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 10 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10 GiB-month / PostgreSQL (two copies) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 10 | `service-adapter-planning-2026-10-22.1` | None reported |
| 100 GiB-month / PostgreSQL (one copy) | PlanningAssumption | 0 / 0 | 0 | 2 | 10 | 150 | 100 | `service-adapter-planning-2026-10-22.1` | None reported |
| 100 GiB-month / PostgreSQL (two copies) | PlanningAssumption | 0 / 0 | 0 | 2 | 10 | 150 | 100 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1000 GiB-month / PostgreSQL (one copy) | PlanningAssumption | 0 / 0 | 0 | 16 | 100 | 1275 | 1000 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1000 GiB-month / PostgreSQL (two copies) | PlanningAssumption | 0 / 0 | 0 | 16 | 100 | 1275 | 1000 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10000 GiB-month / 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 / 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 / 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 / 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 operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| PostgreSQL (one copy) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| PostgreSQL (one copy) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| PostgreSQL (one copy) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| PostgreSQL (one copy) | Origin list price · Control-plane calls | 0 | USD/requests |
| PostgreSQL (one copy) | Representative item size | 1024 | bytes |
| PostgreSQL (one copy) | Strongly consistent read fraction | 1 | fraction |
| PostgreSQL (one copy) | Origin write-unit amplification | 1 | multiplier |
| PostgreSQL (one copy) | Target reads per point read | 1 | operations |
| PostgreSQL (one copy) | Target writes per item write | 1 | operations |
| PostgreSQL (one copy) | Target price guess · read | 0 | USD/read |
| PostgreSQL (one copy) | Target price guess · write | 0 | USD/write |
| PostgreSQL (one copy) | Target price guess · provider operation | 0 | USD/provider operation |
| PostgreSQL (one copy) | Target list price · GiB-month | 0.1 | USD/GiB-month |
| PostgreSQL (one copy) | Target price guess · published GiB | 0 | USD/published GiB |
| PostgreSQL (one copy) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| PostgreSQL (one copy) | Target list price · network GiB | 0.12 | USD/network GiB |
| PostgreSQL (one copy) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| PostgreSQL (one copy) | Target list price · vCPU-hour | 0.031611 | USD/vCPU-hour |
| PostgreSQL (one copy) | Target list price · GiB-hour | 0.004237 | USD/GiB-hour |
| PostgreSQL (one copy) | Target price guess · resource-hour | 0 | USD/resource-hour |
| PostgreSQL (one copy) | Target price guess · resource-month | 0 | USD/resource-month |
| PostgreSQL (one copy) | Target price guess · input token | 0 | USD/input token |
| PostgreSQL (one copy) | Target price guess · output token | 0 | USD/output token |
| PostgreSQL (one copy) | Target monthly base charge | 0 | USD/month |
| PostgreSQL (one copy) | Approximate target service minimum | 0 | USD/month |
| PostgreSQL (one copy) | Minimum primary CPU | 2 | vCPU |
| PostgreSQL (one copy) | Minimum primary RAM | 8 | GiB |
| PostgreSQL (one copy) | Minimum primary disk | 100 | GiB |
| PostgreSQL (one copy) | Additional full-price standby copy | 0 | 0 or 1 |
| PostgreSQL (one copy) | Allocated share of provisioned cost | 1 | fraction |
| PostgreSQL (one copy) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| PostgreSQL (one copy) | Planning peak / mean work | 2 | multiplier |
| PostgreSQL (one copy) | Planning primary CPU utilization | 0.7 | fraction |
| PostgreSQL (one copy) | Resident state reserved in RAM | 0.1 | fraction |
| PostgreSQL (one copy) | Planning disk utilization | 0.8 | fraction |
| PostgreSQL (one copy) | Maintenance and log disk reserve | 20 | GiB |
| PostgreSQL (one copy) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| PostgreSQL (one copy) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| PostgreSQL (one copy) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| PostgreSQL (one copy) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| PostgreSQL (one copy) | Dependent object sink write price guess | 0.000005 | USD/write |
| PostgreSQL (two copies) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| PostgreSQL (two copies) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| PostgreSQL (two copies) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| PostgreSQL (two copies) | Origin list price · Control-plane calls | 0 | USD/requests |
| PostgreSQL (two copies) | Representative item size | 1024 | bytes |
| PostgreSQL (two copies) | Strongly consistent read fraction | 1 | fraction |
| PostgreSQL (two copies) | Origin write-unit amplification | 1 | multiplier |
| PostgreSQL (two copies) | Target reads per point read | 1 | operations |
| PostgreSQL (two copies) | Target writes per item write | 1 | operations |
| PostgreSQL (two copies) | Target price guess · read | 0 | USD/read |
| PostgreSQL (two copies) | Target price guess · write | 0 | USD/write |
| PostgreSQL (two copies) | Target price guess · provider operation | 0 | USD/provider operation |
| PostgreSQL (two copies) | Target list price · GiB-month | 0.1 | USD/GiB-month |
| PostgreSQL (two copies) | Target price guess · published GiB | 0 | USD/published GiB |
| PostgreSQL (two copies) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| PostgreSQL (two copies) | Target list price · network GiB | 0.12 | USD/network GiB |
| PostgreSQL (two copies) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| PostgreSQL (two copies) | Target list price · vCPU-hour | 0.031611 | USD/vCPU-hour |
| PostgreSQL (two copies) | Target list price · GiB-hour | 0.004237 | USD/GiB-hour |
| PostgreSQL (two copies) | Target price guess · resource-hour | 0 | USD/resource-hour |
| PostgreSQL (two copies) | Target price guess · resource-month | 0 | USD/resource-month |
| PostgreSQL (two copies) | Target price guess · input token | 0 | USD/input token |
| PostgreSQL (two copies) | Target price guess · output token | 0 | USD/output token |
| PostgreSQL (two copies) | Target monthly base charge | 0 | USD/month |
| PostgreSQL (two copies) | Approximate target service minimum | 0 | USD/month |
| PostgreSQL (two copies) | Minimum primary CPU | 2 | vCPU |
| PostgreSQL (two copies) | Minimum primary RAM | 8 | GiB |
| PostgreSQL (two copies) | Minimum primary disk | 100 | GiB |
| PostgreSQL (two copies) | Additional full-price standby copy | 1 | 0 or 1 |
| PostgreSQL (two copies) | Allocated share of provisioned cost | 1 | fraction |
| PostgreSQL (two copies) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| PostgreSQL (two copies) | Planning peak / mean work | 2 | multiplier |
| PostgreSQL (two copies) | Planning primary CPU utilization | 0.7 | fraction |
| PostgreSQL (two copies) | Resident state reserved in RAM | 0.1 | fraction |
| PostgreSQL (two copies) | Planning disk utilization | 0.8 | fraction |
| PostgreSQL (two copies) | Maintenance and log disk reserve | 20 | GiB |
| PostgreSQL (two copies) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| PostgreSQL (two copies) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| PostgreSQL (two copies) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| PostgreSQL (two copies) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| 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. us-east-1 → 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 is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* 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.
* The control plane and table facet describe the same family workload; allocate shared capacity once, not once per catalog facet.
* No transactional, global-table, Streams or scan tariff is inferred from ordinary on-demand point units.
* Self-hosted target: PostgreSQL (PostgreSQL License, [https://www.postgresql.org/about/licence/](https://www.postgresql.org/about/licence/)). Selected CPU, RAM and physical disk allocation grow with workload; no per-operation price is assumed. No vendor tariff: the target runs on the customer's Kubernetes nodes, so CPU, RAM and disk bill at the Kubernetes node reference rates, Compute Engine N2 in us-central1 (USD 0.031611/vCPU-hour, 0.004237/GiB-hour) with pd-balanced disk (0.10/GiB-month) and Premium Tier egress. The cost-optimized E2 series lists 0.02181159/vCPU-hour and 0.00292353/GiB-hour; AWS m6i/r6i and Azure D2s v5/E2s v5 both decompose to 0.033/vCPU-hour and 0.00375/GiB-hour. Requested CPU and RAM are billed; node bin-packing waste, system reservations and the cluster control-plane fee are not.
* Row-store throughput (capacityOpsPerVcpuSecond, default 1500) is measured-by-tensor9 as a lower bound: the DynamoDB adapter on Cloud SQL db-custom-2-7680 (2 vCPU, PostgreSQL 16, us-west1) served 2,974 ops/s of YCSB-A at 16 threads without recorded saturation (src/main/kotlin/t9/prime/equiv/generated/eval/CloudsqlPostgresqlYcsbAT16GoYcsbV1\_0\_0.kt). Published CPU-bound pgbench reaches 3,101 read-write transactions and 20,289 point reads per vCPU-second (AWS z1d.2xlarge, PostgreSQL 14.5), so actual capacity is likely higher. Reads and writes share one coefficient: at the same adapter version, read-only YCSB-C was not faster than 50%-update YCSB-A.
* Log-broker throughput (capacityStreamMiBPerVcpuSecond 20 at 0.5 utilization, 4 GiB RAM per vCPU) is provider-documented by Google Managed Service for Apache Kafka sizing ([https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size](https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size)): write-equivalent bytes are replicated writes plus a quarter of reads. Producer batches below 10 KB lower per-CPU throughput; that penalty is not modeled.
* Disk utilization 0.8 is provider-documented headroom below Cloud SQL automatic storage increase, which triggers near 91-95% full ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)). The 20 GiB reserve exceeds PostgreSQL's 1 GB default max\_wal\_size; the remainder of that reserve is unmeasured.
* CPU tiers, 4 GiB per vCPU, at most 6.5 GiB per vCPU, 96 vCPU and 65,536 GiB disk follow Cloud SQL Enterprise custom machine limits (provider-documented, same page); 624 GiB is 96 × 6.5. Targets billed per node, unit or throughput unit are sized by their backend instead.
* No public evidence: peak/mean work (2) and the RAM working-set fraction (0.1). Proposed measurements: the p99 one-minute rate over the monthly mean from customer CloudWatch metrics; the buffer hit ratio while stepping RAM under a fixed YCSB-B load.
* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.
* The operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
* AWS Price List API, AmazonDynamoDB offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json)
* Amazon DynamoDB pricing: [https://aws.amazon.com/dynamodb/pricing/](https://aws.amazon.com/dynamodb/pricing/)
* Compute Engine general-purpose machine pricing: [https://cloud.google.com/products/compute/pricing/general-purpose](https://cloud.google.com/products/compute/pricing/general-purpose)
* Disk and image pricing: [https://cloud.google.com/compute/disks-image-pricing](https://cloud.google.com/compute/disks-image-pricing)
* Network pricing: [https://cloud.google.com/vpc/network-pricing](https://cloud.google.com/vpc/network-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.
* 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-67ab648398db063f54620ef99fe9513d4263793e` / `2026-10-22.planning.2`. Curve: `workload-3`.

Sources: [AWS Price List API, AmazonDynamoDB offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json), [Amazon DynamoDB pricing](https://aws.amazon.com/dynamodb/pricing/), [Compute Engine general-purpose machine pricing](https://cloud.google.com/products/compute/pricing/general-purpose), [Disk and image pricing](https://cloud.google.com/compute/disks-image-pricing), [Network pricing](https://cloud.google.com/vpc/network-pricing).

## DynamoDB → PostgreSQL

Origin API: `aws::1.0.0::dynamodb::table`. Target backend: `postgres::1.0.0::database`.

### DynamoDB · DynamoDB read units

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

![DynamoDB · DynamoDB read units: monthly service charges by DynamoDB read units. Exact values are in the following table.](/images/diagrams/service-cost/8382fef517eda76f19e611cff06433dc02cd8c7f577d733a69e8c0b16b31e60a-light.svg)

![DynamoDB · DynamoDB read units: monthly service charges by DynamoDB read units. Exact values are in the following table.](/images/diagrams/service-cost/e74af201710e1424ddeb5ddaa5965e321fb9ab1f7fdf2d26491b5031e8fdbb1c-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.

| DynamoDB read units (per second) | DynamoDB | Target scenario | PostgreSQL | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | PostgreSQL (one copy) | 80.89614 | 80.89614 |
| 0 | 0 | PostgreSQL (two copies) | 161.79228 | 161.79228 |
| 1 | 0.3285 | PostgreSQL (one copy) | 80.89614 | 80.56764 |
| 1 | 0.3285 | PostgreSQL (two copies) | 161.79228 | 161.46378 |
| 10 | 3.285 | PostgreSQL (one copy) | 80.89614 | 77.61114 |
| 10 | 3.285 | PostgreSQL (two copies) | 161.79228 | 158.50728 |
| 100 | 32.85 | PostgreSQL (one copy) | 80.89614 | 48.04614 |
| 100 | 32.85 | PostgreSQL (two copies) | 161.79228 | 128.94228 |
| 1000 | 328.5 | PostgreSQL (one copy) | 80.89614 | -247.60386 |
| 1000 | 328.5 | PostgreSQL (two copies) | 161.79228 | -166.70772 |
| 10000 | 3285 | PostgreSQL (one copy) | 1144.33824 | -2140.66176 |
| 10000 | 3285 | PostgreSQL (two copies) | 2288.67648 | -996.32352 |

**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 / PostgreSQL (one copy) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 0 per second / PostgreSQL (two copies) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1 per second / PostgreSQL (one copy) | PlanningAssumption | 1 / 2 | 0.001904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1 per second / PostgreSQL (two copies) | PlanningAssumption | 1 / 2 | 0.001904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10 per second / PostgreSQL (one copy) | PlanningAssumption | 10 / 20 | 0.01904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10 per second / PostgreSQL (two copies) | PlanningAssumption | 10 / 20 | 0.01904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 100 per second / PostgreSQL (one copy) | PlanningAssumption | 100 / 200 | 0.1904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 100 per second / PostgreSQL (two copies) | PlanningAssumption | 100 / 200 | 0.1904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1000 per second / PostgreSQL (one copy) | PlanningAssumption | 1000 / 2000 | 1.904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1000 per second / PostgreSQL (two copies) | PlanningAssumption | 1000 / 2000 | 1.904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10000 per second / PostgreSQL (one copy) | PlanningAssumption | 10000 / 20000 | 19.04761904761904761904761904761905 | 32 | 128 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10000 per second / PostgreSQL (two copies) | PlanningAssumption | 10000 / 20000 | 19.04761904761904761904761904761905 | 32 | 128 | 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 operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| PostgreSQL (one copy) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| PostgreSQL (one copy) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| PostgreSQL (one copy) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| PostgreSQL (one copy) | Origin list price · Control-plane calls | 0 | USD/requests |
| PostgreSQL (one copy) | Representative item size | 1024 | bytes |
| PostgreSQL (one copy) | Strongly consistent read fraction | 1 | fraction |
| PostgreSQL (one copy) | Origin write-unit amplification | 1 | multiplier |
| PostgreSQL (one copy) | Target reads per point read | 1 | operations |
| PostgreSQL (one copy) | Target writes per item write | 1 | operations |
| PostgreSQL (one copy) | Target price guess · read | 0 | USD/read |
| PostgreSQL (one copy) | Target price guess · write | 0 | USD/write |
| PostgreSQL (one copy) | Target price guess · provider operation | 0 | USD/provider operation |
| PostgreSQL (one copy) | Target list price · GiB-month | 0.1 | USD/GiB-month |
| PostgreSQL (one copy) | Target price guess · published GiB | 0 | USD/published GiB |
| PostgreSQL (one copy) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| PostgreSQL (one copy) | Target list price · network GiB | 0.12 | USD/network GiB |
| PostgreSQL (one copy) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| PostgreSQL (one copy) | Target list price · vCPU-hour | 0.031611 | USD/vCPU-hour |
| PostgreSQL (one copy) | Target list price · GiB-hour | 0.004237 | USD/GiB-hour |
| PostgreSQL (one copy) | Target price guess · resource-hour | 0 | USD/resource-hour |
| PostgreSQL (one copy) | Target price guess · resource-month | 0 | USD/resource-month |
| PostgreSQL (one copy) | Target price guess · input token | 0 | USD/input token |
| PostgreSQL (one copy) | Target price guess · output token | 0 | USD/output token |
| PostgreSQL (one copy) | Target monthly base charge | 0 | USD/month |
| PostgreSQL (one copy) | Approximate target service minimum | 0 | USD/month |
| PostgreSQL (one copy) | Minimum primary CPU | 2 | vCPU |
| PostgreSQL (one copy) | Minimum primary RAM | 8 | GiB |
| PostgreSQL (one copy) | Minimum primary disk | 100 | GiB |
| PostgreSQL (one copy) | Additional full-price standby copy | 0 | 0 or 1 |
| PostgreSQL (one copy) | Allocated share of provisioned cost | 1 | fraction |
| PostgreSQL (one copy) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| PostgreSQL (one copy) | Planning peak / mean work | 2 | multiplier |
| PostgreSQL (one copy) | Planning primary CPU utilization | 0.7 | fraction |
| PostgreSQL (one copy) | Resident state reserved in RAM | 0.1 | fraction |
| PostgreSQL (one copy) | Planning disk utilization | 0.8 | fraction |
| PostgreSQL (one copy) | Maintenance and log disk reserve | 20 | GiB |
| PostgreSQL (one copy) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| PostgreSQL (one copy) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| PostgreSQL (one copy) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| PostgreSQL (one copy) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| PostgreSQL (one copy) | Dependent object sink write price guess | 0.000005 | USD/write |
| PostgreSQL (two copies) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| PostgreSQL (two copies) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| PostgreSQL (two copies) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| PostgreSQL (two copies) | Origin list price · Control-plane calls | 0 | USD/requests |
| PostgreSQL (two copies) | Representative item size | 1024 | bytes |
| PostgreSQL (two copies) | Strongly consistent read fraction | 1 | fraction |
| PostgreSQL (two copies) | Origin write-unit amplification | 1 | multiplier |
| PostgreSQL (two copies) | Target reads per point read | 1 | operations |
| PostgreSQL (two copies) | Target writes per item write | 1 | operations |
| PostgreSQL (two copies) | Target price guess · read | 0 | USD/read |
| PostgreSQL (two copies) | Target price guess · write | 0 | USD/write |
| PostgreSQL (two copies) | Target price guess · provider operation | 0 | USD/provider operation |
| PostgreSQL (two copies) | Target list price · GiB-month | 0.1 | USD/GiB-month |
| PostgreSQL (two copies) | Target price guess · published GiB | 0 | USD/published GiB |
| PostgreSQL (two copies) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| PostgreSQL (two copies) | Target list price · network GiB | 0.12 | USD/network GiB |
| PostgreSQL (two copies) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| PostgreSQL (two copies) | Target list price · vCPU-hour | 0.031611 | USD/vCPU-hour |
| PostgreSQL (two copies) | Target list price · GiB-hour | 0.004237 | USD/GiB-hour |
| PostgreSQL (two copies) | Target price guess · resource-hour | 0 | USD/resource-hour |
| PostgreSQL (two copies) | Target price guess · resource-month | 0 | USD/resource-month |
| PostgreSQL (two copies) | Target price guess · input token | 0 | USD/input token |
| PostgreSQL (two copies) | Target price guess · output token | 0 | USD/output token |
| PostgreSQL (two copies) | Target monthly base charge | 0 | USD/month |
| PostgreSQL (two copies) | Approximate target service minimum | 0 | USD/month |
| PostgreSQL (two copies) | Minimum primary CPU | 2 | vCPU |
| PostgreSQL (two copies) | Minimum primary RAM | 8 | GiB |
| PostgreSQL (two copies) | Minimum primary disk | 100 | GiB |
| PostgreSQL (two copies) | Additional full-price standby copy | 1 | 0 or 1 |
| PostgreSQL (two copies) | Allocated share of provisioned cost | 1 | fraction |
| PostgreSQL (two copies) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| PostgreSQL (two copies) | Planning peak / mean work | 2 | multiplier |
| PostgreSQL (two copies) | Planning primary CPU utilization | 0.7 | fraction |
| PostgreSQL (two copies) | Resident state reserved in RAM | 0.1 | fraction |
| PostgreSQL (two copies) | Planning disk utilization | 0.8 | fraction |
| PostgreSQL (two copies) | Maintenance and log disk reserve | 20 | GiB |
| PostgreSQL (two copies) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| PostgreSQL (two copies) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| PostgreSQL (two copies) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| PostgreSQL (two copies) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| PostgreSQL (two copies) | Dependent object sink write price guess | 0.000005 | USD/write |

* Writes and storage remain independent. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
* Planning estimate · editable authored rates and sizing assumptions dated 2026-10-22; not verified provider prices. us-east-1 → 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 is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* 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.
* The control plane and table facet describe the same family workload; allocate shared capacity once, not once per catalog facet.
* No transactional, global-table, Streams or scan tariff is inferred from ordinary on-demand point units.
* Self-hosted target: PostgreSQL (PostgreSQL License, [https://www.postgresql.org/about/licence/](https://www.postgresql.org/about/licence/)). Selected CPU, RAM and physical disk allocation grow with workload; no per-operation price is assumed. No vendor tariff: the target runs on the customer's Kubernetes nodes, so CPU, RAM and disk bill at the Kubernetes node reference rates, Compute Engine N2 in us-central1 (USD 0.031611/vCPU-hour, 0.004237/GiB-hour) with pd-balanced disk (0.10/GiB-month) and Premium Tier egress. The cost-optimized E2 series lists 0.02181159/vCPU-hour and 0.00292353/GiB-hour; AWS m6i/r6i and Azure D2s v5/E2s v5 both decompose to 0.033/vCPU-hour and 0.00375/GiB-hour. Requested CPU and RAM are billed; node bin-packing waste, system reservations and the cluster control-plane fee are not.
* Row-store throughput (capacityOpsPerVcpuSecond, default 1500) is measured-by-tensor9 as a lower bound: the DynamoDB adapter on Cloud SQL db-custom-2-7680 (2 vCPU, PostgreSQL 16, us-west1) served 2,974 ops/s of YCSB-A at 16 threads without recorded saturation (src/main/kotlin/t9/prime/equiv/generated/eval/CloudsqlPostgresqlYcsbAT16GoYcsbV1\_0\_0.kt). Published CPU-bound pgbench reaches 3,101 read-write transactions and 20,289 point reads per vCPU-second (AWS z1d.2xlarge, PostgreSQL 14.5), so actual capacity is likely higher. Reads and writes share one coefficient: at the same adapter version, read-only YCSB-C was not faster than 50%-update YCSB-A.
* Log-broker throughput (capacityStreamMiBPerVcpuSecond 20 at 0.5 utilization, 4 GiB RAM per vCPU) is provider-documented by Google Managed Service for Apache Kafka sizing ([https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size](https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size)): write-equivalent bytes are replicated writes plus a quarter of reads. Producer batches below 10 KB lower per-CPU throughput; that penalty is not modeled.
* Disk utilization 0.8 is provider-documented headroom below Cloud SQL automatic storage increase, which triggers near 91-95% full ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)). The 20 GiB reserve exceeds PostgreSQL's 1 GB default max\_wal\_size; the remainder of that reserve is unmeasured.
* CPU tiers, 4 GiB per vCPU, at most 6.5 GiB per vCPU, 96 vCPU and 65,536 GiB disk follow Cloud SQL Enterprise custom machine limits (provider-documented, same page); 624 GiB is 96 × 6.5. Targets billed per node, unit or throughput unit are sized by their backend instead.
* No public evidence: peak/mean work (2) and the RAM working-set fraction (0.1). Proposed measurements: the p99 one-minute rate over the monthly mean from customer CloudWatch metrics; the buffer hit ratio while stepping RAM under a fixed YCSB-B load.
* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.
* The operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
* AWS Price List API, AmazonDynamoDB offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json)
* Amazon DynamoDB pricing: [https://aws.amazon.com/dynamodb/pricing/](https://aws.amazon.com/dynamodb/pricing/)
* Compute Engine general-purpose machine pricing: [https://cloud.google.com/products/compute/pricing/general-purpose](https://cloud.google.com/products/compute/pricing/general-purpose)
* Disk and image pricing: [https://cloud.google.com/compute/disks-image-pricing](https://cloud.google.com/compute/disks-image-pricing)
* Network pricing: [https://cloud.google.com/vpc/network-pricing](https://cloud.google.com/vpc/network-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.
* 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-271febef7b5ad970d96d5373c36c91bf2d6b17bb` / `2026-10-22.planning.2`. Curve: `workload-1`.

Sources: [AWS Price List API, AmazonDynamoDB offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json), [Amazon DynamoDB pricing](https://aws.amazon.com/dynamodb/pricing/), [Compute Engine general-purpose machine pricing](https://cloud.google.com/products/compute/pricing/general-purpose), [Disk and image pricing](https://cloud.google.com/compute/disks-image-pricing), [Network pricing](https://cloud.google.com/vpc/network-pricing).

### DynamoDB · DynamoDB write units

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

![DynamoDB · DynamoDB write units: monthly service charges by DynamoDB write units. Exact values are in the following table.](/images/diagrams/service-cost/b64afff892b6d04b36878388f5929bc0266b61e687f82e46a5a17b3c1ff1bf56-light.svg)

![DynamoDB · DynamoDB write units: monthly service charges by DynamoDB write units. Exact values are in the following table.](/images/diagrams/service-cost/cd8ce963f13c4564ff3d2f80f2e5c3d0d7efd08aba503ffb3e0de58c5ff928e3-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.

| DynamoDB write units (per second) | DynamoDB | Target scenario | PostgreSQL | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | PostgreSQL (one copy) | 80.89614 | 80.89614 |
| 0 | 0 | PostgreSQL (two copies) | 161.79228 | 161.79228 |
| 1 | 1.6425 | PostgreSQL (one copy) | 80.89614 | 79.25364 |
| 1 | 1.6425 | PostgreSQL (two copies) | 161.79228 | 160.14978 |
| 10 | 16.425 | PostgreSQL (one copy) | 80.89614 | 64.47114 |
| 10 | 16.425 | PostgreSQL (two copies) | 161.79228 | 145.36728 |
| 100 | 164.25 | PostgreSQL (one copy) | 80.89614 | -83.35386 |
| 100 | 164.25 | PostgreSQL (two copies) | 161.79228 | -2.45772 |
| 1000 | 1642.5 | PostgreSQL (one copy) | 80.89614 | -1561.60386 |
| 1000 | 1642.5 | PostgreSQL (two copies) | 161.79228 | -1480.70772 |
| 10000 | 16425 | PostgreSQL (one copy) | 1144.33824 | -15280.66176 |
| 10000 | 16425 | PostgreSQL (two copies) | 2288.67648 | -14136.32352 |

**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 / PostgreSQL (one copy) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 0 per second / PostgreSQL (two copies) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1 per second / PostgreSQL (one copy) | PlanningAssumption | 1 / 2 | 0.001904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1 per second / PostgreSQL (two copies) | PlanningAssumption | 1 / 2 | 0.001904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10 per second / PostgreSQL (one copy) | PlanningAssumption | 10 / 20 | 0.01904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10 per second / PostgreSQL (two copies) | PlanningAssumption | 10 / 20 | 0.01904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 100 per second / PostgreSQL (one copy) | PlanningAssumption | 100 / 200 | 0.1904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 100 per second / PostgreSQL (two copies) | PlanningAssumption | 100 / 200 | 0.1904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1000 per second / PostgreSQL (one copy) | PlanningAssumption | 1000 / 2000 | 1.904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1000 per second / PostgreSQL (two copies) | PlanningAssumption | 1000 / 2000 | 1.904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10000 per second / PostgreSQL (one copy) | PlanningAssumption | 10000 / 20000 | 19.04761904761904761904761904761905 | 32 | 128 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10000 per second / PostgreSQL (two copies) | PlanningAssumption | 10000 / 20000 | 19.04761904761904761904761904761905 | 32 | 128 | 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 operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| PostgreSQL (one copy) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| PostgreSQL (one copy) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| PostgreSQL (one copy) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| PostgreSQL (one copy) | Origin list price · Control-plane calls | 0 | USD/requests |
| PostgreSQL (one copy) | Representative item size | 1024 | bytes |
| PostgreSQL (one copy) | Strongly consistent read fraction | 1 | fraction |
| PostgreSQL (one copy) | Origin write-unit amplification | 1 | multiplier |
| PostgreSQL (one copy) | Target reads per point read | 1 | operations |
| PostgreSQL (one copy) | Target writes per item write | 1 | operations |
| PostgreSQL (one copy) | Target price guess · read | 0 | USD/read |
| PostgreSQL (one copy) | Target price guess · write | 0 | USD/write |
| PostgreSQL (one copy) | Target price guess · provider operation | 0 | USD/provider operation |
| PostgreSQL (one copy) | Target list price · GiB-month | 0.1 | USD/GiB-month |
| PostgreSQL (one copy) | Target price guess · published GiB | 0 | USD/published GiB |
| PostgreSQL (one copy) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| PostgreSQL (one copy) | Target list price · network GiB | 0.12 | USD/network GiB |
| PostgreSQL (one copy) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| PostgreSQL (one copy) | Target list price · vCPU-hour | 0.031611 | USD/vCPU-hour |
| PostgreSQL (one copy) | Target list price · GiB-hour | 0.004237 | USD/GiB-hour |
| PostgreSQL (one copy) | Target price guess · resource-hour | 0 | USD/resource-hour |
| PostgreSQL (one copy) | Target price guess · resource-month | 0 | USD/resource-month |
| PostgreSQL (one copy) | Target price guess · input token | 0 | USD/input token |
| PostgreSQL (one copy) | Target price guess · output token | 0 | USD/output token |
| PostgreSQL (one copy) | Target monthly base charge | 0 | USD/month |
| PostgreSQL (one copy) | Approximate target service minimum | 0 | USD/month |
| PostgreSQL (one copy) | Minimum primary CPU | 2 | vCPU |
| PostgreSQL (one copy) | Minimum primary RAM | 8 | GiB |
| PostgreSQL (one copy) | Minimum primary disk | 100 | GiB |
| PostgreSQL (one copy) | Additional full-price standby copy | 0 | 0 or 1 |
| PostgreSQL (one copy) | Allocated share of provisioned cost | 1 | fraction |
| PostgreSQL (one copy) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| PostgreSQL (one copy) | Planning peak / mean work | 2 | multiplier |
| PostgreSQL (one copy) | Planning primary CPU utilization | 0.7 | fraction |
| PostgreSQL (one copy) | Resident state reserved in RAM | 0.1 | fraction |
| PostgreSQL (one copy) | Planning disk utilization | 0.8 | fraction |
| PostgreSQL (one copy) | Maintenance and log disk reserve | 20 | GiB |
| PostgreSQL (one copy) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| PostgreSQL (one copy) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| PostgreSQL (one copy) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| PostgreSQL (one copy) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| PostgreSQL (one copy) | Dependent object sink write price guess | 0.000005 | USD/write |
| PostgreSQL (two copies) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| PostgreSQL (two copies) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| PostgreSQL (two copies) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| PostgreSQL (two copies) | Origin list price · Control-plane calls | 0 | USD/requests |
| PostgreSQL (two copies) | Representative item size | 1024 | bytes |
| PostgreSQL (two copies) | Strongly consistent read fraction | 1 | fraction |
| PostgreSQL (two copies) | Origin write-unit amplification | 1 | multiplier |
| PostgreSQL (two copies) | Target reads per point read | 1 | operations |
| PostgreSQL (two copies) | Target writes per item write | 1 | operations |
| PostgreSQL (two copies) | Target price guess · read | 0 | USD/read |
| PostgreSQL (two copies) | Target price guess · write | 0 | USD/write |
| PostgreSQL (two copies) | Target price guess · provider operation | 0 | USD/provider operation |
| PostgreSQL (two copies) | Target list price · GiB-month | 0.1 | USD/GiB-month |
| PostgreSQL (two copies) | Target price guess · published GiB | 0 | USD/published GiB |
| PostgreSQL (two copies) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| PostgreSQL (two copies) | Target list price · network GiB | 0.12 | USD/network GiB |
| PostgreSQL (two copies) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| PostgreSQL (two copies) | Target list price · vCPU-hour | 0.031611 | USD/vCPU-hour |
| PostgreSQL (two copies) | Target list price · GiB-hour | 0.004237 | USD/GiB-hour |
| PostgreSQL (two copies) | Target price guess · resource-hour | 0 | USD/resource-hour |
| PostgreSQL (two copies) | Target price guess · resource-month | 0 | USD/resource-month |
| PostgreSQL (two copies) | Target price guess · input token | 0 | USD/input token |
| PostgreSQL (two copies) | Target price guess · output token | 0 | USD/output token |
| PostgreSQL (two copies) | Target monthly base charge | 0 | USD/month |
| PostgreSQL (two copies) | Approximate target service minimum | 0 | USD/month |
| PostgreSQL (two copies) | Minimum primary CPU | 2 | vCPU |
| PostgreSQL (two copies) | Minimum primary RAM | 8 | GiB |
| PostgreSQL (two copies) | Minimum primary disk | 100 | GiB |
| PostgreSQL (two copies) | Additional full-price standby copy | 1 | 0 or 1 |
| PostgreSQL (two copies) | Allocated share of provisioned cost | 1 | fraction |
| PostgreSQL (two copies) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| PostgreSQL (two copies) | Planning peak / mean work | 2 | multiplier |
| PostgreSQL (two copies) | Planning primary CPU utilization | 0.7 | fraction |
| PostgreSQL (two copies) | Resident state reserved in RAM | 0.1 | fraction |
| PostgreSQL (two copies) | Planning disk utilization | 0.8 | fraction |
| PostgreSQL (two copies) | Maintenance and log disk reserve | 20 | GiB |
| PostgreSQL (two copies) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| PostgreSQL (two copies) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| PostgreSQL (two copies) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| PostgreSQL (two copies) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| PostgreSQL (two copies) | Dependent object sink write price guess | 0.000005 | USD/write |

* Reads and storage remain independent. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
* Planning estimate · editable authored rates and sizing assumptions dated 2026-10-22; not verified provider prices. us-east-1 → 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 is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* 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.
* The control plane and table facet describe the same family workload; allocate shared capacity once, not once per catalog facet.
* No transactional, global-table, Streams or scan tariff is inferred from ordinary on-demand point units.
* Self-hosted target: PostgreSQL (PostgreSQL License, [https://www.postgresql.org/about/licence/](https://www.postgresql.org/about/licence/)). Selected CPU, RAM and physical disk allocation grow with workload; no per-operation price is assumed. No vendor tariff: the target runs on the customer's Kubernetes nodes, so CPU, RAM and disk bill at the Kubernetes node reference rates, Compute Engine N2 in us-central1 (USD 0.031611/vCPU-hour, 0.004237/GiB-hour) with pd-balanced disk (0.10/GiB-month) and Premium Tier egress. The cost-optimized E2 series lists 0.02181159/vCPU-hour and 0.00292353/GiB-hour; AWS m6i/r6i and Azure D2s v5/E2s v5 both decompose to 0.033/vCPU-hour and 0.00375/GiB-hour. Requested CPU and RAM are billed; node bin-packing waste, system reservations and the cluster control-plane fee are not.
* Row-store throughput (capacityOpsPerVcpuSecond, default 1500) is measured-by-tensor9 as a lower bound: the DynamoDB adapter on Cloud SQL db-custom-2-7680 (2 vCPU, PostgreSQL 16, us-west1) served 2,974 ops/s of YCSB-A at 16 threads without recorded saturation (src/main/kotlin/t9/prime/equiv/generated/eval/CloudsqlPostgresqlYcsbAT16GoYcsbV1\_0\_0.kt). Published CPU-bound pgbench reaches 3,101 read-write transactions and 20,289 point reads per vCPU-second (AWS z1d.2xlarge, PostgreSQL 14.5), so actual capacity is likely higher. Reads and writes share one coefficient: at the same adapter version, read-only YCSB-C was not faster than 50%-update YCSB-A.
* Log-broker throughput (capacityStreamMiBPerVcpuSecond 20 at 0.5 utilization, 4 GiB RAM per vCPU) is provider-documented by Google Managed Service for Apache Kafka sizing ([https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size](https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size)): write-equivalent bytes are replicated writes plus a quarter of reads. Producer batches below 10 KB lower per-CPU throughput; that penalty is not modeled.
* Disk utilization 0.8 is provider-documented headroom below Cloud SQL automatic storage increase, which triggers near 91-95% full ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)). The 20 GiB reserve exceeds PostgreSQL's 1 GB default max\_wal\_size; the remainder of that reserve is unmeasured.
* CPU tiers, 4 GiB per vCPU, at most 6.5 GiB per vCPU, 96 vCPU and 65,536 GiB disk follow Cloud SQL Enterprise custom machine limits (provider-documented, same page); 624 GiB is 96 × 6.5. Targets billed per node, unit or throughput unit are sized by their backend instead.
* No public evidence: peak/mean work (2) and the RAM working-set fraction (0.1). Proposed measurements: the p99 one-minute rate over the monthly mean from customer CloudWatch metrics; the buffer hit ratio while stepping RAM under a fixed YCSB-B load.
* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.
* The operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
* AWS Price List API, AmazonDynamoDB offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json)
* Amazon DynamoDB pricing: [https://aws.amazon.com/dynamodb/pricing/](https://aws.amazon.com/dynamodb/pricing/)
* Compute Engine general-purpose machine pricing: [https://cloud.google.com/products/compute/pricing/general-purpose](https://cloud.google.com/products/compute/pricing/general-purpose)
* Disk and image pricing: [https://cloud.google.com/compute/disks-image-pricing](https://cloud.google.com/compute/disks-image-pricing)
* Network pricing: [https://cloud.google.com/vpc/network-pricing](https://cloud.google.com/vpc/network-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.
* 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-271febef7b5ad970d96d5373c36c91bf2d6b17bb` / `2026-10-22.planning.2`. Curve: `workload-2`.

Sources: [AWS Price List API, AmazonDynamoDB offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json), [Amazon DynamoDB pricing](https://aws.amazon.com/dynamodb/pricing/), [Compute Engine general-purpose machine pricing](https://cloud.google.com/products/compute/pricing/general-purpose), [Disk and image pricing](https://cloud.google.com/compute/disks-image-pricing), [Network pricing](https://cloud.google.com/vpc/network-pricing).

### DynamoDB · Stored data

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

![DynamoDB · Stored data: monthly service charges by Stored data. Exact values are in the following table.](/images/diagrams/service-cost/7a693bc45223c29b46495062c12da4f5dbdf996d9c61806494dfd1dc0ba299ed-light.svg)

![DynamoDB · Stored data: monthly service charges by Stored data. Exact values are in the following table.](/images/diagrams/service-cost/40b2cf0abca756564400e26e6c1d6b630229d29285168629b2aed1215bb5b3a1-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) | DynamoDB | Target scenario | PostgreSQL | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | PostgreSQL (one copy) | 80.89614 | 80.89614 |
| 0 | 0 | PostgreSQL (two copies) | 161.79228 | 161.79228 |
| 10 | 2.5 | PostgreSQL (one copy) | 80.89614 | 78.39614 |
| 10 | 2.5 | PostgreSQL (two copies) | 161.79228 | 159.29228 |
| 100 | 25 | PostgreSQL (one copy) | 92.08216 | 67.08216 |
| 100 | 25 | PostgreSQL (two copies) | 184.16432 | 159.16432 |
| 1000 | 250 | PostgreSQL (one copy) | 806.01748 | 556.01748 |
| 1000 | 250 | PostgreSQL (two copies) | 1612.03496 | 1362.03496 |
| 10000 | 2500 | PostgreSQL (one copy) | Unpriced | Unavailable |
| 10000 | 2500 | PostgreSQL (two copies) | Unpriced | Unavailable |
| 100000 | 25000 | PostgreSQL (one copy) | Unpriced | Unavailable |
| 100000 | 25000 | 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 / PostgreSQL (one copy) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 0 GiB-month / PostgreSQL (two copies) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10 GiB-month / PostgreSQL (one copy) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 10 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10 GiB-month / PostgreSQL (two copies) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 10 | `service-adapter-planning-2026-10-22.1` | None reported |
| 100 GiB-month / PostgreSQL (one copy) | PlanningAssumption | 0 / 0 | 0 | 2 | 10 | 150 | 100 | `service-adapter-planning-2026-10-22.1` | None reported |
| 100 GiB-month / PostgreSQL (two copies) | PlanningAssumption | 0 / 0 | 0 | 2 | 10 | 150 | 100 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1000 GiB-month / PostgreSQL (one copy) | PlanningAssumption | 0 / 0 | 0 | 16 | 100 | 1275 | 1000 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1000 GiB-month / PostgreSQL (two copies) | PlanningAssumption | 0 / 0 | 0 | 16 | 100 | 1275 | 1000 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10000 GiB-month / 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 / 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 / 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 / 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 operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| PostgreSQL (one copy) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| PostgreSQL (one copy) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| PostgreSQL (one copy) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| PostgreSQL (one copy) | Origin list price · Control-plane calls | 0 | USD/requests |
| PostgreSQL (one copy) | Representative item size | 1024 | bytes |
| PostgreSQL (one copy) | Strongly consistent read fraction | 1 | fraction |
| PostgreSQL (one copy) | Origin write-unit amplification | 1 | multiplier |
| PostgreSQL (one copy) | Target reads per point read | 1 | operations |
| PostgreSQL (one copy) | Target writes per item write | 1 | operations |
| PostgreSQL (one copy) | Target price guess · read | 0 | USD/read |
| PostgreSQL (one copy) | Target price guess · write | 0 | USD/write |
| PostgreSQL (one copy) | Target price guess · provider operation | 0 | USD/provider operation |
| PostgreSQL (one copy) | Target list price · GiB-month | 0.1 | USD/GiB-month |
| PostgreSQL (one copy) | Target price guess · published GiB | 0 | USD/published GiB |
| PostgreSQL (one copy) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| PostgreSQL (one copy) | Target list price · network GiB | 0.12 | USD/network GiB |
| PostgreSQL (one copy) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| PostgreSQL (one copy) | Target list price · vCPU-hour | 0.031611 | USD/vCPU-hour |
| PostgreSQL (one copy) | Target list price · GiB-hour | 0.004237 | USD/GiB-hour |
| PostgreSQL (one copy) | Target price guess · resource-hour | 0 | USD/resource-hour |
| PostgreSQL (one copy) | Target price guess · resource-month | 0 | USD/resource-month |
| PostgreSQL (one copy) | Target price guess · input token | 0 | USD/input token |
| PostgreSQL (one copy) | Target price guess · output token | 0 | USD/output token |
| PostgreSQL (one copy) | Target monthly base charge | 0 | USD/month |
| PostgreSQL (one copy) | Approximate target service minimum | 0 | USD/month |
| PostgreSQL (one copy) | Minimum primary CPU | 2 | vCPU |
| PostgreSQL (one copy) | Minimum primary RAM | 8 | GiB |
| PostgreSQL (one copy) | Minimum primary disk | 100 | GiB |
| PostgreSQL (one copy) | Additional full-price standby copy | 0 | 0 or 1 |
| PostgreSQL (one copy) | Allocated share of provisioned cost | 1 | fraction |
| PostgreSQL (one copy) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| PostgreSQL (one copy) | Planning peak / mean work | 2 | multiplier |
| PostgreSQL (one copy) | Planning primary CPU utilization | 0.7 | fraction |
| PostgreSQL (one copy) | Resident state reserved in RAM | 0.1 | fraction |
| PostgreSQL (one copy) | Planning disk utilization | 0.8 | fraction |
| PostgreSQL (one copy) | Maintenance and log disk reserve | 20 | GiB |
| PostgreSQL (one copy) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| PostgreSQL (one copy) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| PostgreSQL (one copy) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| PostgreSQL (one copy) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| PostgreSQL (one copy) | Dependent object sink write price guess | 0.000005 | USD/write |
| PostgreSQL (two copies) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| PostgreSQL (two copies) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| PostgreSQL (two copies) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| PostgreSQL (two copies) | Origin list price · Control-plane calls | 0 | USD/requests |
| PostgreSQL (two copies) | Representative item size | 1024 | bytes |
| PostgreSQL (two copies) | Strongly consistent read fraction | 1 | fraction |
| PostgreSQL (two copies) | Origin write-unit amplification | 1 | multiplier |
| PostgreSQL (two copies) | Target reads per point read | 1 | operations |
| PostgreSQL (two copies) | Target writes per item write | 1 | operations |
| PostgreSQL (two copies) | Target price guess · read | 0 | USD/read |
| PostgreSQL (two copies) | Target price guess · write | 0 | USD/write |
| PostgreSQL (two copies) | Target price guess · provider operation | 0 | USD/provider operation |
| PostgreSQL (two copies) | Target list price · GiB-month | 0.1 | USD/GiB-month |
| PostgreSQL (two copies) | Target price guess · published GiB | 0 | USD/published GiB |
| PostgreSQL (two copies) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| PostgreSQL (two copies) | Target list price · network GiB | 0.12 | USD/network GiB |
| PostgreSQL (two copies) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| PostgreSQL (two copies) | Target list price · vCPU-hour | 0.031611 | USD/vCPU-hour |
| PostgreSQL (two copies) | Target list price · GiB-hour | 0.004237 | USD/GiB-hour |
| PostgreSQL (two copies) | Target price guess · resource-hour | 0 | USD/resource-hour |
| PostgreSQL (two copies) | Target price guess · resource-month | 0 | USD/resource-month |
| PostgreSQL (two copies) | Target price guess · input token | 0 | USD/input token |
| PostgreSQL (two copies) | Target price guess · output token | 0 | USD/output token |
| PostgreSQL (two copies) | Target monthly base charge | 0 | USD/month |
| PostgreSQL (two copies) | Approximate target service minimum | 0 | USD/month |
| PostgreSQL (two copies) | Minimum primary CPU | 2 | vCPU |
| PostgreSQL (two copies) | Minimum primary RAM | 8 | GiB |
| PostgreSQL (two copies) | Minimum primary disk | 100 | GiB |
| PostgreSQL (two copies) | Additional full-price standby copy | 1 | 0 or 1 |
| PostgreSQL (two copies) | Allocated share of provisioned cost | 1 | fraction |
| PostgreSQL (two copies) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| PostgreSQL (two copies) | Planning peak / mean work | 2 | multiplier |
| PostgreSQL (two copies) | Planning primary CPU utilization | 0.7 | fraction |
| PostgreSQL (two copies) | Resident state reserved in RAM | 0.1 | fraction |
| PostgreSQL (two copies) | Planning disk utilization | 0.8 | fraction |
| PostgreSQL (two copies) | Maintenance and log disk reserve | 20 | GiB |
| PostgreSQL (two copies) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| PostgreSQL (two copies) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| PostgreSQL (two copies) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| PostgreSQL (two copies) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| 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. us-east-1 → 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 is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* 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.
* The control plane and table facet describe the same family workload; allocate shared capacity once, not once per catalog facet.
* No transactional, global-table, Streams or scan tariff is inferred from ordinary on-demand point units.
* Self-hosted target: PostgreSQL (PostgreSQL License, [https://www.postgresql.org/about/licence/](https://www.postgresql.org/about/licence/)). Selected CPU, RAM and physical disk allocation grow with workload; no per-operation price is assumed. No vendor tariff: the target runs on the customer's Kubernetes nodes, so CPU, RAM and disk bill at the Kubernetes node reference rates, Compute Engine N2 in us-central1 (USD 0.031611/vCPU-hour, 0.004237/GiB-hour) with pd-balanced disk (0.10/GiB-month) and Premium Tier egress. The cost-optimized E2 series lists 0.02181159/vCPU-hour and 0.00292353/GiB-hour; AWS m6i/r6i and Azure D2s v5/E2s v5 both decompose to 0.033/vCPU-hour and 0.00375/GiB-hour. Requested CPU and RAM are billed; node bin-packing waste, system reservations and the cluster control-plane fee are not.
* Row-store throughput (capacityOpsPerVcpuSecond, default 1500) is measured-by-tensor9 as a lower bound: the DynamoDB adapter on Cloud SQL db-custom-2-7680 (2 vCPU, PostgreSQL 16, us-west1) served 2,974 ops/s of YCSB-A at 16 threads without recorded saturation (src/main/kotlin/t9/prime/equiv/generated/eval/CloudsqlPostgresqlYcsbAT16GoYcsbV1\_0\_0.kt). Published CPU-bound pgbench reaches 3,101 read-write transactions and 20,289 point reads per vCPU-second (AWS z1d.2xlarge, PostgreSQL 14.5), so actual capacity is likely higher. Reads and writes share one coefficient: at the same adapter version, read-only YCSB-C was not faster than 50%-update YCSB-A.
* Log-broker throughput (capacityStreamMiBPerVcpuSecond 20 at 0.5 utilization, 4 GiB RAM per vCPU) is provider-documented by Google Managed Service for Apache Kafka sizing ([https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size](https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size)): write-equivalent bytes are replicated writes plus a quarter of reads. Producer batches below 10 KB lower per-CPU throughput; that penalty is not modeled.
* Disk utilization 0.8 is provider-documented headroom below Cloud SQL automatic storage increase, which triggers near 91-95% full ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)). The 20 GiB reserve exceeds PostgreSQL's 1 GB default max\_wal\_size; the remainder of that reserve is unmeasured.
* CPU tiers, 4 GiB per vCPU, at most 6.5 GiB per vCPU, 96 vCPU and 65,536 GiB disk follow Cloud SQL Enterprise custom machine limits (provider-documented, same page); 624 GiB is 96 × 6.5. Targets billed per node, unit or throughput unit are sized by their backend instead.
* No public evidence: peak/mean work (2) and the RAM working-set fraction (0.1). Proposed measurements: the p99 one-minute rate over the monthly mean from customer CloudWatch metrics; the buffer hit ratio while stepping RAM under a fixed YCSB-B load.
* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.
* The operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
* AWS Price List API, AmazonDynamoDB offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json)
* Amazon DynamoDB pricing: [https://aws.amazon.com/dynamodb/pricing/](https://aws.amazon.com/dynamodb/pricing/)
* Compute Engine general-purpose machine pricing: [https://cloud.google.com/products/compute/pricing/general-purpose](https://cloud.google.com/products/compute/pricing/general-purpose)
* Disk and image pricing: [https://cloud.google.com/compute/disks-image-pricing](https://cloud.google.com/compute/disks-image-pricing)
* Network pricing: [https://cloud.google.com/vpc/network-pricing](https://cloud.google.com/vpc/network-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.
* 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-271febef7b5ad970d96d5373c36c91bf2d6b17bb` / `2026-10-22.planning.2`. Curve: `workload-3`.

Sources: [AWS Price List API, AmazonDynamoDB offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json), [Amazon DynamoDB pricing](https://aws.amazon.com/dynamodb/pricing/), [Compute Engine general-purpose machine pricing](https://cloud.google.com/products/compute/pricing/general-purpose), [Disk and image pricing](https://cloud.google.com/compute/disks-image-pricing), [Network pricing](https://cloud.google.com/vpc/network-pricing).

## DynamoDB → Scaleway Managed Database for PostgreSQL

Origin API: `aws::1.0.0::dynamodb::control`. Target backend: `scaleway::1.0.0::rdb::postgresql`.

### DynamoDB · DynamoDB read units

Estimated monthly service charges by DynamoDB read units. Adapter hosting and Tensor9 fees are excluded. Source: us-east-1; target: fr-par; currency: USD.

![DynamoDB · DynamoDB read units: monthly service charges by DynamoDB read units. Exact values are in the following table.](/images/diagrams/service-cost/3d6cecd11259413f374a82a3866730d92eb8c4eb73d36dbd9d0bd2cf99e4c020-light.svg)

![DynamoDB · DynamoDB read units: monthly service charges by DynamoDB read units. Exact values are in the following table.](/images/diagrams/service-cost/076149b5af03de803d1d2dd084a7f7e101dc26f9e749b11a33d069722eb139d0-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.

| DynamoDB read units (per second) | DynamoDB | Target scenario | Scaleway Managed Database for PostgreSQL | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | Scaleway Managed Database for PostgreSQL (one copy) | 101.102715 | 101.102715 |
| 0 | 0 | Scaleway Managed Database for PostgreSQL (two copies) | 154.68715395 | 154.68715395 |
| 1 | 0.3285 | Scaleway Managed Database for PostgreSQL (one copy) | 101.102715 | 100.774215 |
| 1 | 0.3285 | Scaleway Managed Database for PostgreSQL (two copies) | 154.68715395 | 154.35865395 |
| 10 | 3.285 | Scaleway Managed Database for PostgreSQL (one copy) | 101.102715 | 97.817715 |
| 10 | 3.285 | Scaleway Managed Database for PostgreSQL (two copies) | 154.68715395 | 151.40215395 |
| 100 | 32.85 | Scaleway Managed Database for PostgreSQL (one copy) | 101.102715 | 68.252715 |
| 100 | 32.85 | Scaleway Managed Database for PostgreSQL (two copies) | 154.68715395 | 121.83715395 |
| 1000 | 328.5 | Scaleway Managed Database for PostgreSQL (one copy) | 101.102715 | -227.397285 |
| 1000 | 328.5 | Scaleway Managed Database for PostgreSQL (two copies) | 154.68715395 | -173.81284605 |
| 10000 | 3285 | Scaleway Managed Database for PostgreSQL (one copy) | 1450.744965 | -1834.255035 |
| 10000 | 3285 | Scaleway Managed Database for PostgreSQL (two copies) | 2219.63979645 | -1065.36020355 |

**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 / Scaleway Managed Database for PostgreSQL (one copy) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 0 per second / Scaleway Managed Database for PostgreSQL (two copies) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1 per second / Scaleway Managed Database for PostgreSQL (one copy) | PlanningAssumption | 1 / 2 | 0.001904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1 per second / Scaleway Managed Database for PostgreSQL (two copies) | PlanningAssumption | 1 / 2 | 0.001904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10 per second / Scaleway Managed Database for PostgreSQL (one copy) | PlanningAssumption | 10 / 20 | 0.01904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10 per second / Scaleway Managed Database for PostgreSQL (two copies) | PlanningAssumption | 10 / 20 | 0.01904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 100 per second / Scaleway Managed Database for PostgreSQL (one copy) | PlanningAssumption | 100 / 200 | 0.1904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 100 per second / Scaleway Managed Database for PostgreSQL (two copies) | PlanningAssumption | 100 / 200 | 0.1904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1000 per second / Scaleway Managed Database for PostgreSQL (one copy) | PlanningAssumption | 1000 / 2000 | 1.904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1000 per second / Scaleway Managed Database for PostgreSQL (two copies) | PlanningAssumption | 1000 / 2000 | 1.904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10000 per second / Scaleway Managed Database for PostgreSQL (one copy) | PlanningAssumption | 10000 / 20000 | 19.04761904761904761904761904761905 | 32 | 128 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10000 per second / Scaleway Managed Database for PostgreSQL (two copies) | PlanningAssumption | 10000 / 20000 | 19.04761904761904761904761904761905 | 32 | 128 | 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 operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Scaleway Managed Database for PostgreSQL (one copy) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| Scaleway Managed Database for PostgreSQL (one copy) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| Scaleway Managed Database for PostgreSQL (one copy) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| Scaleway Managed Database for PostgreSQL (one copy) | Origin list price · Control-plane calls | 0 | USD/requests |
| Scaleway Managed Database for PostgreSQL (one copy) | Representative item size | 1024 | bytes |
| Scaleway Managed Database for PostgreSQL (one copy) | Strongly consistent read fraction | 1 | fraction |
| Scaleway Managed Database for PostgreSQL (one copy) | Origin write-unit amplification | 1 | multiplier |
| Scaleway Managed Database for PostgreSQL (one copy) | Target reads per point read | 1 | operations |
| Scaleway Managed Database for PostgreSQL (one copy) | Target writes per item write | 1 | operations |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · read | 0 | USD/read |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · write | 0 | USD/write |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · provider operation | 0 | USD/provider operation |
| Scaleway Managed Database for PostgreSQL (one copy) | Target list price · GiB-month | 0.11126565 | USD/GiB-month |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · published GiB | 0 | USD/published GiB |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · network GiB | 0 | USD/network GiB |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Scaleway Managed Database for PostgreSQL (one copy) | Target list price · vCPU-hour | 0.0367275 | USD/vCPU-hour |
| Scaleway Managed Database for PostgreSQL (one copy) | Target list price · GiB-hour | 0.006225 | USD/GiB-hour |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · resource-hour | 0 | USD/resource-hour |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · resource-month | 0 | USD/resource-month |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · input token | 0 | USD/input token |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · output token | 0 | USD/output token |
| Scaleway Managed Database for PostgreSQL (one copy) | Target monthly base charge | 0 | USD/month |
| Scaleway Managed Database for PostgreSQL (one copy) | Target service minimum | 89.97615 | USD/month |
| Scaleway Managed Database for PostgreSQL (one copy) | Minimum primary CPU | 2 | vCPU |
| Scaleway Managed Database for PostgreSQL (one copy) | Minimum primary RAM | 8 | GiB |
| Scaleway Managed Database for PostgreSQL (one copy) | Minimum primary disk | 100 | GiB |
| Scaleway Managed Database for PostgreSQL (one copy) | Additional full-price standby copy | 0 | 0 or 1 |
| Scaleway Managed Database for PostgreSQL (one copy) | Allocated share of provisioned cost | 1 | fraction |
| Scaleway Managed Database for PostgreSQL (one copy) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Scaleway Managed Database for PostgreSQL (one copy) | Planning peak / mean work | 2 | multiplier |
| Scaleway Managed Database for PostgreSQL (one copy) | Planning primary CPU utilization | 0.7 | fraction |
| Scaleway Managed Database for PostgreSQL (one copy) | Resident state reserved in RAM | 0.1 | fraction |
| Scaleway Managed Database for PostgreSQL (one copy) | Planning disk utilization | 0.8 | fraction |
| Scaleway Managed Database for PostgreSQL (one copy) | Maintenance and log disk reserve | 20 | GiB |
| Scaleway Managed Database for PostgreSQL (one copy) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Scaleway Managed Database for PostgreSQL (one copy) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Scaleway Managed Database for PostgreSQL (one copy) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Scaleway Managed Database for PostgreSQL (one copy) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Scaleway Managed Database for PostgreSQL (one copy) | Dependent object sink write price guess | 0.000005 | USD/write |
| Scaleway Managed Database for PostgreSQL (two copies) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| Scaleway Managed Database for PostgreSQL (two copies) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| Scaleway Managed Database for PostgreSQL (two copies) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| Scaleway Managed Database for PostgreSQL (two copies) | Origin list price · Control-plane calls | 0 | USD/requests |
| Scaleway Managed Database for PostgreSQL (two copies) | Representative item size | 1024 | bytes |
| Scaleway Managed Database for PostgreSQL (two copies) | Strongly consistent read fraction | 1 | fraction |
| Scaleway Managed Database for PostgreSQL (two copies) | Origin write-unit amplification | 1 | multiplier |
| Scaleway Managed Database for PostgreSQL (two copies) | Target reads per point read | 1 | operations |
| Scaleway Managed Database for PostgreSQL (two copies) | Target writes per item write | 1 | operations |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · read | 0 | USD/read |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · write | 0 | USD/write |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · provider operation | 0 | USD/provider operation |
| Scaleway Managed Database for PostgreSQL (two copies) | Target list price · GiB-month | 0.11126565 | USD/GiB-month |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · published GiB | 0 | USD/published GiB |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · network GiB | 0 | USD/network GiB |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Scaleway Managed Database for PostgreSQL (two copies) | Target list price · vCPU-hour | 0.0367275 | USD/vCPU-hour |
| Scaleway Managed Database for PostgreSQL (two copies) | Target list price · GiB-hour | 0.006225 | USD/GiB-hour |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · resource-hour | 0 | USD/resource-hour |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · resource-month | 0 | USD/resource-month |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · input token | 0 | USD/input token |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · output token | 0 | USD/output token |
| Scaleway Managed Database for PostgreSQL (two copies) | Target monthly base charge | 0 | USD/month |
| Scaleway Managed Database for PostgreSQL (two copies) | Target service minimum | 89.97615 | USD/month |
| Scaleway Managed Database for PostgreSQL (two copies) | Minimum primary CPU | 2 | vCPU |
| Scaleway Managed Database for PostgreSQL (two copies) | Minimum primary RAM | 8 | GiB |
| Scaleway Managed Database for PostgreSQL (two copies) | Minimum primary disk | 100 | GiB |
| Scaleway Managed Database for PostgreSQL (two copies) | Additional full-price standby copy | 1 | 0 or 1 |
| Scaleway Managed Database for PostgreSQL (two copies) | Allocated share of provisioned cost | 1 | fraction |
| Scaleway Managed Database for PostgreSQL (two copies) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Scaleway Managed Database for PostgreSQL (two copies) | Planning peak / mean work | 2 | multiplier |
| Scaleway Managed Database for PostgreSQL (two copies) | Planning primary CPU utilization | 0.7 | fraction |
| Scaleway Managed Database for PostgreSQL (two copies) | Resident state reserved in RAM | 0.1 | fraction |
| Scaleway Managed Database for PostgreSQL (two copies) | Planning disk utilization | 0.8 | fraction |
| Scaleway Managed Database for PostgreSQL (two copies) | Maintenance and log disk reserve | 20 | GiB |
| Scaleway Managed Database for PostgreSQL (two copies) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Scaleway Managed Database for PostgreSQL (two copies) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Scaleway Managed Database for PostgreSQL (two copies) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Scaleway Managed Database for PostgreSQL (two copies) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Scaleway Managed Database for PostgreSQL (two copies) | Dependent object sink write price guess | 0.000005 | USD/write |

* Writes and storage remain independent. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
* Planning estimate · editable authored rates and sizing assumptions dated 2026-10-22; not verified provider prices. us-east-1 → fr-par, 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 is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* 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.
* The control plane and table facet describe the same family workload; allocate shared capacity once, not once per catalog facet.
* No transactional, global-table, Streams or scan tariff is inferred from ordinary on-demand point units.
* Scaleway Managed Database for PostgreSQL at Production Optimized (PRO2) prices in EUR converted at the ECB reference rate. A high-availability or replica node bills Scaleway's 'Additional nodes' price, EUR 0.0583 per hour for PRO2-XXS, 53% of the main node. Scaleway lists no egress charge for Managed Databases, so selected network is not charged. Cost Optimized ranges (DB-DEV-S from EUR 0.0156 per hour), Block Storage 15K and backups (EUR 0.03 per GB-month) 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 operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
* AWS Price List API, AmazonDynamoDB offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json)
* Amazon DynamoDB pricing: [https://aws.amazon.com/dynamodb/pricing/](https://aws.amazon.com/dynamodb/pricing/)
* Scaleway Managed Databases pricing: [https://www.scaleway.com/en/pricing/managed-databases/](https://www.scaleway.com/en/pricing/managed-databases/)

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.
* 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-a8af2fac3e931fad8397d4f3a601989b987a7744` / `2026-10-22.planning.2`. Curve: `workload-1`.

Sources: [AWS Price List API, AmazonDynamoDB offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json), [Amazon DynamoDB pricing](https://aws.amazon.com/dynamodb/pricing/), [Scaleway Managed Databases pricing](https://www.scaleway.com/en/pricing/managed-databases/).

### DynamoDB · DynamoDB write units

Estimated monthly service charges by DynamoDB write units. Adapter hosting and Tensor9 fees are excluded. Source: us-east-1; target: fr-par; currency: USD.

![DynamoDB · DynamoDB write units: monthly service charges by DynamoDB write units. Exact values are in the following table.](/images/diagrams/service-cost/90ecebd45a33300a00c15037cd6d23923d7bfbbe56ed44cba0042702c9f75656-light.svg)

![DynamoDB · DynamoDB write units: monthly service charges by DynamoDB write units. Exact values are in the following table.](/images/diagrams/service-cost/a7a968a8f7a8e687adb944ba4933fb790fe8c043cd0ba64cf2f8ebf144d08d40-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.

| DynamoDB write units (per second) | DynamoDB | Target scenario | Scaleway Managed Database for PostgreSQL | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | Scaleway Managed Database for PostgreSQL (one copy) | 101.102715 | 101.102715 |
| 0 | 0 | Scaleway Managed Database for PostgreSQL (two copies) | 154.68715395 | 154.68715395 |
| 1 | 1.6425 | Scaleway Managed Database for PostgreSQL (one copy) | 101.102715 | 99.460215 |
| 1 | 1.6425 | Scaleway Managed Database for PostgreSQL (two copies) | 154.68715395 | 153.04465395 |
| 10 | 16.425 | Scaleway Managed Database for PostgreSQL (one copy) | 101.102715 | 84.677715 |
| 10 | 16.425 | Scaleway Managed Database for PostgreSQL (two copies) | 154.68715395 | 138.26215395 |
| 100 | 164.25 | Scaleway Managed Database for PostgreSQL (one copy) | 101.102715 | -63.147285 |
| 100 | 164.25 | Scaleway Managed Database for PostgreSQL (two copies) | 154.68715395 | -9.56284605 |
| 1000 | 1642.5 | Scaleway Managed Database for PostgreSQL (one copy) | 101.102715 | -1541.397285 |
| 1000 | 1642.5 | Scaleway Managed Database for PostgreSQL (two copies) | 154.68715395 | -1487.81284605 |
| 10000 | 16425 | Scaleway Managed Database for PostgreSQL (one copy) | 1450.744965 | -14974.255035 |
| 10000 | 16425 | Scaleway Managed Database for PostgreSQL (two copies) | 2219.63979645 | -14205.36020355 |

**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 / Scaleway Managed Database for PostgreSQL (one copy) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 0 per second / Scaleway Managed Database for PostgreSQL (two copies) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1 per second / Scaleway Managed Database for PostgreSQL (one copy) | PlanningAssumption | 1 / 2 | 0.001904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1 per second / Scaleway Managed Database for PostgreSQL (two copies) | PlanningAssumption | 1 / 2 | 0.001904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10 per second / Scaleway Managed Database for PostgreSQL (one copy) | PlanningAssumption | 10 / 20 | 0.01904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10 per second / Scaleway Managed Database for PostgreSQL (two copies) | PlanningAssumption | 10 / 20 | 0.01904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 100 per second / Scaleway Managed Database for PostgreSQL (one copy) | PlanningAssumption | 100 / 200 | 0.1904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 100 per second / Scaleway Managed Database for PostgreSQL (two copies) | PlanningAssumption | 100 / 200 | 0.1904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1000 per second / Scaleway Managed Database for PostgreSQL (one copy) | PlanningAssumption | 1000 / 2000 | 1.904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1000 per second / Scaleway Managed Database for PostgreSQL (two copies) | PlanningAssumption | 1000 / 2000 | 1.904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10000 per second / Scaleway Managed Database for PostgreSQL (one copy) | PlanningAssumption | 10000 / 20000 | 19.04761904761904761904761904761905 | 32 | 128 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10000 per second / Scaleway Managed Database for PostgreSQL (two copies) | PlanningAssumption | 10000 / 20000 | 19.04761904761904761904761904761905 | 32 | 128 | 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 operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Scaleway Managed Database for PostgreSQL (one copy) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| Scaleway Managed Database for PostgreSQL (one copy) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| Scaleway Managed Database for PostgreSQL (one copy) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| Scaleway Managed Database for PostgreSQL (one copy) | Origin list price · Control-plane calls | 0 | USD/requests |
| Scaleway Managed Database for PostgreSQL (one copy) | Representative item size | 1024 | bytes |
| Scaleway Managed Database for PostgreSQL (one copy) | Strongly consistent read fraction | 1 | fraction |
| Scaleway Managed Database for PostgreSQL (one copy) | Origin write-unit amplification | 1 | multiplier |
| Scaleway Managed Database for PostgreSQL (one copy) | Target reads per point read | 1 | operations |
| Scaleway Managed Database for PostgreSQL (one copy) | Target writes per item write | 1 | operations |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · read | 0 | USD/read |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · write | 0 | USD/write |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · provider operation | 0 | USD/provider operation |
| Scaleway Managed Database for PostgreSQL (one copy) | Target list price · GiB-month | 0.11126565 | USD/GiB-month |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · published GiB | 0 | USD/published GiB |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · network GiB | 0 | USD/network GiB |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Scaleway Managed Database for PostgreSQL (one copy) | Target list price · vCPU-hour | 0.0367275 | USD/vCPU-hour |
| Scaleway Managed Database for PostgreSQL (one copy) | Target list price · GiB-hour | 0.006225 | USD/GiB-hour |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · resource-hour | 0 | USD/resource-hour |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · resource-month | 0 | USD/resource-month |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · input token | 0 | USD/input token |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · output token | 0 | USD/output token |
| Scaleway Managed Database for PostgreSQL (one copy) | Target monthly base charge | 0 | USD/month |
| Scaleway Managed Database for PostgreSQL (one copy) | Target service minimum | 89.97615 | USD/month |
| Scaleway Managed Database for PostgreSQL (one copy) | Minimum primary CPU | 2 | vCPU |
| Scaleway Managed Database for PostgreSQL (one copy) | Minimum primary RAM | 8 | GiB |
| Scaleway Managed Database for PostgreSQL (one copy) | Minimum primary disk | 100 | GiB |
| Scaleway Managed Database for PostgreSQL (one copy) | Additional full-price standby copy | 0 | 0 or 1 |
| Scaleway Managed Database for PostgreSQL (one copy) | Allocated share of provisioned cost | 1 | fraction |
| Scaleway Managed Database for PostgreSQL (one copy) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Scaleway Managed Database for PostgreSQL (one copy) | Planning peak / mean work | 2 | multiplier |
| Scaleway Managed Database for PostgreSQL (one copy) | Planning primary CPU utilization | 0.7 | fraction |
| Scaleway Managed Database for PostgreSQL (one copy) | Resident state reserved in RAM | 0.1 | fraction |
| Scaleway Managed Database for PostgreSQL (one copy) | Planning disk utilization | 0.8 | fraction |
| Scaleway Managed Database for PostgreSQL (one copy) | Maintenance and log disk reserve | 20 | GiB |
| Scaleway Managed Database for PostgreSQL (one copy) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Scaleway Managed Database for PostgreSQL (one copy) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Scaleway Managed Database for PostgreSQL (one copy) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Scaleway Managed Database for PostgreSQL (one copy) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Scaleway Managed Database for PostgreSQL (one copy) | Dependent object sink write price guess | 0.000005 | USD/write |
| Scaleway Managed Database for PostgreSQL (two copies) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| Scaleway Managed Database for PostgreSQL (two copies) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| Scaleway Managed Database for PostgreSQL (two copies) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| Scaleway Managed Database for PostgreSQL (two copies) | Origin list price · Control-plane calls | 0 | USD/requests |
| Scaleway Managed Database for PostgreSQL (two copies) | Representative item size | 1024 | bytes |
| Scaleway Managed Database for PostgreSQL (two copies) | Strongly consistent read fraction | 1 | fraction |
| Scaleway Managed Database for PostgreSQL (two copies) | Origin write-unit amplification | 1 | multiplier |
| Scaleway Managed Database for PostgreSQL (two copies) | Target reads per point read | 1 | operations |
| Scaleway Managed Database for PostgreSQL (two copies) | Target writes per item write | 1 | operations |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · read | 0 | USD/read |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · write | 0 | USD/write |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · provider operation | 0 | USD/provider operation |
| Scaleway Managed Database for PostgreSQL (two copies) | Target list price · GiB-month | 0.11126565 | USD/GiB-month |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · published GiB | 0 | USD/published GiB |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · network GiB | 0 | USD/network GiB |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Scaleway Managed Database for PostgreSQL (two copies) | Target list price · vCPU-hour | 0.0367275 | USD/vCPU-hour |
| Scaleway Managed Database for PostgreSQL (two copies) | Target list price · GiB-hour | 0.006225 | USD/GiB-hour |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · resource-hour | 0 | USD/resource-hour |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · resource-month | 0 | USD/resource-month |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · input token | 0 | USD/input token |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · output token | 0 | USD/output token |
| Scaleway Managed Database for PostgreSQL (two copies) | Target monthly base charge | 0 | USD/month |
| Scaleway Managed Database for PostgreSQL (two copies) | Target service minimum | 89.97615 | USD/month |
| Scaleway Managed Database for PostgreSQL (two copies) | Minimum primary CPU | 2 | vCPU |
| Scaleway Managed Database for PostgreSQL (two copies) | Minimum primary RAM | 8 | GiB |
| Scaleway Managed Database for PostgreSQL (two copies) | Minimum primary disk | 100 | GiB |
| Scaleway Managed Database for PostgreSQL (two copies) | Additional full-price standby copy | 1 | 0 or 1 |
| Scaleway Managed Database for PostgreSQL (two copies) | Allocated share of provisioned cost | 1 | fraction |
| Scaleway Managed Database for PostgreSQL (two copies) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Scaleway Managed Database for PostgreSQL (two copies) | Planning peak / mean work | 2 | multiplier |
| Scaleway Managed Database for PostgreSQL (two copies) | Planning primary CPU utilization | 0.7 | fraction |
| Scaleway Managed Database for PostgreSQL (two copies) | Resident state reserved in RAM | 0.1 | fraction |
| Scaleway Managed Database for PostgreSQL (two copies) | Planning disk utilization | 0.8 | fraction |
| Scaleway Managed Database for PostgreSQL (two copies) | Maintenance and log disk reserve | 20 | GiB |
| Scaleway Managed Database for PostgreSQL (two copies) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Scaleway Managed Database for PostgreSQL (two copies) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Scaleway Managed Database for PostgreSQL (two copies) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Scaleway Managed Database for PostgreSQL (two copies) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Scaleway Managed Database for PostgreSQL (two copies) | Dependent object sink write price guess | 0.000005 | USD/write |

* Reads and storage remain independent. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
* Planning estimate · editable authored rates and sizing assumptions dated 2026-10-22; not verified provider prices. us-east-1 → fr-par, 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 is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* 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.
* The control plane and table facet describe the same family workload; allocate shared capacity once, not once per catalog facet.
* No transactional, global-table, Streams or scan tariff is inferred from ordinary on-demand point units.
* Scaleway Managed Database for PostgreSQL at Production Optimized (PRO2) prices in EUR converted at the ECB reference rate. A high-availability or replica node bills Scaleway's 'Additional nodes' price, EUR 0.0583 per hour for PRO2-XXS, 53% of the main node. Scaleway lists no egress charge for Managed Databases, so selected network is not charged. Cost Optimized ranges (DB-DEV-S from EUR 0.0156 per hour), Block Storage 15K and backups (EUR 0.03 per GB-month) 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 operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
* AWS Price List API, AmazonDynamoDB offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json)
* Amazon DynamoDB pricing: [https://aws.amazon.com/dynamodb/pricing/](https://aws.amazon.com/dynamodb/pricing/)
* Scaleway Managed Databases pricing: [https://www.scaleway.com/en/pricing/managed-databases/](https://www.scaleway.com/en/pricing/managed-databases/)

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.
* 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-a8af2fac3e931fad8397d4f3a601989b987a7744` / `2026-10-22.planning.2`. Curve: `workload-2`.

Sources: [AWS Price List API, AmazonDynamoDB offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json), [Amazon DynamoDB pricing](https://aws.amazon.com/dynamodb/pricing/), [Scaleway Managed Databases pricing](https://www.scaleway.com/en/pricing/managed-databases/).

### DynamoDB · Stored data

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

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

![DynamoDB · Stored data: monthly service charges by Stored data. Exact values are in the following table.](/images/diagrams/service-cost/8964c86795b5742da69ce64cd3844959c1677fccbd477238b051d0f77ddcc5fa-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) | DynamoDB | Target scenario | Scaleway Managed Database for PostgreSQL | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | Scaleway Managed Database for PostgreSQL (one copy) | 101.102715 | 101.102715 |
| 0 | 0 | Scaleway Managed Database for PostgreSQL (two copies) | 154.68715395 | 154.68715395 |
| 10 | 2.5 | Scaleway Managed Database for PostgreSQL (one copy) | 101.102715 | 98.602715 |
| 10 | 2.5 | Scaleway Managed Database for PostgreSQL (two copies) | 154.68715395 | 152.18715395 |
| 100 | 25 | Scaleway Managed Database for PostgreSQL (one copy) | 115.7544975 | 90.7544975 |
| 100 | 25 | Scaleway Managed Database for PostgreSQL (two copies) | 177.104381175 | 152.104381175 |
| 1000 | 250 | Scaleway Managed Database for PostgreSQL (one copy) | 1025.26590375 | 775.26590375 |
| 1000 | 250 | Scaleway Managed Database for PostgreSQL (two copies) | 1568.6568327375 | 1318.6568327375 |
| 10000 | 2500 | Scaleway Managed Database for PostgreSQL (one copy) | Unpriced | Unavailable |
| 10000 | 2500 | Scaleway Managed Database for PostgreSQL (two copies) | Unpriced | Unavailable |
| 100000 | 25000 | Scaleway Managed Database for PostgreSQL (one copy) | Unpriced | Unavailable |
| 100000 | 25000 | Scaleway Managed Database 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 / Scaleway Managed Database for PostgreSQL (one copy) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 0 GiB-month / Scaleway Managed Database for PostgreSQL (two copies) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10 GiB-month / Scaleway Managed Database for PostgreSQL (one copy) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 10 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10 GiB-month / Scaleway Managed Database for PostgreSQL (two copies) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 10 | `service-adapter-planning-2026-10-22.1` | None reported |
| 100 GiB-month / Scaleway Managed Database for PostgreSQL (one copy) | PlanningAssumption | 0 / 0 | 0 | 2 | 10 | 150 | 100 | `service-adapter-planning-2026-10-22.1` | None reported |
| 100 GiB-month / Scaleway Managed Database for PostgreSQL (two copies) | PlanningAssumption | 0 / 0 | 0 | 2 | 10 | 150 | 100 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1000 GiB-month / Scaleway Managed Database for PostgreSQL (one copy) | PlanningAssumption | 0 / 0 | 0 | 16 | 100 | 1275 | 1000 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1000 GiB-month / Scaleway Managed Database for PostgreSQL (two copies) | PlanningAssumption | 0 / 0 | 0 | 16 | 100 | 1275 | 1000 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10000 GiB-month / Scaleway Managed Database 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 / Scaleway Managed Database 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 / Scaleway Managed Database 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 / Scaleway Managed Database 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 operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Scaleway Managed Database for PostgreSQL (one copy) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| Scaleway Managed Database for PostgreSQL (one copy) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| Scaleway Managed Database for PostgreSQL (one copy) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| Scaleway Managed Database for PostgreSQL (one copy) | Origin list price · Control-plane calls | 0 | USD/requests |
| Scaleway Managed Database for PostgreSQL (one copy) | Representative item size | 1024 | bytes |
| Scaleway Managed Database for PostgreSQL (one copy) | Strongly consistent read fraction | 1 | fraction |
| Scaleway Managed Database for PostgreSQL (one copy) | Origin write-unit amplification | 1 | multiplier |
| Scaleway Managed Database for PostgreSQL (one copy) | Target reads per point read | 1 | operations |
| Scaleway Managed Database for PostgreSQL (one copy) | Target writes per item write | 1 | operations |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · read | 0 | USD/read |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · write | 0 | USD/write |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · provider operation | 0 | USD/provider operation |
| Scaleway Managed Database for PostgreSQL (one copy) | Target list price · GiB-month | 0.11126565 | USD/GiB-month |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · published GiB | 0 | USD/published GiB |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · network GiB | 0 | USD/network GiB |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Scaleway Managed Database for PostgreSQL (one copy) | Target list price · vCPU-hour | 0.0367275 | USD/vCPU-hour |
| Scaleway Managed Database for PostgreSQL (one copy) | Target list price · GiB-hour | 0.006225 | USD/GiB-hour |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · resource-hour | 0 | USD/resource-hour |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · resource-month | 0 | USD/resource-month |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · input token | 0 | USD/input token |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · output token | 0 | USD/output token |
| Scaleway Managed Database for PostgreSQL (one copy) | Target monthly base charge | 0 | USD/month |
| Scaleway Managed Database for PostgreSQL (one copy) | Target service minimum | 89.97615 | USD/month |
| Scaleway Managed Database for PostgreSQL (one copy) | Minimum primary CPU | 2 | vCPU |
| Scaleway Managed Database for PostgreSQL (one copy) | Minimum primary RAM | 8 | GiB |
| Scaleway Managed Database for PostgreSQL (one copy) | Minimum primary disk | 100 | GiB |
| Scaleway Managed Database for PostgreSQL (one copy) | Additional full-price standby copy | 0 | 0 or 1 |
| Scaleway Managed Database for PostgreSQL (one copy) | Allocated share of provisioned cost | 1 | fraction |
| Scaleway Managed Database for PostgreSQL (one copy) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Scaleway Managed Database for PostgreSQL (one copy) | Planning peak / mean work | 2 | multiplier |
| Scaleway Managed Database for PostgreSQL (one copy) | Planning primary CPU utilization | 0.7 | fraction |
| Scaleway Managed Database for PostgreSQL (one copy) | Resident state reserved in RAM | 0.1 | fraction |
| Scaleway Managed Database for PostgreSQL (one copy) | Planning disk utilization | 0.8 | fraction |
| Scaleway Managed Database for PostgreSQL (one copy) | Maintenance and log disk reserve | 20 | GiB |
| Scaleway Managed Database for PostgreSQL (one copy) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Scaleway Managed Database for PostgreSQL (one copy) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Scaleway Managed Database for PostgreSQL (one copy) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Scaleway Managed Database for PostgreSQL (one copy) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Scaleway Managed Database for PostgreSQL (one copy) | Dependent object sink write price guess | 0.000005 | USD/write |
| Scaleway Managed Database for PostgreSQL (two copies) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| Scaleway Managed Database for PostgreSQL (two copies) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| Scaleway Managed Database for PostgreSQL (two copies) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| Scaleway Managed Database for PostgreSQL (two copies) | Origin list price · Control-plane calls | 0 | USD/requests |
| Scaleway Managed Database for PostgreSQL (two copies) | Representative item size | 1024 | bytes |
| Scaleway Managed Database for PostgreSQL (two copies) | Strongly consistent read fraction | 1 | fraction |
| Scaleway Managed Database for PostgreSQL (two copies) | Origin write-unit amplification | 1 | multiplier |
| Scaleway Managed Database for PostgreSQL (two copies) | Target reads per point read | 1 | operations |
| Scaleway Managed Database for PostgreSQL (two copies) | Target writes per item write | 1 | operations |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · read | 0 | USD/read |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · write | 0 | USD/write |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · provider operation | 0 | USD/provider operation |
| Scaleway Managed Database for PostgreSQL (two copies) | Target list price · GiB-month | 0.11126565 | USD/GiB-month |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · published GiB | 0 | USD/published GiB |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · network GiB | 0 | USD/network GiB |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Scaleway Managed Database for PostgreSQL (two copies) | Target list price · vCPU-hour | 0.0367275 | USD/vCPU-hour |
| Scaleway Managed Database for PostgreSQL (two copies) | Target list price · GiB-hour | 0.006225 | USD/GiB-hour |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · resource-hour | 0 | USD/resource-hour |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · resource-month | 0 | USD/resource-month |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · input token | 0 | USD/input token |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · output token | 0 | USD/output token |
| Scaleway Managed Database for PostgreSQL (two copies) | Target monthly base charge | 0 | USD/month |
| Scaleway Managed Database for PostgreSQL (two copies) | Target service minimum | 89.97615 | USD/month |
| Scaleway Managed Database for PostgreSQL (two copies) | Minimum primary CPU | 2 | vCPU |
| Scaleway Managed Database for PostgreSQL (two copies) | Minimum primary RAM | 8 | GiB |
| Scaleway Managed Database for PostgreSQL (two copies) | Minimum primary disk | 100 | GiB |
| Scaleway Managed Database for PostgreSQL (two copies) | Additional full-price standby copy | 1 | 0 or 1 |
| Scaleway Managed Database for PostgreSQL (two copies) | Allocated share of provisioned cost | 1 | fraction |
| Scaleway Managed Database for PostgreSQL (two copies) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Scaleway Managed Database for PostgreSQL (two copies) | Planning peak / mean work | 2 | multiplier |
| Scaleway Managed Database for PostgreSQL (two copies) | Planning primary CPU utilization | 0.7 | fraction |
| Scaleway Managed Database for PostgreSQL (two copies) | Resident state reserved in RAM | 0.1 | fraction |
| Scaleway Managed Database for PostgreSQL (two copies) | Planning disk utilization | 0.8 | fraction |
| Scaleway Managed Database for PostgreSQL (two copies) | Maintenance and log disk reserve | 20 | GiB |
| Scaleway Managed Database for PostgreSQL (two copies) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Scaleway Managed Database for PostgreSQL (two copies) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Scaleway Managed Database for PostgreSQL (two copies) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Scaleway Managed Database for PostgreSQL (two copies) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Scaleway Managed Database 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. us-east-1 → fr-par, 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 is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* 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.
* The control plane and table facet describe the same family workload; allocate shared capacity once, not once per catalog facet.
* No transactional, global-table, Streams or scan tariff is inferred from ordinary on-demand point units.
* Scaleway Managed Database for PostgreSQL at Production Optimized (PRO2) prices in EUR converted at the ECB reference rate. A high-availability or replica node bills Scaleway's 'Additional nodes' price, EUR 0.0583 per hour for PRO2-XXS, 53% of the main node. Scaleway lists no egress charge for Managed Databases, so selected network is not charged. Cost Optimized ranges (DB-DEV-S from EUR 0.0156 per hour), Block Storage 15K and backups (EUR 0.03 per GB-month) 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 operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
* AWS Price List API, AmazonDynamoDB offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json)
* Amazon DynamoDB pricing: [https://aws.amazon.com/dynamodb/pricing/](https://aws.amazon.com/dynamodb/pricing/)
* Scaleway Managed Databases pricing: [https://www.scaleway.com/en/pricing/managed-databases/](https://www.scaleway.com/en/pricing/managed-databases/)

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.
* 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-a8af2fac3e931fad8397d4f3a601989b987a7744` / `2026-10-22.planning.2`. Curve: `workload-3`.

Sources: [AWS Price List API, AmazonDynamoDB offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json), [Amazon DynamoDB pricing](https://aws.amazon.com/dynamodb/pricing/), [Scaleway Managed Databases pricing](https://www.scaleway.com/en/pricing/managed-databases/).

## DynamoDB → Scaleway Managed Database for PostgreSQL

Origin API: `aws::1.0.0::dynamodb::table`. Target backend: `scaleway::1.0.0::rdb::postgresql`.

### DynamoDB · DynamoDB read units

Estimated monthly service charges by DynamoDB read units. Adapter hosting and Tensor9 fees are excluded. Source: us-east-1; target: fr-par; currency: USD.

![DynamoDB · DynamoDB read units: monthly service charges by DynamoDB read units. Exact values are in the following table.](/images/diagrams/service-cost/3d6cecd11259413f374a82a3866730d92eb8c4eb73d36dbd9d0bd2cf99e4c020-light.svg)

![DynamoDB · DynamoDB read units: monthly service charges by DynamoDB read units. Exact values are in the following table.](/images/diagrams/service-cost/076149b5af03de803d1d2dd084a7f7e101dc26f9e749b11a33d069722eb139d0-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.

| DynamoDB read units (per second) | DynamoDB | Target scenario | Scaleway Managed Database for PostgreSQL | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | Scaleway Managed Database for PostgreSQL (one copy) | 101.102715 | 101.102715 |
| 0 | 0 | Scaleway Managed Database for PostgreSQL (two copies) | 154.68715395 | 154.68715395 |
| 1 | 0.3285 | Scaleway Managed Database for PostgreSQL (one copy) | 101.102715 | 100.774215 |
| 1 | 0.3285 | Scaleway Managed Database for PostgreSQL (two copies) | 154.68715395 | 154.35865395 |
| 10 | 3.285 | Scaleway Managed Database for PostgreSQL (one copy) | 101.102715 | 97.817715 |
| 10 | 3.285 | Scaleway Managed Database for PostgreSQL (two copies) | 154.68715395 | 151.40215395 |
| 100 | 32.85 | Scaleway Managed Database for PostgreSQL (one copy) | 101.102715 | 68.252715 |
| 100 | 32.85 | Scaleway Managed Database for PostgreSQL (two copies) | 154.68715395 | 121.83715395 |
| 1000 | 328.5 | Scaleway Managed Database for PostgreSQL (one copy) | 101.102715 | -227.397285 |
| 1000 | 328.5 | Scaleway Managed Database for PostgreSQL (two copies) | 154.68715395 | -173.81284605 |
| 10000 | 3285 | Scaleway Managed Database for PostgreSQL (one copy) | 1450.744965 | -1834.255035 |
| 10000 | 3285 | Scaleway Managed Database for PostgreSQL (two copies) | 2219.63979645 | -1065.36020355 |

**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 / Scaleway Managed Database for PostgreSQL (one copy) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 0 per second / Scaleway Managed Database for PostgreSQL (two copies) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1 per second / Scaleway Managed Database for PostgreSQL (one copy) | PlanningAssumption | 1 / 2 | 0.001904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1 per second / Scaleway Managed Database for PostgreSQL (two copies) | PlanningAssumption | 1 / 2 | 0.001904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10 per second / Scaleway Managed Database for PostgreSQL (one copy) | PlanningAssumption | 10 / 20 | 0.01904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10 per second / Scaleway Managed Database for PostgreSQL (two copies) | PlanningAssumption | 10 / 20 | 0.01904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 100 per second / Scaleway Managed Database for PostgreSQL (one copy) | PlanningAssumption | 100 / 200 | 0.1904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 100 per second / Scaleway Managed Database for PostgreSQL (two copies) | PlanningAssumption | 100 / 200 | 0.1904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1000 per second / Scaleway Managed Database for PostgreSQL (one copy) | PlanningAssumption | 1000 / 2000 | 1.904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1000 per second / Scaleway Managed Database for PostgreSQL (two copies) | PlanningAssumption | 1000 / 2000 | 1.904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10000 per second / Scaleway Managed Database for PostgreSQL (one copy) | PlanningAssumption | 10000 / 20000 | 19.04761904761904761904761904761905 | 32 | 128 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10000 per second / Scaleway Managed Database for PostgreSQL (two copies) | PlanningAssumption | 10000 / 20000 | 19.04761904761904761904761904761905 | 32 | 128 | 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 operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Scaleway Managed Database for PostgreSQL (one copy) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| Scaleway Managed Database for PostgreSQL (one copy) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| Scaleway Managed Database for PostgreSQL (one copy) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| Scaleway Managed Database for PostgreSQL (one copy) | Origin list price · Control-plane calls | 0 | USD/requests |
| Scaleway Managed Database for PostgreSQL (one copy) | Representative item size | 1024 | bytes |
| Scaleway Managed Database for PostgreSQL (one copy) | Strongly consistent read fraction | 1 | fraction |
| Scaleway Managed Database for PostgreSQL (one copy) | Origin write-unit amplification | 1 | multiplier |
| Scaleway Managed Database for PostgreSQL (one copy) | Target reads per point read | 1 | operations |
| Scaleway Managed Database for PostgreSQL (one copy) | Target writes per item write | 1 | operations |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · read | 0 | USD/read |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · write | 0 | USD/write |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · provider operation | 0 | USD/provider operation |
| Scaleway Managed Database for PostgreSQL (one copy) | Target list price · GiB-month | 0.11126565 | USD/GiB-month |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · published GiB | 0 | USD/published GiB |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · network GiB | 0 | USD/network GiB |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Scaleway Managed Database for PostgreSQL (one copy) | Target list price · vCPU-hour | 0.0367275 | USD/vCPU-hour |
| Scaleway Managed Database for PostgreSQL (one copy) | Target list price · GiB-hour | 0.006225 | USD/GiB-hour |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · resource-hour | 0 | USD/resource-hour |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · resource-month | 0 | USD/resource-month |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · input token | 0 | USD/input token |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · output token | 0 | USD/output token |
| Scaleway Managed Database for PostgreSQL (one copy) | Target monthly base charge | 0 | USD/month |
| Scaleway Managed Database for PostgreSQL (one copy) | Target service minimum | 89.97615 | USD/month |
| Scaleway Managed Database for PostgreSQL (one copy) | Minimum primary CPU | 2 | vCPU |
| Scaleway Managed Database for PostgreSQL (one copy) | Minimum primary RAM | 8 | GiB |
| Scaleway Managed Database for PostgreSQL (one copy) | Minimum primary disk | 100 | GiB |
| Scaleway Managed Database for PostgreSQL (one copy) | Additional full-price standby copy | 0 | 0 or 1 |
| Scaleway Managed Database for PostgreSQL (one copy) | Allocated share of provisioned cost | 1 | fraction |
| Scaleway Managed Database for PostgreSQL (one copy) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Scaleway Managed Database for PostgreSQL (one copy) | Planning peak / mean work | 2 | multiplier |
| Scaleway Managed Database for PostgreSQL (one copy) | Planning primary CPU utilization | 0.7 | fraction |
| Scaleway Managed Database for PostgreSQL (one copy) | Resident state reserved in RAM | 0.1 | fraction |
| Scaleway Managed Database for PostgreSQL (one copy) | Planning disk utilization | 0.8 | fraction |
| Scaleway Managed Database for PostgreSQL (one copy) | Maintenance and log disk reserve | 20 | GiB |
| Scaleway Managed Database for PostgreSQL (one copy) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Scaleway Managed Database for PostgreSQL (one copy) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Scaleway Managed Database for PostgreSQL (one copy) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Scaleway Managed Database for PostgreSQL (one copy) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Scaleway Managed Database for PostgreSQL (one copy) | Dependent object sink write price guess | 0.000005 | USD/write |
| Scaleway Managed Database for PostgreSQL (two copies) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| Scaleway Managed Database for PostgreSQL (two copies) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| Scaleway Managed Database for PostgreSQL (two copies) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| Scaleway Managed Database for PostgreSQL (two copies) | Origin list price · Control-plane calls | 0 | USD/requests |
| Scaleway Managed Database for PostgreSQL (two copies) | Representative item size | 1024 | bytes |
| Scaleway Managed Database for PostgreSQL (two copies) | Strongly consistent read fraction | 1 | fraction |
| Scaleway Managed Database for PostgreSQL (two copies) | Origin write-unit amplification | 1 | multiplier |
| Scaleway Managed Database for PostgreSQL (two copies) | Target reads per point read | 1 | operations |
| Scaleway Managed Database for PostgreSQL (two copies) | Target writes per item write | 1 | operations |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · read | 0 | USD/read |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · write | 0 | USD/write |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · provider operation | 0 | USD/provider operation |
| Scaleway Managed Database for PostgreSQL (two copies) | Target list price · GiB-month | 0.11126565 | USD/GiB-month |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · published GiB | 0 | USD/published GiB |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · network GiB | 0 | USD/network GiB |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Scaleway Managed Database for PostgreSQL (two copies) | Target list price · vCPU-hour | 0.0367275 | USD/vCPU-hour |
| Scaleway Managed Database for PostgreSQL (two copies) | Target list price · GiB-hour | 0.006225 | USD/GiB-hour |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · resource-hour | 0 | USD/resource-hour |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · resource-month | 0 | USD/resource-month |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · input token | 0 | USD/input token |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · output token | 0 | USD/output token |
| Scaleway Managed Database for PostgreSQL (two copies) | Target monthly base charge | 0 | USD/month |
| Scaleway Managed Database for PostgreSQL (two copies) | Target service minimum | 89.97615 | USD/month |
| Scaleway Managed Database for PostgreSQL (two copies) | Minimum primary CPU | 2 | vCPU |
| Scaleway Managed Database for PostgreSQL (two copies) | Minimum primary RAM | 8 | GiB |
| Scaleway Managed Database for PostgreSQL (two copies) | Minimum primary disk | 100 | GiB |
| Scaleway Managed Database for PostgreSQL (two copies) | Additional full-price standby copy | 1 | 0 or 1 |
| Scaleway Managed Database for PostgreSQL (two copies) | Allocated share of provisioned cost | 1 | fraction |
| Scaleway Managed Database for PostgreSQL (two copies) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Scaleway Managed Database for PostgreSQL (two copies) | Planning peak / mean work | 2 | multiplier |
| Scaleway Managed Database for PostgreSQL (two copies) | Planning primary CPU utilization | 0.7 | fraction |
| Scaleway Managed Database for PostgreSQL (two copies) | Resident state reserved in RAM | 0.1 | fraction |
| Scaleway Managed Database for PostgreSQL (two copies) | Planning disk utilization | 0.8 | fraction |
| Scaleway Managed Database for PostgreSQL (two copies) | Maintenance and log disk reserve | 20 | GiB |
| Scaleway Managed Database for PostgreSQL (two copies) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Scaleway Managed Database for PostgreSQL (two copies) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Scaleway Managed Database for PostgreSQL (two copies) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Scaleway Managed Database for PostgreSQL (two copies) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Scaleway Managed Database for PostgreSQL (two copies) | Dependent object sink write price guess | 0.000005 | USD/write |

* Writes and storage remain independent. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
* Planning estimate · editable authored rates and sizing assumptions dated 2026-10-22; not verified provider prices. us-east-1 → fr-par, 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 is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* 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.
* The control plane and table facet describe the same family workload; allocate shared capacity once, not once per catalog facet.
* No transactional, global-table, Streams or scan tariff is inferred from ordinary on-demand point units.
* Scaleway Managed Database for PostgreSQL at Production Optimized (PRO2) prices in EUR converted at the ECB reference rate. A high-availability or replica node bills Scaleway's 'Additional nodes' price, EUR 0.0583 per hour for PRO2-XXS, 53% of the main node. Scaleway lists no egress charge for Managed Databases, so selected network is not charged. Cost Optimized ranges (DB-DEV-S from EUR 0.0156 per hour), Block Storage 15K and backups (EUR 0.03 per GB-month) 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 operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
* AWS Price List API, AmazonDynamoDB offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json)
* Amazon DynamoDB pricing: [https://aws.amazon.com/dynamodb/pricing/](https://aws.amazon.com/dynamodb/pricing/)
* Scaleway Managed Databases pricing: [https://www.scaleway.com/en/pricing/managed-databases/](https://www.scaleway.com/en/pricing/managed-databases/)

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.
* 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-a5b2d88776c9acb581992c5176447f34ff522ecc` / `2026-10-22.planning.2`. Curve: `workload-1`.

Sources: [AWS Price List API, AmazonDynamoDB offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json), [Amazon DynamoDB pricing](https://aws.amazon.com/dynamodb/pricing/), [Scaleway Managed Databases pricing](https://www.scaleway.com/en/pricing/managed-databases/).

### DynamoDB · DynamoDB write units

Estimated monthly service charges by DynamoDB write units. Adapter hosting and Tensor9 fees are excluded. Source: us-east-1; target: fr-par; currency: USD.

![DynamoDB · DynamoDB write units: monthly service charges by DynamoDB write units. Exact values are in the following table.](/images/diagrams/service-cost/90ecebd45a33300a00c15037cd6d23923d7bfbbe56ed44cba0042702c9f75656-light.svg)

![DynamoDB · DynamoDB write units: monthly service charges by DynamoDB write units. Exact values are in the following table.](/images/diagrams/service-cost/a7a968a8f7a8e687adb944ba4933fb790fe8c043cd0ba64cf2f8ebf144d08d40-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.

| DynamoDB write units (per second) | DynamoDB | Target scenario | Scaleway Managed Database for PostgreSQL | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | Scaleway Managed Database for PostgreSQL (one copy) | 101.102715 | 101.102715 |
| 0 | 0 | Scaleway Managed Database for PostgreSQL (two copies) | 154.68715395 | 154.68715395 |
| 1 | 1.6425 | Scaleway Managed Database for PostgreSQL (one copy) | 101.102715 | 99.460215 |
| 1 | 1.6425 | Scaleway Managed Database for PostgreSQL (two copies) | 154.68715395 | 153.04465395 |
| 10 | 16.425 | Scaleway Managed Database for PostgreSQL (one copy) | 101.102715 | 84.677715 |
| 10 | 16.425 | Scaleway Managed Database for PostgreSQL (two copies) | 154.68715395 | 138.26215395 |
| 100 | 164.25 | Scaleway Managed Database for PostgreSQL (one copy) | 101.102715 | -63.147285 |
| 100 | 164.25 | Scaleway Managed Database for PostgreSQL (two copies) | 154.68715395 | -9.56284605 |
| 1000 | 1642.5 | Scaleway Managed Database for PostgreSQL (one copy) | 101.102715 | -1541.397285 |
| 1000 | 1642.5 | Scaleway Managed Database for PostgreSQL (two copies) | 154.68715395 | -1487.81284605 |
| 10000 | 16425 | Scaleway Managed Database for PostgreSQL (one copy) | 1450.744965 | -14974.255035 |
| 10000 | 16425 | Scaleway Managed Database for PostgreSQL (two copies) | 2219.63979645 | -14205.36020355 |

**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 / Scaleway Managed Database for PostgreSQL (one copy) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 0 per second / Scaleway Managed Database for PostgreSQL (two copies) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1 per second / Scaleway Managed Database for PostgreSQL (one copy) | PlanningAssumption | 1 / 2 | 0.001904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1 per second / Scaleway Managed Database for PostgreSQL (two copies) | PlanningAssumption | 1 / 2 | 0.001904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10 per second / Scaleway Managed Database for PostgreSQL (one copy) | PlanningAssumption | 10 / 20 | 0.01904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10 per second / Scaleway Managed Database for PostgreSQL (two copies) | PlanningAssumption | 10 / 20 | 0.01904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 100 per second / Scaleway Managed Database for PostgreSQL (one copy) | PlanningAssumption | 100 / 200 | 0.1904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 100 per second / Scaleway Managed Database for PostgreSQL (two copies) | PlanningAssumption | 100 / 200 | 0.1904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1000 per second / Scaleway Managed Database for PostgreSQL (one copy) | PlanningAssumption | 1000 / 2000 | 1.904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1000 per second / Scaleway Managed Database for PostgreSQL (two copies) | PlanningAssumption | 1000 / 2000 | 1.904761904761904761904761904761905 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10000 per second / Scaleway Managed Database for PostgreSQL (one copy) | PlanningAssumption | 10000 / 20000 | 19.04761904761904761904761904761905 | 32 | 128 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10000 per second / Scaleway Managed Database for PostgreSQL (two copies) | PlanningAssumption | 10000 / 20000 | 19.04761904761904761904761904761905 | 32 | 128 | 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 operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Scaleway Managed Database for PostgreSQL (one copy) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| Scaleway Managed Database for PostgreSQL (one copy) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| Scaleway Managed Database for PostgreSQL (one copy) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| Scaleway Managed Database for PostgreSQL (one copy) | Origin list price · Control-plane calls | 0 | USD/requests |
| Scaleway Managed Database for PostgreSQL (one copy) | Representative item size | 1024 | bytes |
| Scaleway Managed Database for PostgreSQL (one copy) | Strongly consistent read fraction | 1 | fraction |
| Scaleway Managed Database for PostgreSQL (one copy) | Origin write-unit amplification | 1 | multiplier |
| Scaleway Managed Database for PostgreSQL (one copy) | Target reads per point read | 1 | operations |
| Scaleway Managed Database for PostgreSQL (one copy) | Target writes per item write | 1 | operations |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · read | 0 | USD/read |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · write | 0 | USD/write |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · provider operation | 0 | USD/provider operation |
| Scaleway Managed Database for PostgreSQL (one copy) | Target list price · GiB-month | 0.11126565 | USD/GiB-month |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · published GiB | 0 | USD/published GiB |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · network GiB | 0 | USD/network GiB |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Scaleway Managed Database for PostgreSQL (one copy) | Target list price · vCPU-hour | 0.0367275 | USD/vCPU-hour |
| Scaleway Managed Database for PostgreSQL (one copy) | Target list price · GiB-hour | 0.006225 | USD/GiB-hour |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · resource-hour | 0 | USD/resource-hour |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · resource-month | 0 | USD/resource-month |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · input token | 0 | USD/input token |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · output token | 0 | USD/output token |
| Scaleway Managed Database for PostgreSQL (one copy) | Target monthly base charge | 0 | USD/month |
| Scaleway Managed Database for PostgreSQL (one copy) | Target service minimum | 89.97615 | USD/month |
| Scaleway Managed Database for PostgreSQL (one copy) | Minimum primary CPU | 2 | vCPU |
| Scaleway Managed Database for PostgreSQL (one copy) | Minimum primary RAM | 8 | GiB |
| Scaleway Managed Database for PostgreSQL (one copy) | Minimum primary disk | 100 | GiB |
| Scaleway Managed Database for PostgreSQL (one copy) | Additional full-price standby copy | 0 | 0 or 1 |
| Scaleway Managed Database for PostgreSQL (one copy) | Allocated share of provisioned cost | 1 | fraction |
| Scaleway Managed Database for PostgreSQL (one copy) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Scaleway Managed Database for PostgreSQL (one copy) | Planning peak / mean work | 2 | multiplier |
| Scaleway Managed Database for PostgreSQL (one copy) | Planning primary CPU utilization | 0.7 | fraction |
| Scaleway Managed Database for PostgreSQL (one copy) | Resident state reserved in RAM | 0.1 | fraction |
| Scaleway Managed Database for PostgreSQL (one copy) | Planning disk utilization | 0.8 | fraction |
| Scaleway Managed Database for PostgreSQL (one copy) | Maintenance and log disk reserve | 20 | GiB |
| Scaleway Managed Database for PostgreSQL (one copy) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Scaleway Managed Database for PostgreSQL (one copy) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Scaleway Managed Database for PostgreSQL (one copy) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Scaleway Managed Database for PostgreSQL (one copy) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Scaleway Managed Database for PostgreSQL (one copy) | Dependent object sink write price guess | 0.000005 | USD/write |
| Scaleway Managed Database for PostgreSQL (two copies) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| Scaleway Managed Database for PostgreSQL (two copies) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| Scaleway Managed Database for PostgreSQL (two copies) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| Scaleway Managed Database for PostgreSQL (two copies) | Origin list price · Control-plane calls | 0 | USD/requests |
| Scaleway Managed Database for PostgreSQL (two copies) | Representative item size | 1024 | bytes |
| Scaleway Managed Database for PostgreSQL (two copies) | Strongly consistent read fraction | 1 | fraction |
| Scaleway Managed Database for PostgreSQL (two copies) | Origin write-unit amplification | 1 | multiplier |
| Scaleway Managed Database for PostgreSQL (two copies) | Target reads per point read | 1 | operations |
| Scaleway Managed Database for PostgreSQL (two copies) | Target writes per item write | 1 | operations |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · read | 0 | USD/read |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · write | 0 | USD/write |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · provider operation | 0 | USD/provider operation |
| Scaleway Managed Database for PostgreSQL (two copies) | Target list price · GiB-month | 0.11126565 | USD/GiB-month |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · published GiB | 0 | USD/published GiB |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · network GiB | 0 | USD/network GiB |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Scaleway Managed Database for PostgreSQL (two copies) | Target list price · vCPU-hour | 0.0367275 | USD/vCPU-hour |
| Scaleway Managed Database for PostgreSQL (two copies) | Target list price · GiB-hour | 0.006225 | USD/GiB-hour |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · resource-hour | 0 | USD/resource-hour |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · resource-month | 0 | USD/resource-month |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · input token | 0 | USD/input token |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · output token | 0 | USD/output token |
| Scaleway Managed Database for PostgreSQL (two copies) | Target monthly base charge | 0 | USD/month |
| Scaleway Managed Database for PostgreSQL (two copies) | Target service minimum | 89.97615 | USD/month |
| Scaleway Managed Database for PostgreSQL (two copies) | Minimum primary CPU | 2 | vCPU |
| Scaleway Managed Database for PostgreSQL (two copies) | Minimum primary RAM | 8 | GiB |
| Scaleway Managed Database for PostgreSQL (two copies) | Minimum primary disk | 100 | GiB |
| Scaleway Managed Database for PostgreSQL (two copies) | Additional full-price standby copy | 1 | 0 or 1 |
| Scaleway Managed Database for PostgreSQL (two copies) | Allocated share of provisioned cost | 1 | fraction |
| Scaleway Managed Database for PostgreSQL (two copies) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Scaleway Managed Database for PostgreSQL (two copies) | Planning peak / mean work | 2 | multiplier |
| Scaleway Managed Database for PostgreSQL (two copies) | Planning primary CPU utilization | 0.7 | fraction |
| Scaleway Managed Database for PostgreSQL (two copies) | Resident state reserved in RAM | 0.1 | fraction |
| Scaleway Managed Database for PostgreSQL (two copies) | Planning disk utilization | 0.8 | fraction |
| Scaleway Managed Database for PostgreSQL (two copies) | Maintenance and log disk reserve | 20 | GiB |
| Scaleway Managed Database for PostgreSQL (two copies) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Scaleway Managed Database for PostgreSQL (two copies) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Scaleway Managed Database for PostgreSQL (two copies) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Scaleway Managed Database for PostgreSQL (two copies) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Scaleway Managed Database for PostgreSQL (two copies) | Dependent object sink write price guess | 0.000005 | USD/write |

* Reads and storage remain independent. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
* Planning estimate · editable authored rates and sizing assumptions dated 2026-10-22; not verified provider prices. us-east-1 → fr-par, 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 is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* 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.
* The control plane and table facet describe the same family workload; allocate shared capacity once, not once per catalog facet.
* No transactional, global-table, Streams or scan tariff is inferred from ordinary on-demand point units.
* Scaleway Managed Database for PostgreSQL at Production Optimized (PRO2) prices in EUR converted at the ECB reference rate. A high-availability or replica node bills Scaleway's 'Additional nodes' price, EUR 0.0583 per hour for PRO2-XXS, 53% of the main node. Scaleway lists no egress charge for Managed Databases, so selected network is not charged. Cost Optimized ranges (DB-DEV-S from EUR 0.0156 per hour), Block Storage 15K and backups (EUR 0.03 per GB-month) 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 operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
* AWS Price List API, AmazonDynamoDB offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json)
* Amazon DynamoDB pricing: [https://aws.amazon.com/dynamodb/pricing/](https://aws.amazon.com/dynamodb/pricing/)
* Scaleway Managed Databases pricing: [https://www.scaleway.com/en/pricing/managed-databases/](https://www.scaleway.com/en/pricing/managed-databases/)

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.
* 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-a5b2d88776c9acb581992c5176447f34ff522ecc` / `2026-10-22.planning.2`. Curve: `workload-2`.

Sources: [AWS Price List API, AmazonDynamoDB offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json), [Amazon DynamoDB pricing](https://aws.amazon.com/dynamodb/pricing/), [Scaleway Managed Databases pricing](https://www.scaleway.com/en/pricing/managed-databases/).

### DynamoDB · Stored data

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

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

![DynamoDB · Stored data: monthly service charges by Stored data. Exact values are in the following table.](/images/diagrams/service-cost/8964c86795b5742da69ce64cd3844959c1677fccbd477238b051d0f77ddcc5fa-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) | DynamoDB | Target scenario | Scaleway Managed Database for PostgreSQL | Difference |
| -: | -: | - | -: | -: |
| 0 | 0 | Scaleway Managed Database for PostgreSQL (one copy) | 101.102715 | 101.102715 |
| 0 | 0 | Scaleway Managed Database for PostgreSQL (two copies) | 154.68715395 | 154.68715395 |
| 10 | 2.5 | Scaleway Managed Database for PostgreSQL (one copy) | 101.102715 | 98.602715 |
| 10 | 2.5 | Scaleway Managed Database for PostgreSQL (two copies) | 154.68715395 | 152.18715395 |
| 100 | 25 | Scaleway Managed Database for PostgreSQL (one copy) | 115.7544975 | 90.7544975 |
| 100 | 25 | Scaleway Managed Database for PostgreSQL (two copies) | 177.104381175 | 152.104381175 |
| 1000 | 250 | Scaleway Managed Database for PostgreSQL (one copy) | 1025.26590375 | 775.26590375 |
| 1000 | 250 | Scaleway Managed Database for PostgreSQL (two copies) | 1568.6568327375 | 1318.6568327375 |
| 10000 | 2500 | Scaleway Managed Database for PostgreSQL (one copy) | Unpriced | Unavailable |
| 10000 | 2500 | Scaleway Managed Database for PostgreSQL (two copies) | Unpriced | Unavailable |
| 100000 | 25000 | Scaleway Managed Database for PostgreSQL (one copy) | Unpriced | Unavailable |
| 100000 | 25000 | Scaleway Managed Database 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 / Scaleway Managed Database for PostgreSQL (one copy) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 0 GiB-month / Scaleway Managed Database for PostgreSQL (two copies) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10 GiB-month / Scaleway Managed Database for PostgreSQL (one copy) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 10 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10 GiB-month / Scaleway Managed Database for PostgreSQL (two copies) | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 10 | `service-adapter-planning-2026-10-22.1` | None reported |
| 100 GiB-month / Scaleway Managed Database for PostgreSQL (one copy) | PlanningAssumption | 0 / 0 | 0 | 2 | 10 | 150 | 100 | `service-adapter-planning-2026-10-22.1` | None reported |
| 100 GiB-month / Scaleway Managed Database for PostgreSQL (two copies) | PlanningAssumption | 0 / 0 | 0 | 2 | 10 | 150 | 100 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1000 GiB-month / Scaleway Managed Database for PostgreSQL (one copy) | PlanningAssumption | 0 / 0 | 0 | 16 | 100 | 1275 | 1000 | `service-adapter-planning-2026-10-22.1` | None reported |
| 1000 GiB-month / Scaleway Managed Database for PostgreSQL (two copies) | PlanningAssumption | 0 / 0 | 0 | 16 | 100 | 1275 | 1000 | `service-adapter-planning-2026-10-22.1` | None reported |
| 10000 GiB-month / Scaleway Managed Database 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 / Scaleway Managed Database 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 / Scaleway Managed Database 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 / Scaleway Managed Database 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 operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Scaleway Managed Database for PostgreSQL (one copy) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| Scaleway Managed Database for PostgreSQL (one copy) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| Scaleway Managed Database for PostgreSQL (one copy) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| Scaleway Managed Database for PostgreSQL (one copy) | Origin list price · Control-plane calls | 0 | USD/requests |
| Scaleway Managed Database for PostgreSQL (one copy) | Representative item size | 1024 | bytes |
| Scaleway Managed Database for PostgreSQL (one copy) | Strongly consistent read fraction | 1 | fraction |
| Scaleway Managed Database for PostgreSQL (one copy) | Origin write-unit amplification | 1 | multiplier |
| Scaleway Managed Database for PostgreSQL (one copy) | Target reads per point read | 1 | operations |
| Scaleway Managed Database for PostgreSQL (one copy) | Target writes per item write | 1 | operations |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · read | 0 | USD/read |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · write | 0 | USD/write |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · provider operation | 0 | USD/provider operation |
| Scaleway Managed Database for PostgreSQL (one copy) | Target list price · GiB-month | 0.11126565 | USD/GiB-month |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · published GiB | 0 | USD/published GiB |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · network GiB | 0 | USD/network GiB |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Scaleway Managed Database for PostgreSQL (one copy) | Target list price · vCPU-hour | 0.0367275 | USD/vCPU-hour |
| Scaleway Managed Database for PostgreSQL (one copy) | Target list price · GiB-hour | 0.006225 | USD/GiB-hour |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · resource-hour | 0 | USD/resource-hour |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · resource-month | 0 | USD/resource-month |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · input token | 0 | USD/input token |
| Scaleway Managed Database for PostgreSQL (one copy) | Target price guess · output token | 0 | USD/output token |
| Scaleway Managed Database for PostgreSQL (one copy) | Target monthly base charge | 0 | USD/month |
| Scaleway Managed Database for PostgreSQL (one copy) | Target service minimum | 89.97615 | USD/month |
| Scaleway Managed Database for PostgreSQL (one copy) | Minimum primary CPU | 2 | vCPU |
| Scaleway Managed Database for PostgreSQL (one copy) | Minimum primary RAM | 8 | GiB |
| Scaleway Managed Database for PostgreSQL (one copy) | Minimum primary disk | 100 | GiB |
| Scaleway Managed Database for PostgreSQL (one copy) | Additional full-price standby copy | 0 | 0 or 1 |
| Scaleway Managed Database for PostgreSQL (one copy) | Allocated share of provisioned cost | 1 | fraction |
| Scaleway Managed Database for PostgreSQL (one copy) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Scaleway Managed Database for PostgreSQL (one copy) | Planning peak / mean work | 2 | multiplier |
| Scaleway Managed Database for PostgreSQL (one copy) | Planning primary CPU utilization | 0.7 | fraction |
| Scaleway Managed Database for PostgreSQL (one copy) | Resident state reserved in RAM | 0.1 | fraction |
| Scaleway Managed Database for PostgreSQL (one copy) | Planning disk utilization | 0.8 | fraction |
| Scaleway Managed Database for PostgreSQL (one copy) | Maintenance and log disk reserve | 20 | GiB |
| Scaleway Managed Database for PostgreSQL (one copy) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Scaleway Managed Database for PostgreSQL (one copy) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Scaleway Managed Database for PostgreSQL (one copy) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Scaleway Managed Database for PostgreSQL (one copy) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Scaleway Managed Database for PostgreSQL (one copy) | Dependent object sink write price guess | 0.000005 | USD/write |
| Scaleway Managed Database for PostgreSQL (two copies) | Origin list price · DynamoDB read units | 0.000000125 | USD/read request units |
| Scaleway Managed Database for PostgreSQL (two copies) | Origin list price · DynamoDB write units | 0.000000625 | USD/write request units |
| Scaleway Managed Database for PostgreSQL (two copies) | Origin list price · DynamoDB stored data | 0.25 | USD/GiB-month |
| Scaleway Managed Database for PostgreSQL (two copies) | Origin list price · Control-plane calls | 0 | USD/requests |
| Scaleway Managed Database for PostgreSQL (two copies) | Representative item size | 1024 | bytes |
| Scaleway Managed Database for PostgreSQL (two copies) | Strongly consistent read fraction | 1 | fraction |
| Scaleway Managed Database for PostgreSQL (two copies) | Origin write-unit amplification | 1 | multiplier |
| Scaleway Managed Database for PostgreSQL (two copies) | Target reads per point read | 1 | operations |
| Scaleway Managed Database for PostgreSQL (two copies) | Target writes per item write | 1 | operations |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · read | 0 | USD/read |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · write | 0 | USD/write |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · provider operation | 0 | USD/provider operation |
| Scaleway Managed Database for PostgreSQL (two copies) | Target list price · GiB-month | 0.11126565 | USD/GiB-month |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · published GiB | 0 | USD/published GiB |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · network GiB | 0 | USD/network GiB |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Scaleway Managed Database for PostgreSQL (two copies) | Target list price · vCPU-hour | 0.0367275 | USD/vCPU-hour |
| Scaleway Managed Database for PostgreSQL (two copies) | Target list price · GiB-hour | 0.006225 | USD/GiB-hour |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · resource-hour | 0 | USD/resource-hour |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · resource-month | 0 | USD/resource-month |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · input token | 0 | USD/input token |
| Scaleway Managed Database for PostgreSQL (two copies) | Target price guess · output token | 0 | USD/output token |
| Scaleway Managed Database for PostgreSQL (two copies) | Target monthly base charge | 0 | USD/month |
| Scaleway Managed Database for PostgreSQL (two copies) | Target service minimum | 89.97615 | USD/month |
| Scaleway Managed Database for PostgreSQL (two copies) | Minimum primary CPU | 2 | vCPU |
| Scaleway Managed Database for PostgreSQL (two copies) | Minimum primary RAM | 8 | GiB |
| Scaleway Managed Database for PostgreSQL (two copies) | Minimum primary disk | 100 | GiB |
| Scaleway Managed Database for PostgreSQL (two copies) | Additional full-price standby copy | 1 | 0 or 1 |
| Scaleway Managed Database for PostgreSQL (two copies) | Allocated share of provisioned cost | 1 | fraction |
| Scaleway Managed Database for PostgreSQL (two copies) | Read/write work per vCPU-second | 1500 | operations/vCPU-second |
| Scaleway Managed Database for PostgreSQL (two copies) | Planning peak / mean work | 2 | multiplier |
| Scaleway Managed Database for PostgreSQL (two copies) | Planning primary CPU utilization | 0.7 | fraction |
| Scaleway Managed Database for PostgreSQL (two copies) | Resident state reserved in RAM | 0.1 | fraction |
| Scaleway Managed Database for PostgreSQL (two copies) | Planning disk utilization | 0.8 | fraction |
| Scaleway Managed Database for PostgreSQL (two copies) | Maintenance and log disk reserve | 20 | GiB |
| Scaleway Managed Database for PostgreSQL (two copies) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Scaleway Managed Database for PostgreSQL (two copies) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Scaleway Managed Database for PostgreSQL (two copies) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Scaleway Managed Database for PostgreSQL (two copies) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Scaleway Managed Database 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. us-east-1 → fr-par, 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 is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* 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.
* The control plane and table facet describe the same family workload; allocate shared capacity once, not once per catalog facet.
* No transactional, global-table, Streams or scan tariff is inferred from ordinary on-demand point units.
* Scaleway Managed Database for PostgreSQL at Production Optimized (PRO2) prices in EUR converted at the ECB reference rate. A high-availability or replica node bills Scaleway's 'Additional nodes' price, EUR 0.0583 per hour for PRO2-XXS, 53% of the main node. Scaleway lists no egress charge for Managed Databases, so selected network is not charged. Cost Optimized ranges (DB-DEV-S from EUR 0.0156 per hour), Block Storage 15K and backups (EUR 0.03 per GB-month) 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 operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
* AWS Price List API, AmazonDynamoDB offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json)
* Amazon DynamoDB pricing: [https://aws.amazon.com/dynamodb/pricing/](https://aws.amazon.com/dynamodb/pricing/)
* Scaleway Managed Databases pricing: [https://www.scaleway.com/en/pricing/managed-databases/](https://www.scaleway.com/en/pricing/managed-databases/)

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.
* 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-a5b2d88776c9acb581992c5176447f34ff522ecc` / `2026-10-22.planning.2`. Curve: `workload-3`.

Sources: [AWS Price List API, AmazonDynamoDB offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonDynamoDB/current/us-east-1/index.json), [Amazon DynamoDB pricing](https://aws.amazon.com/dynamodb/pricing/), [Scaleway Managed Databases pricing](https://www.scaleway.com/en/pricing/managed-databases/).

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


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