When one part of a program changes, other parts may need checking. Kin keeps code, the connections it finds and their history together, so people and AI can ask about that work again.
About Kin
Why rebuild the map every time?
Kin began with a frustration: people and AI keep working out how the same code fits together. We are building a way to keep more of that understanding with the code.
A question behind Kin.
Built at Kin Computing.
I kept watching coding agents piece together code we had already worked through. Then I would repeat parts of that investigation to review the change. I started asking why more of that structural record wasn't part of the repository itself. That is what I'm building with Kin.
I shipped production generative-AI systems before this; the beta is what I've built since, and I'm working toward daily use with developers and teams.
Troy Fortin Jr, Founder, Kin Computing
Public source. Work still ahead.
Kin is open source and in public beta: you can try it now, with language and workflow limits. KinLab is the team product we are building on Kin, and is in development.
Bring a change worth understanding.
Try Kin on code you know, report a gap, or discuss a recurring team workflow.