Deliveries per second
That figure comes from our own benchmark, run on a 2-vCPU VM, and we quote it only as that.
1,800
That figure comes from our own benchmark, run on a 2-vCPU VM, and we quote it only as that.
We give you a public URL for webhooks, store every delivery, and forward it to your local or internal service.
The first line below installs Sluice; the second starts it and forwards each delivery to localhost:3000.
curl -fsSL https://sluice.example/install.sh | sh
sluice serve --forward http://localhost:3000
11 MB
Sluice is one static binary of about 11 MB, built for Linux, macOS and Windows on amd64 and arm64.
We keep every delivery in a single SQLite file, so there is no Redis, no Postgres and no queue to run.
| System | amd64 | arm64 |
|---|---|---|
| Linux | ||
| macOS | ||
| Windows |
When a forward fails, we retry it with exponential backoff for up to 72 hours.
Any stored delivery can go to your service again with one command and its delivery ID.
sluice replay <delivery-id>
5 minutes
We verify HMAC-SHA256 signatures on deliveries and reject any delivery that is older than 5 minutes.
8081
Our web UI runs on port 8081, where you can search deliveries by path, header or body text.
We keep deliveries for 30 days by default, and you can set a different period with --retain.
--retainSluice runs only where you install it, because we offer no hosted service and ask for no account.
We collect no telemetry, and there is nothing to sign up for before you start the binary.
Ines Okafor
Ines Okafor started Sluice in 2023, after losing a weekend of payment webhooks, and she maintains it.
We write it in Go and publish it under the MIT licence; 41 contributors have worked on it.