Launching today

BenVeta Release Safety
Catch the deploy that breaks prod before it ships
2 followers
Catch the deploy that breaks prod before it ships
2 followers
Most outages happen mid-deploy, when old and new versions run side by side. BenVeta checks that in CI on every change: DB migrations, API contracts and event schemas together. You get a pass or block with reasons, plus a safer way to ship. Rule-based verdicts, no AI deciding. 11-day free trial.



Free Options
Launch tags:Developer Tools
Launch Team

AWS Activate CreditsCredits that fuel your startup’s next milestone
Promoted
Hi Product Hunt, Rahul here. I'm a backend engineer and BenVeta came out of a pattern I kept seeing in post-mortems: the code was fine, the review was fine, and production still went down, because for a few minutes during the deploy the old and new versions were running together and nobody had checked that combination.
A column the old pods didn't know about. A renamed field an old client still read. An event the old consumer couldn't parse.
BenVeta runs in your CI on every change and checks DB migrations, API contracts and event schemas together, for each old/new mix a rolling deploy creates. You get pass or block with the reasons, and when it blocks, the steps to ship it safely.
Two things I was strict about: the verdict is rule-based (AI never decides if your release ships), and anything it can't read blocks instead of passing.
There's an 11-day free trial, no card. I'd really like to hear what you'd want checked before a deploy, and which of these has bitten your team.