Pricing Changes Feedback
Hey team, we're just evaluating Neon for use in an upcoming multi-tenant, customer-facing BI tool. I just got the announcement about the pricing updates. Just one bit of feedback on this line:
To reduce complexity, Neon will no longer charge for written data and data transfer, subject to reasonable usage.Lines like "subject to reasonable usage" are not helpful. I like the idea of simple pricing schemes, but more important than simplicity is predictability. Under these adjustments, I'm not sure whether my use case will be subjectively considered "reasonable" and therefore have no way to predictably gauge what we'd actually be paying. Just my 2c. I've followed Neon on Github for over a year now and am excited to try out neon cloud!
3 Replies
wise-white•2y ago
For example when there is no more data transfert fee, what about one or more pg_dump each day, is it reasonable usage ?
equal-aqua•2y ago
Hey! We really do mean reasonable usage. Wilk's example is perfectly reasonable. The wording exists only to protect Neon from malicious actors. We're very happy to discuss your use case with you in detail - reach out to support and we'll talk the specifics of your account.
wise-white•2y ago
Prices are a lot less than with paying writing and egress (specially that when we test we do a lot of writing/egress), thanks for that. For high availability and killer feature like branching it's a lot more valuable than what we use to have elsewhere. But it's really strange for Neon to don't be immediately pay as you go. Also when we don't have metrics it'll be difficult to predict when we should switch to the next plan. For me I would prefer the same as before just without egress/writing, and maybe discount if paying before or something like that.