---
title: "Deploy Svix"
description: "Svix webhook sending service with Postgres, Redis queue and retries."
category: "Automation"
url: https://railway.com/deploy/svix
---

# Deploy Svix

Svix webhook sending service with Postgres, Redis queue and retries.

**[Deploy Svix on Railway](https://railway.com/template/svix)**

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

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

## Template content

### Postgres https://devicons.railway.app/i/postgresql.svg

- **Image:** ghcr.io/railwayapp-templates/postgres-ssl:18

### svix https://github.com/svix.png

- **Image:** svix/svix-server:v1.101.0
- **Start command:** `svix-server --run-migrations --wait-for 60`
- **Health check:** /api/v1/health/
- **Public domain:** Yes

### Redis https://cdn.sanity.io/images/sy1jschh/production/0ce0bfdcfbdbf69662b1116671f97c2dd788b655-157x157.svg

- **Image:** redis:8.2
- **Start command:** `/bin/sh -c "rm -rf $RAILWAY_VOLUME_MOUNT_PATH/lost+found/ && exec docker-entrypoint.sh redis-server --requirepass $REDIS_PASSWORD --save 60 1 --dir $RAILWAY_VOLUME_MOUNT_PATH"`

## Documentation

# 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

- [Svix server repository](https://github.com/svix/svix-webhooks)
- [Svix server v1.101.0](https://hub.docker.com/r/svix/svix-server/tags)
- [Svix API documentation](https://api.svix.com/docs)
- [Railway private networking](https://docs.railway.com/reference/private-networking)

### 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):

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

Then point an SDK at `SVIX_SERVER_URL` with that token:

```js
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.


## Similar templates

- [N8N Main + Worker](https://railway.com/deploy/n8n-main-worker) — Deploy and Host N8N with Inactive worker.
- [Evolution API with n8n](https://railway.com/deploy/evolution-api-with-n8n) — Automate WhatsApp workflows with Evolution API, n8n, and Postgres.
- [Postgres Backup](https://railway.com/deploy/postgres-s3-backups) — Cron-based PostgreSQL backup to bucket storage

Open this page in a browser: https://railway.com/deploy/svix