
Deploy Webhook Tester
Inspect and debug webhooks and HTTP requests live, stored in Redis
Webhook Tester
Just deployed
Redis
Just deployed
/data
Deploy and Host Webhook Tester on Railway
Webhook Tester is an open-source tool for testing and debugging webhooks and other HTTP requests. Open the web UI to get a unique URL, point any service at it, and watch each incoming request (method, headers, query, body) appear live. Each URL can answer with a status code, headers, body and delay you choose.
About Hosting Webhook Tester
Webhook Tester is a single Go server with a built-in web UI. This template runs Webhook Tester 2.3.0 from the official ghcr.io/tarampampam/webhook-tester image, pinned by version and digest, built through the repository aalfath/webhook-tester-railway-template. Sessions and captured requests are kept in a bundled Railway Redis on its own volume, so they survive redeploys and restarts. Redis also carries the live WebSocket feed. The app reaches Redis over Railway's private network with a generated password. The app listens on port 8080, gets a public HTTPS domain, and Railway checks /ready, which answers only when Redis is reachable. The deploy form asks for nothing.
Common Use Cases
- Inspect the exact headers and payload a provider (Stripe, GitHub, Slack and others) sends to your webhook endpoint before you write the handler
- Return chosen status codes, bodies and delays to test how a client handles errors, retries and timeouts
- A private request bin for your team or CI, instead of public services that keep your payloads on someone else's server
Dependencies for Webhook Tester Hosting
- Redis (bundled Railway Redis on a volume) for sessions, captured requests and the live feed
Deployment Dependencies
- Webhook Tester source and releases: https://github.com/tarampampam/webhook-tester (v2.3.0)
- Template repository: https://github.com/aalfath/webhook-tester-railway-template
Implementation Details
Services:
Webhook Tester: the public web UI and capture endpoint on port 8080, built from the template repository'sDockerfile. Health check/ready.Redis: Railway's Redis on a volume at/data, private only. It stores sessions and requests (kept for 7 days, 128 per URL by default).
After deploy, open the public URL. The UI creates a webhook URL of the form https://YOUR-DOMAIN/UUID. Send requests to it, for example curl -X POST https://YOUR-DOMAIN/UUID -d 'hello', and they appear in the UI as they arrive.
There is no login: anyone with the public URL can open the UI and read requests sent to a URL whose UUID they know. Don't send secrets or production data to it.
Optional service variables (set on the Webhook Tester service): SESSION_TTL, MAX_REQUESTS, MAX_REQUEST_BODY_SIZE (10 MiB by default here), AUTO_CREATE_SESSIONS=true to accept requests on any UUID path, and PUBLIC_URL_ROOT for a custom domain.
Updates: the service builds from aalfath/webhook-tester-railway-template. When it moves to a new Webhook Tester release, Railway shows you an update notice; read CHANGELOG.md, then apply it. Data stays in Redis across updates.
Why Deploy Webhook Tester 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 Webhook Tester 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
Webhook Tester
aalfath/webhook-tester-railway-templateRedis
redis:8.2