Eric Della Casa

Lately I ve been feeling a bit overwhelmed with how many new products, repos, and tools are coming out every day.

There s a lot I d like to try or incorporate into my workflow, but in reality I rarely find the time to actually sit down and test things properly.

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