we moved off Google Cloud functions after they become 10x more expensive for us
they first introduced container registry, which made us pay for the storage (before you only paid for invocation and egress)
> If your functions are stored in Container Registry, you'll see small charges after you deploy because Container Registry has no free tier. Container Registry's regional storage costs are currently about $0.026 per GB per month.
recently they sent an email telling us new functions are going to use to “Artifact Registry” and prompting to migrate our old functions
luckily we started migrating before the announcement
i'd recommend checking serverless framework (serverless.com) or openfaas (openfaas.com)
best thing you can do is not get involved with provider-specific APIs: use Docker/Kubernetes for building and executing your code, Postgres-compatible database (Hasura if you want Firebase experience) and S3 for object storage, send e-mails using SMTP
Wanted to add another option to ushakov's comment: KNative (which is actually what CloudRun is built on).
If you run k8s clusters anywhere, OpenFaaS and KNative are both solid options. OpenFaaS is seems better suited for short running, less compute intensive things. Whereas KNative is a great fit for API's.. it just removed a bunch of the complexity around deployment (like writing a helm chart, configuring an HPA, etc).
they first introduced container registry, which made us pay for the storage (before you only paid for invocation and egress)
> If your functions are stored in Container Registry, you'll see small charges after you deploy because Container Registry has no free tier. Container Registry's regional storage costs are currently about $0.026 per GB per month.
recently they sent an email telling us new functions are going to use to “Artifact Registry” and prompting to migrate our old functions
> Cloud Functions (2nd gen) exclusively uses Artifact Registry.
Artifact Registry price: $0.10 per GB per month