DeployHQ

DeployHQ is a Git-based deployment platform that builds your Qwik City application on its build pipeline and transfers the output to your own infrastructure over SSH, SFTP, or FTP. It also supports Amazon S3, Azure Blob Storage, and Rackspace Cloud Files as deployment targets.

Because DeployHQ deploys to a server you control, the recommended adapter is Node (Express or Fastify) for SSR apps, or the Static Site adapter for fully pre-rendered apps.

Installation

Install the Node adapter for SSR (Express shown here):

pnpm run qwik add express

npm run qwik add express

yarn run qwik add express

bun run qwik add express

Or, for a fully static build:

pnpm run qwik add static

npm run qwik add static

yarn run qwik add static

bun run qwik add static

Production build

DeployHQ runs your build command on its own build infrastructure. In your DeployHQ project's Build Pipeline, add a step that runs:

pnpm install --frozen-lockfile && pnpm run build

npm ci && npm run build

yarn install --frozen-lockfile && yarn build

bun install --frozen-lockfile && bun run build

This produces the dist/ directory (client assets) and, for SSR adapters, the server/ directory containing entry.express.js or entry.fastify.js.

Production deploy

1. Connect your Git repository (GitHub, GitLab, or Bitbucket) to a DeployHQ project.
2. Configure one or more servers for the environments you want to deploy to (e.g. staging, production). Each server can deploy over SSH, SFTP, FTP, S3, Azure Blob, or Rackspace Cloud Files.
3. Add the build command above to the project's build pipeline so the dist/ and server/ folders are produced before transfer.
4. On the target server, install production dependencies and start the Node entry file. For Express:

ORIGIN=https://your-domain.com node server/entry.express.js

It's very important to correctly configure the ORIGIN environment variable, which is used to check against CSRF attacks. The origin must match the origin of the client application. A process manager such as PM2 or a systemd unit is recommended for keeping the server running — see the Self-Hosting guide for examples.

For static builds, point the deployment target at the contents of dist/ and serve it with any static web server.

Atomic releases, rollback, and environments

Each deployment creates an immutable release on the target server, so a one-click rollback restores the previous build instantly. Separate DeployHQ projects (or separate servers within the same project) let you keep staging and production isolated, and config-file injection lets you keep environment-specific values like ORIGIN out of the repository.

A free tier is available — sign up at deployhq.com/signup to get started.