throttlekit
Design & architecture

How it actually works — all 15 components.

Most limiters ask you to trust them. This is the other thing: the deep, component-by-component reference behind ThrottleKit — the real data structures, the math, and for every load-bearing choice, why it was built that way. The machine-checked bounds are an engineering verification technique, not a formality.

Self-contained per component · Purpose → architecture → decisions → caveats → what proves it · Source on GitHub ↗

Foundations

The orthogonal core every other piece composes from.

The engines

The four admission axes — and the two no other limiter has.

Distribution & surfaces

One global limit, reached from any language.

Integration & operations

Framework glue, telemetry, and the honest edges.