EVENTS
Apps don't talk to each other. Until they do.
Months of plumbing turn into one connection. Nothing lost. Every action proven.
The Federated Enterprise Service Bus for the agentic era. Publish once. Reach every app, every agent, every partner. Eleven nines of durability. Audit ledger on every flow.
THE PROBLEM
Every team rebuilds the same plumbing. Again. And again.
A trade settles. A fraud pattern fires. An agent decides. A partner publishes. Each event needs to reach every system that cares. Today, every connection is a custom build. Every failure mode is rebuilt from scratch. Every audit is an export.
Your stack
where every team rewrites the wire
Trade settled
Risk, treasury, compliance all need it
Fraud detected
Underwriting, payout, audit all need it
Agent decided
Every dependent system needs the reasoning
Partner published
Every internal app needs the update
Catastrophe alert
Re-rating, dispatch, ops all need it
Viral demand spike
Inventory, pricing, supply all need it
Sensor pinged
Maintenance, ops, analytics all need it
Regulation changed
Every system that touches the rule needs it
Every signal above is a moment your team is rebuilding plumbing instead of shipping product.
WHAT EVENTS IS
One fabric. Every app reached.
Events is the Federated Enterprise Service Bus for the agentic era. Your event publishes once. Every subscribed app, agent, and partner receives it with guaranteed delivery, ordering, and audit. Months of plumbing turn into one connection.
Pub sub, fan out, ordered delivery, consumer groups, streams, compacted channels. Eleven nines of per message durability. Three privacy modes including zero knowledge. Audit ledger on every event. Cross region delivery worldwide.
Microsecond delivery for the robotic era. Your same connections work on the next generation of npayload. No rewrite.
One connection. Every app reached. Every action proven. Decade scale wire.
ONE EVENT, EVERY APP
Your trade settles. Five systems update. Every action recorded. Fifty milliseconds.
Faster than any human could read the alert. Faster than the next reconciliation window.
Trade settles
Your trading system publishes one event. Same fabric. One call.
Fabric routes
Events fans the message out to every subscriber: risk, treasury, compliance, partner systems.
Same region delivered
Every same region subscriber has the event. Ordered. Guaranteed.
Cross region delivered
Every cross region subscriber has it. The fabric runs the same speed everywhere.
Recorded everywhere
Audit ledger writes every delivery. Every action provable. Every replay possible.
Five lines of code. Your first event is live.
Authentication, encryption, delivery guarantees, and audit are handled for you. Connect to one product. Use the others when you are ready.
import { NPayload } from '@npayload/sdk'
const np = await NPayload.connect({
clientId: process.env.NPAYLOAD_CLIENT_ID!,
hmacSecret: process.env.NPAYLOAD_HMAC_SECRET!,
})
// Publish a business event
await np.events.publish('orders', {
orderId: 'ord_123',
amount: 99.99,
})SDKs in Node, Python, React, Browser. Public protocol documentation. Every event your team sends is inspectable.
What life looks like with Events.
Six promises, one for every role that depends on the wire holding.
One fabric. A chain reaction.
Wire one team. Then the next. Then every partner. The integration backlog drains while you ship product.
The first wire.
Your trading team publishes one event into Events. Risk, treasury, and compliance subscribe in an afternoon. The retry logic, the audit, the cross region propagation all come with the wire. The team ships the next feature instead of the next retry layer.
The team that compounds.
Operations subscribes next. Then customer support. Then partner platforms. Each team wires up in hours, not months. The wire your team built once becomes the wire your whole company runs on.
The subscriber that went down.
A downstream service crashed at 3 a.m. The fabric held the events for it. The retry kicked in. The dead letter queue caught anything that still failed. The team came in to a normal queue, not an incident. Recovery was automatic.
The replay request.
A regulator asks for every trade event from last quarter, by region, by counterparty. You do not export. You do not rebuild. You replay from the offset and the answer flows out the same wire. Five minutes.
FOUNDING COHORT
Stacks that run on one fabric.
Platform teams in these sectors run their stack on one fabric. Publish once. Reach every consumer that filtered for it.
Financial services
Trades, settlements, risk events delivered to every system that cares with guaranteed ordering.
Insurance
Claims, payouts, underwriting events shared across teams and partners with audit on the wire.
Healthcare data
Patient events delivered to providers, insurers, and labs with consent and residency controls baked in.
Logistics intelligence
Shipment, customs, delivery events fanned to every system in real time.
Manufacturing
Predictive maintenance signals reach every operations and supply chain system the moment they fire.
Multi tenant platforms
Tenant isolated event routing at scale. Every tenant gets the same wire, isolated by tenant key.
Be the platform your whole team runs on.
Publish your first event. Wire one team. Then the next. The integration backlog drains while you ship product.
Questions platform teams ask before they wire their first event.
Apps don't talk to each other. Until they do.
Publish your first event. Stop rebuilding the same plumbing on every team.
Rebuild the plumbing, or wire it once.