Product

Your events reach every destination

Publish once. npayload distributes to every subscriber with ordering guarantees, priority levels, and real time streams.

The challenge

Your systems produce events. Dozens of services need them. Building reliable distribution with ordering, priority, and failure handling takes months. Then you need to maintain it forever.

See how it flows

PublisherYour service

ChannelPriority + ordering

Subscriber AWebhook

Subscriber BStream consumer

Consumer GroupLoad balanced

Dead Letter QueueAuto recovery

What you get

Publish and subscribe

Send an event to a channel. Every subscriber receives it independently. One call replaces point to point connections.

Fan out delivery

One event reaches hundreds of subscribers simultaneously. If one is slow, the others are unaffected.

Ordered streams

Subscribers read events in order, at their own pace. Resume from where they left off after any interruption.

Consumer groups

Distribute work across a group of subscribers. Each event is processed exactly once by one member of the group.

Priority channels

Critical events are delivered before routine ones. You define the priority. npayload respects it.

Transactional publish

Send events to multiple channels atomically. All succeed or none do. No partial deliveries.

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 groups with load balancing		Months of work
Priority queues
Transactional publish (atomic)
Dead letter queue with auto recovery		Weeks of work
Zero infrastructure to manage

How it works

Create a channel

Define the channel type, privacy mode, and delivery preferences. One API call.

Publish events

Your system sends events to the channel. npayload handles distribution, ordering, and retries.

Subscribers receive

Every subscriber gets the event independently. Failures are retried automatically. Nothing is lost.

Frequently asked questions

What message brokers does npayload replace?+

npayload can replace custom pub/sub implementations or work alongside existing brokers like Kafka or SQS through native adapters. You choose what to keep and what to add.

Is there a message size limit?+

Messages up to 1 MB are supported on all plans. Enterprise plans support larger payloads with configurable limits.

How does ordering work across fan-out?+

Each subscriber receives events in the order they were published. Message groups provide FIFO ordering for related events within a channel.

What happens when a subscriber is down?+

npayload retries delivery with exponential backoff. After all retries are exhausted, the event moves to the dead letter queue for manual review and replay.

Your systems should never miss what matters.

One integration. Real time events. Guaranteed delivery. Proof of everything.

Free tier available. No credit card required.