NewHow the Agent Session Protocol builds trust between autonomous systems.
Solution

Event driven automation

Something happens anywhere in the world. Your systems react.

A sensor fires an event.

Three systems need to react.

The event crosses a network boundary.

It gets dropped.

Nobody notices for hours.

Your team scrambles to find the gap.

npayload delivers across every boundary.

Nothing gets lost.

See how it flows

Cross boundary delivery

Events from any organization reach your systems. Guaranteed.

Billing API42ms
Shipping Service38ms
Analytics51ms
Notification Hub29ms

Visual workflows

Pipes lets your team automate actions visually. Connect data sources without separate tools.

Processing Pipeline
Ingest
Transform
Enrich
Deliver
Raw event in → enriched, routed event out

Zero data loss

If something fails, npayload recovers on its own. Events that cannot be delivered are saved for your team to review and resend.

Delivery Attempts
1
POST /webhook
503
retry
+0s
2
POST /webhook
503
retry
+2s
3
POST /webhook
503
retry
+8s
4
POST /webhook
200
delivered
+32s
Exponential backoff. Never lost.

Instant reactions

Your systems act on events in real time. Reorder inventory. Flag fraud. Route cases. Automatically.

Live Dashboard
Events/sec
12,847
+23%
P99 Latency
38ms
−12%
Delivery Rate
99.97%
+0.02%
Active Channels
1,204
+8

How it works

1

An event is born at another organization

A price changes. An order is placed. A sensor reads a new value. Something happens in the real world.

2

npayload delivers it privately

The event crosses organizational boundaries through encrypted channels. No public ports. No exposed infrastructure.

3

Your workflows process and act

Pipes visual workflows transform, enrich, and route the event. Your system reacts automatically.

Autonomous Processing: Before and After

Without npayload

  • Cross organization workflows require months of custom integration
  • No visibility into processing state when events cross company boundaries
  • Failures in multi step workflows leave data in inconsistent states
  • Building visual workflow tooling for your platform takes quarters of engineering time

With npayload

  • Pipes provides visual workflow building across organizational boundaries
  • Full observability into every step, including cross organization handoffs
  • Durable execution with checkpointing ensures consistency even through failures
  • Embed workflow capabilities into your platform in days, not quarters

npayload vs Building Workflow Automation Yourself

FeaturenpayloadBuild it yourself
Cross org workflowsNative support with consent management and encryptionCustom API integrations per partner, months per connection
Visual builderPipes: drag and drop with 15+ node types and 6+ connectorsBuild from scratch or buy a separate product
Failure recoveryDurable execution with automatic checkpointing and replayCustom retry logic, manual state reconciliation
Event routingContent based routing with schema validation at every stepHard coded routing rules scattered across services
MonitoringEnd to end tracing across every workflow step and organizationStitching logs from multiple systems manually

Frequently asked questions

What is Pipes and how does it relate to npayload?+
Pipes is npayload's visual workflow engine built on distrova flow. It lets you build event driven automations across organizations using a drag and drop interface, with the full power of npayload's messaging infrastructure underneath.
Can non technical users build workflows?+
Yes. Pipes provides a no code visual builder for common patterns. Developers can extend workflows with custom logic, and both approaches work together seamlessly.
How does npayload handle failures in multi step workflows?+
Every workflow step is checkpointed. If a step fails, npayload retries with configurable backoff. If the failure persists, the workflow pauses and alerts your team, with full context to resume from the exact point of failure.