Ines Okafor
She started it in 2023.
She'd lost a weekend of payment webhooks.
Sluice came out of that.
v0.9.2 · out 14 October 2026
You get a public URL.
Sluice stores every delivery.
Then it forwards each one. Local or internal, your call.
No hosted service. No account. No telemetry.
curl -fsSL https://sluice.example/install.sh | sh
One line starts it.
Point --forward at your app.
sluice serve --forward http://localhost:3000
about11 MB
One file. Written in Go.
Pick your OS. Pick your chip.
| System | amd64 | arm64 |
|---|---|---|
| Linux | ||
| macOS | ||
| Windows |
Everything lives in one file. Nothing else to run:
Deliveries stay 30 days.
Want another window? Set --retain.
72 hours
A forward failed? It retries.
Exponential backoff, up to 72 hours.
sluice replay <delivery-id>Need one again? Replay it.
Any stored delivery works.
HMAC-SHA256
Signatures get checked.
Older than 5 minutes? Rejected.
Open it in a browser. Search by path. Or header. Or body text.
1,800
deliveries a second
On a 2-vCPU VM.
The project's own benchmark, mind you.
Ines Okafor
She started it in 2023.
She'd lost a weekend of payment webhooks.
Sluice came out of that.