Deploy Convoy

Self-hosted webhooks gateway: send, receive and retry webhooks

Deploy Convoy

Just deployed

/data

/var/lib/postgresql/data

Deploy and Host Convoy on Railway

Convoy is a source-available webhooks gateway by Frain Technologies. It sends webhooks to your customers' endpoints with signatures, retries, rate limits and a delivery log, and it receives webhooks from other services through ingest URLs, then fans them out to your own endpoints. You manage it from a web dashboard or its REST API.

About Hosting Convoy

Convoy needs a Postgres database, a Redis instance and two processes: the server (dashboard, management API, scheduler) and the agent (delivers webhooks and serves the /ingest and portal event routes). This template runs both processes in one Convoy service built from a public GitHub repo, behind a small Caddy router on one public domain, with Railway's Postgres and Redis on volumes. On the first start, migrations run and your admin account is created from the template variables before Convoy starts, so Convoy's built-in superuser@default.com / default login never exists. Public sign-up is off.

Common Use Cases

  • Send signed, retried webhooks from your SaaS to customer endpoints, with a delivery log and replays
  • Receive webhooks from Stripe, GitHub, Shopify and others on one ingest URL, verify them, and route them to internal services
  • Give customers an embeddable portal to manage their webhook endpoints and see delivery history

Dependencies for Convoy Hosting

  • Postgres (Railway Postgres, included)
  • Redis (Railway Redis, included)

Deployment Dependencies

Implementation Details

  • First login: open the Convoy service's public URL and sign in with CONVOY_ADMIN_EMAIL (default admin@example.com, you can change it before deploying) and the generated CONVOY_ADMIN_PASSWORD from the service's Variables tab. The password is set on the first start only: change it later in Convoy's profile settings.
  • Routing: /ingest/*, /portal-api/events* and /portal-api/eventdeliveries* go to the agent; everything else (dashboard, /api/v1) goes to the server.
  • Edition: Convoy is source-available under the Elastic License 2.0. Without a license key it runs as the Community edition (1 user, 1 organisation, 2 projects). Add CONVOY_LICENSE_KEY to lift those limits.
  • Optional settings: SMTP, Google OAuth, retention and log level use Convoy's own CONVOY_* variables (see convoy.env.example in the Convoy repo). Logs default to warn.
  • Updates: the Convoy service builds from the template repo, so Railway offers you an update when its main branch changes. Check CHANGELOG.md there first; migrations run automatically on start.

Why Deploy Convoy 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 Convoy 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

More templates in this category

View Template
Celery | Web, Worker and Scheduler as Three Services
Web, worker and scheduler wired up: Celery on Redis, outcomes in Postgres.

Templates Guru
0
View Template
Redpanda
Redpanda 26.2: Kafka-compatible streaming broker with Kafbat UI console

Agaz Self-Host
2
View Template
smoothmq
A drop-in replacement for AWS SQS

poundifdef
7