NewHow the Agent Session Protocol builds trust between autonomous systems.→
npayload
Product

Keep your stack. Add everything else.

Native adapters for Kafka, SQS, Azure, GCP, and more. No migration. No downtime.

Your system runs on Kafka.

Your partner runs on SQS.

Another uses Azure Event Hubs.

A fourth expects HTTP webhooks.

You write adapters for each one.

Each adapter needs error handling.

Each adapter needs retries.

Each adapter needs monitoring.

You are building plumbing, not product.

npayload connects them all.

One adapter. Any destination.

Eight adapters. Four SDKs. One connection.

Connect Kafka, SQS, Azure, GCP, and more. Deliver via SDK, REST, or ASP. Everything flows through a single connection point.

Events flow both ways.

Your internal broker and npayload stay in sync. Events arrive at both simultaneously.

Step 1

Connect

Configure your broker credentials and topic mappings. The connection is live within minutes.

Step 2

Sync

Events flow both ways simultaneously. Your internal broker and npayload stay in lockstep.

Step 3

Deliver

npayload adds encryption, audit trails, and consent automatically before every delivery.

Nothing to replace. Nothing to rewrite.

npayload connects to your existing broker. Your internal consumers are completely unaffected. Cross org delivery, encryption, and audit trails are added on top.

Before
Kafka
SQS
Azure
9 connections
Partner A
Partner B
Partner C
After
Kafka
SQS
Azure
npayload
Partner A
Partner B
Partner C
6 connections. Same reach.

Built for developers.

Official SDKs, full type safety, and a REST API for everything else.

Offline queue

The React SDK buffers events locally and delivers them with deduplication when connectivity returns.

TypeScript native

Full type safety end to end. Autocompletion in your IDE. No manual deserialization layer.

OpenAPI spec

Full access from any language via the REST API. Documentation generated automatically.

Before and after npayload Integrations

Without npayload

  • Custom adapter per broker per partner
  • Each adapter needs error handling and retries
  • Each adapter needs separate monitoring
  • No encryption or audit on integrations
  • Cross org delivery requires months of custom work
  • Vendor lock in with each broker

With npayload

  • One connection to npayload, all brokers reached
  • Automatic retries and circuit breakers included
  • Unified monitoring across all adapters
  • Encryption and audit built in
  • Cross org delivery from day one
  • Standard HTTP and JSON, no lock in

npayload vs. managing integrations yourself

FeaturenpayloadDIY
8 native broker adaptersBuild each one
TypeScript SDKs with offline queueBuild and maintain
Bi directional broker syncComplex to build
Built in encryption and auditSeparate project
Cross org delivery with consentMonths of work
ASP SDK included
Zero migrationN/A
REST API with OpenAPI specBuild and maintain

Frequently asked questions

Do I need to migrate off my current message broker?+
No. Adapters connect to your existing broker. npayload adds cross org delivery, encryption, and audit on top.
Which broker adapters are available?+
Kafka, SQS, EventBridge, SNS, Azure Service Bus, GCP Pub/Sub, HTTP webhooks, and a custom adapter.
How do the SDKs handle offline scenarios?+
The React SDK buffers events locally and delivers them with deduplication when connectivity returns.
Can I use npayload without installing an SDK?+
Yes. The REST API gives you full access to every feature from any language.
Is there vendor lock in with the adapters?+
No. Standard JSON over HTTP. Disconnect the adapter and your broker is unaffected.
Can the same event go to both my internal Kafka and an external organization?+
Yes. Events flow through the adapter into npayload for external delivery. Your internal consumers are unaffected.
How is authentication handled for adapters?+
Each adapter uses its broker's native auth (SASL/SSL, IAM roles, etc.). Credentials are encrypted and never exposed.