Match Cloud Run functions to the right pricing model
On this page
This check is due for a source refresh. Confirm the current documentation before you rely on provider-specific details.
Confirm each function's documented version before comparing costs, or the wrong pricing family can distort the result. Cloud Run functions use Cloud Run pricing, while Cloud Run functions (1st gen) use their own pricing model. Do not classify from a management API or endpoint alone.
What you need first
- Tool
- Google Cloud console is Google's browser interface for cloud resources. Start in Cloud Run for current functions or Cloud Run functions (1st gen) for the original version. Have the project, region and function names ready.
- Access
- Ask an authorized Google Cloud colleague to classify the named functions in the documented console areas and report the result for the stated project and region. Ask for retained organizational deployment or change records only if API history matters.
- If you do not use that tool
- Send the function owner the project, region and function names. Request the documented console classification, pricing family and supporting resource details. If history matters, request any retained organizational record showing the creating API or later detachment, and accept unknown when unavailable.
Why this is worth a look
Skipping the version check can place a function in the wrong pricing family and make the comparison unreliable. The Google Cloud console separates current Cloud Run functions from Cloud Run functions (1st gen). Current functions created through the Cloud Functions v2 API can also have cloudfunctions.net endpoints, so that address is not enough to classify them.
Run this check
CHECKLISTComplete in Google Cloud console using the documented version areas. Scope: named functions in one project and region. Time window: current snapshot, plus optional retained organizational history. Output is classification labels, not usage units or cost totals.
Scope: project __________ | region __________ | function names __________
Inspect only. Do not deploy, edit or detach functions.
For each function:
[ ] Classify it in the documented console area: Cloud Run means current Cloud Run functions; Cloud Run functions (1st gen) means the original version. Record the function name and the supporting resource model. Mark unclear cases unresolved.
[ ] Use endpoints only as supporting evidence. Current functions use run.app URLs; functions created through the Cloud Functions v2 API can also have cloudfunctions.net endpoints. A cloudfunctions.net endpoint alone does not establish 1st gen.
[ ] Assign the pricing family only after confirming the version:
Current Cloud Run functions = Cloud Run pricing.
Cloud Run functions (1st gen) = Cloud Run functions (1st gen) pricing.
Unresolved version = leave pricing family unresolved.
[ ] If API management history matters, record the creating API from retained organizational deployment or change records, if available, and any later detachment evidence. Mark missing history unknown. Present-day Cloud Run management does not establish the original API.
[ ] Keep pricing-family classification separate from confirmation of the billed SKU. Do not treat this checklist as bill verification.
Return: function | version | supporting detail | pricing family
Optional: creating API and retained evidence | detachment evidence or unknownHow to confirm it
- 01
Choose the functions to compare
List the project, region and function names. Use the Google Cloud console's documented Cloud Run area for current functions and Cloud Run functions (1st gen) area for the original version, or give that scope to an authorized function owner.
- 02
Classify the documented version
Record the console area and supporting resource model for each function. Leave unclear functions out of the comparison until confirmed; do not guess from an endpoint or current management API.
- 03
Keep API history separate
Request retained organizational deployment or change records only if management history matters. A function detached from the Cloud Functions v2 API can be managed only through the Cloud Run Admin API, so current management does not establish its origin.
- 04
Use the correct pricing family
Group confirmed functions by pricing family for the cost comparison. Do not turn those labels into cost totals or treat them as proof of the billed SKU.
Before making changes
Treat this as a pricing-family review, not a bill audit. It assumes deployed functions can be classified in the documented console areas and covers a current snapshot, not a usage period. Google documents detachment as a way to ensure use of the Cloud Run SKU, a billing identifier. Version classification alone does not verify that identifier, so do not detach functions during this read-only review.