Skip to content
Docs home

SELF-HOSTING · UPDATED AUGUST 2026

Deployment

Installation order, the production compose profile, TLS through the edge, and health verification.

Prerequisites

A dedicated Ubuntu 24.04 host or VM with Docker Engine and the Compose plugin, a stable public IPv4/IPv6 address, and DNS records created before production issuance: the root application host, the wildcard record for tenant subdomains, and named hosts for Supabase, Grafana, Prometheus, and Sentry as required by the operations installer.

Installation order

Provision the operations stack first — the installer brings up self-hosted Supabase, Prometheus, Grafana, and Sentry with loopback/proxy hardening. Then deploy the edge profile from the selfhost directory, which places OpenResty in front of the application and handles tenant custom-domain TLS through lua-resty-acme.

bashProduction bring-up
# 1. Operations stack (Supabase, Prometheus, Grafana, Sentry)
sudo DOMAIN=example.com EMAIL=ops@example.com \
  PROXY=nginx bash scripts/ops/install-ops-stack.sh

# 2. Application directory and secret file
sudo install -d -m 0750 -o root -g root /opt/que
sudo install -m 0600 -o root -g root ops/selfhost/.env.selfhost.example \
  /opt/que/.env.selfhost
sudoedit /opt/que/.env.selfhost

# 3. Bring up the edge profile
sudo docker compose \
  --env-file /opt/que/.env.selfhost \
  -f ops/selfhost/docker-compose.production.yml \
  up -d --build

Health verification

Verify the deployment through the health endpoint and the metrics endpoint. The health check (GET /api/public/healthz) returns the platform status, a database check with latency, and uptime. The metrics endpoint (GET /api/public/metrics, Bearer METRICS_TOKEN) exposes the Prometheus-format counters including webhook delivery and rejection totals. A fresh deployment is healthy when healthz returns status ok with a sub-second db_ms and the metrics endpoint answers with real counters.

No undocumented steps

Everything above is executable against the repository as it ships. If a step here fails on your host, that is either an environment difference worth recording or a defect worth reporting — do not work around it with undocumented commands.

STILL READING

Something here still feels worth checking together.

This documentation describes the product exactly as it is implemented. If a behavior you expected is not here — or is here and does not match your deployment — tell the team. Implementation questions start on the contact page.