Explore the platform
See how OpenPayload supports secure communication, connected products, event delivery, and new data-driven experiences.
Start building
Resolve an identity, create one locally, and send your first message through the public APIs.
Why OpenPayload
Modern products need data to move across organizational and technical boundaries. OpenPayload provides reusable network building blocks so your team can focus on the experience and business logic that make your product unique.Built for private data exchange
Applications encrypt payloads before sending them. Relays and Caches can help deliver data without needing to read its contents.
One identity across experiences
Portable decentralized identifiers connect public keys, devices, service endpoints, and delivery preferences.
Resilient by design
Route live traffic through Relays and use policy-governed temporary storage when an endpoint is unavailable.
Open and application-neutral
Build compatible products on a public protocol instead of designing every connection and delivery layer from scratch.
What you can build
An OpenPayload message is a neutral data envelope, not a format limited to chat. Your application defines what the encrypted payload means.Secure communications
Create private messaging, collaboration, notification, or coordination experiences for people and teams.
Connected devices
Move telemetry, commands, alerts, and status events between devices, control systems, and operators.
Application workflows
Deliver asynchronous events, task handoffs, private packages, and system-to-system updates across product boundaries.
Agent and data networks
Give software agents and data-producing services a discoverable, secure path for exchanging application-defined payloads.
How the platform works
OpenPayload separates identity, live delivery, and temporary storage into focused services. Your application uses only the capabilities it needs.
The typical flow is simple:
- Resolve the recipient through a Directory.
- Encrypt your application data and place it in a DDN envelope.
- Send the envelope through a Relay.
- Use a Cache for temporary delivery fallback when needed.
Choose your next step
Build your first OpenPayload app
Follow the developer path from identity discovery to your first protocol exchange.
Understand OpenPayload identities
Learn how decentralized identifiers connect keys, devices, services, and policies.
Explore the public APIs
Review the Directory, Relay, and Cache contracts available to compatible clients.
Design your data envelope
Package application-defined encrypted data for delivery across the network.