KinLab

ProprietaryPrivate build

Hosted collaboration and control plane

KinLab is the place where Kin becomes a shared engineering surface instead of only a powerful local substrate. It layers semantic review, org-wide search, memory, activity, and control-plane workflows above the open Kin core. The honest current claim is collaboration above Kin, not a full GitHub replacement yet.

Get Early Access Back to Labs

What KinLab Is

KinLab is the hosted layer above the local semantic substrate. It exists to make Kin legible, collaborative, governable, and usable at organizational scale without closing the local core. It gives teams a familiar shared surface for semantic review, search, and coordination while Kin remains the place where truth lives.

What KinLab is not

Not the open semantic core itself
Not a reason to blur the open / proprietary boundary
Not yet a full GitHub replacement promise

Shared semantic review

Review queues, reviewer notes, and decision history attached to semantic scopes rather than line-diff primacy.

Org-wide context

Search across repos, browse domains, and keep memory attached to the graph instead of buried in tickets or tribal knowledge.

Control-plane workflows

Human and agent coordination, org switching, activity feeds, governed APIs, and product UX above the local Kin substrate.

Hosted or local runtime

KinLab can point at a daemon-backed cloud surface or a real local Kin workspace. The product layer does not replace the open core.

Private product boundary

Everything on the developer machine stays open. KinLab is the hosted commercial layer where org-scale collaboration becomes legible and monetizable.

Honest current framing

KinLab is functional and improving. The claim today is collaboration and control plane above Kin, not full GitHub replacement.

Current V1 Slice

+Semantic review queue and routed review detail views
+Org-wide search, repo graph, domain detail views, and memory cards
+Live activity feed, org switching, and writable review decisions
+Control-plane APIs for hosted or local Kin-backed runtime modes

Product Boundary

Everything on the developer machine remains Apache-2.0: Kin, KinDB, kin-vfs, and Kin Editor. KinLab is the hosted product surface where shared semantic review, org memory, policy, and control-plane workflows become the commercial layer.

Local semantic truth is the adoption wedge. Hosted collaboration is the business.