Curated deployment references plus the generated diagrams that explain the runtime reality.
Use the tabs for the three deployment models, then drop into the individual notes for the full operating guidance and generated flow sections.
Reference deployment models
Same platform, different operational trade-offs. Pick your favourite controlled amount of chaos.
Single-server Coolify
Best when one host can still comfortably own the proxy, services, jobs, and database without becoming a space heater with feelings.
- One public ingress and one operational box to reason about.
- Fastest path to production when the platform still fits on a single machine.
- Simplest rollout and rollback model when you want fewer moving pieces.
Generated runtime views
These cards link straight to the generated assets while keeping the related written notes one click away.
Service Topology
The runtime map of frontends, APIs, backing services, ports, and persistent volumes across the monorepo.
Communication Map
HTTP and WebSocket relationships between frontends, Better Auth, APIs, and the supporting services.
Auth Flow
Source-driven Better Auth modules, middleware, and the end-to-end auth request path generated from the auth app.
Forms-Service Auth Flow
Shows how a Better Auth JWT moves from the browser into records-service middleware and then into SurrealDB authenticate(token).
Deployment Order
The rollout sequencing view that helps explain how migrations, runtimes, and frontends come up without stepping on each other.
Hosted Deployment Flow
A flow-first view of Forgejo, Coolify, the build server, the registry, and the runtime host working in sequence.
Multi-node Deployment Flow
Build-once-deploy-everywhere flow with load balancer round-robin and per-server Traefik routing.
Mermaid source explorer
12 generated diagram sources. View the raw .mmd, rendered SVG, or choose one to preview it here.