The loadr blog
What we build, and how
Release notes, build retrospectives, and where loadr is headed next.
Release What shipped · Retrospective How it was built · Roadmap What's coming
-
09:00 · 9 min readRoadmap
What's next: six new feature families
A complete inbuilt session recorder, spec-driven generation and fuzzing, results intelligence, an AI copilot, trace-driven root cause, and a resilience suite. What's coming and why.
Read → -
10:20 · 8 min readRetrospective
Zero to a k6-and-JMeter competitor in four weeks
The first commit landed on 12 June. Four weeks and 180 commits later, loadr had seven protocols, a plugin ecosystem, a desktop app, and a DoS finder. Here's how.
Read → -
14:05 · 6 min readChangelog
What's New in loadr
Everything shipped so far, release by release — from the first protocols to the payload generator and the algorithmic-DoS finder.
Read → -
08:30 · 6 min readDeep dive
Teaching a load tester to find DoS bugs
The payload generator and complexity assertion turn "scale an adversarial input and watch response time bend" into a one-command, super-linear-blowup finder.
Read → -
16:40 · 7 min readRetrospective
The desktop app: seven milestones in forty-eight hours
M1 to M7 — Electron scaffold to a signed, multi-platform, Playwright-tested release — in two days. What we built and what we'd do again.
Read → -
09:15 · 7 min readArchitecture
A plugin ecosystem, not a monolith
WASM, native Rust, and a plain C ABI so any language can add a protocol. How loadr keeps a single binary small while covering Postgres, Kafka, MQTT, Cassandra and 25 more.
Read →