Analytics cookies only (Google Analytics, PostHog). No ad networks, no cross-site tracking. See our privacy policy.
Hu
Self-host Huly
updated Oct 2026deployed by usprices checked · Jul 2026Install verified on Ubuntu 26.04 · Oct 2026 · how we test
We earn commissions when you shop through the links below. Full disclosure →
An open-source business-application platform whose self-hosted build combines project management with chat, CRM, HR and recruiting apps. The official docker compose setup is heavy: it runs nginx, CockroachDB, Redpanda, Elasticsearch, S3-compatible object storage and a set of Huly services, and upstream sets a minimum of 2 vCPUs and 8 GB of RAM. The code is EPL-2.0. The platform README says hosted Huly has shut down and that the hcengineering/platform repository is frozen, with development continuing in Platform-Collective/platform, so self-hosting is the way to run it.
Runs on a VPS from $82.59/mo (Hetzner Cloud CPX42, 16 GB RAM) · prices checked Sep 2026
Our recommendation
Pick Huly when you want one self-hosted platform that covers project management with chat, CRM, HR and recruiting apps, and you have a server to spare. It is an EPL-2.0 TypeScript and Svelte platform, deployed through the separate `huly-selfhost` repository's Docker Compose file, which runs nginx, CockroachDB, Redpanda, Elasticsearch, S3-compatible object storage and a set of Huly services. Upstream sets a minimum of 2 vCPUs and 8 GB of RAM, and recommends 4 vCPUs and 16 GB; the stack idled at about 3.7 GB on our 8 GB test server. For plain issue tracking, cycles and roadmaps on far less hardware, Plane is the catalog's lighter project-management pick.
What you need
Any VPS with at least 8192 MB of RAM
A domain you control — most self-hosted setups need HTTPS in front of them
Paid link — we earn a commission if you shop through it.
Install
Run these commands on your server:
# Huly self-host — the official huly-selfhost repo (docker compose), pinned to commit ca3808a, which runs Huly platform v0.7.426. Upstream's minimum is 2 vCPUs and 8 GB of RAM.git clone https://github.com/hcengineering/huly-selfhost.gitgit -C huly-selfhost checkout ca3808a57c83518b971343df7d073753f38796edcd huly-selfhost# setup.sh is interactive: answers are host address (SERVER_IP, your IP or domain), HTTP port (80), five empty volume paths (Docker named volumes) and Y to start the stackprintf 'SERVER_IP\n80\n\n\n\n\n\nY\n' | ./setup.sh# a few containers restart while the databases come up and docker ps shows redpanda as unhealthy (upstream's healthcheck gets a SASL error); wait a few minutes → http://SERVER_IP, then sign up; the first signup creates the workspace
Huly's self-host README and our test run point to these before you commit:
non-negotiableSize it as upstream says: below 2 vCPUs and 8 GB of RAM "may stop responding or fail". Our test box was exactly the minimum, with Elasticsearch, Redpanda and CockroachDB using most of the memory, so there is no headroom for anything else on the server.
non-negotiableThe platform README says the hosted Huly service has shut down because its hosting is no longer funded, and that this repository is frozen with development moved to Platform-Collective/platform, and points users to the self-hosted setup and a backup and restore guide. Self-hosted deployments are not affected, but you are then running the product without the vendor's hosted offering behind it.
non-negotiableUpstream's own warning: the provided CockroachDB and Redpanda configurations "might not be production-ready". On our run, nginx and the key-value store restarted a few times while the databases came up, and docker ps kept showing Redpanda as unhealthy (its compose healthcheck gets a SASL error) while sign-up and the web app worked. The compose file also leaves some infrastructure images floating (cockroachdb/cockroach:latest-v24.2, an untagged pgsty/silo) and pins Elasticsearch 7.14.2.
non-negotiableRead MIGRATION.md before every upgrade: some versions need extra steps, and moving from any 0.6.x version to 0.7.x requires a dedicated migration rather than an in-place upgrade. Use production v* tags. The repo ships backup-create.sh and backup-restore.sh; plan backups of the CockroachDB, files and Elasticsearch volumes.
non-negotiableOur snippet serves plain HTTP on port 80 for an IP address. For a domain with TLS, answer yes to the SSL prompt in setup.sh and add certificates to the nginx configuration it generates; upstream's setup guide has you run nginx on the host in front of the stack.