Which operating models are realistic for VENTEX Connect?
The reproducibly documented current path is a hardened single-host deployment with containers, TLS gateway, PostgreSQL, Redis and private object storage. Managed EU and a dedicated VPS are realistic operating models; on-premises is a target model requiring additional hardening and acceptance.
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.
Which operating models are realistic for VENTEX Connect?
No. Connect requires persistent Node/container processes, PostgreSQL, Redis, private object storage and realtime connections.
No. More control also creates more responsibility for hardening, updates, backups, monitoring and recovery.
