Rately Discontinued
Customizable rate limiting at the edge, built to protect APIs in seconds.
I built Rately because I couldn’t find a rate limiter that was actually customizable at scale. Most services give you a flat request-per-second number and call it done — fine until your real traffic doesn’t look like that. With Rately you set limits based on your actual user data: per plan tier, per geo, per endpoint, whatever the API actually needs, instead of one number applied everywhere.
Why it ended
Same problem as Usertune: people already do their own rate limiting inside their own app or infra. Adding an extra network hop just to check a limit wasn’t something they wanted, no matter how customizable it was.