google::1.0.0::gcs, with backend choices shown together. Read how Tensor9 estimates service-adapter costs for price scope and capacity qualification, or return to additional services.
Google Cloud Storage → Blob Storage
Origin API:google::1.0.0::gcs. Target backend: azure::1.0.0::blob-storage.
Designed mapping. This cost model describes an intended adapter. Its estimated price does not establish a delivered or selectable backend.
Google Cloud Storage · Stored data
Estimated monthly service charges by Stored data. Adapter hosting and Tensor9 fees are excluded. Source: us-central1; target: eastus; currency: USD.
Curve assumptions
- Request meters remain at their independently authored 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-22; not verified provider prices. us-central1 → eastus, 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.
- Rates are cited provider list prices, editable for discounts, commitments or another region. Workload translation and capacity coefficients remain editable planning assumptions, not 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.
- Authored planning assumptions, not measured adapter capacity. Origin rates are cited first-tier list prices, before free allowances and discounts.
- A cost scenario does not establish backend availability, protocol fidelity or production readiness. Registry serving status remains independent.
- Storage, request throughput and network are independent dimensions; a storage-only curve does not estimate a request mix.
- Object storage bills stored GiB-months, read and write requests and internet egress. Hot LRS block blobs in East US; storage and egress use Azure’s graduated tiers, and the first 100 GB of monthly egress is free. Cool, Cold and Archive tiers are not selected: a Glacier origin is billed at Hot rates.
- Cloud Storage pricing: https://cloud.google.com/storage/pricing
- VPC network data transfer pricing: https://cloud.google.com/vpc/network-pricing
- Azure Retail Prices API: https://prices.azure.com/api/retail/prices
- Additional network transfer, backups, KMS, one-time migration and operational labor unless an explicit meter includes them.
- Destination application execution and separately billed downstream services; supply those allocations separately.
- Replication beyond the selected target policy; archive classes and their minimum-duration/retrieval tariffs need a separate profile.
- 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-4ef56ba9f61f8fac9ef0c33c9bdeec18f348caa5 / 2026-10-22.planning.2. Curve: workload-1.
Sources: Cloud Storage pricing, VPC network data transfer pricing, Azure Retail Prices API.
Google Cloud Storage · Object writes
Estimated monthly service charges by Object writes. Adapter hosting and Tensor9 fees are excluded. Source: us-central1; target: eastus; currency: USD.
Curve assumptions
- Stored GiB and reads stay at independent 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-22; not verified provider prices. us-central1 → eastus, 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.
- Rates are cited provider list prices, editable for discounts, commitments or another region. Workload translation and capacity coefficients remain editable planning assumptions, not 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.
- Authored planning assumptions, not measured adapter capacity. Origin rates are cited first-tier list prices, before free allowances and discounts.
- A cost scenario does not establish backend availability, protocol fidelity or production readiness. Registry serving status remains independent.
- Storage, request throughput and network are independent dimensions; a storage-only curve does not estimate a request mix.
- Object storage bills stored GiB-months, read and write requests and internet egress. Hot LRS block blobs in East US; storage and egress use Azure’s graduated tiers, and the first 100 GB of monthly egress is free. Cool, Cold and Archive tiers are not selected: a Glacier origin is billed at Hot rates.
- Cloud Storage pricing: https://cloud.google.com/storage/pricing
- VPC network data transfer pricing: https://cloud.google.com/vpc/network-pricing
- Azure Retail Prices API: https://prices.azure.com/api/retail/prices
- Additional network transfer, backups, KMS, one-time migration and operational labor unless an explicit meter includes them.
- Destination application execution and separately billed downstream services; supply those allocations separately.
- Replication beyond the selected target policy; archive classes and their minimum-duration/retrieval tariffs need a separate profile.
- 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-4ef56ba9f61f8fac9ef0c33c9bdeec18f348caa5 / 2026-10-22.planning.2. Curve: workload-2.
Sources: Cloud Storage pricing, VPC network data transfer pricing, Azure Retail Prices API.
Google Cloud Storage · Object reads
Estimated monthly service charges by Object reads. Adapter hosting and Tensor9 fees are excluded. Source: us-central1; target: eastus; currency: USD.
Curve assumptions
- Stored GiB and writes stay at independent 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-22; not verified provider prices. us-central1 → eastus, 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.
- Rates are cited provider list prices, editable for discounts, commitments or another region. Workload translation and capacity coefficients remain editable planning assumptions, not 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.
- Authored planning assumptions, not measured adapter capacity. Origin rates are cited first-tier list prices, before free allowances and discounts.
- A cost scenario does not establish backend availability, protocol fidelity or production readiness. Registry serving status remains independent.
- Storage, request throughput and network are independent dimensions; a storage-only curve does not estimate a request mix.
- Object storage bills stored GiB-months, read and write requests and internet egress. Hot LRS block blobs in East US; storage and egress use Azure’s graduated tiers, and the first 100 GB of monthly egress is free. Cool, Cold and Archive tiers are not selected: a Glacier origin is billed at Hot rates.
- Cloud Storage pricing: https://cloud.google.com/storage/pricing
- VPC network data transfer pricing: https://cloud.google.com/vpc/network-pricing
- Azure Retail Prices API: https://prices.azure.com/api/retail/prices
- Additional network transfer, backups, KMS, one-time migration and operational labor unless an explicit meter includes them.
- Destination application execution and separately billed downstream services; supply those allocations separately.
- Replication beyond the selected target policy; archive classes and their minimum-duration/retrieval tariffs need a separate profile.
- 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-4ef56ba9f61f8fac9ef0c33c9bdeec18f348caa5 / 2026-10-22.planning.2. Curve: workload-3.
Sources: Cloud Storage pricing, VPC network data transfer pricing, Azure Retail Prices API.
Google Cloud Storage → S3
Origin API:google::1.0.0::gcs. Target backend: aws::1.0.0::s3.
Designed mapping. This cost model describes an intended adapter. Its estimated price does not establish a delivered or selectable backend.
Google Cloud Storage · Stored data
Estimated monthly service charges by Stored data. Adapter hosting and Tensor9 fees are excluded. Source: us-central1; target: us-east-1; currency: USD.
Curve assumptions
- Request meters remain at their independently authored 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-22; not verified provider prices. us-central1 → us-east-1, 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.
- Rates are cited provider list prices, editable for discounts, commitments or another region. Workload translation and capacity coefficients remain editable planning assumptions, not 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.
- Authored planning assumptions, not measured adapter capacity. Origin rates are cited first-tier list prices, before free allowances and discounts.
- A cost scenario does not establish backend availability, protocol fidelity or production readiness. Registry serving status remains independent.
- Storage, request throughput and network are independent dimensions; a storage-only curve does not estimate a request mix.
- Object storage bills stored GiB-months, read and write requests and internet egress. S3 Standard in us-east-1; storage and egress use AWS’s graduated tiers. The 100 GB monthly free egress is shared by the whole AWS account, so it is an editable allowance here.
- Cloud Storage pricing: https://cloud.google.com/storage/pricing
- VPC network data transfer pricing: https://cloud.google.com/vpc/network-pricing
- AWS Price List API: https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonS3/current/us-east-1/index.json
- AWS Price List API: https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSDataTransfer/current/us-east-1/index.json
- Additional network transfer, backups, KMS, one-time migration and operational labor unless an explicit meter includes them.
- Destination application execution and separately billed downstream services; supply those allocations separately.
- Replication beyond the selected target policy; archive classes and their minimum-duration/retrieval tariffs need a separate profile.
- 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-7a6353b5166007242df339326a7e6bc8b09067c8 / 2026-10-22.planning.2. Curve: workload-1.
Sources: Cloud Storage pricing, VPC network data transfer pricing, AWS Price List API, AWS Price List API.
Google Cloud Storage · Object writes
Estimated monthly service charges by Object writes. Adapter hosting and Tensor9 fees are excluded. Source: us-central1; target: us-east-1; currency: USD.
Curve assumptions
- Stored GiB and reads stay at independent 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-22; not verified provider prices. us-central1 → us-east-1, 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.
- Rates are cited provider list prices, editable for discounts, commitments or another region. Workload translation and capacity coefficients remain editable planning assumptions, not 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.
- Authored planning assumptions, not measured adapter capacity. Origin rates are cited first-tier list prices, before free allowances and discounts.
- A cost scenario does not establish backend availability, protocol fidelity or production readiness. Registry serving status remains independent.
- Storage, request throughput and network are independent dimensions; a storage-only curve does not estimate a request mix.
- Object storage bills stored GiB-months, read and write requests and internet egress. S3 Standard in us-east-1; storage and egress use AWS’s graduated tiers. The 100 GB monthly free egress is shared by the whole AWS account, so it is an editable allowance here.
- Cloud Storage pricing: https://cloud.google.com/storage/pricing
- VPC network data transfer pricing: https://cloud.google.com/vpc/network-pricing
- AWS Price List API: https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonS3/current/us-east-1/index.json
- AWS Price List API: https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSDataTransfer/current/us-east-1/index.json
- Additional network transfer, backups, KMS, one-time migration and operational labor unless an explicit meter includes them.
- Destination application execution and separately billed downstream services; supply those allocations separately.
- Replication beyond the selected target policy; archive classes and their minimum-duration/retrieval tariffs need a separate profile.
- 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-7a6353b5166007242df339326a7e6bc8b09067c8 / 2026-10-22.planning.2. Curve: workload-2.
Sources: Cloud Storage pricing, VPC network data transfer pricing, AWS Price List API, AWS Price List API.
Google Cloud Storage · Object reads
Estimated monthly service charges by Object reads. Adapter hosting and Tensor9 fees are excluded. Source: us-central1; target: us-east-1; currency: USD.
Curve assumptions
- Stored GiB and writes stay at independent 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-22; not verified provider prices. us-central1 → us-east-1, 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.
- Rates are cited provider list prices, editable for discounts, commitments or another region. Workload translation and capacity coefficients remain editable planning assumptions, not 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.
- Authored planning assumptions, not measured adapter capacity. Origin rates are cited first-tier list prices, before free allowances and discounts.
- A cost scenario does not establish backend availability, protocol fidelity or production readiness. Registry serving status remains independent.
- Storage, request throughput and network are independent dimensions; a storage-only curve does not estimate a request mix.
- Object storage bills stored GiB-months, read and write requests and internet egress. S3 Standard in us-east-1; storage and egress use AWS’s graduated tiers. The 100 GB monthly free egress is shared by the whole AWS account, so it is an editable allowance here.
- Cloud Storage pricing: https://cloud.google.com/storage/pricing
- VPC network data transfer pricing: https://cloud.google.com/vpc/network-pricing
- AWS Price List API: https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonS3/current/us-east-1/index.json
- AWS Price List API: https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSDataTransfer/current/us-east-1/index.json
- Additional network transfer, backups, KMS, one-time migration and operational labor unless an explicit meter includes them.
- Destination application execution and separately billed downstream services; supply those allocations separately.
- Replication beyond the selected target policy; archive classes and their minimum-duration/retrieval tariffs need a separate profile.
- 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-7a6353b5166007242df339326a7e6bc8b09067c8 / 2026-10-22.planning.2. Curve: workload-3.
Sources: Cloud Storage pricing, VPC network data transfer pricing, AWS Price List API, AWS Price List API.
See the service catalog for operation coverage, supported directions and backend limitations.