Handle blocked requests without having to call your Redis Database

If the Redis call of the ratelimit is not resolved in some timeframe, allow the request by default

Collect information on which identifiers made how many requests and how many were blocked

Create a deny list to block requests based on user agents, countries, IP addresses and more

Consume different amounts of tokens in different requests (example: limiting based on request/response size)

Utilize several Redis databases in different regions to serve users faster

Use different limits for different kinds of requests (example: paid and free users)

Change rate limits at runtime without recreating the rate limiter instance

Rate limit an API in a Nextjs project

Rate limit an API with a Middleware in a Nextjs project

Rate limit an Vercel Edge Function

Use Deny Lists to Protect Your Website

Rate limit access to your Cloudflare Pages app

Rate limit access to your Cloudflare Workers

Rate limit access to a Remix App

Rate limit a Nexjs app using Vercel KV

Rate limit your deno app

Limiting requests to a Chatbot endpoint which streams LLM outputs