Simple, transparent pricing

Yes. The Free tier is free with no time limit, no credit card, and no account required. All core features — documents, search, knowledge graph, code intelligence, MCP tools, and CLI — work fully offline on your machine.

Pro is for individual power users, consultants, founders, and small teams that want paid cloud sync and hosted backup without an enterprise procurement process. It is the right fit when local GitKB is already useful and you want your agentic workflow to follow you across machines or collaborators.

Yes. Pro is intentionally simple for small teams that do not need SSO, private deployment, procurement review, or dedicated rollout support. If GitKB is becoming part of a department-wide or company-wide AI engineering program, book an Enterprise demo instead.

Enterprise is for larger teams or organizations that need a security and procurement review, SSO/SAML/OIDC, data ownership review, private hosted infrastructure, self-hosted or on-prem evaluation, custom integrations, or rollout planning for multiple engineering teams.

Book a demo when GitKB needs to support a team-wide agentic engineering rollout, a formal pilot, procurement requirements, or private deployment constraints. The demo should map GitKB to your current repositories, docs, agents, and evaluation criteria.

Enterprise buyers can evaluate private hosted, self-hosted, and on-prem deployment paths. The exact model depends on your identity provider, data ownership requirements, network constraints, and support needs.

Free local usage stores knowledge on your machine. Pro cloud sync stores synced knowledge in GitKB-hosted infrastructure. Enterprise deployments can review private hosting, self-hosting, and data ownership requirements before rollout.

GitKB records knowledge changes as versioned history, including document changes and commit metadata. Enterprise buyers should review retention, export, and operational requirements during the pilot and security review.

Yes. The recommended Enterprise motion is a focused pilot on real engineering work before broader procurement. A pilot should measure context recovery, token spend, review quality, knowledge reuse, and deployment constraints.