Docker and Compose Sites
Run Docker/Compose Sites, curated applications and Custom Image workloads.
Docker and Docker Compose Sites keep container workloads inside the normal Control Site lifecycle. Control manages ingress, TLS, Site Data, health, logs, resource attribution and lifecycle actions without becoming a general host-Docker console.
Curated applications, Custom Image and My Recipes
Use Applications for curated workloads such as n8n, PocketBase, Ghost, Uptime Kuma, Forgejo, Mealie, Paperless-ngx, Nextcloud and Immich. Use Custom Image for an OCI web application that does not need application-specific lifecycle support. Reusable Custom Image and Compose definitions can be kept in My Recipes.
Web and background workloads
A Web workload receives Site traffic through Control-managed ingress. A Background workload has no public application port. Deferred start is available for workloads that need environment values before first start.
Persistent Site Data
Put state that must survive container recreation in declared Site Data volumes. Files inside those volumes belong to the Site/application; Control manages the mount boundary without rewriting application data.
Multi-service recipes can use private database/cache companions. Those services are shown as application-owned Site Data Attachments rather than independent databases that can be casually detached.
Compose
A Compose Site can have one ingress service and additional application, database or worker services. Control shows service state, resource use, logs and persistent data attachments.
Where Compose Resource Coverage is available, you can keep the existing ingress-only resource limit or apply the selected CPU/memory budget across the managed Compose stack. Choose a profile large enough for all services in the application.
Host port publication, arbitrary host filesystem mounts, Docker socket mounts, privileged containers and host namespace modes are outside the supported Site boundary.
Updates and recovery
Curated applications preserve their declared persistent state during supported reinstall/update operations. For stateful applications, use application-aware backups or exports in addition to Site recovery where the application requires them.