Updated October 2026

LiveHQ vs Coolify

Both run your apps on a server you own. Coolify hands you a powerful toolkit to assemble and secure; LiveHQ hands you the secured result. Here is the honest difference, sourced from each product's documentation.

~12vs~36–55

documented steps to a private app and database with HTTPS, a global edge and off-site backups

0vs3–6

web ports published on your server by default (80, 443, 8080, plus 8000, 6001 and 6002 when self-hosted)

NovsYes

root SSH key to your server held by the platform's control plane

The ledger, outcome by outcome

One server, one app and one database. The Coolify column follows its own guides to the same posture; the LiveHQ column follows its default console flow. Counts are documented actions, excluding troubleshooting and DNS propagation. Outage alerting is left out on both sides.

OutcomeCoolify, self-hostedLiveHQ
Server connectedGenerate a passphrase-less key, add it to root's authorized_keys, enter IP, port and user, validate: ~5 steps. Port 22 stays open to the control plane unless ~7 more steps move SSH into a Cloudflare tunnel.Copy one console command, run it in your own SSH session, type a single-use code from your console: ~5 steps. No key handed over, no port opened.
No inbound web ports, no server IP in DNSCloudflare account with your DNS on Cloudflare, a tunnel token pasted into cloudflared, a wildcard route, the HTTPS redirect turned off per app, provider-firewall rules for the still-published proxy ports: ~10 steps, plus ~7 for end-to-end TLS.The default. Apps listen on loopback and traffic leaves through the outbound tunnel: 0 steps.
HTTPS addressYour own domain and A record, since the generated sslip.io address is HTTP-only: ~3–4 steps per domain, ~5 more for wildcards.https://name.livehq.app at first deploy. A custom domain is one CNAME and ~3 steps.
Global edge in frontYour own Cloudflare account, configured as above, plus WAF tuning.Cloudflare proxying is inherited automatically.
Login wall for private appsOne shared basic-auth credential (~3 steps per app), or run Authentik and wire Traefik forward-auth (~9+ steps).Private by default. Invite people by email, grant teams or guests, or set an app password.
Off-site database backupsS3 bucket, IAM policy, user and key pair, a per-database schedule and a restore drill: ~15 steps. Backups are not encrypted by Coolify.On Pro, encrypted off-site backups take ~3 steps: pick a schedule and turn on off-site copies. No storage account.
Inbound ports left on the VPS22 unless tunneled. 80, 443 and 8080 stay published on the host and are closed only by provider-firewall rules or ufw-docker; 8000, 6001 and 6002 on a self-hosted instance until overridden.None added. Your own SSH as before, plus one IP-allowlisted port only if you enable external PostgreSQL access.
Total~36–55 steps, plus Cloudflare and S3 accounts~12 steps and one single-use code

Two security models

LiveHQ installs your server's security updates every night and can close every port; with Coolify, OS updates are an opt-in beta and the firewall is yours to set up. Above all, they differ in what is exposed by default, and in who you trust.

Coolify

Your server is the perimeter

  • The control plane connects over SSH with a passphrase-less root key.
  • The proxy publishes web ports on the host, and Docker exposes them past plain UFW.
  • DNS points at your server unless you build a Cloudflare Tunnel.
  • TLS ends on your own server, so no third party sees your traffic by default.
  • Hardening, firewall rules and every mistake in them are yours to maintain.

LiveHQ

A closed server behind an edge

  • The agent dials out. LiveHQ never holds an SSH key to your machine.
  • Apps listen on loopback; no web port is published on the host.
  • DNS points at the edge, never at your server.
  • TLS ends at Cloudflare and LiveHQ's edge, which route and access-check requests.
  • Your app variables are sealed so only your server can read them; LiveHQ holds the keys that protect your backups.

Which one is right for you

Choose Coolify if

  • No third party may ever see your decrypted traffic.
  • You need raw TCP or UDP services; LiveHQ apps speak HTTP, server-sent events and WebSockets.
  • Your sites must keep serving while the platform itself is down. LiveHQ's edge is in the request path.
  • You want a large one-click service catalog today, or open source you run end to end.

Choose LiveHQ if

  • You want a hardened setup without becoming the security team.
  • You ship internal tools and staging sites that must stay private.
  • You want encrypted off-site backups (on Pro) without S3 accounts, keys and restore drills.
  • You want a closed server: no published web ports, no IP in DNS, no root key in someone else's dashboard.
Start free

Sources

Coolify figures come from its documentation and source for v4.5, read in October 2026. LiveHQ figures come from its onboarding, domain and backup flows. See the FAQ for LiveHQ's own trade-offs.