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

See everything that flows through your infrastructure

Distributed tracing, health checks, and audit streaming. Debug any delivery in one click.

Events flow through your system.

You cannot see them.

Something fails.

You check three dashboards.

You search four log stores.

You correlate timestamps manually.

Twenty minutes pass.

You still do not know what happened.

Every event. Every hop. One view.

One trace shows the entire journey.

Every event receives a W3C trace ID automatically. From publish to delivery, every hop is visible in a single view.

Alerts fire before customers notice.

Continuous monitoring at three levels: endpoints, cells, and subscriptions. Degradation triggers alerts before it becomes failure.

Endpoint Health

Continuous monitoring of every endpoint. Latency, error rates, and dependency status in real time.

Cell Health

Infrastructure level monitoring. Capacity, connectivity, and performance per cell.

Subscription Health

Delivery success rates per subscription. Degradation alerts before customer impact.

Stream your audit trail to every destination.

SIEM, data warehouse, and GRC platform at the same time. Adding or removing destinations does not affect others. Every publish, every delivery, and every access is streamed in real time.

Audit Stream
publish
09:14:22.041
Datadog
deliver
09:14:22.187
Splunk SIEM
access
09:14:22.302
BigQuery
Real time. Multi destination. Zero configuration.

Your existing tools see npayload traces.

W3C Trace Context connects npayload to your observability stack. No migration. No replacement. Your tools simply see more.

Event

An event is published. The trace ID is assigned automatically.

npayload Trace

Distributed tracing captures every hop and every delivery.

Your Tools

Datadog, Grafana, Splunk, or anything that accepts OpenTelemetry.

Alert

Your existing alerting rules work with npayload traces.

Before and after npayload Observability

Without Observability

  • Check three dashboards to find one event
  • Search four log stores to correlate timestamps
  • Twenty minutes to find what happened
  • Customers report failures before your team does
  • No end to end visibility across services
  • Manual audit exports for compliance

With Observability

  • One trace shows the entire event journey
  • Real time delivery dashboard per endpoint
  • Debug any delivery in one click
  • Proactive health alerts before degradation
  • W3C Trace Context connects your tools
  • Continuous audit streaming to your SIEM

npayload Observability vs. building it yourself

FeaturenpayloadBuild it yourself
End to end tracingWeeks of work
Proactive health monitoringComplex to build
Audit streaming to SIEMMonths of work
Real time delivery dashboardWeeks of work
W3C Trace ContextDays of work
Key expiry alerting
Multi destination audit streamingComplex to build
Circuit breaker visibilityCustom per endpoint

Frequently asked questions

Do I need to instrument my code?+
No. npayload adds trace context automatically. If you already propagate W3C headers, it continues your trace.
What observability tools are supported?+
Any tool that accepts OpenTelemetry, syslog, or webhooks. Datadog, Grafana, Splunk, Elastic, Jaeger, and more.
How are health checks performed?+
Continuous monitoring of latency, error rates, and dependency status. Alerts fire before failure thresholds are crossed.
Can I stream audits to multiple destinations simultaneously?+
Yes. SIEM, data warehouse, and GRC platform at the same time. Adding or removing destinations does not affect others.
We already use Datadog. Does this add anything?+
Yes. Datadog shows your services. npayload shows your event delivery: publishes, deliveries, retries, circuit breakers. W3C traces connect both seamlessly.
How far back can I see delivery history?+
At least 30 days on all plans. Enterprise supports custom retention. Use audit streaming for indefinite storage.
Does observability work with zero knowledge encryption?+
Yes. Traces include delivery metadata but not payload content. Privacy preserved, operational visibility maintained.