Huly Platform

Put chat, projects, CRM, HRM, and ATS on one shared workspace

The repository contains application areas for Chat, Project Management, CRM, HRM, and ATS. The common denominator is not a single issue tracker but a platform that centralizes authentication, workspace membership, permissions, transaction processing, and document collaboration. That makes it possible to design workflows that connect sales, project work, recruiting, and people data inside one organizational context instead of depending entirely on synchronization between unrelated SaaS products.

Sources: [1]

Separate real-time collaboration and async processing across dedicated services

The Architecture Overview describes more than 30 microservices. The Transactor handles mutations and WebSocket connections, while Collaborator provides simultaneous document editing with Y.js CRDTs. Asynchronous events flow through the Kafka-compatible Redpanda bus to consumers such as Fulltext, Media, and Process for indexing, media work, and workflow automation. CockroachDB stores primary application data, Elasticsearch serves full-text indexes, MinIO stores binary assets, and Redis supports notification caching and pub/sub, giving the platform a deliberately distributed service architecture.

Sources: [2]

Make search, documents, media, backup, and workflows platform services

The service inventory includes Rekoni for extracting searchable content from formats such as PDF and DOCX, full-text indexing, thumbnails and previews, video streaming, PDF generation, digital signatures, workspace export, backup, analytics, and process automation. The README also points to a typed API client for programmatic Huly operations. That makes the project relevant as an application platform for integrations and custom business software, not merely as a collaboration UI that teams must use exactly as shipped.

Sources: [1][2]

For organizations consolidating fragmented collaboration and business data

Huly Platform fits teams whose communication, project management, customer management, and people operations are split across different SaaS products and whose permission, search, history, and automation layers are becoming difficult to keep consistent. It also fits engineering organizations that want to build their own CRM or vertical business application on top of reusable collaboration infrastructure. If the requirement is only a small self-hosted issue tracker or chat service, the operational scale of the full platform can be disproportionate to the problem.

Sources: [1][2]

Self-hosting is substantial; hosted Huly and EPL-2.0 need review

The development architecture spans more than 30 services plus CockroachDB, Elasticsearch, MinIO, Redpanda, and Redis. The README offers a minified Docker variant for resource-constrained development, but also notes that a full WSL deployment can consume more than 35 GB of virtual disk. Users who only want to operate Huly are explicitly directed to hcengineering/huly-selfhost rather than building this platform repository directly. Production deployments should use v* releases, while s* builds are development/pre-release versions and are not recommended for production.

The README also carries a notice that the hosted Huly service is being discontinued and directs users toward migration, while self-hosted deployments are unaffected. Availability of the managed service should therefore be verified rather than assumed. The repository is licensed under Eclipse Public License 2.0, not a permissive MIT-style license. Commercial use is possible, but distribution of the Program or Modified Works brings EPL source-availability and notice obligations into scope, so derivative and redistribution scenarios should be reviewed against the license text.

Sources: [1][2][3]