> ## 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. # Cloud SQL for MySQL costs > Compare Cloud SQL for MySQL backend choices using explicit service-adapter planning assumptions. Tensor9 BYOC planning comparisons for `google::1.0.0::cloudsql::mysql`, with backend choices shown together. Read [how to think about service-adapter costs](/byoc/service-adapters/debugging/costs/overview) for price scope and capacity qualification, or return to [additional services](/byoc/service-adapters/debugging/costs/additional-services). ## Google Cloud SQL MySQL → MySQL Flexible Server Origin API: `google::1.0.0::cloudsql::mysql`. Target backend: `azure::1.0.0::mysql::flexible`. **Planning estimate with editable assumptions.** Unit rates, workload amplification and capacity assumptions are educated guesses awaiting verification. The displayed amounts are planning estimates, not verified provider list-price quotes or benchmark-qualified capacity. Region names identify the authored scenario assumptions. **Designed mapping.** This cost model describes an intended adapter. Its estimated price does not establish a delivered or selectable backend. ### Google Cloud SQL MySQL · Primary allocated compute **Planning estimate with editable assumptions.** These authored unit rates and capacity assumptions require provider-price verification and representative benchmarks. They do not constitute verified list-price quotes or evidence that an adapter is available. Estimated monthly service charges from native source usage; no calculator input is required. Adapter hosting and Tensor9 fees are excluded. Source: Explicit source planning region; target: Explicit target planning region; currency: USD.

Google Cloud SQL MySQL · Primary allocated compute: monthly service charges by Primary allocated compute. Exact values are in the following table.

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. Only discrete samples are shown. Unpriced means no target quote or cost difference is available within the sizing policy. | Primary allocated compute (vCPU-hours/month) | Origin | Target scenario | Target | Difference | | -: | -: | - | -: | -: | | 0 | 0 | Planning allocation · one copy | 125.04 | 125.04 | | 0 | 0 | Planning allocation · two copies | 250.08 | 250.08 | | 1460 | 60.298 | Planning allocation · one copy | 125.04 | 64.742 | | 1460 | 60.298 | Planning allocation · two copies | 250.08 | 189.782 | | 2920 | 120.596 | Planning allocation · one copy | 233.08 | 112.484 | | 2920 | 120.596 | Planning allocation · two copies | 466.16 | 345.564 | | 5840 | 241.192 | Planning allocation · one copy | 449.16 | 207.968 | | 5840 | 241.192 | Planning allocation · two copies | 898.32 | 657.128 | | 11680 | 482.384 | Planning allocation · one copy | 881.32 | 398.936 | | 11680 | 482.384 | Planning allocation · two copies | 1762.64 | 1280.256 | | 23360 | 964.768 | Planning allocation · one copy | 1745.64 | 780.872 | | 23360 | 964.768 | Planning allocation · two copies | 3491.28 | 2526.512 | | 46720 | 1929.536 | Planning allocation · one copy | 3474.28 | 1544.744 | | 46720 | 1929.536 | Planning allocation · two copies | 6948.56 | 5019.024 | **Estimated allocation from planning assumptions; not benchmark calibrated.** The sizing policy grows compute with translated work and peak headroom, memory with compute and working set, and disk with resident working state and reserve. Monthly usage is distinct from resident data; each workload's assumptions define the translation. HA changes pricing, not this policy's throughput estimate. Unpriced workloads exceed the policy's configuration range; no silent vertical cap or automatic sharding is assumed. | Sample / scenario | Basis | Mean / peak work/s | Required vCPU | Allocated vCPU | Memory GiB | SSD GiB | Resident GiB | Policy | Constraints | | - | - | -: | -: | -: | -: | -: | -: | - | - | | 0 vCPU-hours/month / Planning allocation · one copy | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-18.1` | None reported | | 0 vCPU-hours/month / Planning allocation · two copies | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-18.1` | None reported | | 1460 vCPU-hours/month / Planning allocation · one copy | PlanningAssumption | 0 / 0 | 2 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-18.1` | None reported | | 1460 vCPU-hours/month / Planning allocation · two copies | PlanningAssumption | 0 / 0 | 2 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-18.1` | None reported | | 2920 vCPU-hours/month / Planning allocation · one copy | PlanningAssumption | 0 / 0 | 4 | 4 | 16 | 100 | 0 | `service-adapter-planning-2026-10-18.1` | None reported | | 2920 vCPU-hours/month / Planning allocation · two copies | PlanningAssumption | 0 / 0 | 4 | 4 | 16 | 100 | 0 | `service-adapter-planning-2026-10-18.1` | None reported | | 5840 vCPU-hours/month / Planning allocation · one copy | PlanningAssumption | 0 / 0 | 8 | 8 | 32 | 100 | 0 | `service-adapter-planning-2026-10-18.1` | None reported | | 5840 vCPU-hours/month / Planning allocation · two copies | PlanningAssumption | 0 / 0 | 8 | 8 | 32 | 100 | 0 | `service-adapter-planning-2026-10-18.1` | None reported | | 11680 vCPU-hours/month / Planning allocation · one copy | PlanningAssumption | 0 / 0 | 16 | 16 | 64 | 100 | 0 | `service-adapter-planning-2026-10-18.1` | None reported | | 11680 vCPU-hours/month / Planning allocation · two copies | PlanningAssumption | 0 / 0 | 16 | 16 | 64 | 100 | 0 | `service-adapter-planning-2026-10-18.1` | None reported | | 23360 vCPU-hours/month / Planning allocation · one copy | PlanningAssumption | 0 / 0 | 32 | 32 | 128 | 100 | 0 | `service-adapter-planning-2026-10-18.1` | None reported | | 23360 vCPU-hours/month / Planning allocation · two copies | PlanningAssumption | 0 / 0 | 32 | 32 | 128 | 100 | 0 | `service-adapter-planning-2026-10-18.1` | None reported | | 46720 vCPU-hours/month / Planning allocation · one copy | PlanningAssumption | 0 / 0 | 64 | 64 | 256 | 100 | 0 | `service-adapter-planning-2026-10-18.1` | None reported | | 46720 vCPU-hours/month / Planning allocation · two copies | PlanningAssumption | 0 / 0 | 64 | 64 | 256 | 100 | 0 | `service-adapter-planning-2026-10-18.1` | None reported | * Authored operation throughput, peak and working-set assumptions are not benchmark-calibrated. * Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied. * The workload family already selected resource-hours; the generic operations/vCPU coefficient is not applied again. * Copies and allocation fractions change cost only; they do not increase modeled primary capacity. **Curve assumptions** | Target scenario | Assumption | Value | Unit | | - | - | -: | - | | Planning allocation · one copy | Origin price guess · Primary compute | 0.0413 | USD/vCPU-hours | | Planning allocation · one copy | Origin price guess · Primary memory | 0.007 | USD/GiB-hours | | Planning allocation · one copy | Origin price guess · Primary provisioned storage | 0.115 | USD/GiB-month | | Planning allocation · one copy | Origin price guess · Database reads | 0 | USD/operations | | Planning allocation · one copy | Origin price guess · Database writes | 0 | USD/operations | | Planning allocation · one copy | Target CPU / source CPU | 1 | multiplier | | Planning allocation · one copy | Target RAM / source RAM | 1 | multiplier | | Planning allocation · one copy | Target disk / source disk | 1 | multiplier | | Planning allocation · one copy | Target price guess · read | 0 | USD/read | | Planning allocation · one copy | Target price guess · write | 0 | USD/write | | Planning allocation · one copy | Target price guess · provider operation | 0 | USD/provider operation | | Planning allocation · one copy | Target price guess · GiB-month | 0.17 | USD/GiB-month | | Planning allocation · one copy | Target price guess · published GiB | 0 | USD/published GiB | | Planning allocation · one copy | Target price guess · delivered GiB | 0 | USD/delivered GiB | | Planning allocation · one copy | Target price guess · network GiB | 0.09 | USD/network GiB | | Planning allocation · one copy | Target price guess · replica GiB-month | 0 | USD/replica GiB-month | | Planning allocation · one copy | Target price guess · vCPU-hour | 0.05 | USD/vCPU-hour | | Planning allocation · one copy | Target price guess · GiB-hour | 0.006 | USD/GiB-hour | | Planning allocation · one copy | Target price guess · resource-hour | 0 | USD/resource-hour | | Planning allocation · one copy | Target price guess · resource-month | 0 | USD/resource-month | | Planning allocation · one copy | Target price guess · input token | 0 | USD/input token | | Planning allocation · one copy | Target price guess · output token | 0 | USD/output token | | Planning allocation · one copy | Approximate target service minimum | 0 | USD/month | | Planning allocation · one copy | Minimum primary CPU | 2 | vCPU | | Planning allocation · one copy | Minimum primary RAM | 8 | GiB | | Planning allocation · one copy | Minimum primary disk | 100 | GiB | | Planning allocation · one copy | Additional full-price standby copy | 0 | 0 or 1 | | Planning allocation · one copy | Allocated share of provisioned cost | 1 | fraction | | Planning allocation · one copy | Planning read/write work per vCPU-second | 1000 | operations/vCPU-second | | Planning allocation · one copy | Planning peak / mean work | 2 | multiplier | | Planning allocation · one copy | Planning primary CPU utilization | 0.7 | fraction | | Planning allocation · one copy | Resident state reserved in RAM | 0.1 | fraction | | Planning allocation · one copy | Planning disk utilization | 0.7 | fraction | | Planning allocation · one copy | Maintenance and log disk reserve | 20 | GiB | | Planning allocation · one copy | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour | | Planning allocation · one copy | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour | | Planning allocation · one copy | Staging database disk unit-price guess | 0.17 | USD/GiB-month | | Planning allocation · one copy | Dependent object sink storage price guess | 0.023 | USD/GiB-month | | Planning allocation · one copy | Dependent object sink write price guess | 0.000005 | USD/write | | Planning allocation · two copies | Origin price guess · Primary compute | 0.0413 | USD/vCPU-hours | | Planning allocation · two copies | Origin price guess · Primary memory | 0.007 | USD/GiB-hours | | Planning allocation · two copies | Origin price guess · Primary provisioned storage | 0.115 | USD/GiB-month | | Planning allocation · two copies | Origin price guess · Database reads | 0 | USD/operations | | Planning allocation · two copies | Origin price guess · Database writes | 0 | USD/operations | | Planning allocation · two copies | Target CPU / source CPU | 1 | multiplier | | Planning allocation · two copies | Target RAM / source RAM | 1 | multiplier | | Planning allocation · two copies | Target disk / source disk | 1 | multiplier | | Planning allocation · two copies | Target price guess · read | 0 | USD/read | | Planning allocation · two copies | Target price guess · write | 0 | USD/write | | Planning allocation · two copies | Target price guess · provider operation | 0 | USD/provider operation | | Planning allocation · two copies | Target price guess · GiB-month | 0.17 | USD/GiB-month | | Planning allocation · two copies | Target price guess · published GiB | 0 | USD/published GiB | | Planning allocation · two copies | Target price guess · delivered GiB | 0 | USD/delivered GiB | | Planning allocation · two copies | Target price guess · network GiB | 0.09 | USD/network GiB | | Planning allocation · two copies | Target price guess · replica GiB-month | 0 | USD/replica GiB-month | | Planning allocation · two copies | Target price guess · vCPU-hour | 0.05 | USD/vCPU-hour | | Planning allocation · two copies | Target price guess · GiB-hour | 0.006 | USD/GiB-hour | | Planning allocation · two copies | Target price guess · resource-hour | 0 | USD/resource-hour | | Planning allocation · two copies | Target price guess · resource-month | 0 | USD/resource-month | | Planning allocation · two copies | Target price guess · input token | 0 | USD/input token | | Planning allocation · two copies | Target price guess · output token | 0 | USD/output token | | Planning allocation · two copies | Approximate target service minimum | 0 | USD/month | | Planning allocation · two copies | Minimum primary CPU | 2 | vCPU | | Planning allocation · two copies | Minimum primary RAM | 8 | GiB | | Planning allocation · two copies | Minimum primary disk | 100 | GiB | | Planning allocation · two copies | Additional full-price standby copy | 1 | 0 or 1 | | Planning allocation · two copies | Allocated share of provisioned cost | 1 | fraction | | Planning allocation · two copies | Planning read/write work per vCPU-second | 1000 | operations/vCPU-second | | Planning allocation · two copies | Planning peak / mean work | 2 | multiplier | | Planning allocation · two copies | Planning primary CPU utilization | 0.7 | fraction | | Planning allocation · two copies | Resident state reserved in RAM | 0.1 | fraction | | Planning allocation · two copies | Planning disk utilization | 0.7 | fraction | | Planning allocation · two copies | Maintenance and log disk reserve | 20 | GiB | | Planning allocation · two copies | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour | | Planning allocation · two copies | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour | | Planning allocation · two copies | Staging database disk unit-price guess | 0.17 | USD/GiB-month | | Planning allocation · two copies | Dependent object sink storage price guess | 0.023 | USD/GiB-month | | Planning allocation · two copies | Dependent object sink write price guess | 0.000005 | USD/write | * CPU allocation does not imply an achieved transaction rate. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities. * Planning estimate · editable authored rates and sizing assumptions dated 2026-10-18; not verified provider prices. Explicit source planning region → Explicit target planning region, 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. * Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. * Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free. * Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified. * Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity. * A declared adapter mapping and cost model do not establish implementation availability or service equivalence. * This exact directed mapping has a design profile. Cost modeling does not establish an implemented or deployable adapter. * Authored planning assumptions, not measured adapter capacity. Editable origin rates are illustrative tariff profiles, before free allowances and discounts. * A cost scenario does not establish backend availability, protocol fidelity or production readiness. Registry serving status remains independent. * Provisioned compute and RAM are carried as resource-hours; operations are independently authored. Database size cannot be inferred from dollars alone. * Aurora/AlloyDB, MySQL/PostgreSQL and proxied targets retain their distinct backend contracts. HA, replicas and proxy allocations must be selected explicitly. * All target rates are editable authored planning guesses, not verified current list prices, customer discounts or benchmark evidence. * Named provisioned target: selected CPU, RAM and physical disk allocation grow with workload. No additional per-database-operation price is assumed. Managed service premiums and dedicated accelerator/model-fit requirements need explicit qualification. * Authored operation throughput, peak and working-set assumptions are not benchmark-calibrated. * Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied. * The workload family already selected resource-hours; the generic operations/vCPU coefficient is not applied again. * Copies and allocation fractions change cost only; they do not increase modeled primary capacity. Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied. Excluded costs and workload features: * Additional network transfer, backups, KMS, one-time migration and operational labor unless an explicit meter includes them. * Destination application execution and separately billed downstream services; supply those allocations separately. * Aurora per-IO, serverless-capacity, backup and proxy tariffs; reserved/committed-use purchase options. * Taxes, discounts, credits and free-tier allowances unless explicitly reflected in edited rates. * Unmodeled dependent services, task execution and operations outside the selected workload family. Planning assumptions authored: 2026-10-18. Model: `plan-26d892648767218a827cd999a7389676d9558486` / `2026-10-18.planning.1`. Curve: `workload-1`. ### Google Cloud SQL MySQL · Stored data **Planning estimate with editable assumptions.** These authored unit rates and capacity assumptions require provider-price verification and representative benchmarks. They do not constitute verified list-price quotes or evidence that an adapter is available. Estimated monthly service charges from native source usage; no calculator input is required. Adapter hosting and Tensor9 fees are excluded. Source: Explicit source planning region; target: Explicit target planning region; currency: USD.

Google Cloud SQL MySQL · Stored data: monthly service charges by Stored data. Exact values are in the following table.

Google Cloud SQL MySQL · Database writes: monthly service charges by Database writes. Exact values are in the following table.

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. Only discrete samples are shown. Unpriced means no target quote or cost difference is available within the sizing policy. | Database writes (per second) | Origin | Target scenario | Target | Difference | | -: | -: | - | -: | -: | | 0 | 0 | Planning allocation · one copy | 125.04 | 125.04 | | 0 | 0 | Planning allocation · two copies | 250.08 | 250.08 | | 1 | 0 | Planning allocation · one copy | 125.04 | 125.04 | | 1 | 0 | Planning allocation · two copies | 250.08 | 250.08 | | 10 | 0 | Planning allocation · one copy | 125.04 | 125.04 | | 10 | 0 | Planning allocation · two copies | 250.08 | 250.08 | | 100 | 0 | Planning allocation · one copy | 125.04 | 125.04 | | 100 | 0 | Planning allocation · two copies | 250.08 | 250.08 | | 1000 | 0 | Planning allocation · one copy | 125.04 | 125.04 | | 1000 | 0 | Planning allocation · two copies | 250.08 | 250.08 | | 10000 | 0 | Planning allocation · one copy | 125.04 | 125.04 | | 10000 | 0 | Planning allocation · two copies | 250.08 | 250.08 | **Estimated allocation from planning assumptions; not benchmark calibrated.** The sizing policy grows compute with translated work and peak headroom, memory with compute and working set, and disk with resident working state and reserve. Monthly usage is distinct from resident data; each workload's assumptions define the translation. HA changes pricing, not this policy's throughput estimate. Unpriced workloads exceed the policy's configuration range; no silent vertical cap or automatic sharding is assumed. | Sample / scenario | Basis | Mean / peak work/s | Required vCPU | Allocated vCPU | Memory GiB | SSD GiB | Resident GiB | Policy | Constraints | | - | - | -: | -: | -: | -: | -: | -: | - | - | | 0 per second / Planning allocation · one copy | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-18.1` | None reported | | 0 per second / Planning allocation · two copies | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-18.1` | None reported | | 1 per second / Planning allocation · one copy | PlanningAssumption | 1 / 2 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-18.1` | None reported | | 1 per second / Planning allocation · two copies | PlanningAssumption | 1 / 2 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-18.1` | None reported | | 10 per second / Planning allocation · one copy | PlanningAssumption | 10 / 20 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-18.1` | None reported | | 10 per second / Planning allocation · two copies | PlanningAssumption | 10 / 20 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-18.1` | None reported | | 100 per second / Planning allocation · one copy | PlanningAssumption | 100 / 200 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-18.1` | None reported | | 100 per second / Planning allocation · two copies | PlanningAssumption | 100 / 200 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-18.1` | None reported | | 1000 per second / Planning allocation · one copy | PlanningAssumption | 1000 / 2000 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-18.1` | None reported | | 1000 per second / Planning allocation · two copies | PlanningAssumption | 1000 / 2000 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-18.1` | None reported | | 10000 per second / Planning allocation · one copy | PlanningAssumption | 10000 / 20000 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-18.1` | None reported | | 10000 per second / Planning allocation · two copies | PlanningAssumption | 10000 / 20000 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-18.1` | None reported | * Authored operation throughput, peak and working-set assumptions are not benchmark-calibrated. * Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied. * The workload family already selected resource-hours; the generic operations/vCPU coefficient is not applied again. * Copies and allocation fractions change cost only; they do not increase modeled primary capacity. **Curve assumptions** | Target scenario | Assumption | Value | Unit | | - | - | -: | - | | Planning allocation · one copy | Origin price guess · Primary compute | 0.0413 | USD/vCPU-hours | | Planning allocation · one copy | Origin price guess · Primary memory | 0.007 | USD/GiB-hours | | Planning allocation · one copy | Origin price guess · Primary provisioned storage | 0.115 | USD/GiB-month | | Planning allocation · one copy | Origin price guess · Database reads | 0 | USD/operations | | Planning allocation · one copy | Origin price guess · Database writes | 0 | USD/operations | | Planning allocation · one copy | Target CPU / source CPU | 1 | multiplier | | Planning allocation · one copy | Target RAM / source RAM | 1 | multiplier | | Planning allocation · one copy | Target disk / source disk | 1 | multiplier | | Planning allocation · one copy | Target price guess · read | 0 | USD/read | | Planning allocation · one copy | Target price guess · write | 0 | USD/write | | Planning allocation · one copy | Target price guess · provider operation | 0 | USD/provider operation | | Planning allocation · one copy | Target price guess · GiB-month | 0.17 | USD/GiB-month | | Planning allocation · one copy | Target price guess · published GiB | 0 | USD/published GiB | | Planning allocation · one copy | Target price guess · delivered GiB | 0 | USD/delivered GiB | | Planning allocation · one copy | Target price guess · network GiB | 0.09 | USD/network GiB | | Planning allocation · one copy | Target price guess · replica GiB-month | 0 | USD/replica GiB-month | | Planning allocation · one copy | Target price guess · vCPU-hour | 0.05 | USD/vCPU-hour | | Planning allocation · one copy | Target price guess · GiB-hour | 0.006 | USD/GiB-hour | | Planning allocation · one copy | Target price guess · resource-hour | 0 | USD/resource-hour | | Planning allocation · one copy | Target price guess · resource-month | 0 | USD/resource-month | | Planning allocation · one copy | Target price guess · input token | 0 | USD/input token | | Planning allocation · one copy | Target price guess · output token | 0 | USD/output token | | Planning allocation · one copy | Approximate target service minimum | 0 | USD/month | | Planning allocation · one copy | Minimum primary CPU | 2 | vCPU | | Planning allocation · one copy | Minimum primary RAM | 8 | GiB | | Planning allocation · one copy | Minimum primary disk | 100 | GiB | | Planning allocation · one copy | Additional full-price standby copy | 0 | 0 or 1 | | Planning allocation · one copy | Allocated share of provisioned cost | 1 | fraction | | Planning allocation · one copy | Planning read/write work per vCPU-second | 1000 | operations/vCPU-second | | Planning allocation · one copy | Planning peak / mean work | 2 | multiplier | | Planning allocation · one copy | Planning primary CPU utilization | 0.7 | fraction | | Planning allocation · one copy | Resident state reserved in RAM | 0.1 | fraction | | Planning allocation · one copy | Planning disk utilization | 0.7 | fraction | | Planning allocation · one copy | Maintenance and log disk reserve | 20 | GiB | | Planning allocation · one copy | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour | | Planning allocation · one copy | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour | | Planning allocation · one copy | Staging database disk unit-price guess | 0.17 | USD/GiB-month | | Planning allocation · one copy | Dependent object sink storage price guess | 0.023 | USD/GiB-month | | Planning allocation · one copy | Dependent object sink write price guess | 0.000005 | USD/write | | Planning allocation · two copies | Origin price guess · Primary compute | 0.0413 | USD/vCPU-hours | | Planning allocation · two copies | Origin price guess · Primary memory | 0.007 | USD/GiB-hours | | Planning allocation · two copies | Origin price guess · Primary provisioned storage | 0.115 | USD/GiB-month | | Planning allocation · two copies | Origin price guess · Database reads | 0 | USD/operations | | Planning allocation · two copies | Origin price guess · Database writes | 0 | USD/operations | | Planning allocation · two copies | Target CPU / source CPU | 1 | multiplier | | Planning allocation · two copies | Target RAM / source RAM | 1 | multiplier | | Planning allocation · two copies | Target disk / source disk | 1 | multiplier | | Planning allocation · two copies | Target price guess · read | 0 | USD/read | | Planning allocation · two copies | Target price guess · write | 0 | USD/write | | Planning allocation · two copies | Target price guess · provider operation | 0 | USD/provider operation | | Planning allocation · two copies | Target price guess · GiB-month | 0.17 | USD/GiB-month | | Planning allocation · two copies | Target price guess · published GiB | 0 | USD/published GiB | | Planning allocation · two copies | Target price guess · delivered GiB | 0 | USD/delivered GiB | | Planning allocation · two copies | Target price guess · network GiB | 0.09 | USD/network GiB | | Planning allocation · two copies | Target price guess · replica GiB-month | 0 | USD/replica GiB-month | | Planning allocation · two copies | Target price guess · vCPU-hour | 0.05 | USD/vCPU-hour | | Planning allocation · two copies | Target price guess · GiB-hour | 0.006 | USD/GiB-hour | | Planning allocation · two copies | Target price guess · resource-hour | 0 | USD/resource-hour | | Planning allocation · two copies | Target price guess · resource-month | 0 | USD/resource-month | | Planning allocation · two copies | Target price guess · input token | 0 | USD/input token | | Planning allocation · two copies | Target price guess · output token | 0 | USD/output token | | Planning allocation · two copies | Approximate target service minimum | 0 | USD/month | | Planning allocation · two copies | Minimum primary CPU | 2 | vCPU | | Planning allocation · two copies | Minimum primary RAM | 8 | GiB | | Planning allocation · two copies | Minimum primary disk | 100 | GiB | | Planning allocation · two copies | Additional full-price standby copy | 1 | 0 or 1 | | Planning allocation · two copies | Allocated share of provisioned cost | 1 | fraction | | Planning allocation · two copies | Planning read/write work per vCPU-second | 1000 | operations/vCPU-second | | Planning allocation · two copies | Planning peak / mean work | 2 | multiplier | | Planning allocation · two copies | Planning primary CPU utilization | 0.7 | fraction | | Planning allocation · two copies | Resident state reserved in RAM | 0.1 | fraction | | Planning allocation · two copies | Planning disk utilization | 0.7 | fraction | | Planning allocation · two copies | Maintenance and log disk reserve | 20 | GiB | | Planning allocation · two copies | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour | | Planning allocation · two copies | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour | | Planning allocation · two copies | Staging database disk unit-price guess | 0.17 | USD/GiB-month | | Planning allocation · two copies | Dependent object sink storage price guess | 0.023 | USD/GiB-month | | Planning allocation · two copies | Dependent object sink write price guess | 0.000005 | USD/write | * Source compute and stored data remain independent; a throughput view needs explicit workload inputs. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities. * Planning estimate · editable authored rates and sizing assumptions dated 2026-10-18; not verified provider prices. Explicit source planning region → Explicit target planning region, 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. * Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. * Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free. * Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified. * Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity. * A declared adapter mapping and cost model do not establish implementation availability or service equivalence. * This exact directed mapping has a design profile. Cost modeling does not establish an implemented or deployable adapter. * Authored planning assumptions, not measured adapter capacity. Editable origin rates are illustrative tariff profiles, before free allowances and discounts. * A cost scenario does not establish backend availability, protocol fidelity or production readiness. Registry serving status remains independent. * Provisioned compute and RAM are carried as resource-hours; operations are independently authored. Database size cannot be inferred from dollars alone. * Aurora/AlloyDB, MySQL/PostgreSQL and proxied targets retain their distinct backend contracts. HA, replicas and proxy allocations must be selected explicitly. * All target rates are editable authored planning guesses, not verified current list prices, customer discounts or benchmark evidence. * Named provisioned target: selected CPU, RAM and physical disk allocation grow with workload. No additional per-database-operation price is assumed. Managed service premiums and dedicated accelerator/model-fit requirements need explicit qualification. * Authored operation throughput, peak and working-set assumptions are not benchmark-calibrated. * Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied. * The workload family already selected resource-hours; the generic operations/vCPU coefficient is not applied again. * Copies and allocation fractions change cost only; they do not increase modeled primary capacity. Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied. Excluded costs and workload features: * Additional network transfer, backups, KMS, one-time migration and operational labor unless an explicit meter includes them. * Destination application execution and separately billed downstream services; supply those allocations separately. * Aurora per-IO, serverless-capacity, backup and proxy tariffs; reserved/committed-use purchase options. * Taxes, discounts, credits and free-tier allowances unless explicitly reflected in edited rates. * Unmodeled dependent services, task execution and operations outside the selected workload family. Planning assumptions authored: 2026-10-18. Model: `plan-26d892648767218a827cd999a7389676d9558486` / `2026-10-18.planning.1`. Curve: `workload-3`. ## Google Cloud SQL MySQL → RDS MySQL Origin API: `google::1.0.0::cloudsql::mysql`. Target backend: `aws::1.0.0::rds::mysql`. **Planning estimate with editable assumptions.** Unit rates, workload amplification and capacity assumptions are educated guesses awaiting verification. The displayed amounts are planning estimates, not verified provider list-price quotes or benchmark-qualified capacity. Region names identify the authored scenario assumptions. **Designed mapping.** This cost model describes an intended adapter. Its estimated price does not establish a delivered or selectable backend. ### Google Cloud SQL MySQL · Primary allocated compute **Planning estimate with editable assumptions.** These authored unit rates and capacity assumptions require provider-price verification and representative benchmarks. They do not constitute verified list-price quotes or evidence that an adapter is available. Estimated monthly service charges from native source usage; no calculator input is required. Adapter hosting and Tensor9 fees are excluded. Source: Explicit source planning region; target: Explicit target planning region; currency: USD.

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. Only discrete samples are shown. Unpriced means no target quote or cost difference is available within the sizing policy. | Primary allocated compute (vCPU-hours/month) | Origin | Target scenario | Target | Difference | | -: | -: | - | -: | -: | | 0 | 0 | Planning allocation · one copy | 125.04 | 125.04 | | 0 | 0 | Planning allocation · two copies | 250.08 | 250.08 | | 1460 | 60.298 | Planning allocation · one copy | 125.04 | 64.742 | | 1460 | 60.298 | Planning allocation · two copies | 250.08 | 189.782 | | 2920 | 120.596 | Planning allocation · one copy | 233.08 | 112.484 | | 2920 | 120.596 | Planning allocation · two copies | 466.16 | 345.564 | | 5840 | 241.192 | Planning allocation · one copy | 449.16 | 207.968 | | 5840 | 241.192 | Planning allocation · two copies | 898.32 | 657.128 | | 11680 | 482.384 | Planning allocation · one copy | 881.32 | 398.936 | | 11680 | 482.384 | Planning allocation · two copies | 1762.64 | 1280.256 | | 23360 | 964.768 | Planning allocation · one copy | 1745.64 | 780.872 | | 23360 | 964.768 | Planning allocation · two copies | 3491.28 | 2526.512 | | 46720 | 1929.536 | Planning allocation · one copy | 3474.28 | 1544.744 | | 46720 | 1929.536 | Planning allocation · two copies | 6948.56 | 5019.024 | **Estimated allocation from planning assumptions; not benchmark calibrated.** The sizing policy grows compute with translated work and peak headroom, memory with compute and working set, and disk with resident working state and reserve. Monthly usage is distinct from resident data; each workload's assumptions define the translation. HA changes pricing, not this policy's throughput estimate. Unpriced workloads exceed the policy's configuration range; no silent vertical cap or automatic sharding is assumed. | Sample / scenario | Basis | Mean / peak work/s | Required vCPU | Allocated vCPU | Memory GiB | SSD GiB | Resident GiB | Policy | Constraints | | - | - | -: | -: | -: | -: | -: | -: | - | - | | 0 vCPU-hours/month / Planning allocation · one copy | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-18.1` | None reported | | 0 vCPU-hours/month / Planning allocation · two copies | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-18.1` | None reported | | 1460 vCPU-hours/month / Planning allocation · one copy | PlanningAssumption | 0 / 0 | 2 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-18.1` | None reported | | 1460 vCPU-hours/month / Planning allocation · two copies | PlanningAssumption | 0 / 0 | 2 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-18.1` | None reported | | 2920 vCPU-hours/month / Planning allocation · one copy | PlanningAssumption | 0 / 0 | 4 | 4 | 16 | 100 | 0 | `service-adapter-planning-2026-10-18.1` | None reported | | 2920 vCPU-hours/month / Planning allocation · two copies | PlanningAssumption | 0 / 0 | 4 | 4 | 16 | 100 | 0 | `service-adapter-planning-2026-10-18.1` | None reported | | 5840 vCPU-hours/month / Planning allocation · one copy | PlanningAssumption | 0 / 0 | 8 | 8 | 32 | 100 | 0 | `service-adapter-planning-2026-10-18.1` | None reported | | 5840 vCPU-hours/month / Planning allocation · two copies | PlanningAssumption | 0 / 0 | 8 | 8 | 32 | 100 | 0 | `service-adapter-planning-2026-10-18.1` | None reported | | 11680 vCPU-hours/month / Planning allocation · one copy | PlanningAssumption | 0 / 0 | 16 | 16 | 64 | 100 | 0 | `service-adapter-planning-2026-10-18.1` | None reported | | 11680 vCPU-hours/month / Planning allocation · two copies | PlanningAssumption | 0 / 0 | 16 | 16 | 64 | 100 | 0 | `service-adapter-planning-2026-10-18.1` | None reported | | 23360 vCPU-hours/month / Planning allocation · one copy | PlanningAssumption | 0 / 0 | 32 | 32 | 128 | 100 | 0 | `service-adapter-planning-2026-10-18.1` | None reported | | 23360 vCPU-hours/month / Planning allocation · two copies | PlanningAssumption | 0 / 0 | 32 | 32 | 128 | 100 | 0 | `service-adapter-planning-2026-10-18.1` | None reported | | 46720 vCPU-hours/month / Planning allocation · one copy | PlanningAssumption | 0 / 0 | 64 | 64 | 256 | 100 | 0 | `service-adapter-planning-2026-10-18.1` | None reported | | 46720 vCPU-hours/month / Planning allocation · two copies | PlanningAssumption | 0 / 0 | 64 | 64 | 256 | 100 | 0 | `service-adapter-planning-2026-10-18.1` | None reported | * Authored operation throughput, peak and working-set assumptions are not benchmark-calibrated. * Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied. * The workload family already selected resource-hours; the generic operations/vCPU coefficient is not applied again. * Copies and allocation fractions change cost only; they do not increase modeled primary capacity. **Curve assumptions** | Target scenario | Assumption | Value | Unit | | - | - | -: | - | | Planning allocation · one copy | Origin price guess · Primary compute | 0.0413 | USD/vCPU-hours | | Planning allocation · one copy | Origin price guess · Primary memory | 0.007 | USD/GiB-hours | | Planning allocation · one copy | Origin price guess · Primary provisioned storage | 0.115 | USD/GiB-month | | Planning allocation · one copy | Origin price guess · Database reads | 0 | USD/operations | | Planning allocation · one copy | Origin price guess · Database writes | 0 | USD/operations | | Planning allocation · one copy | Target CPU / source CPU | 1 | multiplier | | Planning allocation · one copy | Target RAM / source RAM | 1 | multiplier | | Planning allocation · one copy | Target disk / source disk | 1 | multiplier | | Planning allocation · one copy | Target price guess · read | 0 | USD/read | | Planning allocation · one copy | Target price guess · write | 0 | USD/write | | Planning allocation · one copy | Target price guess · provider operation | 0 | USD/provider operation | | Planning allocation · one copy | Target price guess · GiB-month | 0.17 | USD/GiB-month | | Planning allocation · one copy | Target price guess · published GiB | 0 | USD/published GiB | | Planning allocation · one copy | Target price guess · delivered GiB | 0 | USD/delivered GiB | | Planning allocation · one copy | Target price guess · network GiB | 0.09 | USD/network GiB | | Planning allocation · one copy | Target price guess · replica GiB-month | 0 | USD/replica GiB-month | | Planning allocation · one copy | Target price guess · vCPU-hour | 0.05 | USD/vCPU-hour | | Planning allocation · one copy | Target price guess · GiB-hour | 0.006 | USD/GiB-hour | | Planning allocation · one copy | Target price guess · resource-hour | 0 | USD/resource-hour | | Planning allocation · one copy | Target price guess · resource-month | 0 | USD/resource-month | | Planning allocation · one copy | Target price guess · input token | 0 | USD/input token | | Planning allocation · one copy | Target price guess · output token | 0 | USD/output token | | Planning allocation · one copy | Approximate target service minimum | 0 | USD/month | | Planning allocation · one copy | Minimum primary CPU | 2 | vCPU | | Planning allocation · one copy | Minimum primary RAM | 8 | GiB | | Planning allocation · one copy | Minimum primary disk | 100 | GiB | | Planning allocation · one copy | Additional full-price standby copy | 0 | 0 or 1 | | Planning allocation · one copy | Allocated share of provisioned cost | 1 | fraction | | Planning allocation · one copy | Planning read/write work per vCPU-second | 1000 | operations/vCPU-second | | Planning allocation · one copy | Planning peak / mean work | 2 | multiplier | | Planning allocation · one copy | Planning primary CPU utilization | 0.7 | fraction | | Planning allocation · one copy | Resident state reserved in RAM | 0.1 | fraction | | Planning allocation · one copy | Planning disk utilization | 0.7 | fraction | | Planning allocation · one copy | Maintenance and log disk reserve | 20 | GiB | | Planning allocation · one copy | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour | | Planning allocation · one copy | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour | | Planning allocation · one copy | Staging database disk unit-price guess | 0.17 | USD/GiB-month | | Planning allocation · one copy | Dependent object sink storage price guess | 0.023 | USD/GiB-month | | Planning allocation · one copy | Dependent object sink write price guess | 0.000005 | USD/write | | Planning allocation · two copies | Origin price guess · Primary compute | 0.0413 | USD/vCPU-hours | | Planning allocation · two copies | Origin price guess · Primary memory | 0.007 | USD/GiB-hours | | Planning allocation · two copies | Origin price guess · Primary provisioned storage | 0.115 | USD/GiB-month | | Planning allocation · two copies | Origin price guess · Database reads | 0 | USD/operations | | Planning allocation · two copies | Origin price guess · Database writes | 0 | USD/operations | | Planning allocation · two copies | Target CPU / source CPU | 1 | multiplier | | Planning allocation · two copies | Target RAM / source RAM | 1 | multiplier | | Planning allocation · two copies | Target disk / source disk | 1 | multiplier | | Planning allocation · two copies | Target price guess · read | 0 | USD/read | | Planning allocation · two copies | Target price guess · write | 0 | USD/write | | Planning allocation · two copies | Target price guess · provider operation | 0 | USD/provider operation | | Planning allocation · two copies | Target price guess · GiB-month | 0.17 | USD/GiB-month | | Planning allocation · two copies | Target price guess · published GiB | 0 | USD/published GiB | | Planning allocation · two copies | Target price guess · delivered GiB | 0 | USD/delivered GiB | | Planning allocation · two copies | Target price guess · network GiB | 0.09 | USD/network GiB | | Planning allocation · two copies | Target price guess · replica GiB-month | 0 | USD/replica GiB-month | | Planning allocation · two copies | Target price guess · vCPU-hour | 0.05 | USD/vCPU-hour | | Planning allocation · two copies | Target price guess · GiB-hour | 0.006 | USD/GiB-hour | | Planning allocation · two copies | Target price guess · resource-hour | 0 | USD/resource-hour | | Planning allocation · two copies | Target price guess · resource-month | 0 | USD/resource-month | | Planning allocation · two copies | Target price guess · input token | 0 | USD/input token | | Planning allocation · two copies | Target price guess · output token | 0 | USD/output token | | Planning allocation · two copies | Approximate target service minimum | 0 | USD/month | | Planning allocation · two copies | Minimum primary CPU | 2 | vCPU | | Planning allocation · two copies | Minimum primary RAM | 8 | GiB | | Planning allocation · two copies | Minimum primary disk | 100 | GiB | | Planning allocation · two copies | Additional full-price standby copy | 1 | 0 or 1 | | Planning allocation · two copies | Allocated share of provisioned cost | 1 | fraction | | Planning allocation · two copies | Planning read/write work per vCPU-second | 1000 | operations/vCPU-second | | Planning allocation · two copies | Planning peak / mean work | 2 | multiplier | | Planning allocation · two copies | Planning primary CPU utilization | 0.7 | fraction | | Planning allocation · two copies | Resident state reserved in RAM | 0.1 | fraction | | Planning allocation · two copies | Planning disk utilization | 0.7 | fraction | | Planning allocation · two copies | Maintenance and log disk reserve | 20 | GiB | | Planning allocation · two copies | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour | | Planning allocation · two copies | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour | | Planning allocation · two copies | Staging database disk unit-price guess | 0.17 | USD/GiB-month | | Planning allocation · two copies | Dependent object sink storage price guess | 0.023 | USD/GiB-month | | Planning allocation · two copies | Dependent object sink write price guess | 0.000005 | USD/write | * CPU allocation does not imply an achieved transaction rate. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities. * Planning estimate · editable authored rates and sizing assumptions dated 2026-10-18; not verified provider prices. Explicit source planning region → Explicit target planning region, 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. * Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. * Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free. * Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified. * Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity. * A declared adapter mapping and cost model do not establish implementation availability or service equivalence. * This exact directed mapping has a design profile. Cost modeling does not establish an implemented or deployable adapter. * Authored planning assumptions, not measured adapter capacity. Editable origin rates are illustrative tariff profiles, before free allowances and discounts. * A cost scenario does not establish backend availability, protocol fidelity or production readiness. Registry serving status remains independent. * Provisioned compute and RAM are carried as resource-hours; operations are independently authored. Database size cannot be inferred from dollars alone. * Aurora/AlloyDB, MySQL/PostgreSQL and proxied targets retain their distinct backend contracts. HA, replicas and proxy allocations must be selected explicitly. * All target rates are editable authored planning guesses, not verified current list prices, customer discounts or benchmark evidence. * Named provisioned target: selected CPU, RAM and physical disk allocation grow with workload. No additional per-database-operation price is assumed. Managed service premiums and dedicated accelerator/model-fit requirements need explicit qualification. * Authored operation throughput, peak and working-set assumptions are not benchmark-calibrated. * Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied. * The workload family already selected resource-hours; the generic operations/vCPU coefficient is not applied again. * Copies and allocation fractions change cost only; they do not increase modeled primary capacity. Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied. Excluded costs and workload features: * Additional network transfer, backups, KMS, one-time migration and operational labor unless an explicit meter includes them. * Destination application execution and separately billed downstream services; supply those allocations separately. * Aurora per-IO, serverless-capacity, backup and proxy tariffs; reserved/committed-use purchase options. * Taxes, discounts, credits and free-tier allowances unless explicitly reflected in edited rates. * Unmodeled dependent services, task execution and operations outside the selected workload family. Planning assumptions authored: 2026-10-18. Model: `plan-e101a504b4b64d7a523834103fda85b8f5ab6414` / `2026-10-18.planning.1`. Curve: `workload-1`. ### Google Cloud SQL MySQL · Stored data **Planning estimate with editable assumptions.** These authored unit rates and capacity assumptions require provider-price verification and representative benchmarks. They do not constitute verified list-price quotes or evidence that an adapter is available. Estimated monthly service charges from native source usage; no calculator input is required. Adapter hosting and Tensor9 fees are excluded. Source: Explicit source planning region; target: Explicit target planning region; currency: USD.

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. Only discrete samples are shown. Unpriced means no target quote or cost difference is available within the sizing policy. | Database writes (per second) | Origin | Target scenario | Target | Difference | | -: | -: | - | -: | -: | | 0 | 0 | Planning allocation · one copy | 125.04 | 125.04 | | 0 | 0 | Planning allocation · two copies | 250.08 | 250.08 | | 1 | 0 | Planning allocation · one copy | 125.04 | 125.04 | | 1 | 0 | Planning allocation · two copies | 250.08 | 250.08 | | 10 | 0 | Planning allocation · one copy | 125.04 | 125.04 | | 10 | 0 | Planning allocation · two copies | 250.08 | 250.08 | | 100 | 0 | Planning allocation · one copy | 125.04 | 125.04 | | 100 | 0 | Planning allocation · two copies | 250.08 | 250.08 | | 1000 | 0 | Planning allocation · one copy | 125.04 | 125.04 | | 1000 | 0 | Planning allocation · two copies | 250.08 | 250.08 | | 10000 | 0 | Planning allocation · one copy | 125.04 | 125.04 | | 10000 | 0 | Planning allocation · two copies | 250.08 | 250.08 | **Estimated allocation from planning assumptions; not benchmark calibrated.** The sizing policy grows compute with translated work and peak headroom, memory with compute and working set, and disk with resident working state and reserve. Monthly usage is distinct from resident data; each workload's assumptions define the translation. HA changes pricing, not this policy's throughput estimate. Unpriced workloads exceed the policy's configuration range; no silent vertical cap or automatic sharding is assumed. | Sample / scenario | Basis | Mean / peak work/s | Required vCPU | Allocated vCPU | Memory GiB | SSD GiB | Resident GiB | Policy | Constraints | | - | - | -: | -: | -: | -: | -: | -: | - | - | | 0 per second / Planning allocation · one copy | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-18.1` | None reported | | 0 per second / Planning allocation · two copies | PlanningAssumption | 0 / 0 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-18.1` | None reported | | 1 per second / Planning allocation · one copy | PlanningAssumption | 1 / 2 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-18.1` | None reported | | 1 per second / Planning allocation · two copies | PlanningAssumption | 1 / 2 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-18.1` | None reported | | 10 per second / Planning allocation · one copy | PlanningAssumption | 10 / 20 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-18.1` | None reported | | 10 per second / Planning allocation · two copies | PlanningAssumption | 10 / 20 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-18.1` | None reported | | 100 per second / Planning allocation · one copy | PlanningAssumption | 100 / 200 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-18.1` | None reported | | 100 per second / Planning allocation · two copies | PlanningAssumption | 100 / 200 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-18.1` | None reported | | 1000 per second / Planning allocation · one copy | PlanningAssumption | 1000 / 2000 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-18.1` | None reported | | 1000 per second / Planning allocation · two copies | PlanningAssumption | 1000 / 2000 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-18.1` | None reported | | 10000 per second / Planning allocation · one copy | PlanningAssumption | 10000 / 20000 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-18.1` | None reported | | 10000 per second / Planning allocation · two copies | PlanningAssumption | 10000 / 20000 | 0 | 2 | 8 | 100 | 0 | `service-adapter-planning-2026-10-18.1` | None reported | * Authored operation throughput, peak and working-set assumptions are not benchmark-calibrated. * Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied. * The workload family already selected resource-hours; the generic operations/vCPU coefficient is not applied again. * Copies and allocation fractions change cost only; they do not increase modeled primary capacity. **Curve assumptions** | Target scenario | Assumption | Value | Unit | | - | - | -: | - | | Planning allocation · one copy | Origin price guess · Primary compute | 0.0413 | USD/vCPU-hours | | Planning allocation · one copy | Origin price guess · Primary memory | 0.007 | USD/GiB-hours | | Planning allocation · one copy | Origin price guess · Primary provisioned storage | 0.115 | USD/GiB-month | | Planning allocation · one copy | Origin price guess · Database reads | 0 | USD/operations | | Planning allocation · one copy | Origin price guess · Database writes | 0 | USD/operations | | Planning allocation · one copy | Target CPU / source CPU | 1 | multiplier | | Planning allocation · one copy | Target RAM / source RAM | 1 | multiplier | | Planning allocation · one copy | Target disk / source disk | 1 | multiplier | | Planning allocation · one copy | Target price guess · read | 0 | USD/read | | Planning allocation · one copy | Target price guess · write | 0 | USD/write | | Planning allocation · one copy | Target price guess · provider operation | 0 | USD/provider operation | | Planning allocation · one copy | Target price guess · GiB-month | 0.17 | USD/GiB-month | | Planning allocation · one copy | Target price guess · published GiB | 0 | USD/published GiB | | Planning allocation · one copy | Target price guess · delivered GiB | 0 | USD/delivered GiB | | Planning allocation · one copy | Target price guess · network GiB | 0.09 | USD/network GiB | | Planning allocation · one copy | Target price guess · replica GiB-month | 0 | USD/replica GiB-month | | Planning allocation · one copy | Target price guess · vCPU-hour | 0.05 | USD/vCPU-hour | | Planning allocation · one copy | Target price guess · GiB-hour | 0.006 | USD/GiB-hour | | Planning allocation · one copy | Target price guess · resource-hour | 0 | USD/resource-hour | | Planning allocation · one copy | Target price guess · resource-month | 0 | USD/resource-month | | Planning allocation · one copy | Target price guess · input token | 0 | USD/input token | | Planning allocation · one copy | Target price guess · output token | 0 | USD/output token | | Planning allocation · one copy | Approximate target service minimum | 0 | USD/month | | Planning allocation · one copy | Minimum primary CPU | 2 | vCPU | | Planning allocation · one copy | Minimum primary RAM | 8 | GiB | | Planning allocation · one copy | Minimum primary disk | 100 | GiB | | Planning allocation · one copy | Additional full-price standby copy | 0 | 0 or 1 | | Planning allocation · one copy | Allocated share of provisioned cost | 1 | fraction | | Planning allocation · one copy | Planning read/write work per vCPU-second | 1000 | operations/vCPU-second | | Planning allocation · one copy | Planning peak / mean work | 2 | multiplier | | Planning allocation · one copy | Planning primary CPU utilization | 0.7 | fraction | | Planning allocation · one copy | Resident state reserved in RAM | 0.1 | fraction | | Planning allocation · one copy | Planning disk utilization | 0.7 | fraction | | Planning allocation · one copy | Maintenance and log disk reserve | 20 | GiB | | Planning allocation · one copy | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour | | Planning allocation · one copy | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour | | Planning allocation · one copy | Staging database disk unit-price guess | 0.17 | USD/GiB-month | | Planning allocation · one copy | Dependent object sink storage price guess | 0.023 | USD/GiB-month | | Planning allocation · one copy | Dependent object sink write price guess | 0.000005 | USD/write | | Planning allocation · two copies | Origin price guess · Primary compute | 0.0413 | USD/vCPU-hours | | Planning allocation · two copies | Origin price guess · Primary memory | 0.007 | USD/GiB-hours | | Planning allocation · two copies | Origin price guess · Primary provisioned storage | 0.115 | USD/GiB-month | | Planning allocation · two copies | Origin price guess · Database reads | 0 | USD/operations | | Planning allocation · two copies | Origin price guess · Database writes | 0 | USD/operations | | Planning allocation · two copies | Target CPU / source CPU | 1 | multiplier | | Planning allocation · two copies | Target RAM / source RAM | 1 | multiplier | | Planning allocation · two copies | Target disk / source disk | 1 | multiplier | | Planning allocation · two copies | Target price guess · read | 0 | USD/read | | Planning allocation · two copies | Target price guess · write | 0 | USD/write | | Planning allocation · two copies | Target price guess · provider operation | 0 | USD/provider operation | | Planning allocation · two copies | Target price guess · GiB-month | 0.17 | USD/GiB-month | | Planning allocation · two copies | Target price guess · published GiB | 0 | USD/published GiB | | Planning allocation · two copies | Target price guess · delivered GiB | 0 | USD/delivered GiB | | Planning allocation · two copies | Target price guess · network GiB | 0.09 | USD/network GiB | | Planning allocation · two copies | Target price guess · replica GiB-month | 0 | USD/replica GiB-month | | Planning allocation · two copies | Target price guess · vCPU-hour | 0.05 | USD/vCPU-hour | | Planning allocation · two copies | Target price guess · GiB-hour | 0.006 | USD/GiB-hour | | Planning allocation · two copies | Target price guess · resource-hour | 0 | USD/resource-hour | | Planning allocation · two copies | Target price guess · resource-month | 0 | USD/resource-month | | Planning allocation · two copies | Target price guess · input token | 0 | USD/input token | | Planning allocation · two copies | Target price guess · output token | 0 | USD/output token | | Planning allocation · two copies | Approximate target service minimum | 0 | USD/month | | Planning allocation · two copies | Minimum primary CPU | 2 | vCPU | | Planning allocation · two copies | Minimum primary RAM | 8 | GiB | | Planning allocation · two copies | Minimum primary disk | 100 | GiB | | Planning allocation · two copies | Additional full-price standby copy | 1 | 0 or 1 | | Planning allocation · two copies | Allocated share of provisioned cost | 1 | fraction | | Planning allocation · two copies | Planning read/write work per vCPU-second | 1000 | operations/vCPU-second | | Planning allocation · two copies | Planning peak / mean work | 2 | multiplier | | Planning allocation · two copies | Planning primary CPU utilization | 0.7 | fraction | | Planning allocation · two copies | Resident state reserved in RAM | 0.1 | fraction | | Planning allocation · two copies | Planning disk utilization | 0.7 | fraction | | Planning allocation · two copies | Maintenance and log disk reserve | 20 | GiB | | Planning allocation · two copies | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour | | Planning allocation · two copies | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour | | Planning allocation · two copies | Staging database disk unit-price guess | 0.17 | USD/GiB-month | | Planning allocation · two copies | Dependent object sink storage price guess | 0.023 | USD/GiB-month | | Planning allocation · two copies | Dependent object sink write price guess | 0.000005 | USD/write | * Source compute and stored data remain independent; a throughput view needs explicit workload inputs. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities. * Planning estimate · editable authored rates and sizing assumptions dated 2026-10-18; not verified provider prices. Explicit source planning region → Explicit target planning region, 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. * Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. * Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free. * Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified. * Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity. * A declared adapter mapping and cost model do not establish implementation availability or service equivalence. * This exact directed mapping has a design profile. Cost modeling does not establish an implemented or deployable adapter. * Authored planning assumptions, not measured adapter capacity. Editable origin rates are illustrative tariff profiles, before free allowances and discounts. * A cost scenario does not establish backend availability, protocol fidelity or production readiness. Registry serving status remains independent. * Provisioned compute and RAM are carried as resource-hours; operations are independently authored. Database size cannot be inferred from dollars alone. * Aurora/AlloyDB, MySQL/PostgreSQL and proxied targets retain their distinct backend contracts. HA, replicas and proxy allocations must be selected explicitly. * All target rates are editable authored planning guesses, not verified current list prices, customer discounts or benchmark evidence. * Named provisioned target: selected CPU, RAM and physical disk allocation grow with workload. No additional per-database-operation price is assumed. Managed service premiums and dedicated accelerator/model-fit requirements need explicit qualification. * Authored operation throughput, peak and working-set assumptions are not benchmark-calibrated. * Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied. * The workload family already selected resource-hours; the generic operations/vCPU coefficient is not applied again. * Copies and allocation fractions change cost only; they do not increase modeled primary capacity. Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied. Excluded costs and workload features: * Additional network transfer, backups, KMS, one-time migration and operational labor unless an explicit meter includes them. * Destination application execution and separately billed downstream services; supply those allocations separately. * Aurora per-IO, serverless-capacity, backup and proxy tariffs; reserved/committed-use purchase options. * Taxes, discounts, credits and free-tier allowances unless explicitly reflected in edited rates. * Unmodeled dependent services, task execution and operations outside the selected workload family. Planning assumptions authored: 2026-10-18. Model: `plan-e101a504b4b64d7a523834103fda85b8f5ab6414` / `2026-10-18.planning.1`. Curve: `workload-3`. See the [service catalog](/byoc/service-adapters/catalog) for operation coverage, supported directions and backend limitations. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.