SQS FIFO → Azure Cosmos DB (queue)
Origin API:aws::1.0.0::sqs::fifo. Target backend: azure::1.0.0::cosmosdb::queue.
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.
SQS FIFO · SQS request billing units
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.
Curve assumptions
- 1-KiB messages, unbatched send/receive/delete; actual batch and delivery assumptions stay visible. 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 is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
- 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.
- Storage follows resident original messages, not every monthly message. Broker delivery bytes include redeliveries.
- FIFO estimates do not qualify dedup support, group throughput or single-group latency; backend limitations remain applicable.
- All target rates are editable authored planning guesses, not verified current list prices, customer discounts or benchmark evidence.
- Native broker operations price managedOperations, including selected delivery/ack work; do not substitute published GiB for operation counts.
- One 400-RU/s provisioned allocation is an authored minimum guess; the variable operation equivalent does not reproduce exact RU/s autoscaling or partitions. The editable monthly minimum and usage-equivalent charge compare using their maximum, not their sum; durable adapter state and independently selected network costs remain separate. This is not a verified provider tariff.
- 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.
plan-4f4f008a52eb766d518aa4f34d3302fdb02b1a67 / 2026-10-18.planning.1. Curve: workload-1.
SQS FIFO → Azure Service Bus
Origin API:aws::1.0.0::sqs::fifo. Target backend: azure::1.0.0::servicebus.
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.
SQS FIFO · SQS request billing units
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.
Curve assumptions
- 1-KiB messages, unbatched send/receive/delete; actual batch and delivery assumptions stay visible. 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 is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
- 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.
- Storage follows resident original messages, not every monthly message. Broker delivery bytes include redeliveries.
- FIFO estimates do not qualify dedup support, group throughput or single-group latency; backend limitations remain applicable.
- All target rates are editable authored planning guesses, not verified current list prices, customer discounts or benchmark evidence.
- Native broker operations price managedOperations, including selected delivery/ack work; do not substitute published GiB for operation counts.
- One Standard namespace base allocation is an authored monthly minimum guess; per-operation costs approximate usage above the included allowance. The editable monthly minimum and usage-equivalent charge compare using their maximum, not their sum; durable adapter state and independently selected network costs remain separate. This is not a verified provider tariff.
- 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.
plan-41a96e9bd678520a179bd0f5bb232496011160b0 / 2026-10-18.planning.1. Curve: workload-1.
SQS FIFO → Cloud SQL for PostgreSQL
Origin API:aws::1.0.0::sqs::fifo. Target backend: google::1.0.0::cloudsql::postgresql.
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.
SQS FIFO · SQS request billing units
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.
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.
- 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 generic operations/vCPU coefficient supplies a provisional compute requirement alongside explicit resource-hour minima.
- Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
- 1-KiB messages, unbatched send/receive/delete; actual batch and delivery assumptions stay visible. 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 is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
- 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.
- Storage follows resident original messages, not every monthly message. Broker delivery bytes include redeliveries.
- FIFO estimates do not qualify dedup support, group throughput or single-group latency; backend limitations remain applicable.
- 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 generic operations/vCPU coefficient supplies a provisional compute requirement alongside explicit resource-hour minima.
- Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
- 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.
plan-c35b94f39c83dfc6e65b2063cdc3c7857cb28524 / 2026-10-18.planning.1. Curve: workload-1.
SQS FIFO → PostgreSQL
Origin API:aws::1.0.0::sqs::fifo. Target backend: postgres::1.0.0::database.
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.
SQS FIFO · SQS request billing units
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.
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.
- 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 generic operations/vCPU coefficient supplies a provisional compute requirement alongside explicit resource-hour minima.
- Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
- 1-KiB messages, unbatched send/receive/delete; actual batch and delivery assumptions stay visible. 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 is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
- 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.
- Storage follows resident original messages, not every monthly message. Broker delivery bytes include redeliveries.
- FIFO estimates do not qualify dedup support, group throughput or single-group latency; backend limitations remain applicable.
- 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 generic operations/vCPU coefficient supplies a provisional compute requirement alongside explicit resource-hour minima.
- Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
- 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.
plan-2205b0bb4fecd035329ea8f524e1a885b9bdcdab / 2026-10-18.planning.1. Curve: workload-1.
SQS FIFO → PostgreSQL Flexible Server
Origin API:aws::1.0.0::sqs::fifo. Target backend: azure::1.0.0::postgresql::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.
SQS FIFO · SQS request billing units
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.
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.
- 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 generic operations/vCPU coefficient supplies a provisional compute requirement alongside explicit resource-hour minima.
- Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
- 1-KiB messages, unbatched send/receive/delete; actual batch and delivery assumptions stay visible. 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 is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
- 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.
- Storage follows resident original messages, not every monthly message. Broker delivery bytes include redeliveries.
- FIFO estimates do not qualify dedup support, group throughput or single-group latency; backend limitations remain applicable.
- 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 generic operations/vCPU coefficient supplies a provisional compute requirement alongside explicit resource-hour minima.
- Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
- 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.
plan-d6e6756733e57b05fe1084c81427de33e78217f0 / 2026-10-18.planning.1. Curve: workload-1.
SQS FIFO → Scaleway Managed Database for PostgreSQL
Origin API:aws::1.0.0::sqs::fifo. Target backend: scaleway::1.0.0::rdb::postgresql.
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.
SQS FIFO · SQS request billing units
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.
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.
- 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 generic operations/vCPU coefficient supplies a provisional compute requirement alongside explicit resource-hour minima.
- Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
- 1-KiB messages, unbatched send/receive/delete; actual batch and delivery assumptions stay visible. 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 is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
- 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.
- Storage follows resident original messages, not every monthly message. Broker delivery bytes include redeliveries.
- FIFO estimates do not qualify dedup support, group throughput or single-group latency; backend limitations remain applicable.
- 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 generic operations/vCPU coefficient supplies a provisional compute requirement alongside explicit resource-hour minima.
- Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
- 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.
plan-587f83be80f7d547d383d9abce0fac6d8798d699 / 2026-10-18.planning.1. Curve: workload-1.
SQS Standard → Azure Cosmos DB (queue)
Origin API:aws::1.0.0::sqs::classic. Target backend: azure::1.0.0::cosmosdb::queue.
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.
SQS Standard · SQS request billing units
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.
Curve assumptions
- 1-KiB messages, unbatched send/receive/delete; actual batch and delivery assumptions stay visible. 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 is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
- 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.
- Storage follows resident original messages, not every monthly message. Broker delivery bytes include redeliveries.
- FIFO estimates do not qualify dedup support, group throughput or single-group latency; backend limitations remain applicable.
- All target rates are editable authored planning guesses, not verified current list prices, customer discounts or benchmark evidence.
- Native broker operations price managedOperations, including selected delivery/ack work; do not substitute published GiB for operation counts.
- One 400-RU/s provisioned allocation is an authored minimum guess; the variable operation equivalent does not reproduce exact RU/s autoscaling or partitions. The editable monthly minimum and usage-equivalent charge compare using their maximum, not their sum; durable adapter state and independently selected network costs remain separate. This is not a verified provider tariff.
- 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.
plan-dad0c8f973de92af6643c3cb9f65340d91c718a5 / 2026-10-18.planning.1. Curve: workload-1.
SQS Standard → Azure Queue Storage
Origin API:aws::1.0.0::sqs::classic. Target backend: azure::1.0.0::queue-storage.
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.
SQS Standard · SQS request billing units
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.
Curve assumptions
- 1-KiB messages, unbatched send/receive/delete; actual batch and delivery assumptions stay visible. 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 is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
- 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.
- Storage follows resident original messages, not every monthly message. Broker delivery bytes include redeliveries.
- FIFO estimates do not qualify dedup support, group throughput or single-group latency; backend limitations remain applicable.
- All target rates are editable authored planning guesses, not verified current list prices, customer discounts or benchmark evidence.
- Native broker operations price managedOperations, including selected delivery/ack work; do not substitute published GiB for operation counts.
- 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.
plan-d5bf5eea867ef509a6394c8ab16664bacb37eb07 / 2026-10-18.planning.1. Curve: workload-1.
SQS Standard → Azure Service Bus
Origin API:aws::1.0.0::sqs::classic. Target backend: azure::1.0.0::servicebus.
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.
SQS Standard · SQS request billing units
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.
Curve assumptions
- 1-KiB messages, unbatched send/receive/delete; actual batch and delivery assumptions stay visible. 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 is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
- 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.
- Storage follows resident original messages, not every monthly message. Broker delivery bytes include redeliveries.
- FIFO estimates do not qualify dedup support, group throughput or single-group latency; backend limitations remain applicable.
- All target rates are editable authored planning guesses, not verified current list prices, customer discounts or benchmark evidence.
- Native broker operations price managedOperations, including selected delivery/ack work; do not substitute published GiB for operation counts.
- One Standard namespace base allocation is an authored monthly minimum guess; per-operation costs approximate usage above the included allowance. The editable monthly minimum and usage-equivalent charge compare using their maximum, not their sum; durable adapter state and independently selected network costs remain separate. This is not a verified provider tariff.
- 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.
plan-ca45f8cb19ce07ffe770050ff2faf4e2ac2dad0b / 2026-10-18.planning.1. Curve: workload-1.
SQS Standard → OCI Queue
Origin API:aws::1.0.0::sqs::classic. Target backend: oci::1.0.0::queue.
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.
SQS Standard · SQS request billing units
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.
Curve assumptions
- 1-KiB messages, unbatched send/receive/delete; actual batch and delivery assumptions stay visible. 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 is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
- 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.
- Storage follows resident original messages, not every monthly message. Broker delivery bytes include redeliveries.
- FIFO estimates do not qualify dedup support, group throughput or single-group latency; backend limitations remain applicable.
- All target rates are editable authored planning guesses, not verified current list prices, customer discounts or benchmark evidence.
- Native broker operations price managedOperations, including selected delivery/ack work; do not substitute published GiB for operation counts.
- 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.
plan-15dc11b20607d1fce76620d26b1597e97614129d / 2026-10-18.planning.1. Curve: workload-1.
SQS Standard → PostgreSQL
Origin API:aws::1.0.0::sqs::classic. Target backend: postgres::1.0.0::database.
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.
SQS Standard · SQS request billing units
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.
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.
- 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 generic operations/vCPU coefficient supplies a provisional compute requirement alongside explicit resource-hour minima.
- Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
- 1-KiB messages, unbatched send/receive/delete; actual batch and delivery assumptions stay visible. 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 is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
- 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.
- Storage follows resident original messages, not every monthly message. Broker delivery bytes include redeliveries.
- FIFO estimates do not qualify dedup support, group throughput or single-group latency; backend limitations remain applicable.
- 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 generic operations/vCPU coefficient supplies a provisional compute requirement alongside explicit resource-hour minima.
- Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
- 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.
plan-a5003d6d1b075ed4d7688651bd5e72c32088cf9c / 2026-10-18.planning.1. Curve: workload-1.
SQS Standard → PostgreSQL Flexible Server
Origin API:aws::1.0.0::sqs::classic. Target backend: azure::1.0.0::postgresql::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.
SQS Standard · SQS request billing units
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.
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.
- 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 generic operations/vCPU coefficient supplies a provisional compute requirement alongside explicit resource-hour minima.
- Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
- 1-KiB messages, unbatched send/receive/delete; actual batch and delivery assumptions stay visible. 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 is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
- 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.
- Storage follows resident original messages, not every monthly message. Broker delivery bytes include redeliveries.
- FIFO estimates do not qualify dedup support, group throughput or single-group latency; backend limitations remain applicable.
- 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 generic operations/vCPU coefficient supplies a provisional compute requirement alongside explicit resource-hour minima.
- Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
- 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.
plan-89783f4d5bd47a02bac1ee1d677521ebf845f89c / 2026-10-18.planning.1. Curve: workload-1.
SQS Standard → Scaleway Managed Database for PostgreSQL
Origin API:aws::1.0.0::sqs::classic. Target backend: scaleway::1.0.0::rdb::postgresql.
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.
SQS Standard · SQS request billing units
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.
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.
- 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 generic operations/vCPU coefficient supplies a provisional compute requirement alongside explicit resource-hour minima.
- Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
- 1-KiB messages, unbatched send/receive/delete; actual batch and delivery assumptions stay visible. 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 is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
- 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.
- Storage follows resident original messages, not every monthly message. Broker delivery bytes include redeliveries.
- FIFO estimates do not qualify dedup support, group throughput or single-group latency; backend limitations remain applicable.
- 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 generic operations/vCPU coefficient supplies a provisional compute requirement alongside explicit resource-hour minima.
- Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
- 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.
plan-815ddc40e99f05f91bcd38c679512124353bbc6b / 2026-10-18.planning.1. Curve: workload-1.
SQS Standard → Scaleway Queues (SQS-compatible)
Origin API:aws::1.0.0::sqs::classic. Target backend: scaleway::1.0.0::queues.
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.
SQS Standard · SQS request billing units
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.
Curve assumptions
- 1-KiB messages, unbatched send/receive/delete; actual batch and delivery assumptions stay visible. 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 is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
- 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.
- Storage follows resident original messages, not every monthly message. Broker delivery bytes include redeliveries.
- FIFO estimates do not qualify dedup support, group throughput or single-group latency; backend limitations remain applicable.
- All target rates are editable authored planning guesses, not verified current list prices, customer discounts or benchmark evidence.
- Native broker operations price managedOperations, including selected delivery/ack work; do not substitute published GiB for operation counts.
- 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.
plan-63b489f0a3bfc0d52f4664f3bf3e716a4311cb75 / 2026-10-18.planning.1. Curve: workload-1.
SQS → Cloud SQL PostgreSQL
Origin API:aws::1.0.0::sqs::classic. Target backend: google::1.0.0::cloudsql::postgresql.
Monthly cost by SQS request rate
Reference monthly service charges from native source usage; no calculator input is required. Adapter hosting and Tensor9 fees are excluded. Source: us-east-1; target: us-central1; currency: USD.
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.
- Planning assumption, not benchmark calibrated: 100 full lifecycle equivalents per primary vCPU-second for a 1 KiB reference message (send, receive/claim and delete). These are modeled work units, not measured SQL transactions/s.
- Mean work uses original message arrivals × (2 + deliveries/message + 0.1 × empty receives/message) / 3, then scales by max(1, message bytes / 1024). Source batch fill was already used to infer original messages and is not applied again.
- Peak work is mean work × 2. Required primary CPU divides peak work by 100 lifecycle equivalents/vCPU-second × 0.7 target utilization.
- Resident data uses peak original arrivals × 60 residence seconds × 1024 message bytes × 3 physical storage multiplier. One binary GiB is 1073741824 bytes.
- Provisioned disk rounds (resident GiB + 20 GiB reserve) / 0.7 target disk utilization upward to whole GiB, retaining the caller minimum. Memory is the maximum of caller minimum, CPU × 4 GiB/vCPU and 0.1 of resident data, with a 0.9 GiB/vCPU floor and quarter-GiB upward rounding.
- CPU choices are 2, 4, 8, 16, 32, 64 and 96 primary vCPUs. CPU and memory promote jointly, with at most 6.5 GiB/vCPU, 624 GiB RAM and 65536 GiB disk.
- HA changes standby pricing and does not double primary throughput. Shared allocation changes the assigned cost and does not reduce required capacity.
- No benchmark sample calibrates this policy. Latency, IOPS, polling contention, WAL, vacuum and actual throughput require qualification. Demand beyond the listed configuration bounds is unpriced; this policy does not clamp, automatically shard or extrapolate capacity.
- No listed primary CPU tier through 96 vCPUs satisfies required CPU 285.7142857142857142857142857142857, caller minimum 2 vCPUs and memory at most 6.5 GiB/vCPU or 624 GiB. Required memory at 96 vCPUs is 384 GiB.
- 1 KiB messages; unbatched send, receive and delete requests in a 1:1:1 mix, with no empty receives or redeliveries. 730 hours/month; one billing unit per API request. Requested minima are 2 vCPU, 8 GiB memory and 100 GiB SSD, fully allocated. A versioned planning policy grows CPU, RAM and disk using 2x peak load, 70% utilization and explicit resident-data assumptions; it is not benchmark calibrated. Above the modeled configuration range, target price and savings are unavailable.
- 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.
- 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.
- Estimated allocation from planning assumptions; not benchmark calibrated. CPU, RAM and provisioned disk grow with the inferred workload and explicit peak/backlog assumptions.
- Average API requests, 64-KiB billing units, original messages and complete lifecycle work are distinct. One unbatched send/receive/delete cycle is one lifecycle, not three TPS.
- CPU tiers stop at 96 primary vCPUs; unsupported demand retains source cost but has no target cost, adapted total or savings. No sharding is inferred.
- Actual throughput, latency, connection limits, disk IOPS, claim contention, WAL and vacuum remain unqualified until comparable sustained benchmark samples exist.
- Planning assumption, not benchmark calibrated: 100 full lifecycle equivalents per primary vCPU-second for a 1 KiB reference message (send, receive/claim and delete). These are modeled work units, not measured SQL transactions/s.
- Mean work uses original message arrivals × (2 + deliveries/message + 0.1 × empty receives/message) / 3, then scales by max(1, message bytes / 1024). Source batch fill was already used to infer original messages and is not applied again.
- Peak work is mean work × 2. Required primary CPU divides peak work by 100 lifecycle equivalents/vCPU-second × 0.7 target utilization.
- Resident data uses peak original arrivals × 60 residence seconds × 1024 message bytes × 3 physical storage multiplier. One binary GiB is 1073741824 bytes.
- Provisioned disk rounds (resident GiB + 20 GiB reserve) / 0.7 target disk utilization upward to whole GiB, retaining the caller minimum. Memory is the maximum of caller minimum, CPU × 4 GiB/vCPU and 0.1 of resident data, with a 0.9 GiB/vCPU floor and quarter-GiB upward rounding.
- CPU choices are 2, 4, 8, 16, 32, 64 and 96 primary vCPUs. CPU and memory promote jointly, with at most 6.5 GiB/vCPU, 624 GiB RAM and 65536 GiB disk.
- HA changes standby pricing and does not double primary throughput. Shared allocation changes the assigned cost and does not reduce required capacity.
- No benchmark sample calibrates this policy. Latency, IOPS, polling contention, WAL, vacuum and actual throughput require qualification. Demand beyond the listed configuration bounds is unpriced; this policy does not clamp, automatically shard or extrapolate capacity.
- Source usage is priced at reference rates; source lines are not actual invoice charges. Free or discounted usage still consumes target resources.
- AWS Standard SQS pricing: https://aws.amazon.com/sqs/pricing/
- Cloud SQL Enterprise PostgreSQL pricing: https://cloud.google.com/sql/pricing/
- Cloud SQL PostgreSQL instance resource settings: https://docs.cloud.google.com/sql/docs/postgres/instance-settings
- 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.
- SQS FIFO and fair queues; actual throughput/latency and resident-data behavior beyond the explicit planning assumptions.
sqs-cloudsql / 2026-10-18.4. Curve: request-rate.
Sources: AWS Standard SQS pricing, Cloud SQL Enterprise PostgreSQL pricing, Cloud SQL PostgreSQL instance resource settings.
SQS → Cloud SQL planned scale-point benchmark
This is a benchmark plan, with historical reference observations retained separately. Planned cases are not completed measurements. The observations below do not calibrate the estimated allocation policy. Plan:sqs-cloudsql-scale-v1. Model: sqs-cloudsql. Workload: 1 KiB unbatched SQS send/receive/delete message cycles (sqs-1kib-unbatched-cycle).
Operation mix: SendMessage:ReceiveMessage:DeleteMessage = 1:1:1; no empty receives or retries. Latency scope: send start through successful delete completion.
Planned configurations
Required environment keys must be resolved before a planned case can produce matching evidence:
dbEngineVersion, adapterVcpus, adapterMemoryGiB, adapterReplicas, loadGeneratorVcpus, loadGeneratorMemoryGiB, connectionPoolSize.
- cloudsql-zonal-2vcpu unresolved:
adapterVcpus,adapterMemoryGiB,adapterReplicas,loadGeneratorVcpus,loadGeneratorMemoryGiB,connectionPoolSize. - cloudsql-zonal-4vcpu unresolved:
adapterVcpus,adapterMemoryGiB,adapterReplicas,loadGeneratorVcpus,loadGeneratorMemoryGiB,connectionPoolSize. - cloudsql-zonal-8vcpu unresolved:
adapterVcpus,adapterMemoryGiB,adapterReplicas,loadGeneratorVcpus,loadGeneratorMemoryGiB,connectionPoolSize. - cloudsql-zonal-16vcpu unresolved:
adapterVcpus,adapterMemoryGiB,adapterReplicas,loadGeneratorVcpus,loadGeneratorMemoryGiB,connectionPoolSize.
Historical reference observations
These observations remain separate records. Unknown payload, measurement duration, availability, completed-cycle throughput or other missing fields prevent treating a tool’s request rate as qualified message-lifecycle capacity.
-
historical-k6-roundtrip-r300-t8-1-0-0: source
src/main/kotlin/t9/prime/equiv/generated/eval/CloudsqlK6RoundtripR300T8K6V1_0_0.kt; case unmatched historical observation. Payload unknown bytes; batch fill send/receive/delete unknown/unknown/unknown; queues unknown; concurrency unknown. Operation mix: unknown. Latency scope: historical e2e metric; full send-through-delete timing is not established. Completed cycles unknown; error rate unknown; backlog start/end unknown/unknown; CPU/memory utilization unknown/unknown; p50/p99 24/140 ms; coordinated-omission correction true. The original generated EvalMeasurement is authoritative; metrics are projected from it without independently restating measured values. Tool-reported throughput does not identify offered, produced and sustained completed-message-cycle rates separately. Payload size, batch mix, queue count, concurrency, duration, completed count, errors, backlog, CPU/memory observations and HA are not established by this record. k6/Locust scripts used timestamp-string bodies rather than an exact 1 KiB payload; the OMB payload is also not established here. The source records storage as GB PD_SSD; tier memory is derived from db-custom MiB. Raw tuning is retained alongside the normalized allocation. -
historical-locust-roundtrip-t8-1-0-0: source
src/main/kotlin/t9/prime/equiv/generated/eval/CloudsqlLocustRoundtripT8LocustV1_0_0.kt; case unmatched historical observation. Payload unknown bytes; batch fill send/receive/delete unknown/unknown/unknown; queues unknown; concurrency unknown. Operation mix: unknown. Latency scope: historical e2e metric; full send-through-delete timing is not established. Completed cycles unknown; error rate unknown; backlog start/end unknown/unknown; CPU/memory utilization unknown/unknown; p50/p99 24/35 ms; coordinated-omission correction false. The original generated EvalMeasurement is authoritative; metrics are projected from it without independently restating measured values. Tool-reported throughput does not identify offered, produced and sustained completed-message-cycle rates separately. Payload size, batch mix, queue count, concurrency, duration, completed count, errors, backlog, CPU/memory observations and HA are not established by this record. k6/Locust scripts used timestamp-string bodies rather than an exact 1 KiB payload; the OMB payload is also not established here. The source records storage as GB PD_SSD; tier memory is derived from db-custom MiB. Raw tuning is retained alongside the normalized allocation. -
historical-omb-roundtrip-t2-1-0-0: source
src/main/kotlin/t9/prime/equiv/generated/eval/CloudsqlOmbRoundtripT2OmbV1_0_0.kt; case unmatched historical observation. Payload unknown bytes; batch fill send/receive/delete unknown/unknown/unknown; queues unknown; concurrency unknown. Operation mix: unknown. Latency scope: historical e2e metric; full send-through-delete timing is not established. Completed cycles unknown; error rate unknown; backlog start/end unknown/unknown; CPU/memory utilization unknown/unknown; p50/p99 13/83 ms; coordinated-omission correction true. The original generated EvalMeasurement is authoritative; metrics are projected from it without independently restating measured values. Tool-reported throughput does not identify offered, produced and sustained completed-message-cycle rates separately. Payload size, batch mix, queue count, concurrency, duration, completed count, errors, backlog, CPU/memory observations and HA are not established by this record. k6/Locust scripts used timestamp-string bodies rather than an exact 1 KiB payload; the OMB payload is also not established here. The source records storage as GB PD_SSD; tier memory is derived from db-custom MiB. Raw tuning is retained alongside the normalized allocation. - The 16 cases are planned experiments, each requiring three independent repetitions. No planned case has measured samples yet.
- Pin an adapter version before running a case. Completed-message-cycle throughput, p99 cycle latency, errors and backlog must be measured over 300 seconds after 60 seconds of warmup.
- Acceptance is authored: sustained completed cycles meet the offered rate, p99 ≤ 200 ms, error rate ≤ 0.001 and no backlog growth. This is not measured capacity evidence.
- Tail-latency qualification requires coordinated-omission-corrected measurements under the offered-load workload; correction alone never establishes completion or capacity.
- Historical k6, Locust and OMB observations are different workloads/tools at the same 2-vCPU allocation in us-west1. They are not hardware scaling points and are not averaged.
- Historical observations lack exact payload, HA, duration, completed-cycle counts, error/backlog and resource observations; none qualifies the sizing policy.
- Adapter, load-generator and connection-pool allocations must be recorded before a case can qualify. Empty planned environment values are unresolved requirements, not defaults.
SQS → Google Cloud Pub/Sub
Origin API:aws::1.0.0::sqs::classic. Target backend: google::1.0.0::pubsub.
Monthly cost by SQS request rate
Reference monthly service charges from native source usage; no calculator input is required. Adapter hosting and Tensor9 fees are excluded. Source: us-east-1; target: us-central1; currency: USD.
Curve assumptions
- 1 KiB messages; unbatched send, receive and delete requests in a 1:1:1 mix, with no empty receives or redeliveries. 730 hours/month; one SQS billing unit per API request. Pub/Sub uses one subscription and 64 bytes of assumed overhead.
- 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.
- One pull subscription, Standard SQS semantics compatible with this mapping, representative message size and batching.
- Pub/Sub publish and delivery each cost USD 40/TiB, with a 1,000-byte minimum per request. Metadata overhead is an explicit assumption.
- Source usage is priced at reference rates; source lines are not actual invoice charges. Free or discounted usage still consumes target resources.
- AWS Standard SQS pricing: https://aws.amazon.com/sqs/pricing/
- Pub/Sub pricing: https://cloud.google.com/pubsub/pricing/
- 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.
- Pub/Sub retained-message storage, snapshots, extra subscriptions and transformations; SQS delay/FIFO features and visibility-extension traffic.
sqs-pubsub / 2026-10-18.4. Curve: request-rate.
Sources: AWS Standard SQS pricing, Pub/Sub pricing.
See the service catalog for supported directions, operation coverage and adapter limitations.