Kin and GitHub

Kin works alongside GitHub today.

Keep GitHub for hosting, pull requests, and the workflows your team already uses. Add Kin when developers and agents need a standing semantic view of what the repository means.

Different jobs

Git records changes. Kin keeps their relationships ready.

The comparison is about the information available to a developer or agent, not a claim that GitHub lacks useful code intelligence.

  1. Repository hosting and pull requests

    Keep using GitHub for remote hosting, pull requests, CI, issues, and the collaboration your team depends on.

  2. Semantic context

    Use Kin to locate entities, gather focused context, and follow code relationships from a standing graph.

  3. Review evidence

    Add an advisory report about likely impact and known gaps before the team makes the merge decision.

Adoption path

You do not need a platform migration to try Kin.

Install Kin locally, initialize one existing repository, and connect a supported agent or editor. Your Git hosting, pull requests, and CI stay where they are.

Kin does not claim to replace every GitHub workflow today.

Next step

Add the graph to one GitHub repository.

Start with the project where context is hardest to reconstruct.

Install Kin