BitSpeed, the studio’s twenty-fourth project, ships two tools that share a name and nothing else at runtime. Each one answers a question that usually ends in guessing: where did this request’s time go, and how much of that upload actually made it?
Inspect 0.1.1 records HTTP requests, breaks each one into measured intervals, and says which interval dominated, with every number pointing back to the recorded event it came from. Events that never happened stay unavailable instead of turning into zeros, and the report won’t name a server-side cause from client timings alone. Compare two saved runs and it gives medians and ranges per phase, then calls a change inconclusive when the samples overlap. In the case study, a 180 ms drop in first-byte wait clears that bar and two smaller changes don’t.
Transfer 0.1.0 snapshots a file, sends it in hashed chunks and, after a crash on either side, asks the receiver which chunks it can prove before sending anything. In its case study, both ends of a 256 MiB upload were killed with SIGKILL; after restart the receiver vouched for 136 chunks, the sender sent the other 120, and the final digest matched the deleted original. Success is reported only after the digest checks out and a receipt is saved. The tests kill both processes at three points in the protocol and inject disk and sync failures. Transfer delivers on Linux and macOS; on Windows it checks its version and refuses the rest.
Both are single Go binaries, open source under Apache 2.0, with releases for Linux, macOS and Windows. Inspect pairs well with jvq when a timing needs to become a CI budget.