azure::1.0.0::container-registry, with backend choices shown together. Read how to think about service-adapter costs for price scope and capacity qualification, or return to additional services.
Azure Container Registry image storage and transfer → Artifact Registry
Origin API:azure::1.0.0::container-registry. Target backend: google::1.0.0::artifact-registry.
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.
Azure Container Registry image storage and transfer · Retained image data
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 the selected native meter varies; other usage quantities and assumptions retain their 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.
- Unit prices and capacity coefficients are editable authored planning guesses, not verified provider tariffs or measured capacity.
- The origin is the exact registered azure::1.0.0::container-registry identity. Future aliases and renamed provider products require explicit registry and model updates.
- Stored image data, selected transfer bytes and read/write requests are independent source meters. Requests never create inferred image bytes or registry instances.
- Zero-rate API meters retain physical request quantities; they do not establish that all provider features are free.
- These reverse-cloud directions can be designed rather than delivered. A cost comparison does not establish an implemented adapter.
- The source registry tier is independently allocated in registry-hours. The target tariff must declare whether it has its own tier minimum.
- All target rates are editable authored planning guesses, not verified current list prices, customer discounts or benchmark evidence.
- Artifact storage and selected transferred bytes are priced independently; registry API calls are not image-pull bytes. Fixed premium registry tiers require separate allocation.
- Image scanning, signing, build minutes, vulnerability feeds, geo-replication, regional cache services, private endpoints and network routes outside the selected scope.
- Provider free storage, included tier allowances, volume discounts, architecture-specific image inflation and one-time cross-cloud migration.
- 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-3054e044891d70f213cc5452ee12aa5351510ade / 2026-10-18.planning.1. Curve: workload-1.
Azure Container Registry image storage and transfer · Selected image transfer 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 the selected native meter varies; other usage quantities and assumptions retain their 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.
- Unit prices and capacity coefficients are editable authored planning guesses, not verified provider tariffs or measured capacity.
- The origin is the exact registered azure::1.0.0::container-registry identity. Future aliases and renamed provider products require explicit registry and model updates.
- Stored image data, selected transfer bytes and read/write requests are independent source meters. Requests never create inferred image bytes or registry instances.
- Zero-rate API meters retain physical request quantities; they do not establish that all provider features are free.
- These reverse-cloud directions can be designed rather than delivered. A cost comparison does not establish an implemented adapter.
- The source registry tier is independently allocated in registry-hours. The target tariff must declare whether it has its own tier minimum.
- All target rates are editable authored planning guesses, not verified current list prices, customer discounts or benchmark evidence.
- Artifact storage and selected transferred bytes are priced independently; registry API calls are not image-pull bytes. Fixed premium registry tiers require separate allocation.
- Image scanning, signing, build minutes, vulnerability feeds, geo-replication, regional cache services, private endpoints and network routes outside the selected scope.
- Provider free storage, included tier allowances, volume discounts, architecture-specific image inflation and one-time cross-cloud migration.
- 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-3054e044891d70f213cc5452ee12aa5351510ade / 2026-10-18.planning.1. Curve: workload-2.
Azure Container Registry image storage and transfer · Image read requests 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.
Curve assumptions
- Only the selected native meter varies; other usage quantities and assumptions retain their 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.
- Unit prices and capacity coefficients are editable authored planning guesses, not verified provider tariffs or measured capacity.
- The origin is the exact registered azure::1.0.0::container-registry identity. Future aliases and renamed provider products require explicit registry and model updates.
- Stored image data, selected transfer bytes and read/write requests are independent source meters. Requests never create inferred image bytes or registry instances.
- Zero-rate API meters retain physical request quantities; they do not establish that all provider features are free.
- These reverse-cloud directions can be designed rather than delivered. A cost comparison does not establish an implemented adapter.
- The source registry tier is independently allocated in registry-hours. The target tariff must declare whether it has its own tier minimum.
- All target rates are editable authored planning guesses, not verified current list prices, customer discounts or benchmark evidence.
- Artifact storage and selected transferred bytes are priced independently; registry API calls are not image-pull bytes. Fixed premium registry tiers require separate allocation.
- Image scanning, signing, build minutes, vulnerability feeds, geo-replication, regional cache services, private endpoints and network routes outside the selected scope.
- Provider free storage, included tier allowances, volume discounts, architecture-specific image inflation and one-time cross-cloud migration.
- 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-3054e044891d70f213cc5452ee12aa5351510ade / 2026-10-18.planning.1. Curve: workload-3.
Azure Container Registry image storage and transfer → ECR (Elastic Container Registry)
Origin API:azure::1.0.0::container-registry. Target backend: aws::1.0.0::ecr.
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.
Azure Container Registry image storage and transfer · Retained image data
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 the selected native meter varies; other usage quantities and assumptions retain their 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.
- Unit prices and capacity coefficients are editable authored planning guesses, not verified provider tariffs or measured capacity.
- The origin is the exact registered azure::1.0.0::container-registry identity. Future aliases and renamed provider products require explicit registry and model updates.
- Stored image data, selected transfer bytes and read/write requests are independent source meters. Requests never create inferred image bytes or registry instances.
- Zero-rate API meters retain physical request quantities; they do not establish that all provider features are free.
- These reverse-cloud directions can be designed rather than delivered. A cost comparison does not establish an implemented adapter.
- The source registry tier is independently allocated in registry-hours. The target tariff must declare whether it has its own tier minimum.
- All target rates are editable authored planning guesses, not verified current list prices, customer discounts or benchmark evidence.
- Artifact storage and selected transferred bytes are priced independently; registry API calls are not image-pull bytes. Fixed premium registry tiers require separate allocation.
- Image scanning, signing, build minutes, vulnerability feeds, geo-replication, regional cache services, private endpoints and network routes outside the selected scope.
- Provider free storage, included tier allowances, volume discounts, architecture-specific image inflation and one-time cross-cloud migration.
- 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-467139ccc3b7867e112f92665e29e6fc37f11022 / 2026-10-18.planning.1. Curve: workload-1.
Azure Container Registry image storage and transfer · Selected image transfer 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 the selected native meter varies; other usage quantities and assumptions retain their 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.
- Unit prices and capacity coefficients are editable authored planning guesses, not verified provider tariffs or measured capacity.
- The origin is the exact registered azure::1.0.0::container-registry identity. Future aliases and renamed provider products require explicit registry and model updates.
- Stored image data, selected transfer bytes and read/write requests are independent source meters. Requests never create inferred image bytes or registry instances.
- Zero-rate API meters retain physical request quantities; they do not establish that all provider features are free.
- These reverse-cloud directions can be designed rather than delivered. A cost comparison does not establish an implemented adapter.
- The source registry tier is independently allocated in registry-hours. The target tariff must declare whether it has its own tier minimum.
- All target rates are editable authored planning guesses, not verified current list prices, customer discounts or benchmark evidence.
- Artifact storage and selected transferred bytes are priced independently; registry API calls are not image-pull bytes. Fixed premium registry tiers require separate allocation.
- Image scanning, signing, build minutes, vulnerability feeds, geo-replication, regional cache services, private endpoints and network routes outside the selected scope.
- Provider free storage, included tier allowances, volume discounts, architecture-specific image inflation and one-time cross-cloud migration.
- 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-467139ccc3b7867e112f92665e29e6fc37f11022 / 2026-10-18.planning.1. Curve: workload-2.
Azure Container Registry image storage and transfer · Image read requests 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.
Curve assumptions
- Only the selected native meter varies; other usage quantities and assumptions retain their 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.
- Unit prices and capacity coefficients are editable authored planning guesses, not verified provider tariffs or measured capacity.
- The origin is the exact registered azure::1.0.0::container-registry identity. Future aliases and renamed provider products require explicit registry and model updates.
- Stored image data, selected transfer bytes and read/write requests are independent source meters. Requests never create inferred image bytes or registry instances.
- Zero-rate API meters retain physical request quantities; they do not establish that all provider features are free.
- These reverse-cloud directions can be designed rather than delivered. A cost comparison does not establish an implemented adapter.
- The source registry tier is independently allocated in registry-hours. The target tariff must declare whether it has its own tier minimum.
- All target rates are editable authored planning guesses, not verified current list prices, customer discounts or benchmark evidence.
- Artifact storage and selected transferred bytes are priced independently; registry API calls are not image-pull bytes. Fixed premium registry tiers require separate allocation.
- Image scanning, signing, build minutes, vulnerability feeds, geo-replication, regional cache services, private endpoints and network routes outside the selected scope.
- Provider free storage, included tier allowances, volume discounts, architecture-specific image inflation and one-time cross-cloud migration.
- 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-467139ccc3b7867e112f92665e29e6fc37f11022 / 2026-10-18.planning.1. Curve: workload-3.
See the service catalog for operation coverage, supported directions and backend limitations.