hcengineering/huly-selfhost

Huly for Self Hosting

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 23 minutes ago
Added to GitGenius on September 19th, 2026
Created on March 12th, 2024
Open Issues & Pull Requests: 143 (+0)
GitHub issues: Enabled
Number of forks: 472
Total Stargazers: 3,537 (+0)
Total Subscribers: 26 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 33.6 hours
Mean response time: 12.7 days
90th percentile: 32.5 days
Tracked items: 144

Most active contributors

Sign in to see contributor activity.

How this project is maintained

Roughly one issue in two opened in the past year never receives a reply. 100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 30% of issues opened in the past year have been closed. Three people close 50% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 117
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 470 days
Stale 30+ days: 115
Stale 90+ days: 103

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Huly Self-Hosted is a self-hosted deployment configuration for an all-in-one work platform that runs on your own infrastructure using Docker Compose or Kubernetes.

The tool addresses the need to run Huly on private servers rather than relying on cloud hosting. It provides Docker Compose configurations and Kubernetes manifests to orchestrate the platform's services, along with detailed migration guidance for version upgrades. The deployment includes multiple interconnected services that require careful resource allocation and configuration management.

Organizations should adopt this tool if they need on-premises hosting for compliance, data residency, or privacy reasons. The platform is resource-intensive, requiring a minimum of 2 vCPUs and 8 GB RAM, with 4 vCPUs and 16 GB RAM recommended for stable operation. The tool suits teams deploying on Linux servers, whether on cloud providers or local infrastructure. A quick-start mode is available for local testing, while production deployments require following full setup instructions and consulting the migration documentation before upgrading versions. The README emphasizes that version upgrades must be preceded by reviewing migration steps, as some transitions between major versions require specific procedures beyond simple container image updates.

Development activity shows consistent attention to operational documentation, with detailed architecture overviews and migration guides maintained alongside deployment configurations. The project includes explicit warnings about resource constraints and provides version-specific upgrade paths, indicating focus on preventing common deployment failures. Updates to the self-hosted configuration track changes in the upstream platform, with version tags and release notes referenced for production deployments.