Content Sync

Push to your repo. KBKit publishes.

Connect GitHub, GitLab, or Bitbucket. Webhooks pick up every push and your docs go live in seconds. No CMS to babysit.

terminal

$ git push origin main

Enumerating objects: 5, done.

Counting objects: 100% (5/5), done.

Compressing objects: 100% (3/3), done.

To github.com:acme/docs.git

   a1b2c3d..e4f5g6h  main -> main

 

Webhook received by KBKit

Parsing 12 markdown files...

Indexed and published in 1.4s

Multi-provider OAuth

GitHub, GitLab, Bitbucket. One-click connect.

Authenticate with the provider you already use. KBKit requests only the read access it needs to mirror your docs folder — never write access, never your private code.

  • OAuth-only — no PATs, no SSH keys to rotate
  • Read-scope only — your code stays private
  • Repo picker — choose exactly which repos to sync
  • Re-authorize anytime from settings

Connect a provider

Authorized 2 minutes ago · acme-dev

Webhook-driven updates

Real-time. No polling, no delays.

Every push fires a webhook. KBKit parses the diff, updates only the changed articles, and rebuilds search indexes incrementally. Your docs stay seconds-fresh.

GitHub

push · main

Webhook

KBKit

Updated 4s ago

Frontmatter-driven structure

YAML in your markdown drives everything.

Title, description, category, ordering — KBKit reads it all from frontmatter. No CMS to maintain in parallel; the markdown file IS the source of truth.

markdown
1 ---
2 title: Authentication
3 description: How to authenticate API requests.
4 category: getting-started
5 order: 2
6 ---
7
8 # Authentication
9
10 KBKit supports OAuth and API tokens.

Ready to ship docs by pushing to a repo?

Free on every plan. Connect a repo and you're live.