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.
| Service | Network exposure | Entry point |
|---|---|---|
| OpenResty + lua-resty-acme | Public 80/443 only | Direct internet ingress and tenant custom-domain TLS |
| QUE application | Private Docker network | edge → app:3000 |
| Redis | Private Docker network | Application and OpenResty ACME storage only |
| Supabase (Postgres) | Loopback or private network | App server functions and authenticated edge routes only |
| Grafana / Prometheus / Sentry | Loopback or private network | Identity-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.