> ## Documentation Index
> Fetch the complete documentation index at: https://docs.openpayload.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Welcome to OpenPayload

> A secure, open foundation for moving data between people, applications, devices, and intelligent agents

OpenPayload is an open protocol and community-operated platform for data in motion. It gives builders a shared way to discover trusted endpoints, exchange encrypted payloads, and keep data moving when a recipient is temporarily offline.

Unlike a closed messaging product, OpenPayload is application-neutral. Teams can use the same foundation to connect people, software, devices, and automated agents without locking every experience into one vendor or one data format.

> [card] [Explore the platform](#what-you-can-build)
>
> See how OpenPayload supports secure communication, connected products, event delivery, and new data-driven experiences.

> [card] [Start building](https://docs.openpayload.io/quickstart.md)
>
> 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.

> [card] Built for private data exchange
>
> Applications encrypt payloads before sending them. Relays and Caches can help deliver data without needing to read its contents.

> [card] One identity across experiences
>
> Portable decentralized identifiers connect public keys, devices, service endpoints, and delivery preferences.

> [card] Resilient by design
>
> Route live traffic through Relays and use policy-governed temporary storage when an endpoint is unavailable.

> [card] 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.

> [card] Secure communications
>
> Create private messaging, collaboration, notification, or coordination experiences for people and teams.

> [card] Connected devices
>
> Move telemetry, commands, alerts, and status events between devices, control systems, and operators.

> [card] Application workflows
>
> Deliver asynchronous events, task handoffs, private packages, and system-to-system updates across product boundaries.

> [card] 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.

| Platform service | What it does | Value to your application |
| - | - | - |
| **Directory** | Resolves identities, public keys, service endpoints, devices, and delivery policies | Discover where and how to exchange data with a recipient |
| **Relay** | Routes encrypted envelopes toward connected recipients | Add real-time delivery without exposing plaintext to the forwarding service |
| **Cache** | Temporarily stores encrypted envelopes under recipient-defined policies | Keep experiences reliable when recipients disconnect or change networks |

The typical flow is simple:

1. Resolve the recipient through a **Directory**.
2. Encrypt your application data and place it in a DDN envelope.
3. Send the envelope through a **Relay**.
4. Use a **Cache** for temporary delivery fallback when needed.

## Choose your next step

> [card] [Build your first OpenPayload app](https://docs.openpayload.io/quickstart.md)
>
> Follow the developer path from identity discovery to your first protocol exchange.

> [card] [Understand OpenPayload identities](https://docs.openpayload.io/concepts/what-is-a-did.md)
>
> Learn how decentralized identifiers connect keys, devices, services, and policies.

> [card] [Explore the public APIs](https://docs.openpayload.io/openpayload-directory-api)
>
> Review the Directory, Relay, and Cache contracts available to compatible clients.

> [card] [Design your data envelope](https://docs.openpayload.io/guides/ddn-envelope.md)
>
> Package application-defined encrypted data for delivery across the network.

> [!WARNING]
>
> Never send a private key or seed phrase to an OpenPayload node. Signing, encryption, and decryption happen in your client.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.