Security · Updated November 2026

A breach of LiveHQ shouldn't become yours.

LiveHQ is built so the things attackers come for, your secrets and your servers, aren't sitting in our systems to be taken. Here is exactly how, including what we can see and what we're still building.

Transcript

In October, attackers broke into several developer platforms. At one of them, they pulled customers' encrypted secrets, then used the platform's own internal credentials to decrypt some of them. The encryption didn't help, because the platform held the keys. LiveHQ is built so your secrets never depend on our keys. When you save a variable, your browser encrypts it to a key that belongs to your server, before it leaves the page. LiveHQ stores it and passes it along, but it cannot read it. Not from our database, not from our backups, not by any of our engineers. The only key that opens it lives on your server, and it never leaves. Your server stays closed, too. It opens no web ports, and its address never appears in your DNS. LiveHQ never holds a key to log into it. Your apps run in locked-down containers, your code is built on your own machine, and every agent update is signed with a key that never touches our servers. And we're honest about what comes next: an independent security review, before general availability. LiveHQ. Self-hosting, without the self-defense.

0

keys at LiveHQ that can open your app variables

0

web ports your server opens to the internet

0

SSH keys to your server held by LiveHQ

0

open ports, SSH included, once you lock a server

Your secrets are sealed to your server

Most platforms encrypt your environment variables with keys they hold, so they can decrypt them for you, and so can anyone who steals those keys. LiveHQ removes that key from the platform entirely.

  1. 1

    Your server makes its own key

    When the LiveHQ agent starts, your server creates an encryption key pair. The private half is stored encrypted on your server, readable only by root, and never leaves it.

  2. 2

    Your browser seals each value

    When you save a variable, the console encrypts it to your server's public key before sending it. Each value is bound to its app, server, name and scope.

  3. 3

    LiveHQ only carries the envelope

    LiveHQ stores the sealed value and hands it to your server at deploy time. It refuses plaintext, and nothing in LiveHQ can open what it stores.

  4. 4

    Your server opens it, and only for that app

    Your server decrypts the value, checks it was sealed for exactly this app and name, and passes it to your app privately, never in logs, labels or image layers.

1 Your browser

Sealed here, before it leaves the page.

2 What LiveHQ stores

Nothing yet.

Also all a thief could take.

3 Your server

Waiting for a value.

The only key that opens it never leaves your server.

Try to break it:

Real HPKE (RFC 9180) with X25519 and AES-128-GCM, the encryption LiveHQ uses, running entirely in your browser. Nothing you type is sent anywhere.

Details for security teams
  • Encryption is HPKE (RFC 9180) in base mode with DHKEM(X25519, HKDF-SHA256), HKDF-SHA256 and AES-128-GCM, one ephemeral key per value.
  • Each value's authenticated data binds its organization, app, server, key, name and scope. The server refuses any value sealed for something else.
  • The server's public key is published in a statement signed by its P-256 device key, which LiveHQ verifies before the console may use it. Browsers remember each server's key and block saving if it ever changes.
  • The browser side uses only native WebCrypto; the server side uses the Rust hpke crate. Both reproduce RFC 9180's published test vectors, and a value sealed by the console is opened by the agent in our test suite.
  • The cost: LiveHQ can't show you a saved value again, so keep your own copy.

The Security tab

Your server, hardened.

Every server you connect gets a Security tab. It shows what the internet can see, closes what shouldn't be open and keeps SSH for you alone, each with one switch and a way back.

Server · Security
The LiveHQ console's Security tab for a server marked locked down: nothing answers from the internet, checked from outside 4 minutes ago, and all four protections on: private SSH, password logins off, closed to the internet with SSH only through LiveHQ, and security updates with a planned restart.
The Security tab: locked down, checked from outside, every protection on.

Exposure check · The lock

See what the internet sees. Then close it.

Your server lists everything listening beyond itself, and which program owns it. LiveHQ then checks from outside, the way an attacker would: those ports and about 60 common ones, every week and whenever you press Check now.

  • It only probes the public address your server reports as its own, so nobody can aim it at someone else's machine.
  • Locking closes every port on IPv4 and IPv6, ping and Docker-published ports included. For SSH you choose: keep it open, allow only your addresses, or close it.
  • A lock starts as a five-minute trial with a fresh outside check, and removes itself unless you keep it.
  • A kept lock survives reboots and stays shut even if your server loses touch with LiveHQ. Your provider's web console is always a way back in.
Server · Private SSH
The LiveHQ console's private SSH steps for a server: install websocat once, then create a one-time command that works once for 60 seconds; below, password logins are off and the server is closed to the internet.
Private SSH and keys only, each one switch.

Private SSH · Keys only

SSH that only your keys can open.

With port 22 closed, SSH still works. Ask the console for a one-time command: it reaches your server's SSH daemon through the tunnel your server already opened, so LiveHQ relays encrypted bytes and the login stays between your key and your server.

  • Each command works once, within 60 seconds, and can only ever reach your server's own SSH daemon at 127.0.0.1:22.
  • LiveHQ never adds a key to your server and never issues SSH certificates, so a breach of LiveHQ can't become a login.
  • Keys only turns password logins off in one switch. It first checks an admin who can log in has a key, never loosens root login, and reverts if SSH disagrees.
  • Owners and admins are emailed when someone else opens a session, and when the lock, keys only or private SSH changes.
  • OS health, in plain words

    Your server reports hourly and right after every action: its release and when security support ends, waiting updates, a needed restart, the running kernel and how SSH lets people in. Problems read like “SSH accepts password logins. Keys only is safer.”

  • A weekly server report

    Every Monday, one email per workspace: what each server installed, the CVE numbers it closed, restarts, what's waiting, and what the outside check found. Owners and admins can email it to themselves any time.

  • A second factor for the sharp tools

    With two-factor sign-in on, locking, unlocking, SSH, keys only, restarts, patching settings and database credentials all ask for a passkey or code from the last 15 minutes.

Managed patching

Patched while you sleep.

A security fix only protects a server once it's installed. LiveHQ installs your distribution's security updates every day in your server's maintenance window, 03:00 by default. It proves each one on other servers first and plans the restarts, so you never have to log in to stay current.

  1. Your server checks in at the start of its window. If a deploy, build, backup or restore is running, or disk is short, the run waits.

  2. It looks only at what its distribution's security channel has waiting: never feature updates, release upgrades or repositories you added yourself.

  3. A new version reaches about one server in ten first, and everyone a day later, once it installed cleanly in other workspaces. Trouble in two workspaces halts it for everyone.

  4. Packages signed by your distribution install through APT, each pinned to its version, your configuration kept. Then Docker, every app that was healthy, the tunnel and SSH must all check out.

  5. When the kernel or a core library needs a restart, it is booked into your weekly slot at least a day away and you're emailed. Or it waits for your OK.

  6. The server boots its new kernel once. If that kernel can't start, the machine restarts into the previous one by itself, never tries it again, and reports it toward the fleet-wide halt.

  7. While the server restarts, visitors see a short maintenance page instead of an error, and private apps stay private.

  8. The Security tab lists every run with its packages and the CVE numbers they close, and Monday's weekly report sums up each server's week.

An example week with the default times, in your server's maintenance time zone. The kernel safety net works wherever GRUB is the boot loader; servers whose provider supplies the kernel restart normally.

Server · Security updates
The LiveHQ console's Security updates card for a server: updates every day at 03:00 UTC, tried on other servers first, restarts on Sundays with a day's notice and a fallback to the previous system core; a restart planned for Sunday with Postpone and Restart now; a Docker update waiting for approval; and the recent runs, including updates held back until they've worked on other servers.
The Security updates card: what's waiting, what was fixed, and your settings.

You stay in charge

  • Automatic, I approve restarts, or Off. Off hands updates back to your system's own automatic updates.
  • Install now, approve a restart, postpone it a week, or restart now, all from the card.
  • Pause for 1 to 14 days, for a launch or a change freeze.
  • Docker Engine updates from Docker's own repository, with your approval or automatically for bug-fix releases, with live restore turned on first.
  • Warned 90 days before your Ubuntu or Debian release stops getting security updates.

Changing these settings asks for a second factor when two-factor sign-in is on.

App firewall

Every app gets its own firewall.

It runs at LiveHQ's edge, so whatever it refuses never reaches your server. And blocked traffic is never counted against your plan's bandwidth.

See the firewall
  • Attack signatures

    SQL injection, cross-site scripting, path traversal, command injection, Log4Shell and more, in the spirit of the OWASP Core Rule Set. Try them log-only first.

  • Bot check

    Scripts, headless browsers and fake search-engine bots get a browser check or a refusal. Verified crawlers and webhooks are never challenged.

  • Attack mode

    One switch makes every visitor pass a quick browser check. It can also turn itself on for 15 minutes when traffic jumps far above normal.

  • On every plan

    Plans only size the lists. Every protection is on Free too, and one app's attack never changes another app's limits.

What LiveHQ can and can't do

Trust should be precise. Here is the whole list.

LiveHQ cannot

By design, not by policy

  • Read the values of your app variables, from our database, our backups or our staff.
  • Log into your server or run a shell on it. LiveHQ can only send typed, exact commands.
  • Install an agent update your server hasn't verified against our offline release key.
  • Choose a package for your server to install. Updates come only from your distribution's security channel, or Docker's own repository, as your server finds them; LiveHQ can only say “not yet”.
  • Reach your apps except through the tunnel your own server opened.

LiveHQ can

What running the service requires

  • The names of your variables, so the console can list them.
  • Requests to your apps as they cross the edge. As with any CDN, TLS ends there so we can route them and check access.
  • Your build and deployment logs, and usage metrics.
  • Off-site copies of databases you choose to back up. They are encrypted, and LiveHQ holds those keys so it can restore them for you.
  • Your server's public address, which LiveHQ probes from outside, weekly and when you ask, to show you what's exposed.
  • For 24 hours, details of requests your app firewall refused or logged, such as IP, country and path, so you can see an attack.

Closed by default, at every layer

Most of these are how every LiveHQ server and app starts. The lock, private SSH, passkeys and the firewall's stricter protections are one switch away, on every plan.

Why we built it this way

On October 21, 2026, Railway disclosed that an attacker had escalated privileges in its build infrastructure, pulled customers' encrypted environment variables, and decrypted a subset with compromised internal credentials. Railway estimated that up to about 1.85% of workspaces were affected. Wiz counted at least nine developer platforms with incidents that month, many hunting stored API keys.

The lesson isn't about one company. Any platform that can decrypt its customers' secrets can be made to. So we built LiveHQ so that it can't.

LiveHQ vs Railway

What we're still building

  • An independent security review, before general availability.
  • Hardware-backed signing for the keys LiveHQ's platform holds.
  • A LiveHQ command-line client for private SSH, in place of the console's one-time command.

Found a vulnerability?

Email [email protected] with the details and how to reproduce it. We reply to every report, fix confirmed issues first, and credit you if you wish. Please give us a reasonable chance to fix an issue before disclosing it, and never access other people's data while testing. Our contact details are also in security.txt.

Sources