Warning: High Google Cloud bills from FlutterFlow private API calls - My experience

General Conversations

Hey FlutterFlow community,

I wanted to share a heads-up about a situation I've encountered with Google Cloud Functions used for FlutterFlow private API calls. My hope is that this information might help others avoid unexpected high bills. Prior to this I had over 20 cloud functions that have cost max of $1. Thats with 1000's of invocations monthly.

FYI:

  1. I enabled private API calls which ff created ffPrivateApiCall (1st gen) and ffPrivateApiCallV2 (2nd gen).

  2. Despite minimal recent usage, my Google Cloud bill has skyrocketed - Cloud Functions showed a 1351% cost increase!

  3. The ffPrivateApiCallV2 function was configured automatically with the setting:

    • 256 MiB memory

    • 1 minimum instance

    • 100 maximum instances

    • 80 concurrency

What I changed and will see if it helps:

  1. A minimum of 1 instance means it's always running, incurring costs even when not in use.

  2. Only 1 maximum instances and concurrent which can lead to unexpected scaling and costs.

  3. There was ongoing activity in the function metrics, even without active project usage so maybe have 0 for that.

If you're using private API calls, I'd strongly recommend:

  1. Carefully reviewing your Cloud Function configurations

  2. Setting up billing alerts and quotas

  3. Regularly checking your function metrics for unexpected activity

Stay vigilant with your cloud costs, fellow FlutterFlow devs!

10
7 replies