A safe landing place for every event.
Receive instantly. Deliver reliably.
Website · Product repository · Discussions · Brand guide
Payload Bay is an open-source, self-hosted platform for receiving, verifying, storing, routing, and reliably delivering webhooks and events.
External providers should be able to send an event to a stable ingress URL without being coupled directly to an application's availability, network location, or retry behavior. Payload Bay provides the layer in between: a place where the original request can arrive, be verified and retained, then be delivered through a controlled path.
- Receive events through canonical ingress URLs and custom aliases.
- Preserve the original request body and relevant request metadata.
- Verify provider signatures and identify duplicate or replayed events.
- Store events, receipts, deliveries, and delivery attempts durably.
- Route one event to HTTP targets or private applications reached through outbound runners.
- Retry failed deliveries, respect retry guidance where applicable, and make dead deliveries visible.
- Replay stored events when an application, target, or configuration needs to catch up.
- Inspect events, delivery attempts, responses, and operational incidents.
- Help local, preview, staging, and private production applications receive events without requiring an inbound public webhook endpoint.
- Provide provider-aware integrations alongside generic and custom webhook handling.
The product is intentionally focused. It is not a visual automation builder, a general-purpose job platform, or a replacement for a message broker.
A safe landing place for every event.
An incoming event should not disappear because an application is temporarily unavailable, lives behind a firewall, or cannot safely expose a public endpoint.
Payload Bay is being built around a simple model: receive the event first, verify it, keep a durable record, create the required deliveries, and make the result observable. The delivery guarantee is deliberately honest: at-least-once delivery. Receivers can use event and delivery identifiers to deduplicate when needed.
Payload Bay is an open-source project first. Community is intended to be a capable self-hosted product that people choose because it is good software, not because a restricted free tier happens to fit their current quota.
A self-hosted installation should not become less useful because it receives more events, adds another source, connects another runner, or reaches an arbitrary product limit. Practical capacity depends on the infrastructure an operator chooses to run.
Donations and sponsorship are optional ways to support the project.
Payload Bay is in early development. The architecture and public interfaces may change while the first version is built and validated. The organization, public identity, and development standards are already in place; implementation is now beginning in the product repository.
- Follow the product repository
- Join Discussions for questions, ideas, and show-and-tell
- Read the contribution guide
- Report a security issue privately
Reliable webhook delivery without coupling providers to your application.
