Deploy and Host Velix API on Railway

Velix API is a self-hosted WhatsApp REST API built in Go — connect multiple WhatsApp numbers, send and receive messages over a clean REST interface, get real-time webhooks, and wire it into automations with a native n8n node and built-in Chatwoot integration. Because it's a single compiled Go binary, it's light on resources and fast to start. This template deploys it with PostgreSQL pre-wired, so you have a working WhatsApp automation backend on your own infrastructure in minutes.

What This Template Deploys

Service	Purpose
Velix API	The Go WhatsApp gateway — REST API, multi-instance manager, and webhooks
PostgreSQL	Instance sessions, message data, and configuration

Both connect over Railway's private network; only Velix API is public. Because Velix is a single Go binary, the app service is light on memory compared to browser-based WhatsApp gateways.

About Hosting

Velix is a lean, automation-focused WhatsApp gateway, and a few things are worth understanding before you connect your first number.

It's a lightweight Go binary — low RAM, fast start. Velix compiles to a single binary, so it uses far less memory than browser-based WhatsApp APIs. That makes it inexpensive to run on Railway and well suited to hosting several instances without a heavy resource footprint.

Multi-instance from one deployment. Velix manages multiple WhatsApp numbers from a single service — each number is an instance you connect by scanning its QR code, then address independently through the REST API. One deployment can back several numbers for different projects or clients.

Native n8n node and Chatwoot integration. Velix ships a purpose-built n8n community node, so wiring WhatsApp into automation flows doesn't require hand-built HTTP calls — you drop the node in and connect. The built-in Chatwoot integration turns it into a live customer-support channel. This automation-first design is Velix's distinguishing feature. Incoming messages and status updates are pushed to a webhook URL you configure, so your app reacts in real time.

Set the connection and data variables — verify names against the repo. Velix uses PostgreSQL via a DATABASE_URL connection string (wired here), a public URL for webhooks and QR pairing, and an API key or token to secure the REST API. Because Velix is an early-stage project, confirm the exact environment-variable names against the current repository before publishing, as they may evolve between versions.

Understand the unofficial-API trade-off. Like Evolution API and Baileys, Velix connects through the WhatsApp Web protocol rather than Meta's official Cloud API. This is powerful and flexible, but WhatsApp can restrict numbers that send at high volume or cold-message strangers. Warm up new numbers, rate-limit sends, and avoid mass-messaging people who haven't contacted you. For regulated or large-scale commercial messaging, Meta's official Cloud API is the compliant choice.

Typical cost: ~$5–10/month on Railway for the app and PostgreSQL — low, thanks to the lightweight Go binary. Velix is open source and free.

How It Compares

	Velix API (self-hosted)	Evolution API	WhatsApp Cloud API	Twilio
Cost model	Flat infra	Flat infra	Per conversation	Per message
Engine	WhatsApp Web (Go)	WhatsApp Web + Cloud	Official Meta	Official
Footprint	Light (Go binary)	Heavier stack	N/A (managed)	N/A (managed)
n8n node	Native	Via HTTP/integration	Community	Community
Multi-number	Yes	Yes	Yes	Yes
Self-hostable	Yes	Yes	No	No

The official Cloud API and Twilio are compliant and reliable but bill per message and require Meta business approval. Evolution API is a mature, feature-rich self-hosted option with a larger integration set. Velix's niche is being a lightweight, Go-based, automation-first gateway — a small footprint and a native n8n node — for developers who want a lean self-hosted WhatsApp API wired straight into their workflows.

Deploy in Under 5 Minutes

Click Deploy on Railway — Velix API and PostgreSQL build and wire together (~3 minutes)
Confirm DATABASE_URL is wired and set your public URL and API key/token
Open the Velix API on your Railway domain
Create an instance and scan its QR code with the WhatsApp number you want to connect
Send your first message via the REST API, and point webhooks at your app or an n8n flow

Connect additional numbers by creating more instances from the same deployment.

Common Use Cases

WhatsApp automation with n8n — trigger and send WhatsApp messages inside automation flows via the native node
Customer support — connect WhatsApp to Chatwoot for a shared team inbox and live chat
Notifications and alerts — send order updates, reminders, and alerts programmatically over the REST API
Chatbots — receive messages via webhook, process them, and reply through the API

Configuration

Variable	Required	Description
`DATABASE_URL`	Auto-injected	PostgreSQL connection string via Railway reference variable
`PORT`	Pre-set	The port Velix API listens on
Public URL variable	Required	Your Railway public domain — for webhooks and QR pairing (confirm exact name in the repo)
API key / token	Recommended	Secures the REST API — set a strong value (confirm exact variable name)
Webhook URL	Optional	Destination for incoming-message and status events

Confirm variable names against the repo before publishing. Velix is an early-stage (v0.1.0) project, so exact environment-variable names for the public URL, API key, and webhooks may change between versions. Verify them against the current repository so the template matches the running image.

Respect WhatsApp's limits. Velix uses the WhatsApp Web protocol, so warm up new numbers, rate-limit sends, and don't cold-message strangers. For regulated or high-volume commercial messaging, use Meta's official Cloud API.

Dependencies for Velix API Hosting

Railway account — ~$5–10/month for the app and PostgreSQL
PostgreSQL (included and wired in this template)
A WhatsApp number to connect by scanning its QR code
Optional: n8n and/or Chatwoot for automation and support workflows

Deployment Dependencies

Implementation Details

The template runs the official ghcr.io/paulolinder/velix-api image alongside a Railway PostgreSQL service over the private network, with only Velix exposed. Velix is written in Go and compiles to a single binary, giving it a small memory footprint relative to browser-based gateways — an advantage when hosting multiple instances. PostgreSQL stores instance sessions, message data, and configuration via a DATABASE_URL connection string.

Velix manages multiple WhatsApp numbers from one deployment: each number is an instance connected by scanning a QR code, then addressed independently through the REST API. Incoming messages and status changes are delivered to a configured webhook URL, and Velix's native n8n node plus its Chatwoot integration make it an automation-first gateway rather than a bare API. Because the project is early-stage, exact environment-variable names should be verified against the current repository before publishing. Velix connects through the WhatsApp Web protocol, not Meta's official Cloud API, so standard account-safety practices apply and regulated or high-volume use is better served by the official API.

Frequently Asked Questions

How is Velix different from Evolution API? Both are self-hosted WhatsApp Web gateways. Velix is a lightweight Go binary with a small footprint and a native n8n node, focused on lean automation setups; Evolution API is a heavier, more feature-rich platform with a larger integration set. Choose Velix for a small, automation-first deployment.

Does it support multiple numbers? Yes. Velix manages multiple instances from one deployment — connect each WhatsApp number by scanning its QR code and address them separately through the REST API.

How do I connect it to n8n? Velix ships a native n8n community node, so you add the node to a workflow and connect it rather than building raw HTTP calls. It also integrates with Chatwoot for support inboxes.

Is this the official WhatsApp API? No. Velix uses the WhatsApp Web protocol, not Meta's official Cloud API. It's flexible and self-hosted, but follow account-safety practices, and use the official Cloud API for regulated or high-volume messaging.

How do I keep my number from getting banned? Warm up new numbers gradually, rate-limit your sending, and never cold-message people who haven't contacted you — mass-messaging strangers is the most common cause of restrictions.

Why is it cheaper to run than other gateways? Velix is a compiled Go binary, so it uses much less memory than browser-based WhatsApp APIs, keeping Railway costs low even with several instances.

Why Deploy Velix 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 Velix API on Railway you get a lightweight self-hosted WhatsApp gateway with PostgreSQL wired, private networking, and automatic HTTPS. Multiple numbers, webhooks, and a native n8n node in a small Go footprint — a lean WhatsApp automation backend on infrastructure you own.