Klark and Klara Launch Self-Hosted Corporate Messenger and Task Manager for On-Premise Data Control
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.
Related articles
PT AF Cloud Uses Machine Learning to Detect Shifts in Web Attack Patterns from Millions of WAF Events
Positive Technologies has detailed how its PT AF Cloud service applies anomaly detection to WAF events, turning tens of millions of daily security events into actionable weekly alerts for SOC teams. The system builds traffic profiles based on the distribution of triggered protection rules for each tenant and compares current hourly or daily profiles against a weighted historical baseline using Jensen-Shannon distance. This approach identifies meaningful changes in attack composition even when overall event volume remains stable, catching the start of scans, exploitation of newly published vulnerabilities, or post-release application changes that trigger new rules. Two detection modes operate in parallel: an hourly mode for rapid spikes and a daily mode for gradual shifts distributed across multiple hours. Alerts include comparative tables of top rules, unique attack vectors, and direct links to the relevant events in the PT AF interface. Over four weeks the detector surfaced roughly 1,100 anomalies across the cloud, with expert review confirming that 69 percent indicated either an attack or a protection misconfiguration.
How to Prepare Your Website for Data Center Outages: Business Resilience Checklist
Following strikes on Yandex data centers, many businesses discovered that their sites and all backups were stored in a single location, leading to complete outages. The article provides a detailed checklist to mitigate such risks by separating critical components across different providers. Key recommendations include moving DNS to an independent provider, lowering TTL values, maintaining a live mirror site on separate hosting, and isolating corporate email. Additional steps cover local backups, monitoring, access management, and CDN usage. The guidance differentiates between virtual hosting, VPS or dedicated servers, and website builders like Tilda, while emphasizing compliance with Russian data localization laws such as 152-FZ.
How to Properly Compare CDNs: TTFB, p95 Latency, Caching, DDoS Protection and True Pricing
Selecting a CDN based solely on the number of points of presence is as unreliable as choosing a car by dashboard buttons. Networks with dozens of global PoPs may underperform for audiences concentrated in Novosibirsk or Yekaterinburg, while smaller regional providers often deliver superior peering with Russian operators. The article evaluates CDNVideo, EdgeCenter, Curator, NGENIX and Yandex Cloud CDN across verifiable features, network design, caching behavior, security controls, operations and commercial models. Performance data is separated because marketing claims cannot substitute for independent measurements from services such as CDNMON. Emphasis is placed on p95 metrics, cache hit ratios, origin shielding, raw logs and API limits rather than marketing scores. The analysis shows that no single universal ranking exists; optimal choice depends on traffic profile, audience geography, security requirements and operational workflows.
Innostage Lab Benchmarks PT NGFW 1.10.3 Performance in Eight Load Scenarios
Innostage researchers conducted extensive performance testing of PT NGFW version 1.10.3, the certified release at the time of trials. The evaluation covered TCP connection setup rates, concurrent session capacity, and throughput on a custom EMIX traffic profile with varying security modules enabled. Tests used Cisco TRex generators and a high-rule-count policy of 100,000 entries to simulate realistic enterprise conditions. Results showed the device sustaining 700,000 CPS and 6.4 million concurrent connections, matching or approaching vendor claims under HA-cluster configuration. Throughput remained above 27 Gbps even with IPS, application control, antivirus, NAT, URL filtering, and logging active. The report highlights differences in test methodology compared with vendor figures, including packet sizes and clustering setup.