Flux records API executions so you can replay failures locally, fix them, and resume execution safely. Instead of guessing from logs, you get the exact request, inputs, and behavior. Same request. Same IO. Same outcome.
Hey everyone 👋
I built Flux because debugging production bugs always felt like guesswork.
You look at logs, try to reproduce locally, add more logs, redeploy… and repeat.
Flux changes that.
It records every request (including external calls), so you can replay the exact failure locally.
Fix the bug → replay safely → then resume the same execution with real IO.
No mocks. No staging. No duplicate side effects.
I’m especially curious:
Would you trust something like this in your debugging workflow?
Happy to answer anything — especially how replay/resume works under the hood.
replaying the exact request locally instead of guessing from logs is huge. i spend way too much time trying to reproduce stuff from production. and its open source too which is a plus
The resume-after-fix part is the piece I haven't seen before. Most replay tools let you reproduce the bug, but you still have to re-trigger the whole flow manually. How does the resumption work in practice - does Flux hold state between the failure and the fix, or is it more like re-running from a checkpoint?
Shashi Sharma