quinzee.cloud

Development edition · 16 November 2026. Commands using repository paths, Make targets or sample projects require access to the Quinzee source checkout. No public installer is available. Examples use disposable local environments.

Contributor’s guide

1. Architecture and trust boundaries

Quinzee separates HTTP transport, service semantics, privileged native-engine operation and application clients. The components communicate through explicit APIs or validated mailboxes, rather than sharing service implementation objects.

QHQ / SDK client -- HTTPS --> listener -- worker queue --> module host
                                                        |-- directory / ARM
                                                        |-- in-process services
                                                        |-- private durable state
                                                        |-- engine/hosting mailboxes
AMQP client -- TLS --> Service Bus worker ------------------ SQLite broker
LDAP client -- LDAPS --> slapd -- Unix socket --> shared directory
                                                 |-- dedicated PostgreSQL

operator-run helpers -- Docker --> SQL/cache and Functions/web containers
cloud gateway -- verified upstream HTTPS --> hosted application
native SQL/cache client -- verified TLS --> engine container
DNS module -- zone files --> CoreDNS --> client name resolution
telemetry exporter -- HTTPS OTLP --> optional collector/tools

include/http/ exposes project-owned transport types. include/quinzee/ exposes module hosting, authentication/resource capabilities, persistence, engine-runtime and telemetry contracts. Azure-specific behavior belongs in the modules under src/quinzee_cloud/modules/, not the transport library. QHQ links client code and Simple, not emulator service implementations.

Each HTTP listener owns an I/O thread. The cloud uses a bounded worker executor for service work and posts completions back to the connection's executor. The Service Bus AMQP worker serializes protocol events; a store mutex coordinates it with HTTP callers. Functions gateway exchanges use verified upstream HTTPS with bounded bodies and deadlines. Deployment processing and the native engine supervisor are additional, explicit background-work boundaries. Provider state has its own synchronization; there is no single global JSON database or universal request lock.

The cloud container never receives a Docker socket. The separately operated supervisor translates validated desired state into a fixed set of pinned engine operations. Public CA certificates go to clients; signing keys remain with their owner. Platform diagnostics exclude sensitive request content, while application telemetry submitted to a workspace remains application-controlled data.

See actual architecture (source checkout required), module contracts (source checkout required), provisioning (source checkout required) and observability (source checkout required).