Security

How GitKB protects your data and your organization's knowledge.

Local-First Architecture

GitKB is local-first by design. Your knowledge base lives on your machine as Markdown files and a local SQLite database. No data leaves your infrastructure unless you explicitly choose to sync.

  • All processing happens locally — no cloud dependency for core functionality
  • Works fully offline and in air-gapped environments
  • Local files are the source of truth; indexes are derived and rebuildable
  • The local CLI and MCP tools do not phone home or require network access

Data Ownership

Your knowledge is stored as standard Markdown files with YAML frontmatter. There is no proprietary format and no vendor lock-in.

  • Export your entire knowledge base at any time — it's already files on disk
  • No proprietary encoding or database format
  • Knowledge bases can be versioned, backed up, and migrated with standard tools

Cryptographic Integrity

Every knowledge commit is hashed with BLAKE3, providing tamper-evident versioning for all knowledge changes.

  • Per-document commit chains with cryptographic hashes
  • Full audit trail: author, timestamp, changed document, and line-level diff
  • Integrity verification on sync — corrupted or tampered commits are rejected

Cloud Sync Security

For teams that choose to sync knowledge to GitKB Cloud, data is protected in transit and at rest.

  • TLS 1.3 for all data in transit
  • Encryption at rest for cloud-stored knowledge (AES-256)
  • Sparse sync — teams push and pull only the documents they need
  • Per-organization data isolation with tenant-scoped storage — dedicated isolated environments available upon request

Authentication and Access

  • SSO / SAML / OIDC support for enterprise identity providers
  • API authentication via Bearer tokens
  • Role-based access controls for team and organization management
  • Audit logging for access and knowledge changes

Deployment Options

GitKB supports multiple deployment models to meet your organization's security and compliance requirements.

  • Local only — no cloud, no account, fully offline, completely free
  • GitKB Cloud — managed SaaS with team sync and backup
  • Private hosted — dedicated infrastructure in your preferred region
  • Self-hosted / on-prem — full control within your own infrastructure

Open Source

The GitKB core codebase is open source, currently available to enterprise customers upon request for security review. Our team is working toward broader open-source availability, which we will announce to the community in the future.

Responsible Disclosure

If you discover a security vulnerability in GitKB, please report it responsibly.

  • Email: security@gitkb.com
  • We will acknowledge receipt within 48 hours
  • We will provide an initial assessment within 5 business days
  • We do not pursue legal action against good-faith security researchers

Enterprise Security Review

For enterprise evaluations, we provide detailed security documentation, architecture reviews, and deployment planning as part of the pilot process. Contact sales@gitkb.com or book a demo to start the conversation.