Release notes, design deep-dives, and the occasional honest caveat, straight from the work on ThrottleKit. RSS ↗
-
A performance sweep, then a hardening pass: 1.6.1 to 1.7.0
Two back-to-back releases across all three packages: a measured performance sweep (throttlekit 1.6.1, server 0.4.4, py 0.5.1), followed one day later by a fuzz-and-mutation hardening pass that closed a non-finite-decision bug class (throttlekit 1.7.0).
Read → -
A hardening sweep — throttlekit 1.6.0 and server 0.4.x
A multi-agent audit pass landed across the core and the server: correctness, concurrency, and security fixes — each reproduced on real code, traced to root cause, and pinned by a regression that failed on the prior commit.
Read → -
Policy Plans — a terraform plan for your limits
Replay your own recorded traffic against a candidate config and read the exact per-policy allow↔deny diff before you deploy. Shipped in throttlekit 1.4.0 and gate-able in CI.
Read → -
Scaling to a fleet without changing a line of client code
One global limit across a whole fleet — Tier-1 over the existing RPCs with zero client change, and a Tier-2 lease for the hottest clients. Shipped in throttlekit-server 0.4.0.
Read → -
Every release, from the start
The complete release history of ThrottleKit: every version of the core library, the gRPC server + Lens, and the Python client, and what each one shipped, from the first release to today.
Read → -
Introducing ThrottleKit Lens — which axis throttled me?
A built-in, zero-dependency terminal dashboard that shows, live and per key, which of rate, concurrency, or cost bound each denial — the one view no other rate-limiter dashboard can render.
Read →