Skip to content
Docs home

SELF-HOSTING · UPDATED AUGUST 2026

Self-Hosting Architecture

A dedicated host, an OpenResty edge as the only public process, and every other service on private networks or loopback.

The production profile

QUE's production deployment is a Docker Compose stack on a dedicated Ubuntu host. The defining rule of the architecture is exposure: the OpenResty edge container is the only process with public ports (80 and 443). The application, Redis, database, Grafana, Prometheus, and Sentry never publish their own public ports.

ServiceNetwork exposureEntry point
OpenResty + lua-resty-acmePublic 80/443 onlyDirect internet ingress and tenant custom-domain TLS
QUE applicationPrivate Docker networkedge → app:3000
RedisPrivate Docker networkApplication and OpenResty ACME storage only
Supabase (Postgres)Loopback or private networkApp server functions and authenticated edge routes only
Grafana / Prometheus / SentryLoopback or private networkIdentity-protected OpenResty routes only

Network boundaries

Services communicate over the private Docker network (que-private-services) or via loopback on the host. Monitoring routes are reached only through authenticated OpenResty locations. Do not run two public reverse proxies on 80/443 simultaneously — the edge is the single public entry point by design, not convenience.

Self-hosting is responsibility, not absence

A self-hosted deployment is a system of responsibilities: where the application runs, where the database is stored, how backups are created and restored, how secrets are rotated, how alerts arrive. It is not the absence of operations — it is the transfer of all operations to you.

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.