Deploy and Host Svix on Railway

Svix is an open-source webhooks service. Your application sends events to Svix once, and Svix delivers them to every subscribed endpoint with signing, automatic retries with exponential backoff, rate limiting and delivery logs, so you do not have to build and operate webhook infrastructure yourself. SDKs exist for most languages.

About Hosting Svix

This template deploys the Svix server v1.101.0 with Railway Postgres for data and Railway Redis as the task queue and cache. Migrations run on startup. The API is on the public domain and listens on IPv4 and IPv6 privately. Requests are authenticated with JWTs signed by the generated SVIX_JWT_SECRET; create one with svix-server jwt generate over railway ssh or sign your own HS256 token. The worker runs in the same service and delivered a real test webhook during verification. The Hobby plan is enough for moderate volumes. Back up Postgres regularly to keep delivery history.

Common Use Cases

Sending signed webhooks to your customers without building retry logic
Event notifications from a SaaS product to many customer endpoints
A self-hosted alternative to the Svix cloud with the same SDKs

Dependencies for Svix Hosting

svix/svix-server:v1.101.0 (official image)
Railway Postgres and Railway Redis

Deployment Dependencies

Implementation Details

Service	Image	Networking	Storage
svix	`svix/svix-server:v1.101.0`	public domain on 8071; private	none
Postgres	Railway Postgres 18	private only	volume
Redis	Railway Redis	private only	volume

Create an API token (org id is an example):

railway ssh --service svix -- svix-server jwt generate org_23rb8YdGqMT0qIzpgGwdXfHirMu

Then point an SDK at SVIX_SERVER_URL with that token:

const svix = new Svix(token, { serverUrl: process.env.SVIX_SERVER_URL });
await svix.message.create("app_uid", { eventType: "invoice.paid", payload: { id: "inv_1" } });

Variable	Default	Purpose
`SVIX_JWT_SECRET`	generated	Signs API tokens
`SVIX_DB_DSN` / `SVIX_REDIS_DSN`	Postgres / Redis references	Storage and queue
`SVIX_QUEUE_TYPE` / `SVIX_CACHE_TYPE`	`redis`	Durable queue and shared cache

Notes:

The v2.x releases on GitHub are client libraries; the server image is versioned separately (v1.101.0 is the latest).
Endpoints must be reachable from Railway; delivery attempts and responses are visible through the API.

This is a community-maintained deployment package and does not imply affiliation with or endorsement by the Svix project or its maintainers.

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