Rate limiting is a governance problem (github.com)
by anon | permalink
23/ 99 viralityNiche, low traction
edit & rescore →
9 HN points · front-page probability 45%
p10 · 2p90 · 300
The model already found titles that score higher. Try one.
Hi HN, I’m building Fairvisor — a programmable rate limiting and API governance layer. Most rate limiters today feel operationally incomplete: Redis counters glued onto gateways hardcoded configs weak visibility into why requests were blocked little connection between traffic policy and business logic Fairvisor treats rate limiting as a governance problem instead of just request counting. Current focus: centralized policy management edge enforcement tenant/country-aware rules explainable decisions observability integrations programmable traffic policies I’m also experimenting with a lock-free/event-driven dataplane instead of the classic “everything goes through Redis” architecture. Some example policies: AI agents may consume at most N% of shared capacity expensive endpoints automatically tighten limits under load different limits by geography, tenant, or plan soft throttling instead of binary blocking Mainly interested in feedback from people operating public APIs or AI infrastructure. Especially curious: Do you think API governance becomes its own infrastructure category, or are existing gateway tools already enough?
ForesynWanna keep in touch?
Built this solo over a weekend. Soft-launching before the HN post on Monday. If you scored a draft and the prediction either nailed it or whiffed, I want to know.
DM @crimeacs on Telegram — fastest way to reach me
Connect on LinkedIn — Artemii Novoselov
Edit & re-score