Storage and Scaling

Clouisle's persistent data lives across PostgreSQL, Qdrant, Redis, and upload storage. Backups cannot save only the database.

Storage Backends

Site settings support local filesystem and object storage. Local mode fits a single API replica; when the API scales to multiple replicas, a ReadWriteMany shared volume is required. Object storage fits multi-replica and cross-node deployments, but you must configure the endpoint, bucket, region, access key, Secret Key, security, and path style.

Compose Volumes

• postgres_data: business, audit, configuration, and metadata.
• qdrant_data: vector collections.
• redis_data: Redis persisted data and task/session state.
• uploads_data: user uploads and sandbox artifacts.

Scaling Rules

Worker and Sandbox Worker can scale independently. beat must run exactly one replica. Multiple API replicas require shared upload storage or object storage; scale Qdrant and PostgreSQL according to their own high-availability schemes. Before scaling, confirm connection pool, queue concurrency, provider rate limits, and disk I/O.

Capacity Checks

Monitor the PostgreSQL database, pg_search indexes, Qdrant collections, Redis memory, and the upload directory. Document count growth increases capacity for raw files, chunks, Token statistics, vectors, and full-text indexes simultaneously.