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

Allocated virtual machine capacity → Compute Engine

Origin API: azure::1.0.0::vm. Target backend: google::1.0.0::compute::instance. Planning estimate with editable assumptions. Unit rates, workload amplification and capacity assumptions are educated guesses awaiting verification. The displayed amounts are planning estimates, not verified provider list-price quotes or benchmark-qualified capacity. Region names identify the authored scenario assumptions. Designed mapping. This cost model describes an intended adapter. Its estimated price does not establish a delivered or selectable backend.

Allocated virtual machine capacity · Allocated VM CPU-hours 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.
Allocated virtual machine capacity · Allocated VM CPU-hours per month: monthly service charges by Allocated VM CPU-hours per month. Exact values are in the following table.Allocated virtual machine capacity · Allocated VM CPU-hours per month: monthly service charges by Allocated VM CPU-hours 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 exact directed mapping has a design profile. Cost modeling does not establish an implemented or deployable adapter.
  • All default unit prices and capacity coefficients are editable authored planning guesses, not measured capacity or a provider quote.
  • CPU, RAM, disks and network quantities remain independently editable. Increasing CPU does not silently increase the selected memory meter.
  • VM provisioning and availability of its management adapter are separate facts; this cost model does not enable a runtime endpoint.
  • All target rates are editable authored planning guesses, not verified current list prices, customer discounts or benchmark evidence.
  • Allocated VM/fleet CPU and memory hours are explicit physical usage. Management API counts never create VM-hours.
Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied. Excluded costs and workload features:
  • Operating-system and software licenses, GPUs, reserved/Spot discounts, dedicated tenancy, disk IOPS, snapshots and backup.
  • 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-61a054ceaa8f0f219dc2c5e13939112a9a7c1113 / 2026-10-18.planning.1. Curve: workload-1.

Allocated virtual machine capacity → EC2 Instances

Origin API: azure::1.0.0::vm. Target backend: aws::1.0.0::ec2::instance. Planning estimate with editable assumptions. Unit rates, workload amplification and capacity assumptions are educated guesses awaiting verification. The displayed amounts are planning estimates, not verified provider list-price quotes or benchmark-qualified capacity. Region names identify the authored scenario assumptions. Designed mapping. This cost model describes an intended adapter. Its estimated price does not establish a delivered or selectable backend.

Allocated virtual machine capacity · Allocated VM CPU-hours 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.
Allocated virtual machine capacity · Allocated VM CPU-hours per month: monthly service charges by Allocated VM CPU-hours per month. Exact values are in the following table.Allocated virtual machine capacity · Allocated VM CPU-hours per month: monthly service charges by Allocated VM CPU-hours 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 exact directed mapping has a design profile. Cost modeling does not establish an implemented or deployable adapter.
  • All default unit prices and capacity coefficients are editable authored planning guesses, not measured capacity or a provider quote.
  • CPU, RAM, disks and network quantities remain independently editable. Increasing CPU does not silently increase the selected memory meter.
  • VM provisioning and availability of its management adapter are separate facts; this cost model does not enable a runtime endpoint.
  • All target rates are editable authored planning guesses, not verified current list prices, customer discounts or benchmark evidence.
  • Allocated VM/fleet CPU and memory hours are explicit physical usage. Management API counts never create VM-hours.
Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied. Excluded costs and workload features:
  • Operating-system and software licenses, GPUs, reserved/Spot discounts, dedicated tenancy, disk IOPS, snapshots and backup.
  • 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-900e796b2dc2eb3d3f0281812441395a7f9198cf / 2026-10-18.planning.1. Curve: workload-1. See the service catalog for operation coverage, supported directions and backend limitations.