azure::1.0.0::aks, with backend choices shown together. Read how to think about service-adapter costs for price scope and capacity qualification, or return to additional services.
Managed Kubernetes and discovery → Azure AKS API on AWS EKS
Origin API:azure::1.0.0::aks. Target backend: aws::1.0.0::eks::cluster.
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.
Managed Kubernetes and discovery · Worker 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.
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.
- The discovery adapter does not itself own or provision the cluster. Allocate existing cluster capacity once across adapters.
- All target rates are editable authored planning guesses, not verified current list prices, customer discounts or benchmark evidence.
- Cluster control-plane hours and worker CPU/RAM are separately allocated. Allocate shared cluster costs once across adapters.
- Worker disks, GPUs, ingress, network traffic, extended support and observability.
- 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-81f875cc8106220f4746382cc25d5d85811e9637 / 2026-10-18.planning.1. Curve: workload-1.
Managed Kubernetes and discovery · Cluster-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.
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.
- The discovery adapter does not itself own or provision the cluster. Allocate existing cluster capacity once across adapters.
- All target rates are editable authored planning guesses, not verified current list prices, customer discounts or benchmark evidence.
- Cluster control-plane hours and worker CPU/RAM are separately allocated. Allocate shared cluster costs once across adapters.
- Worker disks, GPUs, ingress, network traffic, extended support and observability.
- 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-81f875cc8106220f4746382cc25d5d85811e9637 / 2026-10-18.planning.1. Curve: workload-2.
See the service catalog for operation coverage, supported directions and backend limitations.