Matteo Avalle

Hi there! :)

I'm at my first PH launch today, and stumbled upon a question I thought could have been interesting to share. I'm sorry in advance if this sounds like a noob question to product experts, but that's exactly what I currently am :D

So my company just launched Bench for Claude Code here: it's an observability tool that logs, stores, and lets you share everything your Claude Code instances do.

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