It's at least potentially valid to suggest that charging the same rate for SSL overhead as for normal traffic is maybe not the best system, though, since I'm as

It's at least potentially valid to suggest that charging the same rate for SSL overhead as for normal traffic is maybe not the best system, though, since I'm assuming that the overhead does not affect load on the value-adding servers but rather at a much more straightforward piece of the networking stack (LB or wherever SSL terminates before data gets into the proper Firebase stack). Say, the $0.12/GB that Google Cloud Functions uses, since there's no value to the user or cost to the provider beyond what you'd see there (and indeed, one solution seems to be to simply route through cloud functions). Is that possible, mayop100, or am I misunderstanding the system? Obviously it's not up to your users to dictate your pricing, of course, but if it's feasible it would probably earn a lot of goodwill.