--- title: "Deploy Evolution API | Open Source Messaging Automation Platform" description: "Self-host Evolution: Connect WhatsApp, Chatwoot, Typebot, Kafka & more." category: "Automation" url: https://railway.com/deploy/self-host-evolution-api --- # Deploy Evolution API | Open Source Messaging Automation Platform Self-host Evolution: Connect WhatsApp, Chatwoot, Typebot, Kafka & more. **[Deploy Evolution API | Open Source Messaging Automation Platform on Railway](https://railway.com/template/self-host-evolution-api)** - **Creator:** bond007's Projects - **Category:** Automation - **Total deploys:** 260 ## Template content ### Postgres https://devicons.railway.app/i/postgresql.svg - **Image:** ghcr.io/railwayapp-templates/postgres-ssl:18 ### Redis https://cdn.sanity.io/images/sy1jschh/production/0ce0bfdcfbdbf69662b1116671f97c2dd788b655-157x157.svg - **Image:** redis:8.2.1 - **Start command:** `/bin/sh -c "rm -rf $RAILWAY_VOLUME_MOUNT_PATH/lost+found/ && exec docker-entrypoint.sh redis-server --requirepass $REDIS_PASSWORD --save 60 1 --dir $RAILWAY_VOLUME_MOUNT_PATH"` ### Evolution API https://res.cloudinary.com/asset-cloudinary/image/upload/v1772629067/evolution_api_rgbwhh.png - **Image:** evoapicloud/evolution-api - **Public domain:** Yes ## Documentation # Deploy and Host DeployEvolution API | Open Source Messaging Automation Platform on Railway Deploy Evolution API on Railway in under 60 seconds using a one-click template. Spin up a production-ready messaging backend with WhatsApp support, PostgreSQL persistence, Redis caching, and automatic SSL—no Docker setup required. ## About Hosting DeployEvolution API | Open Source Messaging Automation Platform Evolution API is an open-source messaging automation platform that provides programmatic control over WhatsApp and other communication channels via a REST API. Built on top of libraries like Baileys and Whatsmeow, it enables developers to build scalable messaging workflows without relying entirely on Meta’s official Cloud API. While WhatsApp is the primary channel, Evolution API is designed to work as an integration layer—connecting with tools like Chatwoot, Typebot, and AI platforms to create multi-channel communication systems. --- ## Key Features * **Multi-instance management**: Manage multiple messaging accounts from a single deployment * **QR-based authentication**: Quickly connect accounts via browser-based QR scanning * **Webhook events**: Stream real-time messages and events into your systems * **Media support**: Handle images, videos, documents, and audio seamlessly * **Group automation**: Create and manage groups programmatically * **Message scheduling**: Queue and send messages at controlled intervals * **PostgreSQL storage**: Persist chats, contacts, and session data * **Redis caching**: Optimize performance for high-throughput messaging * **Integration-ready**: Easily connect with Chatwoot, Typebot, n8n, OpenAI, and more This template deploys Evolution API (`evoapicloud/evolution-api`) alongside PostgreSQL 17 and Redis 8, preconfigured with secure internal networking. --- ## Common Use Cases * **Customer support automation**: Use Chatwoot or Typebot to power AI-driven support workflows * **E-commerce messaging**: Send order updates, delivery notifications, and cart reminders * **Marketing automation**: Broadcast campaigns to segmented audiences with tracking * **Multi-channel orchestration**: Combine WhatsApp with tools like Chatwoot for unified inbox workflows * **SaaS integrations**: Embed messaging capabilities into your product for end users --- ## Evolution API vs Twilio WhatsApp API | Feature | Evolution API (Self-Hosted) | Twilio WhatsApp API | | ---------------- | --------------------------- | ----------------------- | | **Pricing** | Infrastructure cost only | Per-message pricing | | **Setup** | Instant deployment | Approval + integration | | **Limits** | Native WhatsApp limits | Twilio-imposed limits | | **Data control** | Full ownership | Hosted by Twilio | | **Flexibility** | Open-source, customizable | Restricted APIs | | **Verification** | Optional | Required for production | Evolution API is ideal for rapid prototyping, cost optimization, and custom workflows. Twilio is better suited for regulated environments requiring official Meta support. --- ## Dependencies for Evolution API Evolution API relies on: * **PostgreSQL** for persistent data storage * **Redis** for caching and session handling Both are provisioned automatically in this Railway deployment. --- ### Environment Variables Reference | Variable | Description | Required | Default | | ------------------------- | -------------------------- | -------- | -------------- | | `PORT` | Server port | Yes | `8080` | | `SERVER_URL` | Public URL for webhooks/QR | Yes | Railway domain | | `AUTHENTICATION_API_KEY` | Secure API access | Yes | Auto-generated | | `DATABASE_PROVIDER` | Database type | Yes | `postgresql` | | `DATABASE_CONNECTION_URI` | DB connection string | Yes | Railway DB | | `CACHE_REDIS_ENABLED` | Enable caching | Yes | `true` | | `CACHE_REDIS_URI` | Redis connection | Yes | Railway Redis | --- ### Deployment Dependencies * PostgreSQL 15+ * Redis 6+ * Minimum 512MB RAM per instance --- ## FAQ **Can I run multiple accounts?** Yes. Each instance represents a separate session, all backed by a shared database but isolated logically. **Does Evolution API support other platforms?** Recent versions extend beyond WhatsApp, with support for Instagram Direct and Facebook Messenger. Combined with tools like Chatwoot, it can act as part of a broader multi-channel messaging stack. **What happens on restart?** Sessions are persisted in PostgreSQL, so instances reconnect automatically unless expired. **Is it production-ready?** Yes—with proper monitoring, backups, and compliance awareness. High-volume workloads may require dedicated infrastructure. --- ## Integrations Evolution API is built to plug into modern automation and AI ecosystems: * **Chatwoot**: Unified inbox across multiple channels * **Typebot**: No-code chatbot builder * **n8n**: Workflow automation engine * **OpenAI / Dify**: AI-powered conversations and agents * **Kafka / RabbitMQ / SQS**: Event-driven messaging pipelines * **Zapier / Make**: Low-code automation workflows These integrations allow Evolution API to function as a backend messaging layer within a larger multi-channel architecture. --- ## Troubleshooting * **QR not loading**: Verify `SERVER_URL` matches your deployed domain * **DB errors**: Use internal Railway DB connection strings * **Frequent disconnects**: Avoid aggressive automation patterns * **Cache issues**: Confirm Redis connection settings --- ## Why Deploy Evolution API on Railway Railway simplifies infrastructure so you can focus on building messaging workflows: * Private networking between services * Automatic HTTPS with public domains * Managed PostgreSQL and Redis * Easy environment variable management * One-click deployment with zero ops overhead * Free tier for small-scale usage Compared to managing Docker on a VPS, Railway removes the need for manual setup, SSL handling, and database maintenance. ## Similar templates - [N8N Main + Worker](https://railway.com/deploy/n8n-main-worker) — Deploy and Host N8N with Inactive worker. - [Evolution API with n8n](https://railway.com/deploy/evolution-api-with-n8n) — [Jul'26] WhatsApp automation platform using Evolution API, n8n & PostgreSQL - [Postgres Backup](https://railway.com/deploy/postgres-s3-backups) — Cron-based PostgreSQL backup to bucket storage Open this page in a browser: https://railway.com/deploy/self-host-evolution-api