Build the substrate for AI-native software.
We’re a small team building Kin and KinLab: the semantic system of record for software work. We’re not running open reqs yet. But the moment we are, we’ll want a few unusual people. If this is your kind of problem, we’d love to know you before we’re hiring.
The mission
AI now writes a growing share of the code that ships. But the repo, diff, and review substrate underneath it was built for humans editing files. Every tool in the category layers AI on top of that substrate. The expensive failure is rarely in the file that changed. Files compile locally; systems break relationally.
We replace the substrate itself: your code as a living semantic graph, with review by impact, bounded agent access, and a persistent context that every agent reads from. It’s a hard systems problem with a real wedge, and it’s the reason the team exists.
Areas we’ll hire into soon
These aren’t open reqs yet. They’re the shapes of people we expect to want first. If one sounds like you, reach out early.
Systems & Rust
The graph engine, the transparent VFS, retrieval, and local inference. Low-level, performance-sensitive work in Rust: semantic storage, snapshots, and the substrate that everything else reads from.
Full-stack & Next.js
The hosted KinLab control plane: the org graph, collaboration, review, and governance surfaces. TypeScript, Next.js, and the product experience teams live in every day.
Developer relations
The open-source story: docs, examples, talks, and the community around the Kin substrate. Helping developers and agent builders adopt graph-native tooling.
A small team orchestrating agent fleets
We build Kin with Kin. Day to day, a small team directs fleets of AI agents against our own semantic graph: the same governance, review, and context surfaces we’re shipping. The development process is the product thesis: if a few people can steer many agents safely, it’s because the substrate makes that possible. You’d be doing the same from day one.
Say hello before we’re hiring.
No formal application. Just tell us what you’ve built and why replacing the file-and-diff substrate appeals to you. We read every note.