8.8 is the example result. Read it using the units and relationship stated below.
Cloud Infrastructure Cost uses compute units, cost per compute unit, storage (gb).
Keeping usage and formats tied to the receiving system
For cloud infrastructure cost, the relationship is Result = [Compute units] × [Cost per compute unit] + [Storage (GB)] × [Storage cost per GB] + [Egress (GB)] × [Egress cost per GB]. The amount depends on the supplied compute units, cost per compute unit, rather than a live market price or a value imported from another record. A technical estimate needs the billable unit or output format the receiving system expects. Requests, tokens, storage and transfer can have separate rates. A text transformation should preserve meaningful characters rather than promise validation it does not perform.
What the model includes
Result = [Compute units] × [Cost per compute unit] + [Storage (GB)] × [Storage cost per GB] + [Egress (GB)] × [Egress cost per GB] Use current rate-card values for cost fields and a representative source sample for conversion tools. Cached requests, retries and region charges may change an invoice. A successful local transformation does not establish that an external API will accept the record. Keep the original source alongside the result. Before deployment, check the output in the target environment and record any exclusions, such as a rough token estimate or formatting without a parser.
Example with the supplied inputs
Compute units: 100; Cost per compute unit: 0.05; Storage (GB): 100; Storage cost per GB: 0.02; Egress (GB): 20; Egress cost per GB: 0.09. Result: 8.8. The values are illustrative.
Compare one changed input
Compute units changes from 100 to 110. The result becomes 9.3. All other inputs remain fixed.
Calculation rule
Result = [Compute units] × [Cost per compute unit] + [Storage (GB)] × [Storage cost per GB] + [Egress (GB)] × [Egress cost per GB]
Inputs and output
| Input | Example value | Entry convention |
|---|---|---|
| Compute units | 100 | Use the source quantity represented by compute units. Keep the counted population fixed and avoid mixing a unit value with a period total. |
| Cost per compute unit | 0.05 | Use cost per compute unit on the currency and period basis shown by the formula. Keep gross amounts, net amounts and unit amounts distinct; the page does not fetch a price or exchange rate. |
| Storage (GB) | 100 | Use the source quantity represented by storage (gb). Keep the counted population fixed and avoid mixing a unit value with a period total. |
| Storage cost per GB | 0.02 | Use storage cost per gb on the currency and period basis shown by the formula. Keep gross amounts, net amounts and unit amounts distinct; the page does not fetch a price or exchange rate. |
| Egress (GB) | 20 | Use the source quantity represented by egress (gb). Keep the counted population fixed and avoid mixing a unit value with a period total. |
| Egress cost per GB | 0.09 | Use egress cost per gb on the currency and period basis shown by the formula. Keep gross amounts, net amounts and unit amounts distinct; the page does not fetch a price or exchange rate. |
Output: 8.8 is the example result. Read it using the units and relationship stated below. Use the formula to distinguish a cash amount, count, percentage or ratio.
How to use the page
Collect the inputs
Gather Compute units, Cost per compute unit, Storage (GB). Use one period and the units shown in the form.
Run the calculation
Enter the values and select the action. The calculation rule above explains how the inputs produce the result.
Compare a scenario
Change Compute units on its own, keeping the other inputs fixed. Read both results before changing another assumption.
Worked example
With the example inputs listed above, the result is 8.8.
Change Compute units from 100 to 110 while keeping every other value fixed. The result becomes 9.3. This comparison isolates that input; it does not forecast how other variables will respond.
Check the stated formula, units and limits before using the result in a decision.
Keep the displayed formula, input units and model scope with the result. Corrections or questions can be sent through the request section on this page.
Content updated: October 11, 2026