Deploy with Docker
Parcelis ships published container images for the application. The simplest way to run the platform is to use Docker directly when you already have PostgreSQL, Redis, and S3-compatible storage services available.
Deploy with Docker Compose
Docker Compose is the recommended way to deploy Parcelis for a full production-style environment because it starts the application, PostgreSQL, Redis, and MinIO together and runs the migration and storage initialization steps automatically.
Deploy with the Single-Image Docker Build
Parcelis publishes an optional single application image, parcelis/parcelis, that bundles the web app, API, worker, and nginx edge routing into one application image. This is not a single-container deployment: PostgreSQL, Redis, and S3-compatible object storage (such as MinIO) remain separate services. The published parcelis/apps, parcelis/worker, and parcelis/proxy modular images continue to be published alongside it. This stack retains the bundled worker and runs its worker container from parcelis/parcelis; the dedicated parcelis/worker image is only required by the modular stack.
Upgrade PostgreSQL 16 to 18
Parcelis Compose deployments and local development now target PostgreSQL 18. This is a breaking deployment change. PostgreSQL 18 cannot open PostgreSQL 16 data files; Prisma migrations do not convert them.
Email Configuration
Parcelis sends transactional email through SMTP. The SMTP values in your deployment environment provide the default configuration. An organization owner or administrator can optionally save a separate SMTP configuration in Settings → Organization → Email; that configuration takes precedence for email sent for that organization.
Status monitor (POC)
Run the monitor as a separate process from the application:
API token rollout and rollback
Ship persistence, management, REST authentication, settings, and documentation as