Trust and security
Your code stays yours. Every action carries a declared actor.
Kin keeps local repository work in your environment. KinLab adds hosted collaboration under explicit access and early-access agreements. Review the controls that apply to the local or hosted product your team is evaluating.
Separate the surfaces
Local Kin and hosted KinLab have different boundaries.
Open source makes local code inspectable. It does not, by itself, prove the security posture of a hosted service.
Local Kin
Repository ingestion, graph storage, and local queries run in your environment.
Hosted KinLab
Team collaboration and shared access depend on the data and permissions agreed for the engagement.
Attribution
Actor and session context is preserved where the current workflow supplies it.
Current posture
Ask for the controls that affect your decision.
We will describe current hosting, access, retention, and operational practices during early-access review. We do not present planned controls as deployed controls.
During early access, we answer security questions against controls that are operating today.
Next step
Review the boundary before connecting code.
Tell us which controls your organization needs. We will answer against the current system.