Data Firehose → Azure Event Hubs
Origin API:aws::1.0.0::kinesis::firehose. Target backend: azure::1.0.0::eventhubs.
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.
Data Firehose · Billed ingestion
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.
- Billed GiB includes per-record rounding; physical bytes can be much lower for small records. 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.
- The landing buffer, durable staging, delivery workers and object sink are separate allocations. Primary stored GiB is retained landing payload; staging adds delivery metadata.
- Object sink retention and PUTs are priced separately from the landing backend. Even an object-store landing target needs the explicitly modeled temporary buffer allocation.
- These retention and sink-write assumptions are provisional; a broker-only subtotal does not price the complete pipeline.
- All target rates are editable authored planning guesses, not verified current list prices, customer discounts or benchmark evidence.
- Byte-priced native stream illustration; provisioned throughput units, retention and broker minimum allocations can require additional customer-selected capacity.
- One always-on throughput unit at an authored USD 0.03/hour for 730 hours; byte-cost equivalents approximate larger demand and do not establish ingress limits. 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.
- 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.
- Dynamic partitioning, format conversion, VPC delivery and origin sink charges; transformation-specific compute.
- 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-e70d3da9518fe5f10abaa57aa39c4824d78b4e6e / 2026-10-18.planning.1. Curve: workload-1.
Data Firehose → DigitalOcean Managed Kafka
Origin API:aws::1.0.0::kinesis::firehose. Target backend: digitalocean::1.0.0::database::kafka.
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.
Data Firehose · Billed ingestion
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.
- Billed GiB includes per-record rounding; physical bytes can be much lower for small records. 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.
- The landing buffer, durable staging, delivery workers and object sink are separate allocations. Primary stored GiB is retained landing payload; staging adds delivery metadata.
- Object sink retention and PUTs are priced separately from the landing backend. Even an object-store landing target needs the explicitly modeled temporary buffer allocation.
- These retention and sink-write assumptions are provisional; a broker-only subtotal does not price the complete pipeline.
- 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.
- Dynamic partitioning, format conversion, VPC delivery and origin sink charges; transformation-specific compute.
- 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-8e2479a9662ef15033310a5a989b2e07fdda1c17 / 2026-10-18.planning.1. Curve: workload-1.
Data Firehose → OCI Streaming
Origin API:aws::1.0.0::kinesis::firehose. Target backend: oci::1.0.0::streaming.
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.
Data Firehose · Billed ingestion
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.
- Billed GiB includes per-record rounding; physical bytes can be much lower for small records. 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.
- The landing buffer, durable staging, delivery workers and object sink are separate allocations. Primary stored GiB is retained landing payload; staging adds delivery metadata.
- Object sink retention and PUTs are priced separately from the landing backend. Even an object-store landing target needs the explicitly modeled temporary buffer allocation.
- These retention and sink-write assumptions are provisional; a broker-only subtotal does not price the complete pipeline.
- All target rates are editable authored planning guesses, not verified current list prices, customer discounts or benchmark evidence.
- Byte-priced native stream illustration; provisioned throughput units, retention and broker minimum allocations can require additional customer-selected capacity.
- 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.
- Dynamic partitioning, format conversion, VPC delivery and origin sink charges; transformation-specific compute.
- 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-58fa05b1b7165c11f9ab9ab5b17c9cfc69e313e3 / 2026-10-18.planning.1. Curve: workload-1.
Data Firehose → Pub/Sub
Origin API:aws::1.0.0::kinesis::firehose. Target backend: google::1.0.0::pubsub.
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.
Data Firehose · Billed ingestion
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.
- Billed GiB includes per-record rounding; physical bytes can be much lower for small records. 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.
- The landing buffer, durable staging, delivery workers and object sink are separate allocations. Primary stored GiB is retained landing payload; staging adds delivery metadata.
- Object sink retention and PUTs are priced separately from the landing backend. Even an object-store landing target needs the explicitly modeled temporary buffer allocation.
- These retention and sink-write assumptions are provisional; a broker-only subtotal does not price the complete pipeline.
- All target rates are editable authored planning guesses, not verified current list prices, customer discounts or benchmark evidence.
- Pub/Sub uses binary GiB of published and delivered physical work independently. Do not also apply a per-broker-operation price. Minimum billable request size, batching and delivery amplification must already be represented by the family workload assumptions.
- 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.
- Dynamic partitioning, format conversion, VPC delivery and origin sink charges; transformation-specific compute.
- 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-8e313c75fd8bde1c00ef6902b0b9b1fc60233239 / 2026-10-18.planning.1. Curve: workload-1.
Data Firehose → Strimzi Kafka
Origin API:aws::1.0.0::kinesis::firehose. Target backend: strimzi::1.0.0::kafka.
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.
Data Firehose · Billed ingestion
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.
- Billed GiB includes per-record rounding; physical bytes can be much lower for small records. 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.
- The landing buffer, durable staging, delivery workers and object sink are separate allocations. Primary stored GiB is retained landing payload; staging adds delivery metadata.
- Object sink retention and PUTs are priced separately from the landing backend. Even an object-store landing target needs the explicitly modeled temporary buffer allocation.
- These retention and sink-write assumptions are provisional; a broker-only subtotal does not price the complete pipeline.
- 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.
- Dynamic partitioning, format conversion, VPC delivery and origin sink charges; transformation-specific compute.
- 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-6c87f4e94978e5b55e2f427442b2d980d92de89e / 2026-10-18.planning.1. Curve: workload-1.
Kinesis Data Streams → Azure Event Hubs
Origin API:aws::1.0.0::kinesis::stream. Target backend: azure::1.0.0::eventhubs.
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.
Kinesis Data Streams · PUT payload 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
- Payload size determines physical record and byte throughput. 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.
- Retention and consumer copies drive physical work. Origin shard-hours are not proof that a target broker or database meets the same throughput.
- A KCL DynamoDB lease table is a separate workload; enhanced fan-out and extended retention origin tariffs are outside this provisioned profile.
- All target rates are editable authored planning guesses, not verified current list prices, customer discounts or benchmark evidence.
- Byte-priced native stream illustration; provisioned throughput units, retention and broker minimum allocations can require additional customer-selected capacity.
- One always-on throughput unit at an authored USD 0.03/hour for 730 hours; byte-cost equivalents approximate larger demand and do not establish ingress limits. 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-50b2735e718e9d039b897f1878bcc337362c365f / 2026-10-18.planning.1. Curve: workload-1.
Kinesis Data Streams · Origin provisioned shards
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
- Provisioned capacity alone does not reveal actual record traffic; PUT meter stays independent. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
- Planning estimate · editable authored rates and sizing assumptions dated 2026-10-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.
- Retention and consumer copies drive physical work. Origin shard-hours are not proof that a target broker or database meets the same throughput.
- A KCL DynamoDB lease table is a separate workload; enhanced fan-out and extended retention origin tariffs are outside this provisioned profile.
- All target rates are editable authored planning guesses, not verified current list prices, customer discounts or benchmark evidence.
- Byte-priced native stream illustration; provisioned throughput units, retention and broker minimum allocations can require additional customer-selected capacity.
- One always-on throughput unit at an authored USD 0.03/hour for 730 hours; byte-cost equivalents approximate larger demand and do not establish ingress limits. 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-50b2735e718e9d039b897f1878bcc337362c365f / 2026-10-18.planning.1. Curve: workload-2.
Kinesis Data Streams → DigitalOcean Managed Kafka
Origin API:aws::1.0.0::kinesis::stream. Target backend: digitalocean::1.0.0::database::kafka.
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.
Kinesis Data Streams · PUT payload 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.
- Payload size determines physical record and byte throughput. 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.
- Retention and consumer copies drive physical work. Origin shard-hours are not proof that a target broker or database meets the same throughput.
- A KCL DynamoDB lease table is a separate workload; enhanced fan-out and extended retention origin tariffs are outside this provisioned profile.
- 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-e96780116175bd9af9e4631e78692cc13c7a74a7 / 2026-10-18.planning.1. Curve: workload-1.
Kinesis Data Streams · Origin provisioned shards
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.
- Provisioned capacity alone does not reveal actual record traffic; PUT meter stays independent. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
- Planning estimate · editable authored rates and sizing assumptions dated 2026-10-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.
- Retention and consumer copies drive physical work. Origin shard-hours are not proof that a target broker or database meets the same throughput.
- A KCL DynamoDB lease table is a separate workload; enhanced fan-out and extended retention origin tariffs are outside this provisioned profile.
- 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-e96780116175bd9af9e4631e78692cc13c7a74a7 / 2026-10-18.planning.1. Curve: workload-2.
Kinesis Data Streams → Google Cloud Pub/Sub
Origin API:aws::1.0.0::kinesis::stream. Target backend: google::1.0.0::pubsub.
Monthly cost by provisioned Kinesis shards
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
- 100 records/s per provisioned source shard, each 1 KiB; one full-stream consumer; 730 hours/month. Pub/Sub retains the physical stream at topic level for 24 hours, including 64 bytes of assumed overhead per record. Source shard count and traffic are authored scenario choices, not measured adapter throughput or semantic equivalence.
- 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.
- Provisioned Kinesis, 24-hour retention and shared-throughput consumers only; on-demand, enhanced fan-out and extended retention use different tariffs.
- Pub/Sub publishes and delivers each full consumer copy, and retains the physical stream for 24 hours at topic level for replay. Steady traffic over 730 hours is assumed.
- Pub/Sub ordering keys do not reproduce addressable shards or exact per-record offsets. This pricing comparison does not qualify semantic compatibility or throughput.
- Source usage is priced at reference rates; source lines are not actual invoice charges. Free or discounted usage still consumes target resources.
- Kinesis Data Streams provisioned pricing: https://aws.amazon.com/kinesis/data-streams/pricing/
- Pub/Sub throughput and retained-message 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.
- KCL DynamoDB lease-table costs, replay/redelivery beyond the declared consumer copies, snapshots and extra subscriptions.
kinesis-pubsub / 2026-10-18.4. Curve: provisioned-shards.
Sources: Kinesis Data Streams provisioned pricing, Pub/Sub throughput and retained-message pricing.
Kinesis Data Streams → Google Managed Kafka
Origin API:aws::1.0.0::kinesis::stream. Target backend: google::1.0.0::managed-kafka.
Monthly cost by provisioned Kinesis shards
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
- 100 records/s per source shard, each 1 KiB; one full-stream consumer; 24-hour retention; 730 hours/month. The target remains a named 3-vCPU/12-GiB cluster with 300 GiB local disk: its throughput is unqualified. The full retained physical stream is also allocated to single-copy long-term storage, a conservative storage scenario; actual tier placement can reduce it. Three replicas and their inter-zone transfer are priced; same-zone clients and local follower reads are assumed.
- 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.
- Provisioned Kinesis with 24-hour retention and shared-read consumers; 730 running hours. Google Managed Kafka uses three replicas across zones.
- Cluster allocation pricing only: throughput, peak load, retention suitability and latency remain unqualified. The curve does not resize compute automatically.
- Compute is USD 0.09 per DCU-hour; one vCPU is 0.6 DCU and one GiB RAM is 0.1 DCU. All local disk is charged, plus the explicitly selected single-copy long-term storage allocation.
- Replication transfers two physical copies at USD 0.01/GiB. Same-zone client traffic assumes local follower reads; extra client traffic must be supplied separately.
- Source usage is priced at reference rates; source lines are not actual invoice charges. Free or discounted usage still consumes target resources.
- Kinesis Data Streams provisioned pricing: https://aws.amazon.com/kinesis/data-streams/pricing/
- Google Managed Kafka pricing: https://cloud.google.com/managed-service-for-apache-kafka/pricing
- Managed Kafka capacity configuration: https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/create-cluster
- 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.
- KCL DynamoDB lease-table costs, Connect clusters, extra replication/consumer copies, unsupported resharding behavior and unqualified cluster capacity.
kinesis-managed-kafka / 2026-10-18.4. Curve: provisioned-shards.
Sources: Kinesis Data Streams provisioned pricing, Google Managed Kafka pricing, Managed Kafka capacity configuration.
Kinesis Data Streams → OCI Streaming
Origin API:aws::1.0.0::kinesis::stream. Target backend: oci::1.0.0::streaming.
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.
Kinesis Data Streams · PUT payload 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
- Payload size determines physical record and byte throughput. 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.
- Retention and consumer copies drive physical work. Origin shard-hours are not proof that a target broker or database meets the same throughput.
- A KCL DynamoDB lease table is a separate workload; enhanced fan-out and extended retention origin tariffs are outside this provisioned profile.
- All target rates are editable authored planning guesses, not verified current list prices, customer discounts or benchmark evidence.
- Byte-priced native stream illustration; provisioned throughput units, retention and broker minimum allocations can require additional customer-selected 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-9811d8ea456c7e42af3f0509a197ed3539f77d7f / 2026-10-18.planning.1. Curve: workload-1.
Kinesis Data Streams · Origin provisioned shards
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
- Provisioned capacity alone does not reveal actual record traffic; PUT meter stays independent. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
- Planning estimate · editable authored rates and sizing assumptions dated 2026-10-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.
- Retention and consumer copies drive physical work. Origin shard-hours are not proof that a target broker or database meets the same throughput.
- A KCL DynamoDB lease table is a separate workload; enhanced fan-out and extended retention origin tariffs are outside this provisioned profile.
- All target rates are editable authored planning guesses, not verified current list prices, customer discounts or benchmark evidence.
- Byte-priced native stream illustration; provisioned throughput units, retention and broker minimum allocations can require additional customer-selected 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-9811d8ea456c7e42af3f0509a197ed3539f77d7f / 2026-10-18.planning.1. Curve: workload-2.
Kinesis Data Streams → Strimzi Kafka
Origin API:aws::1.0.0::kinesis::stream. Target backend: strimzi::1.0.0::kafka.
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.
Kinesis Data Streams · PUT payload 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.
- Payload size determines physical record and byte throughput. 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.
- Retention and consumer copies drive physical work. Origin shard-hours are not proof that a target broker or database meets the same throughput.
- A KCL DynamoDB lease table is a separate workload; enhanced fan-out and extended retention origin tariffs are outside this provisioned profile.
- 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-345e11fb79eca5767bb2e6fcf2891ab45eff792c / 2026-10-18.planning.1. Curve: workload-1.
Kinesis Data Streams · Origin provisioned shards
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.
- Provisioned capacity alone does not reveal actual record traffic; PUT meter stays independent. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
- Planning estimate · editable authored rates and sizing assumptions dated 2026-10-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.
- Retention and consumer copies drive physical work. Origin shard-hours are not proof that a target broker or database meets the same throughput.
- A KCL DynamoDB lease table is a separate workload; enhanced fan-out and extended retention origin tariffs are outside this provisioned profile.
- 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-345e11fb79eca5767bb2e6fcf2891ab45eff792c / 2026-10-18.planning.1. Curve: workload-2.
See the service catalog for supported directions, operation coverage and adapter limitations.