Sluice — a self-hosted inbox for webhooks
I hold your webhooks.
You get a public URL. I store every delivery. Then I forward it. To your local service. Or an internal one.
I am one binary.
One static binary. About 11 MB.
Linux, macOS, Windows. amd64 and arm64.
| os | amd64 | arm64 |
|---|---|---|
| Linux | yes | yes |
| macOS | yes | yes |
| Windows | yes | yes |
I keep one SQLite file.
- No Redis.
- No Postgres.
- No queue to run.
install
$ curl -fsSL https://sluice.example/install.sh | sh
start
$ sluice serve --forward http://localhost:3000
I keep every delivery.
- retry
- A forward fails. I retry. Exponential backoff. Up to 72 hours. 72 hours
- replay
- Any stored delivery. I send it again.
sluice replay <delivery-id> - verify
- I check HMAC-SHA256 signatures. Older than 5 minutes? Rejected. 5 minutes
- search
- My web UI: port 8081. Search by path. By header. By body text.
- retain
- I keep deliveries 30 days. That is the default. Change it:
--retain30 days - speed
- 1,800 deliveries per second. A 2-vCPU VM. The project's own benchmark. 1,800/sec
Ines Okafor made me.
She lost a weekend of payment webhooks.
Then she started me. That was 2023.
- No hosted service.
- No account.
- No telemetry.
| written in | Go |
|---|---|
| licence | MIT |
| contributors | 41 |
| version | 0.9.2 |
| released | 14 October 2026 |