Skip to content

Why I Love Keybase

Keybase changed how I collaborate:

  • Git over KBFS: shared private git repos in /keybase/team/...
  • Chats: encrypted, team-based, persistent history
  • KBFS: files shared between machines, users, teams
  • Sigchain: identity with proof — not trust

Sovereign Git

I run full git projects inside:

/keybase/private/me/project-name
/keybase/team/myteamname/project-name

No GitHub dependency. No third-party repo visibility. Sovereign git.

Encrypted, Always

Every message, file, commit is encrypted:

  • End-to-end by default
  • No passwords
  • No servers to trust

Social Proofs + Sigchain

Your identity isn't just a username — it's backed by:

  • Device keys
  • Linked social accounts (Twitter, GitHub, Reddit)
  • Signed messages + files
  • Immutable sigchain

My digital fingerprint spans all platforms — and can’t be faked.

Bonus: PHP over KBFS

You can serve static assets, templates, or PHP from Keybase to local daemons. It’s weird, but it works — like a private, distributed NFS.

Keybase is digital sovereignty:
git + identity + E2E infra + team chat + portable auth.

One stack to rule them all — signed, synced, secure.