Send an event to a channel and let subscribers handle it independently. Filtering, retries, and replay included.
Event-driven messaging
Publish events to channels, subscribe handlers with pattern matching, and deliver to webhooks. Build event- driven systems without managing Kafka, RabbitMQ, or other message brokers.
Capabilities
Publish events to named channels. Multiple subscribers receive each event independently.
Subscribe to specific event types within channels. Filter by event properties without receiving all messages.
Route events to HTTP endpoints. Automatic retries with exponential backoff for failed deliveries.
One publish reaches multiple subscribers. Each subscriber processes independently with isolated failures.
At-least-once delivery with configurable retry policies. Dead-letter handling for persistent failures.
Replay events from a point in time for debugging or reprocessing. Catch up subscribers after outages.
Replay events from a point in time for debugging or reprocessing. Catch up subscribers after outages.
Publish to subscriber
For replay capability
After retry attempts
Why it matters
Publish an order.created event. Three services subscribe: inventory updates stock, billing charges the card, and notifications sends confirmation. Each service handles failures independently.
Subscribe a webhook endpoint to payment events. If the endpoint fails, retries happen at 1, 5, 15, and 60 minutes. After all retries fail, events move to dead-letter for investigation.
A bug in the order processing service caused incorrect inventory updates. Fix the bug, replay events from the past hour, and reprocess with correct logic. No lost orders.
Built for Your Workflow
Publish events to channels when state changes. Interested services subscribe independently and receive events without the publisher knowing who is listening.
Decouple services with pub/sub patterns without operating message brokers.
Subscribe endpoints with configurable retry policies. Failed deliveries retry with exponential backoff, and persistent failures move to dead-letter queues for investigation.
Deliver webhooks reliably without building retry logic or failure tracking.
View event history with delivery status for each subscriber. Trace an event from publish through all delivery attempts to see exactly what happened.
Debug event flows with complete visibility instead of correlating logs.
Replay events from a point in time after subscriber recovery. Conjoin retains events within the retention window, letting you reprocess what was missed during outages.
Recover from subscriber failures without losing events.
Start building with Conjoin today. Free tier includes everything you need to prototype and launch. Scale when you're ready.