For the IT manager and architect#

What you will run#

Five application containers (core API, asset processor, gateway, admin dashboard, editor), PostgreSQL 16 and an S3-compatible store; nginx is the only public listener. One installation is one workspace for one organisation; you may run many on a host.

Your questions#

Question	Answer and where
What are the parts and how do they talk?	Architecture overview
Why this shape?	Design decisions, especially a simple stack
Where is data stored, how does the schema evolve?	Data and storage
How do people sign in, what can they do?	Authentication and authorization: local accounts, optional TOTP, roles and permissions per route; no single sign-on for staff
How do our applications use it?	API clients: server keys or tokens of your identity provider (Keycloak, Entra ID...), scopes, limits
How do we connect our ERP, CRM, mail?	Integrations; credentials stay on the server
How does it scale, and how available is it?	Capacity and scaling: vertical first, one instance per service, restore from backup is the recovery path
What do I have to add around it?	Monitoring, SSO if needed, backup of the bucket, retention jobs: overview 7.2
What are the data model and its limits?	Data model
Which licences and dependencies?	Supply chain (SBOM)

Before production#

Rehearse a restore on a spare host; test an upgrade; run your own load test; run a TLS check on your real hostname; decide log and data retention; decide how people will sign in given there is no SSO.

Reading path#

What Whoobe is, architecture overview, design decisions, authentication, capacity, then the operators' page.