Deploy Whatomate
Self-hosted WhatsApp Business API inbox, chatbots and campaigns
Just deployed
/var/lib/postgresql/data
Redis
Just deployed
/data
Whatomate
Just deployed
/app/data
Deploy and Host Whatomate on Railway
Whatomate is an open-source, self-hosted platform for the WhatsApp Business Cloud API, written in Go with a Vue web app. It gives your team a shared WhatsApp inbox, keyword and AI chatbots, broadcast campaigns, message templates, WhatsApp Flows, contacts, webhooks and an API, all on your own server.
About Hosting Whatomate
Whatomate is a single Go binary that serves both the web app and the API, plus background workers for campaigns. It needs PostgreSQL for its data and Redis for the job queue, caches and rate limits. This template runs Whatomate 0.1.1-beta-0.17 from the official image, pinned by digest, with Railway Postgres and Redis on the private network. Media uploads and IVR audio go on a volume. Production mode is on, with a generated JWT secret, encryption key, admin password and webhook verify token. Migrations run on every start. Updates arrive as Railway update notices from our GitHub repo.
Common Use Cases
- Shared WhatsApp inbox for support or sales teams, with assignment, canned responses and SLAs
- Chatbots that answer by keyword, flow or AI (OpenAI, Anthropic or Google)
- Broadcast campaigns with approved WhatsApp message templates
Dependencies for Whatomate Hosting
- PostgreSQL (Railway Postgres, included)
- Redis (Railway Redis, included)
- A Meta WhatsApp Business account with Cloud API access (phone number ID, business account ID and access token)
Deployment Dependencies
- Whatomate source and releases: https://github.com/shridarpatil/whatomate
- Configuration reference: https://github.com/shridarpatil/whatomate/blob/main/docs/src/content/docs/getting-started/configuration.mdx
- Template repo: https://github.com/aalfath/whatomate-railway-template
- WhatsApp Cloud API setup: https://developers.facebook.com/docs/whatsapp/cloud-api/get-started
Implementation Details
There's nothing to fill in at deploy. After it's up:
- Open the public URL and sign in as
admin@admin.comwith the password in the Whatomate service'sWHATOMATE_DEFAULT_ADMIN__PASSWORDvariable. Then change the email and password in your profile. - Add your WhatsApp number under Settings → Accounts. Include the app secret, so incoming webhooks are verified.
- In your Meta app, set the webhook URL to
https://YOUR-DOMAIN/api/webhook, use theWHATOMATE_WHATSAPP__WEBHOOK_VERIFY_TOKENvalue as the verify token, and subscribe tomessages. - Optional: add an AI provider key under Settings → Chatbot → AI. If you add a custom domain, append it to
WHATOMATE_SERVER__ALLOWED_ORIGINS.
Never change WHATOMATE_APP__ENCRYPTION_KEY after adding accounts: it decrypts the stored access tokens. Any other setting can be overridden with variables named WHATOMATE_SECTION__KEY (for example WHATOMATE_RATE_LIMIT__ENABLED). Not set up: Meta Embedded Signup, call recording (needs AWS S3), and voice calling (needs UDP ports and a TURN server). Updates: when we bump the version, Railway shows an update notice; read the repo's CHANGELOG.md first.
Why Deploy Whatomate 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 Whatomate 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.
Template Content
Redis
redis:8.2Whatomate
aalfath/whatomate-railway-template