Simple, transparent pricing

Yes. Free is $0 with no time limit and no credit card required. You get 1 private knowledge base and 250 live documents, with a maximum of 1 MiB per document. Public publishing requires a paid plan. Local desktop and CLI capabilities include search, knowledge graph, code intelligence, MCP tools, and versioned history.

Team is for organizations that need shared private and public knowledge bases, cloud sync, and per-seat collaboration without an enterprise procurement process. It includes unlimited private and public knowledge bases with 5,000 live documents shared across the organization, not per KB or seat, and a maximum of 2 MiB per document. Team is billed at $15/seat/month or $12/seat/month annual-effective.

Team is billed per seat. Monthly is $15 per seat; annual billing is $12 per seat per month effective ($144/seat/year). Add or remove seats as your organization grows.

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. Free cloud and Team store synced knowledge in GitKB-hosted infrastructure within plan limits. 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.