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

Authoritative DNS zones and queries → Azure DNS

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

Authoritative DNS zones and queries · Authoritative DNS queries per second

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.
Authoritative DNS zones and queries · Authoritative DNS queries per second: monthly service charges by Authoritative DNS queries per second. Exact values are in the following table.Authoritative DNS zones and queries · Authoritative DNS queries per second: monthly service charges by Authoritative DNS queries per second. 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.
  • This compares authoritative zones and query meters; resolver forwarding has a different allocation and tariff.
  • A cost scenario does not establish live-qualified runtime DNS propagation or public authority.
  • All target rates are editable authored planning guesses, not verified current list prices, customer discounts or benchmark evidence.
  • Zone-month allocation and authoritative query operations are independent; management reads are not resolution queries. Resolver forwarding needs its own scenario.
Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied. Excluded costs and workload features:
  • Health checks, DNSSEC premiums, resolver endpoints, query logs, domain registration and routing-policy premiums.
  • 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-e814138b3589e4584681dfbb2713fa1ae4e3f7f5 / 2026-10-18.planning.1. Curve: workload-1.

Authoritative DNS zones and queries → Cloud DNS

Origin API: aws::1.0.0::route53. Target backend: google::1.0.0::dns. 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.

Authoritative DNS zones and queries · Authoritative DNS queries per second

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.
Authoritative DNS zones and queries · Authoritative DNS queries per second: monthly service charges by Authoritative DNS queries per second. Exact values are in the following table.Authoritative DNS zones and queries · Authoritative DNS queries per second: monthly service charges by Authoritative DNS queries per second. 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.
  • This compares authoritative zones and query meters; resolver forwarding has a different allocation and tariff.
  • A cost scenario does not establish live-qualified runtime DNS propagation or public authority.
  • All target rates are editable authored planning guesses, not verified current list prices, customer discounts or benchmark evidence.
  • Zone-month allocation and authoritative query operations are independent; management reads are not resolution queries. Resolver forwarding needs its own scenario.
Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied. Excluded costs and workload features:
  • Health checks, DNSSEC premiums, resolver endpoints, query logs, domain registration and routing-policy premiums.
  • 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-bc96b4c81d9aeb673035e632cdbd5ab340d4a1cd / 2026-10-18.planning.1. Curve: workload-1.

Authoritative DNS zones and queries → Cloudflare DNS

Origin API: aws::1.0.0::route53. Target backend: cloudflare::1.0.0::dns. 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.

Authoritative DNS zones and queries · Authoritative DNS queries per second

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.
Authoritative DNS zones and queries · Authoritative DNS queries per second: monthly service charges by Authoritative DNS queries per second. Exact values are in the following table.Authoritative DNS zones and queries · Authoritative DNS queries per second: monthly service charges by Authoritative DNS queries per second. 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.
  • This compares authoritative zones and query meters; resolver forwarding has a different allocation and tariff.
  • A cost scenario does not establish live-qualified runtime DNS propagation or public authority.
  • All target rates are editable authored planning guesses, not verified current list prices, customer discounts or benchmark evidence.
  • Zone-month allocation and authoritative query operations are independent; management reads are not resolution queries. Resolver forwarding needs its own scenario.
Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied. Excluded costs and workload features:
  • Health checks, DNSSEC premiums, resolver endpoints, query logs, domain registration and routing-policy premiums.
  • 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-a2b15e7e8b9d97cacc6d80c0dd48118358a26fab / 2026-10-18.planning.1. Curve: workload-1.

Authoritative DNS zones and queries → OCI DNS

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

Authoritative DNS zones and queries · Authoritative DNS queries per second

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.
Authoritative DNS zones and queries · Authoritative DNS queries per second: monthly service charges by Authoritative DNS queries per second. Exact values are in the following table.Authoritative DNS zones and queries · Authoritative DNS queries per second: monthly service charges by Authoritative DNS queries per second. 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.
  • This compares authoritative zones and query meters; resolver forwarding has a different allocation and tariff.
  • A cost scenario does not establish live-qualified runtime DNS propagation or public authority.
  • All target rates are editable authored planning guesses, not verified current list prices, customer discounts or benchmark evidence.
  • Zone-month allocation and authoritative query operations are independent; management reads are not resolution queries. Resolver forwarding needs its own scenario.
Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied. Excluded costs and workload features:
  • Health checks, DNSSEC premiums, resolver endpoints, query logs, domain registration and routing-policy premiums.
  • 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-ee40e35d319a19f9bbdbba556f2be4d11b13bd9e / 2026-10-18.planning.1. Curve: workload-1.

Authoritative DNS zones and queries → Route 53 (any cloud)

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

Authoritative DNS zones and queries · Authoritative DNS queries per second

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.
Authoritative DNS zones and queries · Authoritative DNS queries per second: monthly service charges by Authoritative DNS queries per second. Exact values are in the following table.Authoritative DNS zones and queries · Authoritative DNS queries per second: monthly service charges by Authoritative DNS queries per second. 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.
  • This compares authoritative zones and query meters; resolver forwarding has a different allocation and tariff.
  • A cost scenario does not establish live-qualified runtime DNS propagation or public authority.
  • All target rates are editable authored planning guesses, not verified current list prices, customer discounts or benchmark evidence.
  • Zone-month allocation and authoritative query operations are independent; management reads are not resolution queries. Resolver forwarding needs its own scenario.
Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied. Excluded costs and workload features:
  • Health checks, DNSSEC premiums, resolver endpoints, query logs, domain registration and routing-policy premiums.
  • 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-e390fc07b2c09ccd76f15f73b45d266273dc1a87 / 2026-10-18.planning.1. Curve: workload-1.

Authoritative DNS zones and queries → Scaleway Domains and DNS

Origin API: aws::1.0.0::route53. Target backend: scaleway::1.0.0::dns. 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. DNS zones and records are provisioned through the target provider. This mapping has no Route 53 management adapter endpoint, and DNS lookups go directly to the provider’s name servers. Cost estimates describe the selected service resources; operation coverage remains separate.

Authoritative DNS zones and queries · Authoritative DNS queries per second

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.
Authoritative DNS zones and queries · Authoritative DNS queries per second: monthly service charges by Authoritative DNS queries per second. Exact values are in the following table.Authoritative DNS zones and queries · Authoritative DNS queries per second: monthly service charges by Authoritative DNS queries per second. 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: DNS zones and records are provisioned through the target provider. This mapping has no Route 53 management adapter endpoint, and DNS lookups go directly to the provider’s name servers.
  • 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.
  • This compares authoritative zones and query meters; resolver forwarding has a different allocation and tariff.
  • A cost scenario does not establish live-qualified runtime DNS propagation or public authority.
  • All target rates are editable authored planning guesses, not verified current list prices, customer discounts or benchmark evidence.
  • Zone-month allocation and authoritative query operations are independent; management reads are not resolution queries. Resolver forwarding needs its own scenario.
Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied. Excluded costs and workload features:
  • Health checks, DNSSEC premiums, resolver endpoints, query logs, domain registration and routing-policy premiums.
  • 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-d57847d8e28e4638b04b8c1c69373ac005f231d4 / 2026-10-18.planning.1. Curve: workload-1. See the service catalog for operation coverage, supported directions and backend limitations.