I read the mostly negative comments but actually rate limiting is a vast subject. It can be hacked in less than half an hour or it can take days. It depends on

I read the mostly negative comments but actually rate limiting is a vast subject. It can be hacked in less than half an hour or it can take days. It depends on the degree of sophistication that an app needs. Sometimes we want to rate limit ourselves not to be temporarily banned from another service with a rate limit on its API. This SaaS can be used for that too. I built a system like that for a customer of mine and it didn't take half an hour. The free tier or the $5 per month would have cost my customer less. Furthermore it would work globally on all our machines on different networks. I remember that I told my customer that we would need a rate limiting server to keep track of the global limits, but the answer was to keep working on features and keep using our imperfect solution until we don't run into troubles.