Skip to content

Rakkr Documentation

Rakkr Documentation

Rakkr is a centrally managed Linux audio recording platform for reliable room recording. It captures audio on managed Linux nodes, watches the audio while it is being recorded, and gives operators a single console to start, schedule, monitor, and ship every recording — with an audit trail behind every privileged action.

Rakkr is built around one idea: a recording failure should become visible while the session can still be saved, not after the meeting is over.

The system in one picture

flowchart LR
  room["Room audio"] --> agent["Recorder agent (Rust)"]
  agent -->|"capture / meters / health"| cache["Local cache"]
  agent <-->|"encrypted HTTP / WS"| api["Controller API (Hono)"]
  api <--> db["Postgres + Drizzle"]
  api --> ui["Operator console (React)"]
  cache -->|"upload"| storage["SMB / S3"]
  api --> metrics["/metrics → Prometheus / Grafana"]

Rakkr has four parts:

  • a controller API (Hono/Node) for auth, RBAC, audit, inventory, recordings, jobs, schedules, settings, health, uploads, and metrics;
  • a React operator console for day-to-day operations;
  • a Rust recorder agent that runs on each Linux audio node — it captures audio, samples meters, scores quality, manages local cache, and syncs with the controller;
  • Postgres + Drizzle for controller persistence, with JSON/in-memory fallback stores so the controller can run without a database.

An optional Dockerized Ansible runner provisions and updates recorder nodes over SSH.

Where to start

If you want to…Read
Understand what Rakkr is and why it existsIntroduction
Run it locally in a few minutesQuick start
Learn the vocabulary (nodes, jobs, schedules, channel maps…)Core concepts
Understand how the pieces fit togetherArchitecture overview
Operate a specific featureThe Guides
Look up an env var, endpoint, or permissionThe Reference
Deploy or monitor a controllerOperations
Contribute codeContributing

Documentation map

Source of truth

The product contract, status ledger, and promotion record live in RAKKR_SOURCE_OF_TRUTH.md. When code, docs, and the ledger disagree, investigate before changing behavior.