00/Founder
Hi. GDS K S here. I built kavachOS because the auth tools I wanted for AI agents did not exist. Every other library treats humans as the default identity and agents as an afterthought. That is backwards for where software is going, so I started writing the primitives I wished existed.
The library is MIT and stable. The cloud is launching in May 2026. I answer my own email, I read every issue, and I will tell you the truth about what works and what's still rough. If that's the kind of vendor you want, we're a fit.
01/What has shipped
Dates are real. Tags tell you what got touched. If a milestone is labeled saffron, it means it's happening now or next. Muted means it's on the list but not yet committed to a date.
kavachos on npm
Marketing site and docs
Cloud early access
SOC 2 Type I, enterprise tier
02/How I work
Principle / 01
Most auth libraries stop at human sessions. Agents and delegation are the hard parts. They are the reason this exists.
Principle / 02
RFC 9728, 8707, 8414, 7591 are implemented because the spec is the spec. If there's a corner case, the test covers it or the docs name it.
Principle / 03
I'm one person. I don't pretend to have 10,000 users. I tell you the real state and build the real thing next.
Principle / 04
The library is MIT and will stay that way. The cloud pays for the dashboard, SLA, and support. Self-host is always an option.
A note for early customers
I will personally answer when something breaks. That is worse than some vendors and better than others. Know what you're signing up for.
If you need SOC 2 Type II on your procurement form today, we're probably not the right fit yet. Tell me anyway. Procurement cycles are long, and we might line up by the time you need to sign.
Open line founder@kavachos.com
I don't want to build the world's largest auth company. I want to build the one that agents and the people who write them can actually trust.