Thanks for your feedback :) You have to send quite a few json messages to fill up 1GB. We think overall thin provides a lot of value and saves a lot of developer time (atleast for businesses), so we price it as that.
I think you should use different unit for pricing.
Bandwidth is frequently used in the context of file storage which can get expensive really fast even with a few users.
This doesn't translate well on the data side where most json responses will likely be lower than a few kb.
It's extremely unintuitive which is why I think most Paas providers use request and inflate the number (10 million requests sounds a lot in comparison).
I echo the sibling: I really recommend you change this. Pricing by bandwidth only makes sense if bandwidth is one of the main cost factors, because people will, consciously or not, compare it to other services that are priced by bandwidth.
