---
title: "Deploy Evolution API"
description: "Deploy and Host Evolution API with Railway"
category: "Other"
url: https://railway.com/deploy/evolution-api-2
---

# Deploy Evolution API

Deploy and Host Evolution API with Railway

**[Deploy Evolution API on Railway](https://railway.com/template/evolution-api-2)**

- **Creator:** Automatiza A.I.
- **Category:** Other
- **Total deploys:** 707

## Template content

### Postgres https://devicons.railway.app/i/postgresql.svg

- **Image:** ghcr.io/railwayapp-templates/postgres-ssl

### Redis https://devicons.railway.app/i/redis.svg

- **Image:** bitnami/redis

### Evolution API https://meta-q.cdn.bubble.io/f1735656025985x589899456761148800/evolution-logo.png

- **Image:** evoapicloud/evolution-api:v2.3.0
- **Public domain:** Yes

## Documentation

# Deploy and Host Evolution API on Railway

**Evolution API** is a Node.js REST interface that brings WhatsApp Web multi-device features to your stack. It handles session management, QR authentication, message send/receive (text, media, groups), and webhooks. Ideal for powering support agents, notifications, and AI assistants that need reliable WhatsApp connectivity with minimal setup.

## About Hosting Evolution API

Hosting Evolution API on Railway is straightforward. Use the template to provision a service, set environment variables for access control and webhooks, and attach a persistent Volume for WhatsApp sessions. You can optionally connect a database or cache for queues, metrics, or rate control. Enable a custom domain with HTTPS, add a healthcheck for safe deploys, and monitor logs directly in the dashboard. For production, allocate sufficient RAM/CPU and keep sessions on a mounted Volume to avoid re-pairing. Once deployed, authenticate by scanning the QR code from your session endpoint and start wiring events to your automation platform or CRM.

## Common Use Cases

* Connect WhatsApp to chatbots, CRMs, and automation workflows for support, alerts, and follow-ups.
* AI assistant for triage and FAQs, sending media and collecting documents from users.
* Transactional notifications, reminders, and broadcast to opted-in audiences with delivery tracking.

## Dependencies for Evolution API Hosting

* Node.js 18+ runtime or a production-ready Docker image.
* A persistent Volume on Railway for session storage; optional PostgreSQL/Redis for queues, cache, or metrics.

### Deployment Dependencies

* Railway Volumes: [https://docs.railway.app/develop/volumes](https://docs.railway.app/develop/volumes)
* Environment Variables: [https://docs.railway.app/develop/variables](https://docs.railway.app/develop/variables)
* Domains & HTTPS: [https://docs.railway.app/deploy/domains](https://docs.railway.app/deploy/domains)
* Healthchecks: [https://docs.railway.app/guides/healthchecks](https://docs.railway.app/guides/healthchecks)

## Why Deploy Evolution API 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.

By deploying Evolution API on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.




## Similar templates

- [Rocky Linux](https://railway.com/deploy/rocky-linux) — Hosted Rocky Linux 9 workspace with SSH and persistent storage. 🚀
- [Foundry Virtual Tabletop](https://railway.com/deploy/X5tR6G) — A Self-Hosted & Modern Roleplaying Platform
- [Letta Code Remote](https://railway.com/deploy/letta-code-remote) — Run a Letta Code agent 24/7. No inbound ports, just deploy.

Open this page in a browser: https://railway.com/deploy/evolution-api-2