Your events reach every destination
Publish once. Every subscriber receives it with ordering, priority, and streaming built in.
You publish an event.
Ten services need it.
Some need it now.
Others can wait.
One subscriber fails.
The rest are stuck.
Retry logic in every service.
No ordering guarantees.
No dead letter queue.
You built plumbing instead of product.
Not anymore.
One channel type for every pattern
Classic pub/sub, ordered streams, or compacted channels. Choose the semantics that match your use case.
Pub/Sub
Publish an event. Every subscriber receives it independently. Slow consumers never block others.
Streams
Ordered consumption with resume from any offset. Your consumers never lose their place.
Compacted Channels
Only the latest value per key is retained. Ideal for configuration state and registries.
Publish once. Deliver everywhere.
One event reaches hundreds of subscribers. Slow consumers never block others. Failures route to the dead letter queue automatically.
Every message arrives in the right order.
Message groups provide strict FIFO ordering for events sharing a partition key. Events for the same order always arrive in publish sequence, regardless of throughput on other partitions. No complex rebalancing. No manual coordination. Ordering is guaranteed by the infrastructure.
Atomic publish across multiple channels
Publish to multiple channels in one operation. All channels receive the event or none do. Zero partial state in your system.
Publish
Your service publishes to multiple channels in a single atomic operation.
Validate
npayload verifies schema, permissions, and limits before persisting.
Deliver
All channels receive the event or none do. Zero partial state.
Before and after npayload Messaging
Without npayload
- Retry logic in every service
- No ordering guarantees across subscribers
- Lost events discovered when customers complain
- No dead letter queue or a fragile homegrown one
- Atomic multi channel publish is impossible
- Months to build the distribution infrastructure
With npayload
- Automatic retries with exponential backoff
- Guaranteed ordering per partition key
- Dead letter queue with one click replay
- Fan out to hundreds of subscribers instantly
- Native transactional multi channel publish
- First event published in minutes
npayload vs. building it yourself
| Feature | npayload | Build it yourself |
|---|---|---|
| Fan out to hundreds of subscribers | Months of work | |
| Ordered streams with resume | Complex to build | |
| Consumer group rebalancing | Months of work | |
| Priority queues | ||
| Atomic multi channel publish | ||
| Dead letter queue with replay | Weeks of work | |
| Three privacy modes | ||
| Cross org delivery with consent | ||
| Zero infrastructure |