---
title: "Deploy WAHA"
description: "Self-hosted WhatsApp HTTP API: GOWS engine, persistent sessions, dashboard"
category: "Bots"
url: https://railway.com/deploy/waha-1
---

# Deploy WAHA

Self-hosted WhatsApp HTTP API: GOWS engine, persistent sessions, dashboard

**[Deploy WAHA on Railway](https://railway.com/template/waha-1)**

Machine-readable deploy manifest (JSON, validated by TemplateCI): https://railway.com/deploy/waha-1/manifest.json

- **Creator:** Agaz Self-Host
- **Category:** Bots

## Template content

### WAHA https://raw.githubusercontent.com/devlikeapro/waha/2026.10.1/logo.png

- **Source:** https://github.com/aalfath/waha-railway-template
- **Health check:** /ping
- **Public domain:** Yes

## Documentation

# Deploy and Host WAHA on Railway

WAHA (WhatsApp HTTP API) is an open-source, self-hosted REST API for WhatsApp. You link a WhatsApp number by scanning a QR code, then send and receive messages, media and group events over HTTP and webhooks. It ships with a web dashboard and Swagger API docs, and runs from a single Docker image.

## About Hosting WAHA

This template runs WAHA Core 2026.10.1 with the GOWS engine, a Go client that runs without a browser. Railway builds it from a public GitHub repo that pins the official image by digest, so you get update notices when a new version is merged. WhatsApp logins and downloaded media are kept on a Railway volume at /app/data, and sessions reconnect on their own after a redeploy. The API key, dashboard password and Swagger password are generated for each deploy, so nothing is left on a default. You only need to scan the QR code once.

## Common Use Cases

* Send order updates, reminders and one-time codes to customers on WhatsApp from your own app
* Receive incoming WhatsApp messages as webhooks in n8n, Chatwoot, Make or your own backend
* Build WhatsApp chatbots and AI assistants without per-message fees

## Dependencies for WAHA Hosting

* One WhatsApp account (phone number) to link by QR code
* A Railway volume for sessions and media (included)

### Deployment Dependencies

* WAHA source and releases: https://github.com/devlikeapro/waha/releases
* WAHA documentation: https://waha.devlike.pro/docs/overview/introduction/
* Template repo (Dockerfile, changelog): https://github.com/aalfath/waha-railway-template

### Implementation Details

After the deploy finishes:

1. Open `https://YOUR-DOMAIN/dashboard` and sign in as `admin` with `WAHA_DASHBOARD_PASSWORD` from the service's Variables tab.
2. Add the server in the dashboard with the URL `https://YOUR-DOMAIN` and the `WAHA_API_KEY` value.
3. Start the `default` session and scan the QR code in WhatsApp under Linked devices. WAHA Core runs one session, named `default`.

Every API call needs the header `X-Api-Key: YOUR-API-KEY`. Swagger docs are at `https://YOUR-DOMAIN/` with the dashboard login. To receive messages, add `WHATSAPP_HOOK_URL` and `WHATSAPP_HOOK_EVENTS` (for example `message,session.status`) as service variables. WAHA is not affiliated with WhatsApp; follow WhatsApp's terms to avoid having the number banned.

## Why Deploy WAHA 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 WAHA 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

- [Telegram JavaScript Bot](https://railway.com/deploy/5lRkWa) — A template for Telegram bot in JavaScript using grammY
- [Cobalt Tools [Updated Nov ’26]](https://railway.com/deploy/cobalt) — Cobalt Tools [Nov ’26] (Media Downloader, Converter & Automation) Self Host
- [Telegram Gateway](https://railway.com/deploy/railway-telegram-gateway) — Multi-bot Telegram webhook gateway with WebSocket event streaming

Open this page in a browser: https://railway.com/deploy/waha-1
