Works beside Git today
Adoption without a forced migration.
Git records file changes. Kin runs beside it and brings the living record into tools developers already use.
Kin / investor briefThe next software foundation
AI made writing software cheap.Understanding it is the new bottleneck.
Kin gives software a living, always-current understanding of itself so people and AI work from the same truth.
Why now / 01
More creation raises the value of shared understanding.
AI can create software faster than people can safely understand and manage it.
- 01
Code is becoming abundant.
AI can produce more software across more of the system.
- 02
Understanding is still scarce.
People and agents rebuild partial context from scattered files, tools, and decisions.
- 03
Consequence is the bottleneck.
The scarce skill is seeing what a change affects and what must be preserved.
The product / 02
Give software one living record.
Kin stays current as software changes, so people, agents, editors, review, and automation can work from one shared record.
What teams reconstruct today
Codewhat exists
Decisionswhy it changed
Relationshipswhat it affects
Historyhow it arrived
The Kin record
Updated with the softwareOne current picture. Shared by people and AI.
The long-term bet
Make the living record the direct source of truth.
Kin aims to preserve code, relationships, and every version directly, replacing Git and disconnected adaptation layers.
The entry point / 03
Start with one repository. Expand into the way a team works.
The buyer is an engineering organization using AI agents on consequential software work.
- 01Open-source entry point
Start with one developer
Judge Kin on one repository.
A developer can run open-source Kin locally on one repository and judge the living record directly.
- 02Hosted expansion path
Expand with the team
Bring the shared record into KinLab.
Teams expand into KinLab, the hosted product for collaboration, governance, access, and organization memory.
Defensibility / 04
A graph is easy to draw. Trusted truth is hard to earn.
Kin has to preserve code, relationships, history, origin, policy, and collaboration across tools and teams. That continuously updated record is the challenge.
- 01
History accumulates
Each change adds history, relationships, and decisions to the record.
- 02
Integrations deepen
Editors, agents, review, and automation can share the same durable truth.
- 03
Workflow depends on trust
The advantage is becoming the record a team trusts and relies on.
This is the long-term defensibility thesis, not a claim of established market leadership.
Proof and boundaries / 05
Inspect the product, not a promise.
Kin is early. Source, proof, and releases are public. KinLab remains guided access. Each claim stops where its evidence stops.
Available now
Surface
Open source
Boundary
Early alpha. Public source is not production maturity.
Public proof
Surface
Evidence
Boundary
Each artifact proves only its stated scope, not customer outcomes.
Current release
Surface
Delivery
Boundary
Delivery is not adoption or category leadership.
Guided access
Surface
KinLab
Boundary
No public customer, revenue, or production-scale claim.
This page makes no customer, revenue, benchmark, market-size, or adoption claim.
The conversation / 06
AI made software creation abundant. Kin is building the truth layer beneath it.
If this is the kind of foundational company you like to interrogate, talk with Troy about the product and the bet.