About Kin
The trust layer for AI-generated code. Kin proves every change is safe to ship before it merges.
The wedge
The expensive failure is rarely in the file that changed. Files compile locally; systems break relationally.
Every other tool in the category layers AI on top of the file-and-diff substrate: Copilot, Graphite, Sourcegraph, Cursor, Greptile. Kin replaces the substrate. Code lives as a living semantic graph, and review, agents, and collaboration all read from that graph instead of re-deriving structure from text.
Why now
AI writes a fast-growing share of the code that ships. But the repo, diff, and review substrate underneath it was built for one thing: humans editing files, one line at a time. That model is straining.
When an agent refactors across a dozen files, a unified diff hides the one change that quietly breaks an assumption three modules away. When many agents work at once, a file-locking, branch-merging workflow has no idea what they each intended. Proving each change is safe has become the bottleneck. Kin clears it, so machine-written code can ship at machine speed.
The dual thesis
KinLab has two jobs at once. It is the entrypoint to the open Kin tooling, the easiest way to adopt the semantic substrate and wire it into your editor and your agents. And it is the hosted control plane, where teams enforce the merge gate, govern agent access, and review change by impact across an org-wide graph.
Open tooling earns adoption; the hosted layer is the business. The two reinforce each other: the more the open substrate spreads, the more valuable the shared, governed layer on top becomes.
The stack
One system, a few clear surfaces, from graph-owned truth at the core to hosted collaboration on top.
Semantic system of record
The graph-native repo format, CLI, daemon, and review/provenance semantics. Graph-owned truth is the source of authority.
Transparent filesystem projection
A virtual filesystem that serves graph-backed files to any tool, so adoption is invisible to existing workflows.
Editor and agent surfaces
A lightweight editor extension and an MCP server that give humans and AI agents graph-native search, context, and edits.
Hosted collaboration
The hosted KinLab control plane for teams, org memory, governance, and review. The commercial layer on the open substrate.
Open at the core
Open-source Kin substrate, hosted KinLab control plane. Adopt the tooling for free, scale on the platform. The Kin substrate is open source under Apache-2.0: semantic version control, the transparent VFS, the MCP server, the editor, and the engine. It runs locally, free, forever. Features that ship open never move to a paid tier; the moat is the hosted control plane and your org’s graph. See what’s open.
We build Kin with Kin
A small team directs fleets of AI agents against our own semantic graph, using the same governance, review, and context surfaces we’re shipping. The development process is the product thesis: if a few people can safely steer many agents, it’s because the substrate makes that possible.
Where this is today
This is a pre-release project. The open-source tooling is on GitHub and dogfooded daily; the hosted workspace is still maturing. Nothing here asserts a finished public launch. Early access is granted by request, and we keep our claims to what we can reproduce. You can read the reproducible proof and browse every repo in the open Kin ecosystem.