Product upvotes vs the next 3

Waiting for data. Loading

Product comments vs the next 3

Waiting for data. Loading

Product upvote speed vs the next 3

Waiting for data. Loading

Product upvotes and comments

Waiting for data. Loading

Product vs the next 3

Loading

Flux

Fix production bugs by replaying them locally

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.

Top comment

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.