Deploy Clouisle
Deploy and operate Clouisle with Docker Compose, Kubernetes, or Sealos
The official Docker Compose and Kubernetes deployments consist of the frontend, a FastAPI API, Celery Worker, Sandbox Worker, Beat, and PostgreSQL, Redis, and Qdrant. For a single server, prefer the guided installer and Docker Compose; for production clusters, prefer Helm; the community-maintained Sealos template is another option.
Architecture
Understand application services, infrastructure dependencies, request routing, and data volumes.
Deploy
Choose the guided installer, Docker Compose, Helm, a Kubernetes manifest, or the community-maintained Sealos template.
Configuration
View environment variables, secrets, ports, internal addresses, and retrieval switches.
Operations
Handle storage, backup, upgrades, monitoring, and troubleshooting.
Deployment FAQ
Quickly locate common issues with services, databases, Workers, and the sandbox.
Support matrix
| Scenario | Recommended approach | Best for |
|---|---|---|
| Single-server trial or small-scale production | Docker Compose | One server, external reverse proxy |
| Scalable production cluster | Helm | Kubernetes, Ingress, shared storage |
| Sealos workspace | Sealos community-maintained template | PostgreSQL, Redis, Qdrant, and persistent upload storage; Sandbox Worker disabled by default |
| Controlled review deployment | Generated single-file manifest | Reviewing Secrets and resources before apply |
| Local development | Backend + frontend source code | Contributing code, debugging the product |
Production deployments using the official Compose, Helm, or single-file manifest must replace the example SECRET_KEY, database passwords, Redis/Qdrant credentials, and the internal Worker gateway Token. Do not expose the API service port directly to the public internet.
How is this guide?