cvince

5 ms·

1.
by cvince 1mo ago
Really cool idea. Skimmed the writeup, but none of this is emulated???
2.
by cvince 1mo ago
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&#x27
3.
by cvince 1mo ago
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 mach
4.
by cvince 1mo ago
This is such a clever technical demo. Do you work for Posthog? LOL
5.
by cvince 1mo ago
I love this question, because it's something I've been thinking about a lot for the next evolution of this product. My solution, currently, is that the CLI provides all the guardrails. All the security and logical primitives are e
6.
by cvince 1mo ago
https://compyl.com/blog/soc-2-software-timeout-requirements/ See CC6.2 Creation and Removal of User Credentials and CC6.6 External Protections, but if you don't work in a regulated environment, world's y
7.
by cvince 1mo ago
Great showcase for what your company does!
8.
by cvince 1mo ago
Thanks! Try it out and let me know what you think!
9.
by cvince 1mo ago
On the crypto side, the values are encrypted client-side before they’re sent. This means the service stores ciphertext it has no ability to decrypt. So the worst case for a backend compromise is someone getting encrypted blobs plus some met
10.
by cvince 1mo ago
People really dont take this stuff seriously enough, but my experience with Firestore (circa ~2014) was that it was too "easy" with a lot of stuff. Not sure how to describe this, but it's almost like the product gives you the
11.
by cvince 1mo ago
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 cryptographical
12.
Show HN: Capy – A Git-style platform for managing your team's secrets(github.com)
13 points by cvince 1mo ago|13 comments
13.
by cvince 3mo ago
Full disclosure, I am making a secrets management product myself, but thought this market research might be of interest to y'all. My question would be where you think this space is moving next? I have my own hypotheses but before shari
14.
A tier list of secrets managers, after using all of them(vincentchan.vc)
2 points by cvince 3mo ago|1 comments
15.
by cvince 4mo ago
I think your insight is spot on. We're already starting to see the shift towards "hard/deep tech". My observation is that investors are scrambling away from pure software plays and LLM wrappers, and more towards foundati
16.
by cvince 4mo ago
Of course you can. It doesn't replace the dom, just changes how it's calculated. https://chenglou.me/pretext/dynamic-layout/
17.
by cvince 4mo ago
I think it's amazing how deep you can go in something as simple as rendering diffs, and I'm really grateful you shared that writeup (in fact I've been following you loosely since the Kiip days as a then aspiring designer+deve
18.
Why I'm still building a SaaS company in 2026(vincentchan.vc)
5 points by cvince 4mo ago|2 comments
19.
by cvince 4mo ago
Whatever happened to all the pretext hype? I feel like that would be perfect for rendering huge diffs.