Doppler

Name secrets the way your app already reads them. Doppler secret names now allow for more than just UPPER_SNAKE_CASE. Turn on Permissive secret naming for your workplace to use lowercase letters, dashes, forward slashes, colons, and periods. See more → https://lnkd.in/gJcj-DwY Turn on → https://lnkd.in/gqAVukmk

Your secrets made the guest list. We're bringing the VIP lounge for your secrets to Supabase Select. Stop by to meet the Doppler team, talk secrets and AI infrastructure, and get access to exclusive merch drops throughout the day. 📍 Supabase Select 📅 October 2 #Doppler #Select2026 #SFTech

Your VIP pass to secrets management starts here. Doppler is heading to Supabase Select on October 2. Find us at the Doppler Lounge for secrets, swag, and a few surprises throughout the day. See you there! #Doppler #Select2026 #SFTech

Your AI agents can't do anything without credentials. They need keys to your APIs, your databases, and whatever internal services they call. Run enough of them across CI and code review, and the non-human identities in your stack outnumber the people in it. Our CEO, Amber Britton, talked with TFiR about what that does to secrets management, and how to think about access when the thing asking for a credential isn't a person. Where we land: An agent should get the same scrutiny you'd give a new hire. That means access to what it needs and nothing more, plus a record of every secret it touches. If something looks wrong, cutting that access should take seconds. Watch the interview: https://lnkd.in/geEtt_Tw #SecretsManagement #AIAgents #DevSecOps #CyberSecurity

Help Net Security walked through how we think about secrets now that agents are part of the stack. The shift is easy to describe and annoying to solve. Your identity count went up. A coding agent that queries a staging database needs credentials the same way a developer does, except it asks at 2am and nobody is around to approve it. We give both the same path. Secrets stay in one place, get injected at runtime instead of living in a .env file, and every request is scoped to the identity making it. Same rotation, same audit trail, whether the caller is a person or a process. #secretsmanagement #AIagents #DevSecOps #MCP

We're excited to welcome John Kilian to Doppler as our newest Account Executive! 🎉 John is joining the team to help more organizations simplify how they manage and secure secrets. Welcome aboard! Fun fact: John spends his free time hiking, fly fishing, and snowboarding across New England. He's summited all 67 of New England's 4,000+ foot mountains and is now chasing the region's 100 highest, with 82 already checked off. 🥾🏔️

You can now connect Doppler to GCP Secret Manager, GCP Cloud SQL, and Azure Service Principal rotation without static credentials. Doppler authenticates with workload identity federation on both clouds. Each connection presents a short-lived OIDC token that your GCP workload identity pool or your Entra app registration verifies. Nothing to store, rotate, or manage on your side. Docs for all three below 👇

Cloudy with a chance of migrations... and secret sprawl. On Bare Metal to Cloud, Ned Bellavance and Doppler CEO Amber Britton talk about managing secrets as infrastructure moves to the cloud, and how to keep sprawl from following you there. Watch the full conversation below 👇 https://lnkd.in/gMmnf3n2

Secrets sprawl usually starts quietly. A token gets copied into a CI job. A shared credential ends up in one more place than anyone expected, and a staging secret gets hard to trace after a few team changes. A quick audit shows you where secrets are stored and who can access them, so you can clean up the workflows that need it before they turn into bigger operational or security problems. Start with the basics. Inventory where secrets live, clear out duplicate copies, rotate what's stale, and centralize management where your team already works. Check out more tips and tricks: https://lnkd.in/gyCeHKbq