hello, how can we avoid that something like this happens with graphcool users as well? https://medium.com/@contact_16315/firebase-costs-increased-by-7-000-81dc0a27271d

@jv.bianchi Hi Victor! When I saw that post on hn this morning I new immediately that it was a train wreck in the making. It’s important for Firebase to align their pricing with underlying costs, so I actually think that including failed requests in the pricing model is the correct thing for them to do. But! The way this change was rolled out was completely mismanaged. Pricing 101 dictates that you newer ever increase prices for existing users - especially not without informing them first. The right thing for Firebase to do would have been to introduce this change for new customers, and keep all existing projects on the current model. This is how Graphcool approach pricing, and that is why you can be confident something like that won’t happen to you.