You might not need Redis (github.com)
by anon | permalink
34/ 99 viralityNiche, low traction
edit & rescore →
19 HN points · front-page probability 45%
p10 · 2p90 · 386
The model already found titles that score higher. Try one.
Hi HN, I’m building Fairvisor — a programmable rate limiting and API governance layer. The idea came from frustration with the usual setup: hardcoded gateway configs Redis counters everywhere poor visibility into why requests were blocked no connection between traffic policy and business rules Fairvisor treats rate limiting as a governance problem instead of just traffic shaping. Current focus: edge enforcement centralized policies tenant/country-aware rules explainable decisions observability integrations I’m also experimenting with a lock-free/event-driven dataplane instead of Redis-based counters. Curious whether others see API governance becoming its own infrastructure layer, especially with AI agents and automated traffic growing. Feedback and criticism welcome.
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