Live data from Hacker News

Show HN: Capy – A Git-style platform for managing your team's secrets

github.com

11–17 of 17 posts

Re: Show HN: Capy – A Git-style platform for managing your team's secrets

#12

How does this compete with built in secrets management already available in Coder, Claude, and Copilot? Do I need another “C” in my workflow?

I'd say the two biggest things are Portability, and Ergonomics.

For portability your secrets in those platforms can't move around with you, but with Capy they can move with you wherever you're doing your work. Your local machine, your sandbox, etc.

Capy also helps you deploy your secrets into Coder, Claude, Copilot and whatever other Clever product you prefer to use ;)

For ergonomics, Capy is built from the ground up as a CLI, which means it's extremely flexible in where you want to use it. I'm also working currently on making it work SUPER well in agentic coding workflows. There's going to be more on that coming soon!

Re: Show HN: Capy – A Git-style platform for managing your team's secrets

#13

Very interesting, so would you consider yourself more secure than other tools like doppler because of the split secret management? Are you going to build an MCP for this?

Absolutely. Doppler custodies the credentials entirely themselves, and Infisical ditched zero-trust earlier on citing complexity and UX concerns - IMO they just didn't try hard enough ;)

I also decided to embrace .env because that's how humans (and apparently agents -- for now) like to work when building stuff. Except Capy is the only solution I know of that allows you to cryptographically revoke access to those .env files in real time.

Regarding the MCP, watch this space: https://www.capy.sc/

Post reply on HN