Connect was not built as an isolated chat app. Its domains allow communication to connect with security events later without rebuilding the core.
Production Compose, multi-stage images, health endpoints and migration job.
A single host is not high availability or multi-region operation.
Release script, claim verification, schema-to-migration alignment, browser walkthroughs and a server-side rehearsal of pending migrations in a disposable clone of the running data.
An internal release gate is not a penetration test or operating certification. The migration rehearsal does not modify the running data; an actual recovery exercise from the encrypted backup remains a separate operational proof.
Container and module boundaries allow isolated target environments.
Network, secrets, backups, monitoring, recovery, patching and acceptance must be defined per environment.
Authentication, users, collaboration, messages, storage, realtime, notifications and keys are separated into modules. The monolith remains operable without becoming inseparable.
PostgreSQL is the durable source, Redis distributes transient events and Socket.IO synchronises clients. After reconnect, persisted state wins.
Files live in private S3-compatible object storage. The browser encrypts before upload and access uses short-lived signed URLs.
Events, alerts, cameras, sensors, control centre, monitoring and AI expose prepared ports and capability endpoints. Without a provider they report disabled or contract-ready.
Place operational events into rooms later.
Route priority signals to roles and teams.
Attach camera context as a controlled source.
Reference sensor state and events.
Prepare summaries and translation without vendor lock-in.
Accept service status through explicit adapters.
“A good platform does not promise every integration — it makes every future integration controllable.”
VENTEX architecture principle
The ports exist; real providers activate only behind explicit security contracts.
