20 min
Lesson 3 of 4
Production Deployment & Self-Hosting
From the course n8n AI Workflow Builder
Moving n8n AI workflows to production requires careful planning around reliability, security, and scaling.
Self-Hosting Best Practices
Docker Compose Setup
For production, use Docker Compose with a persistent database:
services:
n8n:
image: n8nio/n8n
ports:
- "5678:5678"
environment:
- DB_TYPE=postgresdb
- DB_POSTGRESDB_HOST=postgres
- N8N_ENCRYPTION_KEY=your-secret-key
volumes:
- n8n_data:/home/node/.n8n
postgres:
image: postgres:15
volumes:
- postgres_data:/var/lib/postgresql/data
Security Considerations
- Always set a strong
N8N_ENCRYPTION_KEY— it encrypts your credentials - Use environment variables for API keys, never hardcode them
- Enable authentication with
N8N_BASIC_AUTH_ACTIVE=true - Place n8n behind a reverse proxy (Nginx/Caddy) with SSL
- Restrict webhook URLs to known IP ranges when possible
Scaling AI Workflows
Queue Mode
For high-volume workflows, enable queue mode with Redis:
- Main process handles webhook triggers
- Worker processes execute the workflows
- Scale workers independently based on load
Cost Management
- Cache AI responses for repeated queries
- Use cheaper models for classification, premium models for generation
- Set rate limits on webhook-triggered workflows
- Monitor API usage with n8n's execution logs
Monitoring
- Use n8n's built-in execution history
- Set up alerts for failed executions
- Export metrics to Prometheus/Grafana
- Log AI token usage for cost tracking
Key Takeaways
- •Use Docker Compose with PostgreSQL for production self-hosting
- •Always encrypt credentials and use environment variables for API keys
- •Queue mode with Redis enables horizontal scaling of AI workflows
- •Cache AI responses and use tiered models to manage costs
0 of 4 lessons marked complete
Progress is kept in this browser only.