3 ms·
I second making a very generous free tier, and then charging reasonably for more requests in wide buckets. As a user, free or paid, it'd give me a lot more fai
by jszymborski 2y ago
I second making a very generous free tier, and then charging reasonably for more requests in wide buckets.
As a user, free or paid, it'd give me a lot more faith in this living past tomorrow.
- hyperknot 2y agoI definitely not want to charge for requests, that's the founding principle of this project. And the risk of this project is largely mitigated by offering the full repo as open-source, so you can always self host this if needed.
- wongarsu 2y agoIf you don't want to charge per request, you could also offer two pools of backend servers: free servers that are provided on a best-effort basis with fair-use-policy, and paid servers that are exclusive to people in the $150/month plan. The latter should be easier to manage with more predictable traffic, while giving you more leeway to deal with abuse on the free servers if it ever becomes an issue.
- hyperknot 2y agoYes, I was thinking about that, it might actually be a good idea. Provide a premium service with SLAs, while providing the SLA-less service for free, with two pool of servers.