2.2 is the example result. Read it using the units and relationship stated below.
Serverless Function Cost uses invocations, cost per invocation, compute units.
Keeping usage and formats tied to the receiving system
For serverless function cost, the relationship is Result = [Invocations] × [Cost per invocation] + [Compute units] × [Cost per compute unit]. The amount depends on the supplied invocations, cost per invocation, 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 = [Invocations] × [Cost per invocation] + [Compute units] × [Cost per compute unit] 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
Invocations: 1000000; Cost per invocation: 2e-07; Compute units: 100000; Cost per compute unit: 2e-05. Result: 2.2. The values are illustrative.
Compare one changed input
Invocations changes from 1000000 to 1100000. The result becomes 2.22. All other inputs remain fixed.
Calculation rule
Result = [Invocations] × [Cost per invocation] + [Compute units] × [Cost per compute unit]
Inputs and output
| Input | Example value | Entry convention |
|---|---|---|
| Invocations | 1000000 | Use the source quantity represented by invocations. Keep the counted population fixed and avoid mixing a unit value with a period total. |
| Cost per invocation | 2.0E-7 | Use cost per invocation 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. |
| Compute units | 100000 | 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 | 2.0E-5 | 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. |
Output: 2.2 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 Invocations, Cost per invocation, Compute units. 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 Invocations 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 2.2.
Change Invocations from 1000000 to 1100000 while keeping every other value fixed. The result becomes 2.22. 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.