Skip to main content
Tensor9 BYOC planning comparisons for aws::1.0.0::vpc, with backend choices shown together. Read how to think about service-adapter costs for price scope and capacity qualification, or return to additional services.

Virtual network and NAT allocation → Scaleway VPC

Origin API: aws::1.0.0::vpc. Target backend: scaleway::1.0.0::vpc. 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. Native or deployment mapping. This mapping configures native networking. Application packets pass through the target network or load balancer, not the adapter fabric, and this directed mapping does not expose an origin-cloud network-management endpoint. The target provider’s networking terms apply. Cost estimates describe the selected service resources; operation coverage remains separate.

Virtual network and NAT allocation · Selected network GiB per month

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.
Virtual network and NAT allocation · Selected network GiB per month: monthly service charges by Selected network GiB per month. Exact values are in the following table.Virtual network and NAT allocation · Selected network GiB per month: monthly service charges by Selected network GiB per month. Exact values are in the following table.
Exact sampled model outputs in USD/month. Difference means target minus origin; a positive difference means the target costs more. Curve assumptions
  • Only this native meter varies; all other source usage and translation assumptions retain the displayed defaults. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
  • Planning estimate · editable authored rates and sizing assumptions dated 2026-10-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.
  • Native/deployment comparison scope: This mapping configures native networking. Application packets pass through the target network or load balancer, not the adapter fabric, and this directed mapping does not expose an origin-cloud network-management endpoint. The target provider’s networking terms apply.
  • All default unit prices and capacity coefficients are editable authored planning guesses, not measured capacity or a provider quote.
  • Management requests do not reveal resource allocation or workload traffic. Provisioned resources and traffic are independent inputs.
  • Resource-hours represent selected gateway allocation, not a claim that the network object has an hourly fee.
  • Use matching source and target traffic scope: NAT processing, inter-zone transfer and internet egress are different meters.
  • All target rates are editable authored planning guesses, not verified current list prices, customer discounts or benchmark evidence.
  • Resource-hours represent explicitly selected NAT/gateway allocation, not a fee for the network object. Free management API calls do not reveal network traffic.
Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied. Excluded costs and workload features:
  • Public IPv4, VPN/interconnect, firewalls, private endpoints, DNS, peering and traffic outside the selected transfer scope.
  • Taxes, discounts, credits and free-tier allowances unless explicitly reflected in edited rates.
  • Unmodeled dependent services, task execution and operations outside the selected workload family.
Planning assumptions authored: 2026-10-18. Model: plan-d0b2d2646d986c913f12976fbf30715785940a5f / 2026-10-18.planning.1. Curve: workload-1.

Virtual network and NAT allocation → Virtual Cloud Network

Origin API: aws::1.0.0::vpc. Target backend: oci::1.0.0::vcn. 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.

Virtual network and NAT allocation · Selected network GiB per month

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.
Virtual network and NAT allocation · Selected network GiB per month: monthly service charges by Selected network GiB per month. Exact values are in the following table.Virtual network and NAT allocation · Selected network GiB per month: monthly service charges by Selected network GiB per month. Exact values are in the following table.
Exact sampled model outputs in USD/month. Difference means target minus origin; a positive difference means the target costs more. Curve assumptions
  • Only this native meter varies; all other source usage and translation assumptions retain the displayed defaults. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
  • Planning estimate · editable authored rates and sizing assumptions dated 2026-10-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.
  • All default unit prices and capacity coefficients are editable authored planning guesses, not measured capacity or a provider quote.
  • Management requests do not reveal resource allocation or workload traffic. Provisioned resources and traffic are independent inputs.
  • Resource-hours represent selected gateway allocation, not a claim that the network object has an hourly fee.
  • Use matching source and target traffic scope: NAT processing, inter-zone transfer and internet egress are different meters.
  • All target rates are editable authored planning guesses, not verified current list prices, customer discounts or benchmark evidence.
  • Resource-hours represent explicitly selected NAT/gateway allocation, not a fee for the network object. Free management API calls do not reveal network traffic.
Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied. Excluded costs and workload features:
  • Public IPv4, VPN/interconnect, firewalls, private endpoints, DNS, peering and traffic outside the selected transfer scope.
  • Taxes, discounts, credits and free-tier allowances unless explicitly reflected in edited rates.
  • Unmodeled dependent services, task execution and operations outside the selected workload family.
Planning assumptions authored: 2026-10-18. Model: plan-95441666831b4ce50a1ee860569b2535dc66553c / 2026-10-18.planning.1. Curve: workload-1.

Virtual network and NAT allocation → Virtual Network

Origin API: aws::1.0.0::vpc. Target backend: azure::1.0.0::vnet. 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.

Virtual network and NAT allocation · Selected network GiB per month

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.
Virtual network and NAT allocation · Selected network GiB per month: monthly service charges by Selected network GiB per month. Exact values are in the following table.Virtual network and NAT allocation · Selected network GiB per month: monthly service charges by Selected network GiB per month. Exact values are in the following table.
Exact sampled model outputs in USD/month. Difference means target minus origin; a positive difference means the target costs more. Curve assumptions
  • Only this native meter varies; all other source usage and translation assumptions retain the displayed defaults. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
  • Planning estimate · editable authored rates and sizing assumptions dated 2026-10-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.
  • All default unit prices and capacity coefficients are editable authored planning guesses, not measured capacity or a provider quote.
  • Management requests do not reveal resource allocation or workload traffic. Provisioned resources and traffic are independent inputs.
  • Resource-hours represent selected gateway allocation, not a claim that the network object has an hourly fee.
  • Use matching source and target traffic scope: NAT processing, inter-zone transfer and internet egress are different meters.
  • All target rates are editable authored planning guesses, not verified current list prices, customer discounts or benchmark evidence.
  • Resource-hours represent explicitly selected NAT/gateway allocation, not a fee for the network object. Free management API calls do not reveal network traffic.
Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied. Excluded costs and workload features:
  • Public IPv4, VPN/interconnect, firewalls, private endpoints, DNS, peering and traffic outside the selected transfer scope.
  • Taxes, discounts, credits and free-tier allowances unless explicitly reflected in edited rates.
  • Unmodeled dependent services, task execution and operations outside the selected workload family.
Planning assumptions authored: 2026-10-18. Model: plan-34eea51598bf0f8620a54e3566f90ac9abbc71fb / 2026-10-18.planning.1. Curve: workload-1.

Virtual network and NAT allocation → Virtual Private Cloud (VPC)

Origin API: aws::1.0.0::vpc. Target backend: google::1.0.0::compute::network. 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.

Virtual network and NAT allocation · Selected network GiB per month

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.
Virtual network and NAT allocation · Selected network GiB per month: monthly service charges by Selected network GiB per month. Exact values are in the following table.Virtual network and NAT allocation · Selected network GiB per month: monthly service charges by Selected network GiB per month. Exact values are in the following table.
Exact sampled model outputs in USD/month. Difference means target minus origin; a positive difference means the target costs more. Curve assumptions
  • Only this native meter varies; all other source usage and translation assumptions retain the displayed defaults. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
  • Planning estimate · editable authored rates and sizing assumptions dated 2026-10-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.
  • All default unit prices and capacity coefficients are editable authored planning guesses, not measured capacity or a provider quote.
  • Management requests do not reveal resource allocation or workload traffic. Provisioned resources and traffic are independent inputs.
  • Resource-hours represent selected gateway allocation, not a claim that the network object has an hourly fee.
  • Use matching source and target traffic scope: NAT processing, inter-zone transfer and internet egress are different meters.
  • All target rates are editable authored planning guesses, not verified current list prices, customer discounts or benchmark evidence.
  • Resource-hours represent explicitly selected NAT/gateway allocation, not a fee for the network object. Free management API calls do not reveal network traffic.
Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied. Excluded costs and workload features:
  • Public IPv4, VPN/interconnect, firewalls, private endpoints, DNS, peering and traffic outside the selected transfer scope.
  • Taxes, discounts, credits and free-tier allowances unless explicitly reflected in edited rates.
  • Unmodeled dependent services, task execution and operations outside the selected workload family.
Planning assumptions authored: 2026-10-18. Model: plan-e3747b96fbaaafb9d5b0a89ae6f48d55edf6ca32 / 2026-10-18.planning.1. Curve: workload-1. See the service catalog for operation coverage, supported directions and backend limitations.