Per-tenant rate limits (CKEYLIMIT): how it works and when to use it
Per-tenant rate limits (CKEYLIMIT), caps requests and tokens per minute per tenant, enforced at the cache before the spend happens. Here's how Crowkis does it and why it matters for cost and safety.
Production LLM traffic is deeply repetitive, and repetition is exactly what a bill is made of. Per-tenant rate limits (CKEYLIMIT) is how Crowkis caps requests and tokens per minute per tenant, enforced at the cache before the spend happens.
How it works
Crowkis caps requests and tokens per minute per tenant, enforced at the cache before the spend happens. It runs inside one Redis-compatible engine, so it composes with semantic caching, agent memory, and the other intelligence layers instead of being a separate service you wire together.
CKEYLIMIT SET acme RPM 60 TPM 40000
Why it matters
Repetitive LLM workloads are where the money is, and semantic caching can cut costs up to 60-70% on repetitive workloads. Per-tenant rate limits (CKEYLIMIT) is part of what makes that reuse safe rather than reckless, the difference between a cache you trust in production and one you audit after every incident. It's one self-hosted binary, Redis-compatible, free to run.
Infrastructure earns the critical path one boring, verifiable feature at a time.