---
title: "Deploy Evolution API Messaging Starter"
description: "Messaging integration API with Postgres, private Redis and generated auth."
category: "Bots"
url: https://railway.com/deploy/evolution-api-messaging-starter
---

# Deploy Evolution API Messaging Starter

Messaging integration API with Postgres, private Redis and generated auth.

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

Machine-readable deploy manifest (JSON, validated by TemplateCI): https://railway.com/deploy/evolution-api-messaging-starter/manifest.json

- **Creator:** dankeewithtwoes's Projects
- **Category:** Bots

## Template content

### Redis https://cdn.sanity.io/images/sy1jschh/production/0ce0bfdcfbdbf69662b1116671f97c2dd788b655-157x157.svg

- **Image:** redis@sha256:47670742d7924adbcdb404d1288b6327815b23141969c0939b8e5d61f78c2634
- **Start command:** `/bin/sh -c 'exec docker-entrypoint.sh redis-server --requirepass "$REDIS_PASSWORD" --appendonly yes --save 60 1 --maxmemory-policy noeviction --bind 0.0.0.0 :: --dir /data'`

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

- **Image:** ghcr.io/railwayapp-templates/postgres-ssl@sha256:87184beace8ec657a760401a466a13c5b689066b31b77993103b4771933a9d31

### Evolution API https://evolutionfoundation.com.br/favicon.png

- **Image:** evoapicloud/evolution-api@sha256:966625532d9076a2381e973a271307d107e6f070450de3abeeea8bd18be07252
- **Public domain:** Yes

## Documentation

# Deploy and Host Evolution API Messaging Starter on Railway

Messaging integration API with Postgres, private Redis and generated auth.

## About Hosting Evolution API Messaging Starter

This deployment fork provisions Evolution API, Redis, Postgres. Application domains and any authored TCP endpoints are generated for each new deployment. Database and queue services are private by default.

## Why Deploy Evolution API Messaging Starter on Railway

- New setup and maintenance documentation with attribution to the original template.
- Public container sources are locked by image digest and public Git repositories by commit SHA.
- Database and queue services use private networking; external database access is an explicit deployer choice.

## Common Use Cases

- Connect a permitted messaging account to business workflows.
- Integrate messaging events with an application.
- Store instance state and integration data persistently.

## Dependencies for Evolution API Messaging Starter

- A Railway account with capacity for 3 service definitions and the authored storage.
- Your own external accounts and credentials when an integration or model provider is needed. No paid provider subscription is included.
- Local passwords and service secrets are generated or referenced at deployment; external integrations are configured by the deployer.

## First Launch

Wait for the app, Postgres and Redis. Open the generated API domain, read AUTHENTICATION_API_KEY from service variables, and create/pair your own messaging instance using the upstream instructions.

## Included Services and Storage

| Service | Persistent paths |
| --- | --- |
| Evolution API | No attached volume |
| Redis | `/data` |
| Postgres | `/var/lib/postgresql/data` |

## Operations

No messaging account or third-party credentials are included. Back up the database and instance volume. Use your own authorized account and configure webhooks and application access controls for your deployment.

Railway bills the deployer for actual services, storage and network use. Back up persistent data before source/version changes. This publication was checked against Railway's configuration schema and upstream source/registry availability; a full runtime deployment test has not been performed.

## Attribution and Source

Based on [Evolution API](https://railway.com/template/evolution-api-4) by RBR Digital. It appeared at position 9 in Railway's backend Popular/browse results captured on 2026-10-18, with 5,375 deployments reported for the original. That count belongs to the original, not this new fork.

The original software and repositories remain owned by their upstream authors and retain their licenses. This is a deployment configuration fork with new documentation, not a claim of software authorship or official vendor affiliation.

For template wiring issues, use this template's discussion link and share redacted logs. Never post passwords, API keys or login tokens.


## Deploy this recipe

[![Deploy on Railway](https://railway.com/button.svg)](https://railway.com/new/template/evolution-api-messaging-starter?utm_source=railway-marketplace&utm_medium=listing&utm_campaign=toolkit-discovery&utm_content=evolution-messaging-api-starter)

Review the required inputs and hosting resource costs before deploying.

### Related deployment recipes

- [Uptime Kuma with Persistent Storage](https://railway.com/template/uptime-kuma-with-persistent-storage) — Uptime checks, alerts and status pages with persistent monitor data.
- [ntfy Private Notifications with Persistent Data](https://railway.com/template/ntfy-private-notifications-with-persiste) — Private push notifications with generated admin and persistent storage.

These are separate deployments; no preconfigured integration between the applications is implied.

Disclosure: this template is maintained independently. Its maintainer may earn Railway usage kickbacks when other people deploy it. Railway bills hosting separately; no paid software subscription or provider credits are included.



## Similar templates

- [Swarm](https://railway.com/deploy/swarm) — Named LLM bots join channels, take jobs, run routines on your Railway box
- [Telegram JavaScript Bot](https://railway.com/deploy/5lRkWa) — A template for Telegram bot in JavaScript using grammY
- [Cobalt Tools [Updated Oct ’26]](https://railway.com/deploy/cobalt) — Cobalt Tools [Oct ’26] (Media Downloader, Converter & Automation) Self Host

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