Klark and Klara represent a paired self-hosted solution that combines corporate messaging with task management while ensuring all data remains on company servers.
The project originated from common enterprise pain points: work discussions scattered across personal Telegram groups, tasks lost in chat history, and departing employees taking files and context with them. The developers aimed for three core capabilities: internal-only storage of messages and files, one-click task creation from conversations, and single-command deployment without external cloud dependencies or subscriptions.
Klark offers familiar messaging features including private chats, groups, channels, and self-notes. Supergroups support forum-style topics, threaded replies, and read receipts showing exactly who viewed each message. Voice messages can be recorded with simple gestures and transcribed locally using an on-premise speech model. All attachments undergo scanning by ClamAV before delivery. Audio and video calls, screen sharing, and conferences run through the LiveKit media server installed on the customer’s infrastructure.
A dedicated “Today” panel displays unread messages, scheduled meetings, and tasks pulled from Klara without leaving the chat interface. One-time secret links allow secure sharing of passwords or keys that expire after a single view. Bot API support enables automated alerts from monitoring systems and CI pipelines.
Klara provides project and product tracking with a strict workflow of “Not started → In progress → Review → Completed.” Weekly sprints close automatically, carrying unfinished items forward with clear change history. The built-in wiki supports version control, approval workflows, scheduled publishing, and live embedding of task cards. Both products share an LDAP connector for Active Directory, OpenLDAP, and FreeIPA authentication while enforcing TOTP two-factor authentication and detailed audit logging.
Deployment uses a single Docker Compose script that generates secrets, obtains certificates, and starts all services. Updates require only a git pull and rebuild, leaving data volumes untouched. The stack relies on standard components: PostgreSQL 16, Redis, FastAPI, React, Capacitor, and Electron to ensure maintainability by ordinary system administrators.


