Deploy chatbot-whatsapp

Deploy and Host WhatsApp Gateway + Evolution API on Railway

One-click production stack: Evolution API (WhatsApp), Postgres, Redis, MySQL, and a ProfesIA-branded gateway UI with multi-LLM bots (Gemini, OpenAI, Claude, Groq).

About Hosting WhatsApp Gateway + Evolution API

This template provisions a full WhatsApp operations stack on Railway: Evolution API for WhatsApp sessions, a gateway UI for QR linking / chats / bots, plus Postgres, Redis, MySQL, and a persistent volume for device sessions.

Why Deploy WhatsApp Gateway + Evolution API

• Ship a production WhatsApp bot without managing Baileys servers yourself.
• Keep sessions across redeploys with a mounted volume.
• Run multi-LLM bots (Gemini, OpenAI, Claude, Groq) behind one gateway UI.
• Use private networking between gateway and Evolution, with reliable public webhooks for inbound messages.

Common Use Cases

• Customer support bots on WhatsApp
• Internal ops / notifications for teams
• Multi-instance WhatsApp linking with QR and reconnect flows
• Experimenting with Groq / Gemini / GPT / Claude replies on live chats

Dependencies for WhatsApp Gateway + Evolution API

Deployment Dependencies

After deploy

1. Open the whatsapp-gateway public URL.
2. Log in with DEFAULT_ADMIN_USER / DEFAULT_ADMIN_PASSWORD from the gateway Variables tab (password is auto-generated).
3. Optional: set GEMINI_API_KEY, GROQ_API_KEY, OPENAI_API_KEY, or ANTHROPIC_API_KEY — or add models in the UI (Modelos).
   • If GROQ_API_KEY is set, the first migrate seeds working Groq chat models (openai/gpt-oss-20b, openai/gpt-oss-120b, qwen/qwen3.6-27b, qwen/qwen3.8-27b).
4. Create an instance → scan QR (auto-generated when disconnected) → enable the bot → pick a model.

Architecture

Browser → WhatsApp Gateway → Evolution API → WhatsApp
                ↑                  │
           public webhook     Postgres + Redis
                │
              MySQL

Gateway ↔ Evolution API uses Railway private networking. Evolution webhooks call the gateway public URL so message events are reliable.

Security

• AUTHENTICATION_API_KEY is generated with ${{secret(64)}} and shared automatically.
• Default admin password is generated with ${{secret(20)}} — change it after first login if you prefer.
• Never commit real API keys to git.

Source

GitHub: ProfesIA-IA/chatbot-whatsapp
IaC: .railway/railway.ts