Earlier quoted context omitted.
Thanks for laying out your concerns. Is your feeling that any sort of usage-based tiers that go beyond per-user pricing are too complex? Or is there some way to limit usage in a reasonable way that wouldn't rub you the wrong way?
Just to clarify, I truly believe it's in your interest to make pricing simpler. It just helps building trust, and conveys the same product simplicity. This is key (no pun intended) with this kind of service. Specifically, I think per-developer pricing should correlate well with value. Sharing secrets increases in complexity when more people are involved. One other thing I can think of perhaps is environments. Maybe b…
We'll probably need to put some sort of sanity check rate limits in place eventually, but I really don't want people be confused or have to worry about this stuff while using EnvKey.
Pricing is hard :-/ Thanks again!