Do I need a Cloudflare or S3 account?
No. LiveHQ runs the edge, issues the certificates and, on Pro, stores your database backups. You bring a VPS and a GitHub repository.
Which servers does LiveHQ support?
Ubuntu or Debian on x86-64 or ARM64, from any provider. The installer sets up Docker if it's missing. Two vCPUs and 4 GB of RAM is a comfortable start.
What can I deploy?
Web apps and APIs that speak HTTP, server-sent events or WebSockets: Next.js, React, Vue and Vite, Python and FastAPI, Rust, static sites, or anything with a Dockerfile, plus PostgreSQL databases. Background workers, cron jobs, persistent volumes and Redis aren't supported yet.
Can LiveHQ get into my server?
No. You run the installer yourself and type a single-use enrollment code from your console, so your LiveHQ password never reaches the server. LiveHQ never holds or adds an SSH key. It can only send typed, exact commands that your server's agent checks, such as deploying a commit or installing waiting security updates, never a shell. Private SSH relays encrypted bytes to your server's own SSH daemon, which only your keys open.
How are my servers kept up to date?
Every day in your server's maintenance window, LiveHQ installs your distribution's security updates and nothing else: no feature updates, no release upgrades. Each new version reaches most servers only after it installed cleanly on others, and is halted for everyone if it causes trouble in two workspaces. LiveHQ can delay an update but never choose one. Docker Engine updates wait for your approval unless you allow bug-fix releases, and you're warned 90 days before your Ubuntu or Debian release loses security support.
Will LiveHQ restart my server?
Only when an update needs it, and only the way you choose. Security updates install in your server's nightly maintenance window. Restarts go in a weekly slot with a day's notice by email, or wait for your approval, and you can pause or turn patching off. A restart keeps the last good kernel as a safety net, and visitors see a “Back in a moment” page meanwhile.
Can I close SSH too?
Yes. Locking a server closes every port on IPv4 and IPv6, SSH included if you choose, starting with a five-minute trial that reopens on its own unless you keep it. An outside check confirms what the internet can see. You can still reach SSH through your server's own tunnel with a one-time command from the console, with your own keys end to end.
What happens when my app is attacked?
Every app has its own firewall at LiveHQ's edge, so whatever it refuses never reaches your server and never counts against your bandwidth. A per-app flood guard is on by default. You can add rules and rate limits, turn on attack signatures and a bot check, or switch on attack mode, which asks every visitor to pass a quick browser check and can turn itself on when traffic spikes. Owners and admins get an email when an app comes under heavy attack. It's all on every plan. The browser check stops scripts and simple bots, not a determined person in a real browser.
What happens when I reach my bandwidth limit?
Owners and admins get an email at 80% and at 100%, and everyone in the workspace sees a banner from 75%. At 100%, your apps pause until the next period starts or you upgrade. Bytes the edge saves through compression and caching never count.
Can LiveHQ read my environment variables?
No. Your browser encrypts each value to your server's own key before it's sent. LiveHQ stores and delivers the encrypted value but holds no key that opens it; only your server can. The flip side: LiveHQ can't show a saved value back to you, so keep your own copy, for example in a password manager.
Could October's platform breaches happen on LiveHQ?
At Railway, the attacker escalated through shared build machines, then decrypted stored secrets with the platform's own credentials. LiveHQ builds on your own server and holds no key that opens your variables, so a stolen LiveHQ database or backup reveals none of them. No platform is immune to every attack; the security page lists what we protect and what we're still building.
Can LiveHQ see my traffic?
Like any edge or CDN, TLS ends at Cloudflare and LiveHQ's edge so requests can be routed and access-checked, then they travel to your server over the agent's tunnel. Your code, builds, containers and databases stay on your server.
What happens if LiveHQ has an outage?
Your apps, builds and data live on your server and keep running there. Visitors reach them through LiveHQ's edge, so while the edge is unreachable they can't load your apps. That's the trade for keeping your server closed to the internet.
Can I leave?
Yes. Your apps are built from your own repository into containers on your server, and your database is standard PostgreSQL. Take your code and your data whenever you want.