Re:Launch HN: Alter (YC S25) – Access control for multi-user...
by kdodhia on Thursday October 22, 2026 @10:03PM
(#50203675)
Yeah we've put most of our effort so far into security, this part especially. Keys are encrypted in a dedicated secrets vault and once saved nobody can read them back, not even the dev who set them up. In proxy mode the key never even reaches the agent, we inject it on our side and only into requests going to hosts that are allowlisted for that provider. Every use gets checked against policy and logged with who used it and on whose behalf
Every change we ship gets scanned for supply chain attacks and goes through static code scanners too. We've been pen tested by two separate firms and we're in the observation period for SOC 2 type 2, details are at trust.alterauth.com. We're also planning open sourcing the full platform soon so you'll be able to look at the code yourself.
Re:Launch HN: Alter (YC S25) – Access control for multi-user...
by verdverm on Friday October 23, 2026 @04:14PM
(#50214688)
> nobody can read them back
how are they sent to the upstream vendor?
it's bad practice to upload such important keys to new vendors, OpenCode has their certs and trust page too, they got their user keys hacked
Re:Launch HN: Alter (YC S25) – Access control for multi-user...
by simfinii on Saturday October 24, 2026 @12:52AM
(#50218441)
Hey! Great question. So here when we say nobody can read them back we mean no user/developer can read them back. During the time of the request the backend code retrieves the credential from the vault and auto injects it in the request path.
We will be open sourcing our codebase soon so you can examine the code yoursef!
This seems like a bad idea to me these days. Companies doing this make themselves a target and then get hacked like OpenCode. Customer accounts get drained or bills run up.
Run your own gateway behind a firewall / vpn. I personally use GoModel + Tailscale.
https://news.ycombinator.com/item?id=50133401 (OpenCode hacked story)