Deploy and Host betterMQ on Railway

betterMQ is an open-source, self-hosted HTTP message broker. Enqueue durable jobs over HTTP and deliver them with signed webhook push—no pull workers or Redis required. One process serves the API, control panel, and docs for async jobs, cron, delays, fan-out, and flow control.

About Hosting betterMQ

This template runs the public Docker image with HTTP on port 8080 and a persistent volume at /data for queues, auth, RocksDB indexes, and local message storage. After deploy, open /panel/ to set a panel password and copy your API token. Defaults use local disk storage; you can later switch to SlateDB/S3 from Infrastructure in the panel. Redeploys keep data as long as the volume stays attached. No database sidecar is required for the basic setup.

Common Use Cases

Async background jobs with webhook delivery to your app
Cron, interval, and delayed HTTP schedules without a separate scheduler
Fan-out / groups and flow-controlled pipelines with retries and DLQ

Dependencies for betterMQ Hosting

Public image: ghcr.io/bettermq/bettermq (linux/amd64 and linux/arm64)
Persistent volume mounted at /data
HTTP port 8080 (PORT / BETTERMQ_PORT)

Deployment Dependencies

Why Deploy betterMQ 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 betterMQ 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.