Kergit is a realtime chat and voice system built around a C++ backend, protobuf over WebSocket, a Nuxt web client, and LiveKit for media.
Project page · Architecture · Voice lifecycle
Kergit is an advanced prototype / personal systems project. It is not production-ready. The core text and state-sync paths are usable, but setup, operations, and some voice flows still need cleanup.
- C++ backend with Bazel
- Protobuf over WebSocket
- Nuxt 4 / Vue 3 web and admin clients
- LiveKit for voice/media
- PostgreSQL + Supabase for persistence and auth
- Redis for short-lived coordination
- Caddy for local and edge routing
server/,app/,net/, andcontrol/contain the backend runtime.proto/defines the shared client/server protocol.clients/web/is the main user-facing client.clients/admin/is an operator-only dashboard.docker/andlivekit/conf/contain the local stack.
Core docs:
docs/ARCHITECTURE.mddocs/SETUP.mddocs/ENVIRONMENT.mddocs/SECURITY.mddocs/ROADMAP.md
- authenticated sessions with Supabase-backed identity
- hub and channel state sync
- realtime text chat and invite links
- session-owned voice join / revoke / resume flows
- operator metrics and control surfaces
git submodule update --init --recursive
cp .env.dev .env
./docker/run-server.shStop the stack with:
./docker/stop-server.shUseful variants:
./docker/run-server.sh --prodFor backend-only operation, use the independent scripts:
./docker/services/backend/run-container.sh
./docker/services/backend/exec-server.shThe committed .env.dev contains public, non-secret defaults and does not connect
PostgreSQL or Supabase. Put real local credentials only in the ignored .env when
testing persistence, authentication, or storage. See docs/SETUP.md for prerequisites,
production-mode requirements, and client-only workflows.
- voice/video UX and dynamic multi-node LiveKit behavior still need more validation
- admin and control-plane routes are operator-only, not public endpoints
- some internal protocol and build identifiers still use legacy
sercomnames for compatibility
Create the ignored environment file from the safe tracked defaults before invoking Bazel directly. CI performs the same copy.
cp .env.dev .env
bazel build //...
bazel test //...
cd clients/web && pnpm testIf the web protobuf artifacts are missing:
./clients/web/docker/generate-proto.shSee CONTRIBUTING.md. Good early contributions are targeted tests, setup fixes, documentation improvements, and small reliability fixes.