This has been needed long before agents were a thing - and now with agents, even more so! Excited to try it out. But I would like to understand more about the security posture. What documentation do you have for how Capy keeps secrets safe?
Capy uses a split-key encryption model, meaning secrets are encrypted client-side before reaching our servers—so the backend never sees or stores raw plaintext keys. The design is also pretty unique in that it can be used to cryptographically revoke local secrets remotely.
Looks pretty cool, what steps are you taking to ensure that the backend is secure?
This has been needed long before agents were a thing - and now with agents, even more so! Excited to try it out. But I would like to understand more about the security posture. What documentation do you have for how Capy keeps secrets safe?
Capy uses a split-key encryption model, meaning secrets are encrypted client-side before reaching our servers—so the backend never sees or stores raw plaintext keys. The design is also pretty unique in that it can be used to cryptographically revoke local secrets remotely.
You can read more about it here: https://www.capy.sc/docs/internals/zero-trust
In addition, the company is right around the corner on our SOC2 Type I audit. It should be available within the next week!
https://trust.capy.sc/
Good idea