NewHow the Agent Session Protocol builds trust between autonomous systems.
Platform Connect

Your app is blind to every other app on the same platform.

Publish and subscribe to events across apps installed on the same customer account. Consent gated by the account owner. Enforced at the infrastructure level. Works on Shopify, Salesforce, HubSpot, and any platform with an app ecosystem.

You built an app on the Shopify App Store.

Your customers install it alongside dozens of other apps.

Those apps can't talk to each other.

The loyalty app upgrades a customer to VIP.

Your shipping app has no idea.

The reviews app detects negative sentiment.

Your ads app keeps spending money.

Thousands of apps on the app store.

You cannot integrate with all of them.

There is no shared event layer.

Your app is blind.

Until now.

Your app is no longer alone.

One event layer for every app

Connect apps within the same app store or across different platforms. Shopify, HubSpot, Intercom, Salesforce, and beyond.

Within a platform

Cross-platform

Consent in three steps

The account owner controls which apps see which events. No developer can fabricate consent.

Step 1

Initiate

Your app triggers a consent challenge to npayload.

Step 2

Authorize

The account owner clicks Authorize on the npayload consent page.

Step 3

Enforced

Cryptographic consent gates every event in real time.

Isolation at the infrastructure level

Code level filters are one bug away from a data leak. Isolation is enforced by the infrastructure, not by code.

Account gating

Every event is tied to a specific customer account. No event passes without verification.

Consent validation

Consent is validated before any event is accepted and before any delivery is scheduled.

Zero cross-leak

Two customers sharing the same apps never see each other's events. Not a filter. A gate.

Same person, different names. Resolved.

Different apps call the same customer by different names. npayload resolves identities at the infrastructure level so events arrive mapped to your own records. No shared databases. No exposed internal data. Each app sees only its own view of the customer.

Identity Resolution
CRM App
Customer profile
Your customer
Support App
Ticket owner
Your customer
Loyalty App
Reward member
Your customer
No internal data shared between apps

Uninstall triggers automatic cleanup

Cleanup is always manual and always late. With Platform Connect, uninstall triggers an automatic cascade.

Uninstall

The platform sends an uninstall signal.

Revoke

npayload revokes all active consents for that customer account.

Stop

New events stop immediately.

Grace

In-flight deliveries complete with a grace period.

Before and after Platform Connect

Without Platform Connect

  • Apps are isolated on the app store
  • No shared event layer exists
  • Point-to-point integrations for each app
  • No consent standard
  • Manual cleanup when apps are uninstalled
  • No usage attribution per customer

With Platform Connect

  • All apps share one event layer
  • One SDK integration, any app store
  • Account owner controls consent
  • Isolation enforced by infrastructure
  • Automatic cleanup on uninstall
  • Real-time attribution per app, per customer

Frequently asked questions

Does the platform need to integrate with npayload?+
No. npayload does not integrate with any platform's APIs. The platform registry is purely informational. Your app initiates consent. The account owner authorizes on npayload.
How does the account owner authorize?+
Your app initiates a consent challenge. The account owner clicks Authorize on npayload's consent page. The consent is cryptographically signed and cached for real time enforcement.
Can two customers on the same platform see each other's events?+
No. Isolation is enforced at the infrastructure level. Every event is gated by the customer account. Not a filter. A gate.
What happens when an app is uninstalled?+
npayload revokes all active consents for that customer account. New events stop immediately. In flight deliveries complete with a grace period.
How does identity resolution work?+
Each app has its own way of identifying customers. npayload maps these references at the infrastructure level so events arrive resolved to your own records. No data is shared between apps.
How is usage billed?+
Per event, per customer, in real time. You choose the model: bill the app, the customer, or split it.