Skip to main content

Trust and security

Know where your code goes and who did what.

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.

Read more: Local Kin and hosted KinLab have different boundaries.
  1. Local Kin

    Repository ingestion, graph storage, and local queries run in your environment.

  2. Hosted KinLab

    Team collaboration and shared access depend on the data and permissions agreed for the engagement.

  3. 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.

Regulatory readiness

The evidence is either already there, or it is a project.

Keep a checkable account of changes and the review behind them. Kin does not certify that your product meets a legal or security requirement.

How change records relate to regulatory review

Software security regimes, including the EU's Cyber Resilience Act, ask for the same evidence: what changed, who changed it, and whether anyone reviewed the consequences. Kin keeps that record as work happens: a change enters the graph with what it touched, its declared actor, and the review evidence and gaps that informed it.

Whether your product meets a given obligation is a determination for you and your assessor. Kin does not evaluate conformity, does not certify it, and does not tell you that you are compliant. It keeps the record that makes the question answerable.

Next step

Review the boundary before connecting code.

Tell us which controls your organization needs. We will answer against the current system.

Request KinLab access