Serverless Cost Calculator
Cost function invocations and GB-seconds at your own prices.
What this calculator does
The two charge lines are computed separately and added, using only the prices and allowances the user entered.
Inputs and what they mean
- Currency
- — Amounts are shown in the currency you pick. No exchange rate is applied..
- Price per million invocations
- — Take this from your own bill or the provider's price page. No provider price is built in..
- Price per GB-second
- — Take this from your own bill or the provider's price page. No provider price is built in..
- Invocations in the period
- — number value.
- Average duration
- — Average billed duration of one invocation..
- Memory allocated
- — Memory configured for the function..
- Free invocations (optional)
- — Optional component. Leave at 0 to exclude it from the result..
- Free GB-seconds (optional)
- — Optional component. Leave at 0 to exclude it from the result..
- Price as of (optional)
- — The date you took these prices. It is shown with the result so the figure is never read as a current vendor price..
- Price source (optional)
- — Where the prices came from. Shown with the result..
How to use it
- Enter your own figures — the calculator never fills in a rate, price or benchmark for you.
- Press Calculate to see the result.
- Read the formula, variables, assumptions and source below the result before you rely on it.
Formula
GB-seconds = Invocations × (Duration ÷ 1000) × Memory; Cost = ((Invocations − Free invocations) ÷ 1,000,000) × Price per million + (GB-seconds − Free GB-seconds) × Price per GB-second
Worked example
50 million invocations of a 512 MB function
Invocation and duration pricing entered from your own bill.
Reading the result
The headline figure is the main answer. Any breakdown underneath shows the parts that make it up, so you can check the working and see what changes when you adjust an input.
Limitations and assumptions
Results depend entirely on the figures you enter and are rounded for display. They are for general information and education, not professional advice.
Reference: The Linux Foundation — Workload optimisation — FinOps Framework
Last reviewed:
Common questions
Formula, source and verification
Invocation charges and duration charges, each priced at the rate the user entered.
The question it answers: What will this compute, storage, transfer, function, container, cluster or database cost us for the period, at our own rates?
The formula
GB-seconds = Invocations × (Duration ÷ 1000) × Memory; Cost = ((Invocations − Free invocations) ÷ 1,000,000) × Price per million + (GB-seconds − Free GB-seconds) × Price per GB-second
- N — Invocations
- (count). Calls in the period.
- t — Average duration
- (ms). Average billed duration of one call.
- M — Memory
- (GB). Memory configured for the function.
- r1 — Price per million invocations
- (currency). From the user's own bill.
- r2 — Price per GB-second
- (currency). From the user's own bill.
- F — Free allowances
- (count). Optional free invocations and free GB-seconds.
Units: Currency; counts; milliseconds; gigabytes; GB-seconds.
What kind of calculation this is
Business input model. The answer depends on business figures only you can supply, such as your own costs, rates or volumes. No market or benchmark values are assumed for you.
Method
The two charge lines are computed separately and added, using only the prices and allowances the user entered.
Assumptions built into the result
- Mathematical: Every price is the one the user entered, in the currency they chose; no exchange rate is applied.
- Mathematical: Usage and prices cover the same period.
- Statistical: Average duration stands in for the distribution of durations.
Figures this calculator will never guess for you
- No provider price, instance rate, storage rate or transfer rate is built in.
- No typical discount, saving or industry average is suggested.
- No free tier is assumed.
Limitations
- The result is only as current as the prices entered; a price taken months ago is not a current vendor price.
- Arithmetic over the figures entered — it cannot tell whether the usage or the rate card behind them is right.
- Using an average duration understates cost when durations are strongly skewed.
Source and version
- Standard or reference
- FinOps Framework — workload optimisation — FinOps Foundation (FinOps Framework capability: workload optimisation — cloud resource cost is the metered quantity of a resource multiplied by the rate on the organisation's own rate card.)
- Published source
- The Linux Foundation — FinOps Framework
- Formula version
- Version 1
- Verification
- Reviewed against the cited source on
- How much weight the source carries
- Standards or government
- Applies to
- Currency
- Amounts stay in the currency you choose; no exchange rate is applied.
Related tools
Work out the hourly rate to charge a client so that target margin is met after overhead and non-billable time.
Find the true hourly cost of an employee once benefits, payroll cost and overhead are included.
Size a software application from its data and transaction functions before estimating effort or cost.
Estimate development effort, schedule and average team size for a software project of a known size.
Express cloud spend as a cost per customer, per transaction or per other business unit.
Set the rate used to apply manufacturing overhead to jobs for the coming period.