Query the operational database directlyA swarm of independent applications and agents connects directly to ClickHouse Managed Postgres using ORMs, database drivers, or SQL tools. Separate arrows lead to the Postgres primary, read replica 1, and read replica 2. Each database instance has local NVMe storage. The read replicas are optional. There is no shared application container or mandatory ORM layer. CLICKHOUSE MANAGED POSTGRES Application 1ORM Application 2Database driver Agent 1SQL tools Agent 2ORM Agent 3SQL tools Agent 4Database driver Postgres primaryReads + writesLOCAL NVMe STORAGE OPTIONAL READ REPLICAS Read replica 1LOCAL NVMe STORAGE Read replica 2LOCAL NVMe STORAGE One authoritative write path, without a synchronized dataset for every agent.

A swarm of independent applications and agents connects directly to ClickHouse Managed Postgres using ORMs, database drivers, or SQL tools. Separate arrows lead to the Postgres primary, read replica 1, and read replica 2. Each database instance has local NVMe storage. The read replicas are optional. There is no shared application container or mandatory ORM layer. Animation timing is illustrative, not a latency measurement. Flows animate continuously and simultaneously along all connections.