NewIntroducing npayload. The communication infrastructure that makes your systems react to the world in real time.→
npayload
Product

Keep your stack. Add everything else.

Native adapters for Kafka, SQS, EventBridge, SNS, Azure Service Bus, Google Pub/Sub, and more. Connect in minutes.

The challenge

Your team already runs Kafka or SQS. Replacing them is not an option. But they lack delivery guarantees, encryption, and audit trails. Building these features on top takes months per integration.

See how it flows

What you get

Native adapters

Eight adapters that connect your existing broker to npayload. Kafka, SQS, EventBridge, SNS, Azure, GCP Pub/Sub, HTTP, and more.

Official SDKs

Node.js, React, and Browser SDKs with TypeScript support. Install, import, and start sending events.

REST API

Any language, any platform. A clean REST API with comprehensive documentation.

ASP SDK

A dedicated SDK for the Agent Session Protocol. Build agent communication into your application.

Bi-directional sync

Events flow in both directions. Publish from Kafka into npayload. Deliver from npayload into SQS.

Zero migration

No need to move off your current stack. npayload adds capabilities on top of what you already have.

npayload vs. managing integrations yourself

FeaturenpayloadBuild it yourself
8 native broker adaptersBuild each one
TypeScript SDKs (Node, React, Browser)Build and maintain
Bi-directional sync with existing brokersComplex to build
Built in encryption and auditSeparate project
Agent protocol SDK included
Zero migration requiredN/A

How it works

1

Choose your adapter

Select the adapter for your existing broker. Configure credentials and topic mappings.

2

Events flow through npayload

Your broker sends events to npayload. npayload adds delivery guarantees, encryption, and audit trails.

3

Deliver anywhere

Events reach webhooks, other brokers, or agent sessions. All with the same guarantees.

Frequently asked questions

Do I need to migrate off my current message broker?+
No. npayload adapters connect to your existing broker. Events flow bi-directionally. You keep your infrastructure and add npayload capabilities on top.
Which broker adapters are available?+
Kafka, Amazon SQS, EventBridge, SNS, Azure Service Bus, Google Pub/Sub, HTTP webhooks, and a custom adapter for any source. More are added regularly.
How do the SDKs handle offline scenarios?+
The React SDK includes an offline queue. Events are buffered locally and delivered when connectivity returns. Deduplication ensures no duplicates.
Can I use npayload without an SDK?+
Yes. The REST API supports any language and platform. SDKs are provided for convenience but are not required.

Your systems should never miss what matters.

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

Free tier available. No credit card required.