This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Baldur
Circuit breaker and retry for Python, with an ops console
One decorator composes circuit breaker, retry, timeout, fallback, and idempotency, and a built-in console shows every breaker live. Zero-config to start; add Redis and workers share state. Django, FastAPI, Flask, Celery. Apache-2.0 core. tenacity and pybreaker give you the patterns. Baldur also answers what happens when retries run out, who notices a breaker is open, and how you replay a call that failed for good.
Hi PH - author here.
Baldur started with a question I couldn't answer in a side project. I was building a Django shopping app and asked myself: "what happens if this payment call fails?" I hand-rolled a circuit breaker before finding out pybreaker and tenacity existed - and that is when I noticed the actual gap. The patterns exist as libraries. What didn't exist was the layer that composes them and makes them operable.
So Baldur is one decorator: you name the operation, switch on retry, timeout, fallback and an idempotency key, and it composes them into one ordered pipeline. The second image shows the real thing.
Then there is running it: a built-in console showing every breaker's live state with runtime on/off controls, health checks that tell your load balancer the truth, and Prometheus/OpenTelemetry metrics.
Zero config runs entirely in-memory - no Redis, no Docker, no env vars. Add Redis when you grow to multiple workers and the same call sites share breaker state across the fleet. Django, FastAPI, Flask and Celery adapters wire it at startup. Sync and async both work.
Who it's for - it's about stakes, not traffic. If losing a single operation costs real money (a payment, an invoice, a webhook), this matters at 10 requests a day. If you're already running a service mesh with an SRE team, you likely don't need me.
Upfront: the core is Apache-2.0 and stays that way. There's a paid PRO tier for fleet-level machinery (durable DLQ with batch replay, audit trail, unified notifications, emergency mode) - flat price, one person, no VC.
I'd genuinely appreciate feedback on the API shape, and on what your team does today when a dependency dies mid-request.
No comment highlights available yet. Please check back later!
About Baldur on Product Hunt
“Circuit breaker and retry for Python, with an ops console”
Baldur was submitted on Product Hunt and earned 0 upvotes and 1 comments, placing #123 on the daily leaderboard. One decorator composes circuit breaker, retry, timeout, fallback, and idempotency, and a built-in console shows every breaker live. Zero-config to start; add Redis and workers share state. Django, FastAPI, Flask, Celery. Apache-2.0 core. tenacity and pybreaker give you the patterns. Baldur also answers what happens when retries run out, who notices a breaker is open, and how you replay a call that failed for good.
Baldur was featured in Open Source (68.8k followers), Software Engineering (43k followers), Developer Tools (519k followers) and GitHub (41.4k followers) on Product Hunt. Together, these topics include over 134.3k products, making this a competitive space to launch in.
Who hunted Baldur?
Baldur was hunted by Baldur. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Baldur stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.