We re teaming up with @Vercel for a special launch day on Product Hunt.
If you re building on Vercel, schedule your launch for midnight PT on April 17 and tag it under 'Vercel Day' to be included in a dedicated leaderboard for the day.
Every team has shipped code that passed review… and still broke production. CI and code reviews miss real risk. MergAI analyzes pull requests, scores engineering risk, and blocks unsafe merges before they ship. It works with GitHub and your existing CI/CD as a final decision layer. If it’s risky, it doesn’t ship.
A lot of people trying the product, building agents, sharing ideas. Super interesting to see how differently teams approach it. Some go straight into ops and support, others start with leads or research.
Feels like we re just at the beginning of figuring out how this should actually work.
When I started my first job after school at a small local agency, a project manager once said something like: If someone has three companies on their CV and stayed less than a year in each, it doesn t look good.
I took that to heart. I tried to stay longer in every role, so I wouldn t seem unreliable, even in underpaid jobs I didn t enjoy. I endured it just to make my CV look stable. In hindsight, it was a little bit stupid. (Sometimes a waste of time.)
One recurring issue we ve been seeing with Supabase setups is not the database itself, but how credentials are managed across environments. The common pattern looks something like:
credentials stored in .env files or secrets managers
multiple environments (dev, staging, prod)
manual propagation or duplication across those environments
It works, but over time it seems easy for things to drift:
a key gets rotated in one environment but not others
a redeploy misses an env var
credentials get misconfigured during setup or migration
