Uniqcli

Cloud transfer and local delivery cost scenario

Compare explicit transfer, request and local-cost assumptions without presenting a live quote.

Operations

Cloud transfer and local delivery cost scenario

Compare explicit transfer, request and local-cost assumptions without presenting a live quote.

Example inputs · Replace these with your measurements to build your plan.

Method, example and sources
  1. Enter delivered volume and a clearly defined cloud-offload share.
  2. Apply the dated transfer and request rates you supply.
  3. Add local recurring cost and spread the entered one-time cost across the term.
  4. Solve equal monthly costs for either per-GB slope; distinguish a non-negative crossing, parallel costs and equal costs at every modeled volume.

Worked example. At an example 0.09 USD/GB, 10,000 billable GB is 900 USD before requests and other charges. The example rate is editable and is not a current provider quote.

Planning result · confirm model details

Compare explicitly entered delivery-cost scenarios

Editable example rates are assumptions, not a live cloud quote or a catalog price.

Cloud billable transfer
10,000GB/month
Cloud monthly scenario
900USD
Local monthly scenario including amortization
800USD
Local minus cloud
-100USD/month
Linear crossing
8,823.5294GB/month
Term cost difference
-1,200USD
  • Tiering, free allowances, region/service/direction, minimum fees, commitments, taxes and operations can change costs. Enter the applicable dated rates.
  • The crossing holds request charges and recurring costs fixed while volume varies; it is not a traffic forecast, savings promise or hardware ROI claim.

From the catalog

Storage Arrays & Servers

Explore related listings, then confirm the exact model requirements against your plan. These listings are not an automatic compatibility or capacity verdict.

Browse storage arrays & servers Browse network interface cards Get help with the specification

State what is actually billed

Transfer direction, service, region, tiers, free allowances and contractual terms can all change a cloud bill. The worksheet uses only rates and volume assumptions you enter, with request charges shown separately. Its offload field must describe data that really avoids the chosen charge; a cache hit or local copy does not automatically remove every provider fee or recurring service cost.

A crossing is a model result

The local scenario includes entered recurring delivery costs and a simple spread of one-time cost across the chosen term. The crossing holds those fixed terms and request charges constant as volume changes. Operations, resilience, support, taxes and workload changes may alter the comparison. This is not a hardware savings promise, an accounting valuation or proof of return; keep dated quotes and actual bills with the plan.

Worked example

At an example 0.09 USD/GB, 10,000 billable GB is 900 USD before requests and other charges. The example rate is editable and is not a current provider quote.

Cloud transfer and local delivery cost scenario — Uniqcli