Deploy Pneumatic

Deploy and Host Pneumatic on Railway

Pneumatic is an open-source workflow management system that empowers teams to create, run, and optimize business processes collaboratively. It features reusable workflow templates, parallel multi-workflow execution, individual task buckets for staff, and automated stage tracking with real-time handoffs between teams.

About Hosting Pneumatic

Deploying Pneumatic involves running a multi-service architecture composed of a Django/Gunicorn backend (with ASGI via Uvicorn), a Next.js frontend served through PM2, Celery workers and Celery Beat for async task processing and scheduled jobs. The stack requires PostgreSQL for data persistence, Redis for caching, sessions, and WebSocket channels, and RabbitMQ as the Celery message broker. Railway simplifies this by managing each service as a separate component with shared networking and environment variables, eliminating the need to manually configure Docker Compose, SSL, and inter-service communication.

Common Use Cases

• Business Process Automation: Design reusable workflow templates for recurring processes like employee onboarding, customer support escalation, or content approval pipelines.
• Cross-Team Task Coordination: Assign multi-step workflows that automatically hand off tasks between departments, with real-time tracking of each stage's progress.
• SaaS Integration Hub: Connect Pneumatic to external tools via its public REST API or Zapier integration, automating data flow between CRM, HR, and project management systems.

Dependencies for Pneumatic Hosting

• PostgreSQL 15 — primary relational database for all application data
• Redis 6.2 — used for auth tokens, caching, Django Channels (WebSockets), and session storage
• RabbitMQ 3.13 — message broker for Celery async task queue

Deployment Dependencies

• Pneumatic GitHub Repository
• Pneumatic Configuration Wiki
• Pneumatic Support Center

Optional integrations

All integrations are disabled by default. Flipping a flag to yes is not enough on its own — each integration needs its provider credentials, and those variables are not part of this template. Add them to the Backend, celery-worker and celery-beat services (all three read the same settings), and to Frontend where noted.

# --- Access ---
SIGNUP=yes            # Public self-registration. Set to "no" for an invite-only instance
VERIFICATION_CHECK=no # Require email confirmation. Needs EMAIL=yes, otherwise nobody can finish signup

# --- Email (invitations, password reset, notifications, digests) ---
EMAIL=no              # With "no" the app sends no mail at all
EMAIL_PROVIDER=smtp   # smtp | customerio

# --- Authentication ---
GOOGLE_AUTH=no        # Google OAuth
MS_AUTH=no            # Microsoft Entra ID (Azure AD)
SSO_AUTH=no           # SSO
SSO_PROVIDER=okta     # okta | auth0

# --- Features ---
AI=no                 # AI-assisted template generation
AI_PROVIDER=openai
PUSH=no               # Web push notifications
PUSH_PROVIDER=firebase
CAPTCHA=no            # reCAPTCHA on public forms
ANALYTICS=no          # Segment analytics
BILLING=no            # Stripe subscriptions

# --- Error tracking ---
SENTRY_DSN=           # Backend
SENTRY_FRONTEND_DSN=  # Frontend

Why Deploy Pneumatic on Railway?

Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.