NewThe wire for AI agents that act in milliseconds.

CONNECT

Six months to integrate one partner. One afternoon for every partner.

One subscription request. One approval. Data flows. Consent at every step. Revoke any time.

Cross organization communication infrastructure for the agentic era. One integration reaches every partner you have, every tenant in their ecosystem, every app in any platform you do not own. Consent at every step. Every flow on the ledger.

Read the Docs

THE PROBLEM

The integration backlog is older than your last quarter's roadmap.

A custodian needs your event. A partner platform wants to subscribe to your storefront. A partner CRM needs your customer update. A partner workflow needs your trade. Each one used to be a quarter of engineering. Each one cost you a deal.

Your integration backlog

where partnerships stall

Custodian needs your event

Your trade should reach them in milliseconds

Partner platform subscribes

Cross ecosystem, today a custom build

Partner CRM needs an update

Your customer change should hit theirs

Partner workflow needs trigger

Today, six weeks of integration work

Partner channel alert

Cross platform, today a hack

Partner wants live access

Your sales team waits a quarter

Compliance asks for proof

Today, screenshots and exports

Revoke a partner's access

Today, a manual cleanup that takes weeks

Every signal above is a partnership your team is delaying because the integration cost outweighs the deal value.

WHAT CONNECT IS

One integration. Every partner.

Connect is cross organization communication infrastructure for the agentic era. Your event publishes once. Consent is checked per partner and per tenant. PII is filtered before any byte leaves your boundary. The flow routes across ecosystems. Every cross boundary delivery sits on the audit ledger.

Live todayLive

Cross organization, cross tenant, cross ecosystem delivery in milliseconds. Consent applied per partner and per tenant automatically. PII filtered at the boundary. Every flow recorded with proof. Revoke any time and the change propagates in milliseconds.

On the horizonHorizon

AI agent to AI agent across companies. Your agent reaches the partner's agent through the same Connect fabric. No new integration. No new contract. Same consent and audit rails.

One event. Every partner. Every tenant. Consent per partner. Proof per flow.

ONE EVENT, EVERY PARTNER

Your trade clears at noon. Your custodian, your platform partner, and your client know by 12:00.05.

What used to take a 90 day integration project per partner now takes one publish call.

Wire delivery, cross boundary
T+000ms
T+0ms

Your app publishes

Your application publishes one event. Same event, one publish call.

T+5ms

Consent applied

Connect checks which partners have approved access. PII filtered automatically per partner and per tenant.

T+15ms

Crosses boundaries

Your trade reaches your custodian, your platform partner, and your client. Three different ecosystems. Same call.

T+30ms

Recorded on the ledger

Every cross boundary flow on the audit ledger. Your compliance team has proof in real time.

T+50ms

Action complete

Custodian books the trade. Partner platform updates their dashboard. Client receives the confirmation.

Plaintext stays in your boundary
Every step on the audit ledger
Eleven nines of per message durability

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!,
})

// Request a partner data sharing grant
const grant = await np.connect.grants.request({
  partnerOrgId: 'org_partner',
  scope: ['read:orders'],
})

SDKs in Node, Python, React, Browser. Public protocol documentation. Every event your team sends is inspectable.

What life looks like with Connect.

Six promises, one for every role that runs your partnerships.

PublishnpayloadService AService BService C
One integration. Every partner.
One subscription, one approval, data flows. Add the next partner with no new contract, no new code, no new shape. The first integration is the last one.
A
PROPOSE
B
Trust Score0.40
Two parties. One ledger.
Subscription request. Approval. Counter. Commit. Every step recorded. Both sides see the same record. Disputes settle in minutes, not quarters.
Standard
Full features
Headers
Metadata
Payload
Three privacy modes.
Standard. Hybrid. Zero knowledge. You decide what your partner can read on the wire. Your partner sees only what you allow.
0x7a3f...
tick.published
0xb21c...
agent.acted
Every cross org flow on the ledger.
Who approved what data sharing. When. For how long. Every grant a block. Revocation breaks the chain in real time. Your compliance team has proof, not promises.
USEUAP
Partners across regions.
Data residency by region. EU stays EU. US stays US. AP stays AP. Your partner sees their region. You see the audit. Sovereignty respected on every cross boundary flow.
IoT Sensor
SaaS Event
API Feed
npayload
Any partner source. One shape.
Workflows, channels, custom systems your partners run. Each becomes a destination you subscribe to once. The integration is the subscription itself.

One integration. A chain reaction.

One partner connects. Their tenants follow. Their partners follow. The wedge compounds.

The first partner.

You ship Connect on a deal that used to take six months. They subscribe through their existing platform. You approve. The events flow before lunch. The integration backlog clears one partner. The next deal closes faster.

The tenant who is also a partner.

A platform you integrated with has thousands of tenants. Each tenant becomes a Connect destination with one consent click. No new code per tenant. No new contract. The platform deal becomes thousands of deals.

The compliance review.

A regulator asks who approved a partner's access to a sensitive event. You open the audit ledger, scrub to the grant, read the consent record. Five minutes. No screenshots. No exports. Proof on the wire.

The revoke that took seconds.

A partnership ends. You revoke in one action. Every flow stops in milliseconds. The audit shows exactly what was delivered before the cutoff. Cleanup is automatic. The exit is as clean as the start.

FOUNDING COHORT

Platforms and teams that reach every partner.

Platforms and partnership teams in these sectors stopped building per partner integrations.

Financial services

Trades cleared and delivered to every custodian and counterparty in milliseconds with consent on the ledger.

Insurance

Claims data shared with brokers, reinsurers, and adjusters. Every consent recorded. Every revocation propagates in seconds.

Healthcare data

Patient events shared across providers, insurers, and labs. Consent on every transfer. Audit baked in.

Retail and commerce platforms

Your storefront talks to your CRM and your loyalty engine through one connection. Tenant consent in one click.

Logistics and supply chain

Shipment events cross carriers, customs, and customers in real time. Cross ecosystem on the same fabric.

Platform marketplaces

Your app reaches apps inside every platform you do not own. Each tenant approves once. The integration is the request.

Be the platform partners want to plug into.

Connect your first partner. One subscription. One approval. Data flows. Add the next partner with no new contract, no new code, no new shape.

Questions partnership teams ask before they wire their first partner.

Six months to integrate one partner. One afternoon for every partner.

Add your first partner. Six month integrations become one afternoon, forever.

Build the next integration, or build the next product.