Small runtime surface
Cotton runs as one ASP.NET Core application with managed preview and passkey libraries. Postgres stores metadata; the chunk store can live on filesystem or S3-compatible storage. The application image no longer needs F3D, Xvfb or Mesa/OpenGL for model previews, or native libheif, PDFium and Skia libraries for static previews.
Explicit external tools
FFmpeg and ffprobe handle audio/video processing. PostgreSQL's pg_dump and pg_restore handle database backup and recovery. These tools are included in the application image; they are not extra services to deploy. The .NET runtime, OS libraries and container startup helper remain part of the base environment, so managed application libraries do not mean a dependency-free operating system.
Compose without ceremony
The basic Compose shape is intentionally direct: Postgres, Cotton, a bind mount for /app/files, database connection variables, and no manual Docker network or connection-string ceremony.
Key mode is a deployment choice
New exposed instances can leave COTTON_MASTER_KEY out and unlock in the browser. Trusted home deployments can uncomment the master key line for unattended restarts when that tradeoff is acceptable.
Setup wizard
First-run setup covers admin creation, storage choice, email mode, timezone, and telemetry preference. Basic setup lives in the product instead of hidden environment folklore.
Email modes
Cotton can use Cloud Cotton Mail, custom SMTP, or disabled email. That keeps simple home deployments and public instances from needing the same mail setup.
Storage backends
Filesystem storage uses atomic temp-file moves and capacity reporting. S3-compatible storage can use existence-checked writes behind the same logical chunk model.
Production paths
The same small start can grow into real operation: local testing, home server behind a reverse proxy, public instance with security checkup and admin 2FA, or S3-backed storage when local filesystem capacity is not the right boundary.
Quotas and pressure guard
User quotas and storage pressure checks help public/demo instances avoid uncontrolled growth and prevent filesystem-backed storage from filling the host disk to zero.
Security diagnostics
After deployment, the admin security checkup points at concrete risks such as public account creation, missing 2FA, writable rootfs, seccomp, ptrace, and Docker socket exposure.
Operational surface area
The deployment story is backed by a single application image, PostgreSQL metadata, filesystem or S3-compatible chunk storage, first-run setup, email-mode selection, quota policy, storage pressure checks, and admin security diagnostics.
Small start, real operations
Cotton is easy to start without pretending production operations are fake. The deployment story is compact enough for a home server, but still exposes the knobs that matter when the instance is public.
What Docker does not solve
Docker and Postgres are only the application shape. Public deployments still need TLS, tested backups, key custody, updates, storage monitoring, and host/container hardening that matches the real threat model.