Categories
Self-Hosted Developer Tools Infrastructure API Notifications Webhooks Backend IntegrationStars
Forks
Watchers
Developer links
Svix
Development teams hand their outgoing webhooks to Svix, which delivers each event to customer endpoints with retries, signed payloads, and a delivery record for every attempt. Your app makes one API call when something happens, a user signs up, an invoice is paid, a build finishes, and Svix delivers the event to every subscribed endpoint your customers registered. Endpoints that fail get automatic retries on a schedule, deliveries are logged attempt by attempt, and failed messages can be resent instead of vanishing. Customers organize their integrations as applications, subscribe endpoints to the event types they care about, filter by channels, and verify signed payloads so forged requests get rejected. You define the event catalog once, and fanout, throttling, and endpoint bookkeeping stop being code you maintain. Official libraries for nine languages and a CLI make the first integration an afternoon task, and the whole service runs from a Docker Compose stack with Postgres and Redis when you want it on your own infrastructure. Your product gains the webhook system customers expect, without your team becoming a deliverability department. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.
Benefits
- Webhooks Without The Grind
- Deliverability, retries, fanout, and endpoint bookkeeping move into a purpose-built service. Your team ships product features; Svix worries about flaky customer servers, slow responses, and the long tail of delivery failures.
- Customers Debug Their Own Endpoints
- Every message records its delivery attempts and responses, so a customer asking why an event never arrived gets an answer from logs, not guesswork. Failed deliveries can be resent once their server recovers.
- Signed, Verifiable Payloads
- Outgoing webhooks carry HMAC signatures with timestamps that receivers verify using official libraries, following the Standard Webhooks specification. Forged or replayed requests are rejected instead of trusted by your customers blindly.
- One Integration, Every Language
- Official SDKs for Go, Python, TypeScript, Java, Kotlin, Ruby, C#, Rust, and PHP, plus a CLI, wrap the same API. Each of your services integrates idiomatically without hand-rolled HTTP and signing code everywhere.
Features
- Applications And Endpoints
- Model each customer as an application holding their webhook endpoints, each subscribed to chosen event types and channels. Fanout delivers one published message to every matching endpoint automatically and reliably.
- Automatic Retry Schedule
- Failed deliveries retry with exponential backoff over hours instead of giving up after one timeout. Endpoint failures are tracked per attempt, and operators can resend messages after the receiver recovers.
- Event Types And Channels
- Define a catalog of event types like user.created or invoice.paid, and tag messages with channels for finer routing. Endpoints subscribe only to the slices they want to receive and process.
- Signed Standard Webhooks
- Messages are signed with HMAC-SHA256 and sent with id, timestamp, and signature headers compatible with Standard Webhooks. Receiver libraries in every SDK verify authenticity and freshness in a few lines.
- Delivery Logs And Attempts
- Inspect every message, its target endpoints, response codes, and attempt history through the API. Support questions about missing events become lookups, and replaying history takes one call per message.
- Self-Host With Compose
- The MIT licensed server runs from the official Docker image and Compose stack with PostgreSQL and Redis on port 8071. Migrations to the hosted service stay painless.
