Reference
Technical reference for the Qubital engineering stack. Every page here describes what something is and how it works — not how to operate it under pressure (that's runbooks/) or how to do a specific task (that's how-to/).
Sections
backend/
The Go backend service: domain features, REST and WebSocket API, database schema, and environment configuration. Deployed on Sevalla as a Docker container, built from StartingQuoTechDivision/livekit-backend-go.
frontend/
The Electron + React/TypeScript desktop client: UI components, custom hooks, Zustand stores, and route definitions. Covers both the renderer and main process.
platform/
Everything the system depends on that isn't application code:
services/— external vendors: WorkOS (auth), LiveKit Cloud (video), Cloudflare (Workers + R2), Supabase (DB extensions), Google (Calendar + YouTube + Sheets), Grafana/Mimir (metrics)devops/— CI/CD pipelines, Sevalla deployment, observability stack, and internal automations (ClickUp bot, doc-writer agent)
What belongs here vs elsewhere
| Question | Go to |
|---|---|
| What does feature X do and how is it structured? | reference/backend/features/ |
| How do I call the API for X? | reference/backend/api/ |
| How do I set up or configure external service Y? | reference/platform/services/ |
| How do I do task Z? | how-to/ |
| What do I do when something is broken? | runbooks/ |
| Why did we decide to do it this way? | adr/ |
| How does data flow across the full system? | architecture/ |