2 ms·
First is the overall pricing strategy: Plans.. Why it has to be plans? Neither AWS nor GCP, nor Azure have plans for any of their products. I understand that p
by rafaelturk 6y ago
First is the overall pricing strategy: Plans..
Why it has to be plans? Neither AWS nor GCP, nor Azure have plans for any of their products.
I understand that plans make sense for SaaS, platforms and user based products. But this is a DB where costs are mostly related to storage+cpu usage.
Second the plans have fancy names, but they are actually just $ based volume commitment.
So the $25 Plan gives you $25 worth of usage, the $150 gives you $150 worth of usage.. This is not a plan is a monthly commitment. AWS Saving Plans is far smarter on this case, after you have a monthly commitment you'll receive a discount for your loyalty.
Third:
Some features are only unlocked after a certain plan. I'm interested in `premium regions` but this is only unlocked at $500/month. So in order to test this i need to commit to the `business plan`. With AWS, Azure, GCP you can pretty much use any feature at any scale, so you can test complex features with just a few users or even for just a few days, but you'll only pay what you use.
Lastly:
The real, clear, pricing is already there! At the bottom of the page: Billing unit rates. This is a simple, clean table that I can easy reason about and evaluate costs my business plan.
P.S
Sorry the headline `Pay only for what you need`? sorry this BS marketing, as stated above I can't use premium regions in the individual plan, so well technically incorrect.
Hope this helps.. Project looks really amazing..
- northstar702 6y agoThx. Useful feedback. We will take this into account as we iterate.