Deploy Outpost
Outbound webhooks and event destinations with retries, logs and a portal
Just deployed
RabbitMQ
Just deployed
/var/lib/rabbitmq
Just deployed
/var/lib/postgresql/data
Just deployed
/data
Deploy and Host Outpost on Railway
Outpost is an open-source (Apache-2.0) event delivery service by Hookdeck for teams that offer webhooks to their customers. Your app publishes an event once, and Outpost delivers it to each tenant's webhook endpoints or queues, with retries, signed requests, delivery logs and a tenant portal.
About Hosting Outpost
This template runs Outpost 1.9.0 (API, delivery and log services in one process) with Redis 8, RabbitMQ 4.4 and Railway's Postgres, all on private networking and volumes. Outpost, Redis and RabbitMQ build from a public GitHub repo with images pinned by version and digest, so you get Railway's update notices when we test a new release. The API key, JWT secret, encryption key and all passwords are generated per deploy, and the template asks you for nothing. Migrations run on every start. After deploy, copy API_KEY from the Outpost service and call the API on its public domain.
Common Use Cases
- Add outbound webhooks to your SaaS with retries, HMAC signatures and delivery logs
- Deliver events to customers' queues and buses (SQS, RabbitMQ, Kinesis, Azure Service Bus, Hookdeck)
- Give each customer a portal to manage their own destinations and replay failed events
Dependencies for Outpost Hosting
- Redis 8 (tenants, destinations and their encrypted credentials, retry schedule)
- RabbitMQ (internal delivery and log queues) and PostgreSQL (event and delivery log)
Deployment Dependencies
- Outpost source and releases: https://github.com/hookdeck/outpost/releases/tag/v1.9.0
- Outpost docs: https://hookdeck.com/docs/outpost
- Configuration reference: https://hookdeck.com/docs/outpost/self-hosting/configuration
- Template repository: https://github.com/aalfath/outpost-railway-template
Implementation Details
Health check: /healthz. All API calls use Authorization: Bearer API_KEY against https://YOUR-DOMAIN/api/v1:
curl -X PUT https://YOUR-DOMAIN/api/v1/tenants/acme -H "Authorization: Bearer API_KEY"
curl https://YOUR-DOMAIN/api/v1/tenants/acme/destinations -H "Authorization: Bearer API_KEY" -H "Content-Type: application/json" -d '{"type":"webhook","topics":["*"],"config":{"url":"https://example.com/hook"}}'
curl https://YOUR-DOMAIN/api/v1/publish -H "Authorization: Bearer API_KEY" -H "Content-Type: application/json" -d '{"tenant_id":"acme","topic":"user.created","data":{"id":1}}'
Defaults you can change on the Outpost service: webhook destinations may not point at private addresses (DESTINATIONS_BLOCK_PRIVATE_ADDRESSES=true, so tenants can't reach your Railway services), queue workers restart after a broker or Redis outage, and delivery concurrency is 100. Optional: TOPICS (allowed topics; empty allows any), PORTAL_REFERER_URL and the other PORTAL_* branding settings, DISABLE_TELEMETRY=true. Keep AES_ENCRYPTION_SECRET unchanged: it decrypts stored destination credentials. Updates: the repo's CHANGELOG.md lists each version; apply the update notice when you are ready.
Why Deploy Outpost 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 Outpost 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
