When someone changes code, they need to know what else might be affected. Kin keeps code, the connections it finds and their history together. Our bet is that keeping that understanding will help people and AI do useful work with less repeated investigation.
For investors
AI changed who writes code. Kin changes what they build on.
Kin is building a new foundation for code. The bet is that code structure and relationships should be versioned repository data, giving people and agents a durable record to build on.
We are raising seed financing to take the open-source public alpha from a founder-built product to daily team use.
Why keep the connections?
More code still needs understanding.
AI can draft code quickly. People still need to check how a change fits into the rest of a project and whether it works.
How Kin changes the information available to AI
Kin makes recorded code relationships and change history queryable repository data. An agent can ask about those relationships instead of reconstructing them from file contents for each question. Results depend on the connections Kin has resolved, and do not establish that a proposed change is correct.
A local product, then a team product.
People can try the open-source Kin alpha on their own machines. Language support and setup requirements still vary.
What the local product includes
Kin is licensed under Apache-2.0. It includes the graph storage engine, background service, command-line tool, MCP server for supported AI tools and a filesystem view for compatible tools.
KinLab is our hosted commercial product for teams, in development. We are building shared repository state, access controls and change review on top of Kin.
From public alpha to daily team use.
A 24-month plan for repository reliability, agent adoption and shared KinLab workflows.
Retained external use.
Developers return to Kin for useful work on real repositories.
Paid team workflows.
Turn local utility into a shared product teams choose to pay for.
Independent evidence.
Measure the workflow, including preparation and the quality of the finished change.
These are intended outcomes, not achieved results. KinLab remains in development.
Progress to date.
Kin is built by Troy Fortin Jr. under Firelock. It began from the firsthand experience of paying out of pocket to watch AI repeatedly work out how software fit together.
Kin is a public alpha. The source and published examples let readers inspect what exists and its limits. Seed financing would fund reliability, support for more languages and the hosted team product.
Inspect the product. Then let's talk.
The deck includes the business thesis, founder background and operating plan. Product evidence and its limits are available separately.